wildfire305 Posted March 19, 2022 Share Posted March 19, 2022 I was testing some 2TB and 3TB non-array disks in the same enclosure as my array disks. Docker and VMs were already disabled prior to testing. One of the non-array test disks started vibrating wildly and kicking udma crc errors left and right. Then, some array disks started building crc errors and one of them became disabled. I stopped all of my processes (badblocks on 5 disks) and tried to powerdown gracefully with the powerdown command. The system hung and could not be ping-ed. I waited 15 minutes and manually powered off everything. I removed the offending drive and promptly put two .22 caliber bullet holes into it for a quick, easy, and satisfying wipe before putting it in the trash. Now the server is restarted, and I'm testing the non-array disks again. The array came up with one disabled/emulated disk. I started it leaving the configuration alone as it said it would do a read test of all the other disks. I figured that would be a good thing and it continued gracefully with no weird format prompts. Questions/Options: Is it possible to get this disabled disk back in the array, or do I have to rebuild it onto itself? Do I have to stop the array to run an XFS filesystem check on the disabled disk? It won't mount read only because I assume the emulated disk is using its uuid. If I were successful at getting it back into the array (possibly using new config), would I need to rebuild/recheck the parity? Ideally, I would like to get this disk mounted somehow, copy it's contents to another disk, and then put it in the array letting the parity rebuild it. Someone helped me before with an XFS command that generated a new UUID (I found my previous post), But I know if I do that, I probably can't bring it back into the array. All the data is backed up...to B2. The disks I'm testing are for my onsite backup pool which I had to destroy the data to retest them. I got some larger disks and freed up slots in the server (12 total) So I could move my backup disks from esata/usb3 enclosures and put them into the main server box. Diagnostics attached for posterity. If y'all have any better paths than what I've thought of, I'm open to suggestions. cvg02-diagnostics-20220319-1817.zip Quote Link to comment
trurl Posted March 19, 2022 Share Posted March 19, 2022 Emulated disk1 is mounted. Since the original disk was bad, standard procedure at this point is to replace with another disk and rebuild. Quote Link to comment
wildfire305 Posted March 19, 2022 Author Share Posted March 19, 2022 Do I...stop the array switch emulated disk to none, start array, stop array, put original disk back in that slot, start array and it will rebuild from parity Quote Link to comment
trurl Posted March 20, 2022 Share Posted March 20, 2022 1 hour ago, wildfire305 said: put original disk back I thought you 2 hours ago, wildfire305 said: put two .22 caliber bullet holes into it Quote Link to comment
trurl Posted March 20, 2022 Share Posted March 20, 2022 If you assign any disk to the emulated slot and start the array it will rebuild to that disk. Quote Link to comment
wildfire305 Posted March 20, 2022 Author Share Posted March 20, 2022 4 minutes ago, trurl said: I thought you Original array disk, no. Vibrating disk I was testing, yes Quote Link to comment
trurl Posted March 20, 2022 Share Posted March 20, 2022 https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself Quote Link to comment
Recommended Posts
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.