Failure to find HDD during installation

Comments

6 comments

  • Forrest Smith

    Donal - 

     

    Let's check a couple things:

     

    1) What kind of USB are you using? Do you have any others of different brand you can switch to? Some USBs cause significant issues installing.

    2) When you run 'sudo fdisk -l' are you running it from a TTY (using 'ctrl+alt+f2') or are you running it from a shell (by logging in and then pressing 'ctrl+alt+t' and then typing 'shell')? If you haven't yet, try to second one instead - that should let you scroll up and down and see more output from fdisk so we can be sure your devices are named what we expect.

     

    If AtB's builds work for you you shouldn't hesitate to use his - they're great. But if you want to use Neverware we can hopefully help.

  • Donal Óg

    Hi,

    First of all, thank you for helping, and regarding AtB, I may just, but I always like to compare before deciding on something, but your encouragement is reassuring! :)

    1. It's a Sandisk Cruzer U - 16GB. I have no other sticks available at the moment unfortunately.

     

    2. I was running TTY.

    Here an output from running your second method:

    Disk /dev/loop0: 292.8 MiB, 306991104 bytes, 599592 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk /dev/sda: 7.2 GiB, 7682605056 bytes, 15005088 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk /dev/sdb: 14.6 GiB, 15631122432 bytes, 30529536 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: 6668E840-330A-964E-90EA-C45906667946
    
    Device       Start      End Sectors  Size Type
    /dev/sdb1       64       64       1  512B ChromeOS reserved
    /dev/sdb2       65       65       1  512B ChromeOS reserved
    /dev/sdb3       66       66       1  512B ChromeOS reserved
    /dev/sdb4       67       67       1  512B ChromeOS reserved
    /dev/sdb5       68       68       1  512B ChromeOS reserved
    /dev/sdb6       69       69       1  512B ChromeOS reserved
    /dev/sdb7       70       70       1  512B ChromeOS reserved
    /dev/sdb8       71       71       1  512B ChromeOS reserved
    /dev/sdb9       72       72       1  512B ChromeOS reserved
    /dev/sdb10      73       73       1  512B ChromeOS reserved
    /dev/sdb11      74       74       1  512B ChromeOS reserved
    /dev/sdb12      75       75       1  512B ChromeOS reserved
    /dev/sdb13      76       76       1  512B ChromeOS reserved
    /dev/sdb14      77       77       1  512B ChromeOS reserved
    /dev/sdb15      78       78       1  512B ChromeOS reserved
    /dev/sdb16 8593474 10690625 2097152    1G Microsoft basic data
    /dev/sdb17   20546    53313   32768   16M ChromeOS kernel
    /dev/sdb18 2351170  8593473 6242304    3G ChromeOS root fs
    /dev/sdb19   53314    86081   32768   16M ChromeOS kernel
    /dev/sdb20 2347074  2351169    4096    2M ChromeOS root fs
    /dev/sdb21   16514    16514       1  512B ChromeOS kernel
    /dev/sdb22   16515    16515       1  512B ChromeOS root fs
    /dev/sdb23   86082  2183233 2097152    1G Microsoft basic data
    /dev/sdb24   16516    16516       1  512B ChromeOS reserved
    /dev/sdb25   16517    16517       1  512B ChromeOS reserved
    /dev/sdb26     130    16513   16384    8M unknown
    /dev/sdb27 2314306  2347073   32768   16M EFI System
    
    Partition table entries are not in disk order.
    Disk /dev/mapper/encstateful: 292.8 MiB, 306991104 bytes, 599592 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
  • Forrest Smith

    Donal - 

     

    Looks like /dev/sda isn't even recognized - this machine may have a storage type that we don't have drivers for. That's a pretty complex thing for us to add, so though I would love to have you on CloudReady, I must admit that Arnold's builds are better suited here.

     

    Good luck!

  • Donal Óg

    Ok. Thanks anyway Forrest!

  • Forrest Smith

    Donal -

     

    I worked with some engineers internally and we now think the issue is that 8 GB is too small.

     

    Our minimum for installation (as compared to installer USB size) is 16 GB.

    So if you can upgrade that machine you should be good to go! 

  • Donal Óg

    Hi Forrest, if this were an option I would totally leap on it. Unfortunately, we're taking about 20+ ten year netbooks that I'm voluntarily configuring for the school I teach in. But thank you for still looking into this for me, I truly appreciate the update. I have a laptop at home missing a power cable, but once I find it I hope to install Neverware and bring it back to life!

Please sign in to leave a comment.