March 15Mar 15 I have been at version 7.0.1 because my licence had ended. I recently updated that and was looking to also update my machine. The first time 7.2.4 showed as the available update so I ran that. However, after the reboot one of my drives showed as wrong/missing and the array would not start. Thinking that maybe there was too much of a gap in versions, I reverted back to 7.0.1, the drive in question came back and the array was working fine. I have tried versions 7.1.2. & 7.1.3 and I get the same problem. Is there something I need to do before I can update?
March 15Mar 15 Author 29 minutes ago, trurl said:Attach Diagnostics ZIP to your NEXT post in this thread.This is from 7.0.1 where everything works. Is this what you are looking for? mcp-diagnostics-20260315-1136.zip
March 15Mar 15 Community Expert You don't have a parity disk?Marvell controllers are not recommended, but it doesn't look like it has any disks on it anyway,disk1 is using the same controller as 2-5 and it is not a RAID controller so I don't know why it would have problem identifying that disk. Is that the only one?
March 15Mar 15 Author No my parity disk died and I will be getting a new one soon. Disk one is the only drive that does this. None of the other drives go into this "wrong" status.
March 16Mar 16 Community Expert 16 hours ago, freggit said:This is from 7.0.1 where everything works. Is this what you are looking for?Also post diags after upgrading to see why the disk is being detected as wrong
March 16Mar 16 Author 5 hours ago, JorgeB said:Also post diags after upgrading to see why the disk is being detected as wrongmcp-diagnostics-20260316-0939(7.2.4).zipHere is the diagnostics after trying to upgrade.
March 16Mar 16 Community Expert In vars, they show as different [size] for some reason. Maybe partitioning?
March 16Mar 16 Author 14 minutes ago, trurl said:In vars, they show as different [size] for some reason. Maybe partitioning?I guess what does that mean? The drive was never used in another device and unraid created the partition when it was added to the array.
March 16Mar 16 Community Expert 5 minutes ago, freggit said:what does that mean?I don't know. Just putting it out there in case someone does.
March 16Mar 16 Community Expert Partition layout appears to be wrong, with the array stopped post the output fromfdisk -l /dev/sdfblkid /dev/sdf1This can be done from 7.0 or 7.2
March 16Mar 16 Author 3 minutes ago, JorgeB said:Partition layout appears to be wrong, with the array stopped post the output fromfdisk -l /dev/sdfblkid /dev/sdf1This can be done from 7.0 or 7.2attached
March 16Mar 16 Community Expert Solution Unraid 7.0 is not using the actual partition layout because it's not the standard Unraid layout, it just ignores it, but from 7.1 Unraid will use the actual partition, hence the issue. You should be able to resolve this by deleting that partition and creating a new one with the correct layout. This should not cause any issues with the current data, and to avoid a new config, should be done in 7.0 with the array stopped.wipefs -a /dex/sdXThis will zap the partition, not the data. Replace X with the correct identifier; double check as this can change with a reboot.Then create a new partition with the correct layout:sgdisk -o -a 8 -n 1:32K:0 /dev/sdXAgain, replace X.Start the array, confirm the disk still mounts correctly, and you can now upgrade to 7.2.
March 16Mar 16 Author Used :wipefs -a /dev/sdX (changed dex to dev from your comment ) replacing X with correct identifiersgdisk -o -a 8 -n 1:32K:0 /dev/sdX replacing X with correct identifierI was able to complete the upgrade to the latest version 7.2.4. Thank you for your assistance!2 hours ago, JorgeB said:Unraid 7.0 is not using the actual partition layout because it's not the standard Unraid layout, it just ignores it, but from 7.1 Unraid will use the actual partition, hence the issue.You should be able to resolve this by deleting that partition and creating a new one with the correct layout. This should not cause any issues with the current data, and to avoid a new config, should be done in 7.0 with the array stopped.wipefs -a /dex/sdXThis will zap the partition, not the data. Replace X with the correct identifier; double check as this can change with a reboot.Then create a new partition with the correct layout:sgdisk -o -a 8 -n 1:32K:0 /dev/sdX
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.