Guanyin Posted April 5, 2023 Share Posted April 5, 2023 I’ve added a new drive to my unraid array by replacing a smaller one. However, another drive, not included in the transaction, became unmountable. It said it was dissbled. I’ve done short and long SMART tests and both gave no errors. Here’s the output of “xfs_repair -v /dev/md5” and my diagnostics. Quote Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! attempting to find secondary superblock... ...found candidate secondary superblock... unable to verify superblock, continuing... ....found candidate secondary superblock... unable to verify superblock, continuing... <bunch of dots> unable to verify superblock, continuing... <bunch of dots> Exiting now. g1-diagnostics-20230405-0810.zip Quote Link to comment
JorgeB Posted April 5, 2023 Share Posted April 5, 2023 Diags show filesystem issues with disk4, please reboot and post new diags after array start. Quote Link to comment
Guanyin Posted April 5, 2023 Author Share Posted April 5, 2023 Hi JorgeB! Here are the new diags. g1-diagnostics-20230405-2351.zip Quote Link to comment
JorgeB Posted April 6, 2023 Share Posted April 6, 2023 Yes, there are still issues with disk4, upgrade to v6.11.5 for the newer xfs_repair and check filesystem on disks 4 and 5. 1 Quote Link to comment
Guanyin Posted April 6, 2023 Author Share Posted April 6, 2023 (edited) Disk 4 repaired a bunch of errors. Disk 5 is giving the same result as I mentioned in my initial post. Edit: Disk 5 is still running, since it took a loooong time last time. g1-diagnostics-20230406-0943.zip Edited April 6, 2023 by Guanyin Quote Link to comment
JorgeB Posted April 6, 2023 Share Posted April 6, 2023 Disk4 should be fixed, you can cancel, once v6.12-rc3 is released, which should be very soon, try running it again using that one, since it will have an even newer xfs_repair, failing that you'll need to restore the data from a backup or use a file recovery util. Quote Link to comment
Guanyin Posted April 7, 2023 Author Share Posted April 7, 2023 Is it possible to replace the unmountable disk with a new one and solve the issue that way? Quote Link to comment
JorgeB Posted April 8, 2023 Share Posted April 8, 2023 Nope, rebuilding a disk won't generally fix filesystem issues. Quote Link to comment
Guanyin Posted April 8, 2023 Author Share Posted April 8, 2023 What kind of file recovery util could I use? Do I understand correctly that I’d be recovering files from the unmountable drive using a recovery util, put those files on another drive, and then format the unmountable drive to add it back to the array? Quote Link to comment
JorgeB Posted April 8, 2023 Share Posted April 8, 2023 26 minutes ago, Guanyin said: Do I understand correctly that I’d be recovering files from the unmountable drive using a recovery util, put those files on another drive, and then format the unmountable drive to add it back to the array? Correct, UFS explorer is one utility often used, but I would first wait for v6.12-rc3 that should be released very soon, possibly during this weekend. Quote Link to comment
Guanyin Posted April 9, 2023 Author Share Posted April 9, 2023 On 4/8/2023 at 9:54 AM, JorgeB said: Nope, rebuilding a disk won't generally fix filesystem issues. Could you elaborate on this? Isn't the filesystem issue with that specific disk? Or is a filesystem issue an array issue? Another question: which version of UFS explorer is required? Another question: What if I forfeit the data on that drive, format the drive and add it back to the array? Would that work? Obviously, I wouldn't know which data I would lose. Quote Link to comment
Guanyin Posted April 9, 2023 Author Share Posted April 9, 2023 Now I get this notification 🤔 Quote Link to comment
JorgeB Posted April 9, 2023 Share Posted April 9, 2023 7 hours ago, Guanyin said: Could you elaborate on this? Isn't the filesystem issue with that specific disk? Or is a filesystem issue an array issue? Rebuild is to replace a failed disk, when there are filesystem issues usually the parity will emulate the same issues, but there have been exceptions, when the parity is not 100% in sync. 7 hours ago, Guanyin said: which version of UFS explorer is required? I believe standard version. 7 hours ago, Guanyin said: Another question: What if I forfeit the data on that drive, format the drive and add it back to the array? Would that work? Obviously, I wouldn't know which data I would lose. Yes. 7 hours ago, Guanyin said: Now I get this notification 🤔 That suggests you are rebuilding the disk, I assume the emulated disk is still unmountable? Quote Link to comment
Guanyin Posted April 9, 2023 Author Share Posted April 9, 2023 Quote I assume the emulated disk is still unmountable? Yes. I’m going to wait for another xfs_repair (which is giving the same result as my initial post, so far). When that doesn’t work I’ll await the v6.12-rc3 update. If that doesn’t help I’ll try file recovery. If that doesn’t help I’ll try replacing the disk with a new one. Is that a sound strategy? Thanks for all the help so far!! Quote Link to comment
JorgeB Posted April 10, 2023 Share Posted April 10, 2023 13 hours ago, Guanyin said: Is that a sound strategy? I think so. 1 Quote Link to comment
Guanyin Posted June 6, 2023 Author Share Posted June 6, 2023 I've ended up formatting the disk and forfeiting the data. All the data is replaceable, hence this decision. Thanks for all the help @JorgeB 1 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.