February 17, 20242 yr All working fine on v6.12.6 and pulled the trigger on updating to v6.12.8. OS has booted up fine but array was not started with the below error: Not changed any hardware and clearly as per the screenshot, that is the correct disk for that slot as the expected vs actual S/N's match. Downgraded and no joy. I've therefore upgraded back to v6.12.8 and again, no joy. Diagnostics attached. Any suggestions on how I can resolve this? unraid-server-diagnostics-20240217-2136.zip
February 18, 20242 yr Was disk6 recently added/formatted and this was the first time the server was reboot since? If yes, type: sgdisk -o -a 8 -n 1:1M:0 /dev/sdX Replace X with the correct disk identifier, after that's done reboot and the disk should no longer show as wrong.
February 18, 20242 yr Author Nope, disk had been in the array for array for month, about 40% and had valid party. Browisng about, it seems people have had success by creating a New Config, then starting to array so the problem drive rebuilds from Partiy. The data is replaceable so think I will attempt that and report back on progress….
February 18, 20242 yr And you are sure the server was rebooted since? New config won't help if the problem is what I think, but it won't hurt, just make sure you don't format the disk, and you can still try the other option.
February 18, 20242 yr Author God, I can’t actually definitively say… I added the disk around 5 months ago and didn’t check the server uptime prior to updating last night! Before anything else then I’ll attempt to run that command you suggested, reboot and advise results when I’m back home later today. Thanks for the suggestion!
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.