March 30, 20206 yr Drive issue not related to 6.8.2 upgrade as I did xfs check on all drives in maintenance mode before bringing array up after upgrade. Got a read error on disk 2 on array start so I rebooted. Drive came up and normal, but of course it is now disabled. No smart errors so just something the repair did (but no lost+found either on that disk either). Only options I have in 6.8.2 to bring the array online is to do a 'read check' which is a no-correct parity operation. Question is why does it force this as the only option instead of allowing a disk rebuild on the disabled drive? This seems new as I don't recall seeing this behavior on 6.7.2 and older. I need to rebuild the disk not read the emulated disk contents, or am I missing something? Thanks Edited March 30, 20206 yr by unevent
March 30, 20206 yr Community Expert Just now, unevent said: Only options I have in 6.8.2 to bring the array online is to do a 'read check' which is a no-correct parity operation. That won't bring the disk online, to re-enable a disable disk is the same as before: https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive
March 30, 20206 yr Community Expert You need to follow the procedure that has always applied to do this Stop array Unassign disabled disk Start array so the missing disk is registered Stop array Reassign disabled disk Start array to begin rebuild
Archived
This topic is now archived and is closed to further replies.