Hyper-V and 386 failed to detect /dev/sda

Forum Forums Official Releases antiX-17 “Heather Heyer” Hyper-V and 386 failed to detect /dev/sda

Tagged: 

This topic contains 6 replies, has 3 voices, and was last updated by sevilla.larry May 20-6:02 pm.

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #10279
    Member

    sevilla.larry

    installing by cli-installer using antiX-17.1_x64-net.iso, no problem.

    but with antiX-17.1_386-{net/core/base/full}.iso, the installer can NOT detect /dev/sda.

    #10280
    Forum Admin
    anticapitalista
    anticapitalista

    Did you update the cli-installer before running it?

    Philosophers have interpreted the world in many ways; the point is to change it.

    #10288
    Member

    sevilla.larry

    No. Just execute cli-installer.

    What needs to be updated?
    Is it updatable? Can it be modified? (it’s in .iso).

    #10292
    Forum Admin
    anticapitalista
    anticapitalista

    The script in is /usr/local/bin.

    No idea about Hyper-V though, sorry.
    If 64 bit sees it, why not use a 64 bit iso?

    Philosophers have interpreted the world in many ways; the point is to change it.

    #10321
    Member

    sevilla.larry

    since you offered 386 / 32 bit, I tried it.
    a DHCP server / router is an example for light usage.

    The problem is actually the failed detection of the virtual hard disk (/dev/sda) using the 32 bit iso.
    The 64 bit iso detected the virtual hard disk (/dev/sda).

    btw, I’m using Windows Server 2016 w/ Hyper-V.

    fyi…

    #10341
    Member

    wean_irdeh

    Post the output of blkid command

    #10393
    Member

    sevilla.larry

    blkid

    /dev/loop0: TYPE=”squashfs”
    /dev/sr0: UUID=”2018-03-17-17-58-56-00″ LABEL=”antiXlive” TYPE=”iso9660″ PTUUID=”45c153b2″ PTTYPE=”dos”

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.