February 10, 20206 yr Hi, My server is in an odd state and I'm not sure how to resolve, I think it was caused by my 3ware raid controller crashing. Disk 4 Wrong ID. This drive is showing up correctly however I think Unraid is expecting it to be 1TB rather than 4TB, maybe because it was recently upgraded from a 1TB to a 4TB. The old 1TB drive is still installed but unused. Disk 13 Showing up correctly and ID matches but being emulated for some reason? Diagnostics attached. Thanks alphav2-diagnostics-20200210-1839.zip
February 10, 20206 yr Community Expert This isn't a very straight forward situation, you could re-enable disk4 as 4TB and rebuild disk13, but if disk13 is healthy it would be probably best to do a new config and re-sync parity, can you get a SMART report for disk13? It's not on the diags.
February 10, 20206 yr Author Disk 13 smart attached. Its relatively new so should be healthy. What are the steps to create a new config? Any risks of data loss? alphav2-smart-20200210-1916.zip Edited February 10, 20206 yr by Phoenix26
February 10, 20206 yr Community Expert 9 minutes ago, Phoenix26 said: What are the steps to create a new config? -Tools -> New Config -> Retain current configuration: All -> Apply -Then on the main page check all disks are correctly assigned, assign any missing disks if needed, we're going to assume parity is mostly valid, maybe even 100% valid, so check "parity is already valid" before starting the array. After array start if all disks mount correctly run a parity check, if not post new diags. 13 minutes ago, Phoenix26 said: Any risks of data loss? There's always some risk if any of the disks is really failing or have a corrupt file system, but the other options also have similar risks.
February 10, 20206 yr Author Have created a new config and the array started correctly, parity check is now running. Will report back once its complete. Thank you very much for your help.
Archived
This topic is now archived and is closed to further replies.