I have Unraid running as a VM under Proxmox and its been running great until I tried to upgrade to 7.0 rc2 and 7.0 Final.

 

 

After upgrading to 7.0 the system fails to boot with the following error.

Notice the dev mapping of the USB stick - sdi

 

 

 

If I remove a drive from the system it will boot under 7.0, the drive will be recognized as sdh. But I am of course down a disk. 

I can then boot into Unraid and downgrade to 6.

 

After I roll back to 6.12.14 with all my drives notice that the USB drive is detected as sda.

 

 

So booting with 9 drive fails, but booting with 8 works.

 

My theory is that the new kernel detects or assigns the SCSI drives in a different order placing the USB stick at the end of the /dev mapping instead of the beginning and the boot only checks the first 8 devices.

tower-diagnostics-20250111_1419.zip

UDEV rule?

Did you find a way to fix it? 

2 hours ago, 10bn said:

Did you find a way to fix it? 

Only a way to roll back. By removing some drives so I can boot again, downgrade, and then add drives back.

 

I was gonna give it a couple days to see if anyone else has resolved it, if not I'll try and chase it down. I think it can be rectified by using some udev rules. If I figure it out I'll post here.

10 hours ago, McSexy said:

Only a way to roll back. By removing some drives so I can boot again, downgrade, and then add drives back.

 

I was gonna give it a couple days to see if anyone else has resolved it, if not I'll try and chase it down. I think it can be rectified by using some udev rules. If I figure it out I'll post here.

hmm, I just tried and removed all pcie device so now it's a plain vm with just the usb attached and I run into the same issue. 

Starting off the usb barematel works without problem.

I also tried setting um udev rules as mentioned here: https://github.com/unraid/webgui/commit/bc761b06791f9ed38d47a269db4c9fac0a9c1786

 

mkdir -p /boot/config/udev/rules.d
touch /boot/config/udev/rules.d/99-unraid.rules
echo 'SUBSYSTEM=="block", ENV{ID_FS_UUID}=="XXXX-XXXX", NAME="sda1"' >> /boot/config/udev/rules.d/99-unraid.rules

Any suggestions are welcome.

I don't know why it was on, must have changed it when I checked the settings, but turning of vIOMMU fixed it fore me. 

 

Ya, that didn't work for me, but I am running a q35 machine insted of a 440lx.

 

Prior I did try changing the machine type to some older versions, but had no luck.

 

Glad you got it working.

Same Problem here :-/
Also have a i440fx but it didnt work for me.

Jonas can you confirm its the same problem;

 

What dev# is your USB being detecting as?

13 hours ago, McSexy said:

Jonas can you confirm its the same problem;

 

What dev# is your USB being detecting as?

I'm not sure which dev# it was, but I would do it again later. However, I was also able to remove 4 of my 12 disks and suddenly the machine is booting again.
i remember that the usb stick was pushed further and further back the more disks i added. The 6.12.13 i am coming from does not do this.

Generally same issue. Generic v7 image doesn't boot on my Dell PowerEdge T430. I've had a support issue #6232 open since the day of the release. V6 works, upgrade does not, V7 generic does not, v7 with config copy does not.  I also completely remade the USB and that didn't help.

 

NOTE: This is bare metal, not virtualized. 

 

Edited January 18, 20251 yr by joey911

23 hours ago, joey911 said:

Generally same issue. Generic v7 image doesn't boot on my Dell PowerEdge T430. I've had a support issue #6232 open since the day of the release. V6 works, upgrade does not, V7 generic does not, v7 with config copy does not.  I also completely remade the USB and that didn't help.

 

NOTE: This is bare metal, not virtualized. 

 

looks like this is a SCSI problem

Thanks for confirming.

On 1/19/2025 at 1:02 PM, Jonas Wenger said:

looks like this is a SCSI problem

Support had me test without my USB expansion drives and V7 boots so it appears it is something related to not finding the flash USB during the mount process. 

