Array destroyed after upgrade

Looks like something about your disk controller(s) changed the way the drives were identified.

 

How are these drives connected?

 

They are connected to the motherboard. ASRock Z87 Extreme11/ac

You are likely to get better informed feedback if you post your system’s diagnostics zip file taken while running the 6.10.x release.  
 

If you are running VMs and passing through hardware have you checked whether the device ids have changed?    Your symptoms suggest that the disk controller is not available to Unraid.

Here is the diagnostics under 6.10.0-RC4

 

I haven't checked the device ID's for passthrough. I'll try it out tomorrow.

 

I have noticed the 6 main SATA ports work do not have any issue. The secondary SATA ports on the board are ones that break.

6-10-rc4-unraid1-diagnostics-20220522-2238.zip

We would need the diagnostics when the drives cannot be seen for them to be of any use in trying to diagnose the issue.

Problem is that you're using a very old firmware for the LSI HBA, those ancient firmware versions used the long name for SATA devices, this has been fixed a long time ago, and now it was also fixed in the driver for people still using an old firmware, you just need to do a new config and re-assign all the devices, then check "parity is already valid" before starting the array.

 

I would also recommend updating the LSI firmware to latest, note that if you update the firmware first you'll see the same issue with -rc4 you're seeing now with v6.10.1

This should be the diagnostics when the drives cannot be seen.

unraid1-diagnostics-20220522-1548.zip

3 minutes ago, JorgeB said:

Problem is that you're using a very old firmware for the LSI HBA, those ancient firmware versions used the long name for SATA devices, this has been fixed a long time ago, and now it was also fixed in the driver for people still using an old firmware, you just need to do a new config and re-assign all the devices, then check "parity is already valid" before starting the array.

 

I would also recommend updating the LSI firmware to latest, note that if you update the firmware first you'll see the same issue with -rc4 you're seeing now with v6.10.1

 

 

I'll give this a go tomorrow and report back.

I haven't been able to figure out how to upgrade the firmware yet, but I rebuilt the array with a new config in 6.10.1. I do still feel like it is a bug since it works fine in RC4 but breaks in 6.10.1

24 minutes ago, marcusfan said:

I do still feel like it is a bug

I would be surprised if it was Unraid causing this, likely something changed in the LSI driver or in one of packages that Unraid uses, in any case it's much better for you like that, as it was if you replaced the controller with a different model the same would happen, now it's using the standard names.

Changed Status to Closed

29 minutes ago, JorgeB said:

I would be surprised if it was Unraid causing this, likely something changed in the LSI driver or in one of packages that Unraid uses, in any case it's much better for you like that, as it was if you replaced the controller with a different model the same would happen, now it's using the standard names.

 

Fair enough. Closing the thread.