July 21, 20232 yr After upgrading Unraid, I noticed that my SSDs are all pretty much unhealthy except for the parity drive. I have no idea what the root cause is besides the upgrade. Attached are my diagnostics. xaviertower-diagnostics-20230720-2113.zip
July 21, 20232 yr Community Expert That error usually means something changed the partition/MBR and it's no longer valid, if parity is valid you can see if the emulated device mounts, since Unraid will recreate the partition, to test unassign of the affected data devices and post new diags after array start.
July 21, 20232 yr Author Ok will do that shortly, but how does this happen? Knock on wood, but I haven't had any issues with Synology or when I was running TrueNAS.
July 21, 20232 yr Author When I try to take the array off-line, which I believe is the way I'd unassign them from the array, it just hangs at "Stopping" and doesn't do anything unless I reboot the device. Spinning down all the disks also does nothing. Is there a better way to remove the devices from the array? Under "Historical Devices" there's a "X" to remove a device's configuration, but I'm not sure what that would do exactly. I didn't use Unraid as a NAS server, more like an App Server and have the docker backups on my Synology. So I'm debating whether or not I should just format the disks or not, but what's still disturbing is that Disk 4 has a red "X" next to it saying that the device is disabled, and the contents are emulated. So, somehow 3 of my 4 disks got screwed up.
July 21, 20232 yr Community Expert If the array isn't stopping you have other issues, you can disable array auto-start, reboot and then unassign the disk before array start.
July 21, 20232 yr Author Another thing that's interesting is that I'm 99% sure that my file system was btrfs, as that's what my Cache device is, and for the array disks it shows "XFS" and in the default settings for disks it also shows "btrfs"
July 21, 20232 yr Author 10 minutes ago, JorgeB said: If the array isn't stopping you have other issues, you can disable array auto-start, reboot and then unassign the disk before array start. I'll give that a shot, but I'm also starting to think that this got FUBAR'd somehow. It happened after upgrading to the latest version of Unraid, so unless it's just pure coincidence, the upgrade did something that wreaked havoc on my server.
July 21, 20232 yr Author So, I tried removing the devices from the array but it said invalid configuration. The parity drive may very well be messed up as there's no file system specified for it.
July 21, 20232 yr Community Expert 1 hour ago, ajtatum said: I tried removing the devices from the array but it said invalid configuration. I posted to remove one device.
July 21, 20232 yr Author 1 hour ago, JorgeB said: I posted to remove one device. Yea, I tried that too... Left parity drive on and attempted to boot up with disk 1 & 2, 1 & 3, 2 & 3 but disk 3 continued to not mount correctly and disk 1 & 2 showed "Unsupported Partition Layout".
July 21, 20232 yr Community Expert 4 minutes ago, ajtatum said: Left parity drive on and attempted to boot up with disk 1 & 2, 1 & 3, 2 & 3 but disk 3 continued to not mount correctly and disk 1 & 2 showed "Unsupported Partition Layout". Disk3 was mounting according to diags, were were supposed to unassign disk1 or disk2, start array and post new diags.
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.