• [6.10.0] Unraid boot device not found


    GrimD
    • Solved Minor

    After upgrading to 6.10.0 the server stopped booting with the message "Unraid boot device not found" after the 30 second time out. Tried formatting the USB, and doing a fresh (didn't copy my config folder across) manual install of 6.10 but the issue was the same. Have manually installed 6.9.2, copied my old config folder across and am backup and running with out issue. So seems there is a bug\issue in 6.10. 

     

    I'm using a 16GB SanDisk Corp. Cruzer Fit as the boot USB

    dbunraid01-diagnostics-20220518-2106.zip

    • Upvote 1



    User Feedback

    Recommended Comments



    @limetech I know but MBR is old and GPT is new ;)

     

    Everything else seems to be working as expected on 6.10 now I'm on it so thats good so far :)

    Link to comment

    @limetechthanks for addressing the issue and providing details and a workaround.

     

    I just wanted to point out that I did not to anything special when I set up the boot drive several years ago and never messed with any partitions. At the time, the imager app was not available so I'm pretty sure I just formatted it in Windows, with the UNRAID label, added the unraid files and ran the make bootable script.

     

    I'll check its partitions next time I take my server offline and get ready for another attempt at an upgrade.

    Link to comment

    OK what about this.

     

    root@nas:~# blkid
    /dev/sda1: LABEL="External USB" BLOCK_SIZE="512" UUID="01D28AE67523FE50" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="740c9ae0-8ae6-01d2-704d-063a7345e900"
    /dev/sdb1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="2732-64F5" BLOCK_SIZE="512" TYPE="vfat"
    /dev/loop1: TYPE="squashfs"
    /dev/sdf1: UUID="17b664ed-15cd-4bf2-b575-7fe0cde7d481" UUID_SUB="cf5b2483-201e-4c02-981e-f2aa0a086ea9" BLOCK_SIZE="4096" TYPE="btrfs"
    /dev/sdd1: UUID="0388e9a3-f50c-4509-92c2-e54bbd6f66d1" UUID_SUB="164520f4-46ba-4f65-ada2-8ca0a902a394" BLOCK_SIZE="4096" TYPE="btrfs"
    /dev/md2: UUID="3cc4eee7-88e3-4d68-bfdd-d475bcc4c84f" BLOCK_SIZE="512" TYPE="xfs"
    /dev/sdi1: UUID="0b50b5bb-a16d-4ec7-a34f-84f3b1c8965e" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="bac94e19-3760-449c-8417-ca4a955c7adc"
    /dev/sdg1: UUID="12e9017d-c270-4e56-a128-b8a56439a339" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="3c0e6c61-9c10-4809-8dd2-35f0ae79cfe2"
    /dev/loop0: TYPE="squashfs"
    /dev/sde1: UUID="17b664ed-15cd-4bf2-b575-7fe0cde7d481" UUID_SUB="04839745-fc3f-4820-b5ea-8aef210826a9" BLOCK_SIZE="4096" TYPE="btrfs"
    /dev/sdc1: UUID="0388e9a3-f50c-4509-92c2-e54bbd6f66d1" UUID_SUB="a9a92d89-34e4-410a-9b7c-6bb74fb3c80a" BLOCK_SIZE="4096" TYPE="btrfs"
    /dev/md3: UUID="257d5a21-ebfe-4df9-bdba-e8236935fd28" BLOCK_SIZE="512" TYPE="xfs"
    /dev/sdj1: UUID="257d5a21-ebfe-4df9-bdba-e8236935fd28" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="ce956125-26cc-4a3b-928a-082254ac8aa8"
    /dev/md1: UUID="0b50b5bb-a16d-4ec7-a34f-84f3b1c8965e" BLOCK_SIZE="512" TYPE="xfs"
    /dev/sdh1: UUID="3cc4eee7-88e3-4d68-bfdd-d475bcc4c84f" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="845c5dee-579a-4721-8486-248b779d456c"
    /dev/loop2: UUID="9189f30b-12c6-4510-a976-0b71758dd971" UUID_SUB="877baabc-8c26-4193-bdb6-b98755e78d8b" BLOCK_SIZE="4096" TYPE="btrfs"
    /dev/loop3: UUID="407b681c-1695-406e-a8b8-6d046b8a3b38" UUID_SUB="2236014a-bd7a-403c-8ca3-bfcf69eb7d4d" BLOCK_SIZE="4096" TYPE="btrfs"

     

    sda1 is a 4tb NTFS USB hard drive mounted by unassigned devices

    sdb1 is the USB flash boot.

     

    Why is it choking on sda1 when it is clean anyway and still not booting sdb1

     

    20220428_201030.jpg

    Edited by agh1701
    • Upvote 1
    Link to comment
    21 minutes ago, dumurluk said:

    I'll check its partitions

    When checking in Windows best to do it with dispart, disk management isn't always the best when there are very small partitions, this is the same flash drive:

     

    imagem.thumb.png.a6da903779457296c92f8383de4f4283.png

    imagem.png.b251a78ddc6ce3fd36f221fe215ef421.png

    Link to comment

    @dumurluk I would assume yours is MBR, I belive most USB drives are still MBR by default when shipped. I tend to convert mine to GPT as its newer amd most things support it now. The issue seems to be that as soon as you convert a drive to GPT in windows it creats a hidden efi system partition at the beginning of the drive. ONce I put the drive back to MBR. I had just had to do a normal format in wimdows and it worked fine as there is no extra hidden system partition created with MBR. 

    Link to comment

    Mine is MBR.  Earlier in the thread something @limetech said about udev indicates something has changed in the startup routine.  I think somehow this is affecting me maybe to do with booting from sdb1?

    Link to comment
    3 hours ago, limetech said:

     

    Actually not true... pre-6.10 the 'udev' subsystem was started very early.  This let us look for which device was assigned to the flash by looking at:

    /dev/disk/by-label/UNRAID

    which is a symlink which points to a partition, such as 'sda1' or 'sda2'

     

    In 6.10 we have to find the flash device before starting 'udev', so we switch to using 'blkid' to find a device with label "UNRAID".  However the code only checks partition 1 label on each device because I've never seen a case where anything other than partition 1 was ever used.

     

    We will add code to check partitions 1, 2, 3, and 4 in the 6.10.1 release.  To get your flash to boot now, you will have to reformat and make sure partition 1 is the boot partition with the UNRAID label.

     

    I just ran "blkid" on my server currently running 6.9.2 and there is only one "sda" partition listed:

    /dev/sda: LABEL="UNRAID" UUID="DAA4-D416" BLOCK_SIZE="512" TYPE="vfat"

     

    Yet when I update to 6.10, unraid can't find the device

    • Confused 1
    Link to comment
    29 minutes ago, dumurluk said:

     

    I just ran "blkid" on my server currently running 6.9.2 and there is only one "sda" partition listed:

    /dev/sda: LABEL="UNRAID" UUID="DAA4-D416" BLOCK_SIZE="512" TYPE="vfat"

     

    Yet when I update to 6.10, unraid can't find the device

    That indicates there is actually no specific partition on the drive (as that would be sda1). 

    Link to comment

    I can't remember where I saw it, but at some point in the past I seem to remember that it wasn't always required to partition a flash drive, formatting the entire device without a partition defined is somewhat supported. How supported, depends on the implementation of the OS.

     

    Perhaps looking for a valid FAT system on the /dev/sd? device itself as well as parsing the partitions?

    Link to comment
    30 minutes ago, JonathanM said:

    I can't remember where I saw it, but at some point in the past I seem to remember that it wasn't always required to partition a flash drive, formatting the entire device without a partition defined is somewhat supported. How supported, depends on the implementation of the OS.

     

    Perhaps looking for a valid FAT system on the /dev/sd? device itself as well as parsing the partitions?

    I don't believe partitioning was ever a requirement when I set my servers up. The process was just format, label, unzip the files and run the make bootable script.

    • Upvote 1
    Link to comment
    2 minutes ago, dumurluk said:

    I don't believe partitioning was ever a requirement when I set my servers up. The process was just format, label, unzip the files and run the make bootable script.

    It was assumed the factory would put a single partition on the USB stick. This was valid for a large percentage of sticks, but some manufacturers tried to be cute and add partitions with various functions, like U3

    Link to comment

    Added my systems for comparison, I have not updated prod to 6.10.0

     

    Prod 6.9.2
    
    root@unraid:~# blkid /dev/sdb1
    /dev/sdb1: SEC_TYPE="msdos" LABEL="UNRAID" UUID="CE38-0C92" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="04cf5187-01"
    root@unraid:~# blkid /dev/sdb
    /dev/sdb: PTUUID="04cf5187" PTTYPE="dos"
    root@unraid:~# 
    
    Test servers both 6.10.0
    
    root@computenode:~# blkid /dev/sdc1
    /dev/sdc1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="272C-EBE2" BLOCK_SIZE="512" TYPE="vfat"
    root@computenode:~# blkid /dev/sdc
    /dev/sdc: PTTYPE="dos"
    root@computenode:~# 
    
    /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="272C-EBE2" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="93323e23-01"
    root@Tower:~# blkid /dev/sda
    /dev/sda: PTUUID="93323e23" PTTYPE="dos"
    root@Tower:~# 

     

    Edited by SimonF
    Link to comment
    6 minutes ago, limetech said:

    Changed Status to Retest

    Currently running 6.10 with MBR fine but will look to convert the USB back to GPT and test with 6.10.1 ASAP. 

    Link to comment

    I highly recommend the Samsung BAR USB sticks. Also I just changed out my old original sandisk for a Samsung BAR and had to mess around with secure boot settings and UEFI settings in my BIOS so it would find the bootable flash. When I used the USB creator tool with Windows I selected UEFI, so that was probably a change from my original boot device and just confused the BIOS of my mainboard. Had to go in there and select UEFI: Samsung as my boot device and it booted  normally. It wasn't even starting unraid previously before I did that. Just a BIOS error about UEFI settings. Thie flash is a Samsung BAR 64gig. Was only $10 on sale.

     

    https://www.samsung.com/us/computing/memory-storage/usb-flash-drives/usb-3-1-flash-drive-bar-plus-32gb-champagne-silver-muf-32be3-am/

     

    Also if you really want to check out your USB device and do not have a linux machine you can download LinuxMint, stick it on a USB stick and that will boot you into a full blown Linux. Then use a great utility called GPARTED. That will really examine your USB stick and can even change around or move/delete partitions without affecting others.

    Edited by opentoe
    • Like 1
    Link to comment
    19 hours ago, limetech said:

    6.10.1 released, please retest

     

    Updated the same server that was previously having issues, without any changes to the flash drive and 6.10.1 is starting up just fine. Thanks

     

    By the way, the issue with my flash drive was that it doesn't have a partition and is listed at "/dev/sda"

    Edited by dumurluk
    Link to comment



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.