[6.11.0] NVMEs unavailable after upgrade 6.9.2 => 6.11.0

Also I cannot roll back to 6.10 per tools/os updates. Only showing 6.11 and 6.11.1. My server is dead in the water. Any way to get back to 6.9?

8 minutes ago, CablDeViL said:

Also I cannot roll back to 6.10 per tools/os updates. Only showing 6.11 and 6.11.1. My server is dead in the water. Any way to get back to 6.9?

https://unraid.net/download

https://wiki.unraid.net/Articles/Getting_Started#Manual_Install_Method

1 hour ago, ChatNoir said:

https://unraid.net/download

https://wiki.unraid.net/Articles/Getting_Started#Manual_Install_Method

Thank you. Downloaded 6.10 zip. pulled my Unraid USB drive and copied over the bz files. Plugged it back in and booted.  Everything is back to normal.  Will monitor this thread before next upgrade attempt.

17 hours ago, JorgeB said:

Some quirks were added for v6.11.1, but LT can only add the ones that are reported, I added yours to the list, it should be added for the next release.

Thanks a bunch!

15 hours ago, CablDeViL said:

I have the same issue with my Samsung 970 evo 1tb cache drive.

It's not the same issue:

Oct  8 10:50:05 Unraid kernel: nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0
Oct  8 10:50:05 Unraid kernel: nvme nvme0: Removing after probe failure status: -19

 

The device failed to initialize.

 

15 hours ago, CablDeViL said:

But it was fine at 6.11.0

 

15 hours ago, CablDeViL said:

Rolled back the 6.11 and still missing. 

This also suggests it's not a software problem if it was it would always work or always not work with the same release, please try upgrading to v6.11.1 again to see if it was a one time thing.

@JorgeB. Thank you I know your a busy person.

 

I tried to upgrade from 6.10 to 7.11. and it all work like it did last time.  I will next try to upgrade to 6.11.1. Here are my logs before and after.  I will report back after the next update.

CD

 

unraid-diagnostics-20221010-1524.zip unraid-diagnostics-20221010-1528.zip

@JorgeB,

 

Thanks again for the help.  Upgraded from 6.10 to .11 then to .11.1 and the nvme is fine.  I am not sure why or how come but thank you. Maybe time to upgrade the 1151  z170 platform.

 

Log attached if it helps.

 

CD

unraid-diagnostics-20221010-1539.zip

11 hours ago, CablDeViL said:

Log attached if it helps.

Everything looks normal for now, hopefully it was a one time thing, but in any case it was not Unraid related.

@Traumfaenger please try again after removing or commenting out these lines from your go file:

 

# Copy and apply udev rules for white label drives
cp /boot/config/rules.d/60-persistent-storage.rules /etc/udev/rules.d/
chmod 644 /etc/udev/rules.d/60-persistent-storage.rules
udevadm control --reload-rules
udevadm trigger --attr-match=subsystem=block

# Copy and apply udev rules for white label drives
cp /boot/config/rules.d/60-whitelabel.rules /etc/udev/rules.d/
chmod 644 /etc/udev/rules.d/60-whitelabel.rules
udevadm control --reload-rules
udevadm trigger --attr-match=subsystem=block

 

17 hours ago, JorgeB said:

@Traumfaenger please try again after removing or commenting out these lines from your go file:

 

# Copy and apply udev rules for white label drives
cp /boot/config/rules.d/60-persistent-storage.rules /etc/udev/rules.d/
chmod 644 /etc/udev/rules.d/60-persistent-storage.rules
udevadm control --reload-rules
udevadm trigger --attr-match=subsystem=block

# Copy and apply udev rules for white label drives
cp /boot/config/rules.d/60-whitelabel.rules /etc/udev/rules.d/
chmod 644 /etc/udev/rules.d/60-whitelabel.rules
udevadm control --reload-rules
udevadm trigger --attr-match=subsystem=block

 

 

I can confirm that my NVMEs are recognized when I uncomment the scripts. But then my two whitelabled HDDs are not usable. That's why I had added this script in first place.

Copy 60-persistent-storage.rules from the newer release and modify that file again, that should work, problem is likely because you are using a modified file from an older release.

21 minutes ago, JorgeB said:

Copy 60-persistent-storage.rules from the newer release and modify that file again, that should work, problem is likely because you are using a modified file from an older release.

JorgeB, thank you man!

This works!!! 🙂

Changed Status to Solved

You can thank @NDDanhe had the same problem and remembered changing that file, I would never think of looking at the go file for that, also keep in mind that if something storage related stops working in the future after an Unraid update you might need to do the same.

On 10/8/2022 at 12:18 AM, thetadawg said:

Tried 6.11 and lost one of my ADATA SX8200 nvmes, I think that I have the same issue.  So I reverted back to 6.10.3 and both nvmes showed back up.  I then saw the there was an newer update (6.11.1), so I figured that I would give it a shot again.  Looks like it is still happening

Your device should now be detected with v6.11.2