whoopn Posted July 24 Share Posted July 24 Ok so here is what happened: 1. First disk down I dropped my phone and it just happened to smack the disk release for the caddy (couldn't do that again if i tried), that got me my first red X. 2. Second disk, I accidentally pulled a drive I thought was in unassigned devices (stupid mistake) 3. I had my drives IN another array and the disk got wiped (yeah that sucked) So, disks 1 and 2 with red x's, those are technically probably fine, what I cant figure out is how to make unraid think that. What can I do? Quote Link to comment
whoopn Posted July 26 Author Share Posted July 26 On 7/24/2024 at 1:48 AM, JorgeB said: Please post the diagnostics. tower-diagnostics-20240726-0943.zip Quote Link to comment
whoopn Posted July 26 Author Share Posted July 26 1 hour ago, JorgeB said: Diags after array start please. I was able to repair the wiped disk to the point of being able to grab files off. I’m going to do that first. Everything is in lost&found though so it’s requiring a lot of scripting to get everything. Quote Link to comment
whoopn Posted July 27 Author Share Posted July 27 12 hours ago, JorgeB said: Diags after array start please. Array started in maintenance mode, if i start it regular it will begin rebuilding one of the disks. Let me know if we have to bite that bullet. Thanks for your help btw. tower-diagnostics-20240726-2235.zip Quote Link to comment
JorgeB Posted July 27 Share Posted July 27 It must be in normal mode, you can unassing the disk to not start a rebuild, or just cancel Quote Link to comment
whoopn Posted July 27 Author Share Posted July 27 7 hours ago, JorgeB said: It must be in normal mode, you can unassing the disk to not start a rebuild, or just cancel Ok this time in regular mode. Thank you for reviewing it! tower-diagnostics-20240727-0909.zip Quote Link to comment
JorgeB Posted July 27 Share Posted July 27 O only see two unmountable disks, check filesystem for emulated disks 1 and 9, run it without -n Quote Link to comment
whoopn Posted July 27 Author Share Posted July 27 1 hour ago, JorgeB said: O only see two unmountable disks, check filesystem for emulated disks 1 and 9, run it without -n Disk 5 has been wiped (it’s not right, but like I saw you point out in another post it’s not filesystem integrity aware). what is -n? How do I do that? Quote Link to comment
JorgeB Posted July 27 Share Posted July 27 3 hours ago, whoopn said: Disk 5 has been wiped What do you mean wiped? It's still showing mostly full: Filesystem Size Used Avail Use% Mounted on /dev/md5p1 3.7T 3.1T 642G 83% /mnt/disk5 3 hours ago, whoopn said: what is -n? How do I do that? For the repair options, see the link above. Quote Link to comment
whoopn Posted July 27 Author Share Posted July 27 1 hour ago, JorgeB said: What do you mean wiped? It's still showing mostly full: Filesystem Size Used Avail Use% Mounted on /dev/md5p1 3.7T 3.1T 642G 83% /mnt/disk5 For the repair options, see the link above. Full yes, but an absolute mess, I performed xfs_repair on it and b/c it lost a lot of the inode data i just put everything in lost and found. Ok running xfs_repair first WITH -n to see what we're dealing with. Bad superblock, its looking for the secondary one now. I'll try the repair on Disk 1 first. Thanks for your help What should I do after we've run through the xfs_repair? Quote Link to comment
JorgeB Posted July 28 Share Posted July 28 After repairing both disks post new diags after array start Quote Link to comment
whoopn Posted July 28 Author Share Posted July 28 8 hours ago, JorgeB said: After repairing both disks post new diags after array start So, both 1 and 9 have zero superblocks. Both primary and secondary are gone. It did find a candidate but ultimately didn’t. Are these disks kind of cooked and I should just rebuild one at a time? Quote Link to comment
JorgeB Posted July 29 Share Posted July 29 That suggests parity is not valid, if you still have the old disks see if they mount with UD. Quote Link to comment
whoopn Posted August 4 Author Share Posted August 4 I think the array might be toast, but I did manage to get like 99% of the data over to my zfs array. I rebuilt disk 1, but its not mountable, here are the diagnostics. I'm free to do just about anything I need to to this array, so if there is a chance we can get a little dangerous and make it work again I'm game. The most important data (photos) are all safe and sound on two separate arrays plus backed up to the cloud. tower-diagnostics-20240804-1302.zip Quote Link to comment
JorgeB Posted August 4 Share Posted August 4 Check filesystem on disks 1 and 9, run it without -n Quote Link to comment
whoopn Posted August 6 Author Share Posted August 6 On 8/4/2024 at 4:05 PM, JorgeB said: Check filesystem on disks 1 and 9, run it without -n Both eventually responded with "Sorry, could not find valid secondary superblock Exiting now." At least it said it was sorry. Anything else we should try or should I just scoop these into my zfs array? Quote Link to comment
JorgeB Posted August 6 Share Posted August 6 Post the command you are using to run that. Quote Link to comment
whoopn Posted August 7 Author Share Posted August 7 (edited) 18 hours ago, JorgeB said: Post the command you are using to run that. xfs_repair /dev/sdX Edited August 7 by whoopn Quote Link to comment
whoopn Posted August 7 Author Share Posted August 7 30 minutes ago, whoopn said: xfs_repair /dev/sdX I'm a dummy, I'm doing it correctly now. Quote Link to comment
JorgeB Posted August 7 Share Posted August 7 Make sure you are using the md device, not sdX1, or parity will be invalided. Quote Link to comment
whoopn Posted August 7 Author Share Posted August 7 Parity is already messed up. I did the partition so it could actually get me access to the files. It was able to fully repair one but the other it put it all into lost and found. I’m about done getting the last of my files off. This array isn’t going to be saved. Thank you for your help! I really appreciate you taking your time to help me. 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.