All drive names change with any OS update

[Brandonien]

My setup is 2 Parity drives and 5 array drives, when I perform ANY update to the OS it changes all of my drive names (adds a bunch of characters to the original names). Because the first part is the same I can place them in their appropriate slots through the dropdown, but they all show as wrong. I can rollback the OS version and its all fine, this has been the case for multiple versions I've attempted updating to.

Please help? Pic attached for context.

[JorgeB]

This can happen with some raid controllers, or with an LSI HBA using a very old firmware, please post the diagnostics. 

[Wiseone001]

On 8/6/2022 at 3:17 AM, JorgeB said:

This can happen with some raid controllers, or with an LSI HBA using a very old firmware, please post the diagnostics. 

resurecting this but im experianceing the same issue after moving to 6.12 rc2

 

Suggestions? how to get them back to original names and what happened to my other drives? they show up as pool to be mounted ...

my cache drives show like this:

 

hpunraid-diagnostics-20230324-0705.zip

[JorgeB]

6 minutes ago, Wiseone001 said:

Suggestions?

Do a new config and re-assign all disk to the correct slots, you can check "parity is already valid", you should also update the LSI firmware.

[Wiseone001]

Question, I did do a new config and my data and parity drives coming back online now.. but the pool for my cache drives dont show up , but they are all in the unassigned drives. they all show a mount point but do not show as a valid drive to use in the pool that was created. 

Screen shots to follow so you can see what im trying to get across ..   

 

But i can not assign the drives in the existing pool should i just format the cache? I dont think much was stored and then reassign them?

 

[JorgeB]

6 minutes ago, Wiseone001 said:

But i can not assign the drives in the existing pool should i just format the cache? I dont think much was stored and then reassign them?

Those are connected to a RAID controller, that is not recommended, was cache that single 600GB logic volume you can assign?

[Wiseone001]

1 minute ago, JorgeB said:

Those are connected to a RAID controller, that is not recommended, was cache that single 600GB logic volume you can assign?

No that was a single disk i left unassigned as possible back up for a failed drive..

So you think the controller created a raid config of all those drives and is combining outside of unraid as individual disks?

Is there any harm in resetting the cache pool and rebuilding the drives? (IE unmounting/ removing from cache pool and then formatting and reinstalling as new drive to cache pool?

 

[JorgeB]

Not familiar with that controller, but taking a second look I see the problem:

 

Mar 24 03:57:54 HPUnraid emhttpd: device /dev/sdj problem getting id
Mar 24 03:57:54 HPUnraid emhttpd: device /dev/sdh problem getting id
Mar 24 03:57:54 HPUnraid emhttpd: device /dev/sdg problem getting id
Mar 24 03:57:54 HPUnraid emhttpd: device /dev/sde problem getting id
Mar 24 03:57:54 HPUnraid emhttpd: device /dev/sdf problem getting id
Mar 24 03:57:54 HPUnraid emhttpd: device /dev/sdi problem getting id

 

This happens when Unraid sees multiple disks with the same identifier, in this case "600GB_DISK_B", see if you can change that, until you do they won't work with Unraid.