I've confirmed with LT, and the issue is likely because there's an 8 device USB limit during boot, so the flash drive cannot be device #9 (sdi), now curious why the virtual disks are now being detected before the flash drive now, maybe related to the UASP driver, which is new to v7.0.0, if anyone can boot v7.0.0 with just 7 virtual disks, then please post the output from

lusb -t

and

lsusb

 

to see if they are using the UASP driver, which would be strange, possibly something else changed in the kernel.

 

In any case, LT is going to look at changing the limit to 26 devices during boot for v7.0.1.

4 hours ago, JorgeB said:

I've confirmed with LT, and the issue is likely because there's an 8 device USB limit during boot, so the flash drive cannot be device #9 (sdi), now curious why the virtual disks are now being detected before the flash drive now, maybe related to the UASP driver, which is new to v7.0.0, if anyone can boot v7.0.0 with just 7 virtual disks, then please post the output from

lusb -t

and

lsusb

 

to see if they are using the UASP driver, which would be strange, possibly something else changed in the kernel.

 

In any case, LT is going to look at changing the limit to 26 devices during boot for v7.0.1.

Again thanks for the update.

Hitting this same issue unfortunately.  I'll be rolling back for the time being as well

 

On 1/24/2025 at 1:17 PM, JorgeB said:

In any case, LT is going to look at changing the limit to 26 devices during boot for v7.0.1.

 

@JorgeB Any idea when 7.0.1 will be on the table?  or a beta for 7.0.1?

Edited January 30, 20251 yr by VACInc

On 1/24/2025 at 6:17 PM, JorgeB said:

In any case, LT is going to look at changing the limit to 26 devices during boot for v7.0.1.

Update on this, turns out that LT can only easily change the devices detected during early boot to 16 max, to change it to more than that will require significant changes, so with v7.0.1 the flash drive detected as sdp or lower should no longer be a problem, if it's detected as sdq or above, it still will.

 

This issue appears to come from a kernel change, where before, the flash drive was always sda and the virtual disks were detected much later in the boot process, now, they are detected before the flash drive.

 

Another option for using more than 16 disks, would be to pass-through a controller, that should also resolve the issue, and be a preferred option in general for virtualizing Unraid, instead of using /dev/disk/by-id

i have the same issue, removing some drives didn´t help. i´m also with proxmox. Now i´m stuck. I´m look for the way to downgrade

I just remove another 2 drives, total of 4 and now is booting, let see what happend

 

I can confirm i have the same issue after updating.
Removed all my disks to downgrade. look forward to 7.0.1...

On 2/16/2025 at 7:46 PM, dodert said:

I just remove another 2 drives, total of 4 and now is booting, let see what happend

 

all good after remove some disks and downgrade.

7.0.1 is now out, please retest.

 

P.S. as mentioned above, the limit went from 8 to 16 for early devices, meaning if you have more than 15 virtual disks with Proxmox for example, it will still be a problem.

I ran into this problem this morning on my 7.0.0 unRAID server. I had rebooted and it hung with this error message:
 

waiting up to 30 sec for device with label unraid to come online ... scsi
umount: /: not mounted.
not found - press enter key to reboot..._

Being as how I had this Mediasonic 8-bay external USB/eSATA drive case w/8 sata drives in it*** connected to the server:

https://mediasonicstore.com/products/mediasonic-8-bay-hard-drive-enclosure-usb-3-0-esata-h82-su3s2

I unplugged its USB cable and rebooted. The server then came up. 👍🙂

 

I then upgraded from 7.0.0 to 7.0.1 and rebooted to verify the server upgraded correctly (it had)

I then reattached the external USB drive case and rebooted once more. The server came up normally, so

Bottom line: Upgrading to 7.0.1 fixes the issue for me

***And, before any more people start yelling about usb drives on unraid being "abnormal!" and "unsupported!" and "not recommended!", for the record- I don't plan to use this box for an array or storage!  I use it as an easy way to add/remove a bunch of old small drives to format/pre-clear & get SMART stats before the drives get recycled or repurposed. 👍🙂

@sognix please continue here, since it's unrelated to this issue: