Matthew Kent Posted July 26, 2020 Author Share Posted July 26, 2020 Not sure what to do next. I think I'm going to try rebuilding the drive again, but with the XFS encryption set this time in the drive settings. It was set to automatic before. Quote Link to comment
Matthew Kent Posted July 26, 2020 Author Share Posted July 26, 2020 K, the 2nd rebuild is underway, but from what I can tell, the drive should mount and emulate the contents, which it's not doing. I'm not holding out hope for this rebuild. Do you have any recommendations for the failed drive? I've gone ahead and pulled it. On powerup it sounds normal. When I had attempting to read from it, it eventually fails and disappears. Could the controller board possibly be bad? I have an identical drive that failed on me about 6 months ago that I could swap the board out with. Quote Link to comment
JorgeB Posted July 26, 2020 Share Posted July 26, 2020 10 hours ago, Matthew Kent said: I have, but it just shows it's an unmountable filesystem Please post the diags. Quote Link to comment
JorgeB Posted July 26, 2020 Share Posted July 26, 2020 5 hours ago, Matthew Kent said: K, the 2nd rebuild is underway, 2nd rebuild will be identical to the 1st one. Quote Link to comment
Matthew Kent Posted July 26, 2020 Author Share Posted July 26, 2020 (edited) I kind of figured that would be the case. I'm including my current diagnostic, however, the drive that's rebuilding won't be done for a few more hours, I can post another if needed afterwards. I also found my old damaged 5TB drive that was the raid twin In a previous NAS to this one before it died. Judging from the fact my current 5TB drive that failed still sounds normal when powering up, but is no longer showing up in bios or on other systems, I'm pretty sure the controller board has gone bad. I've read I can swap boards, but will need to swap a chip or two on the PCBs to make the board work. nas-diagnostics-20200725-2122.zip Edited July 26, 2020 by Matthew Kent Quote Link to comment
JorgeB Posted July 26, 2020 Share Posted July 26, 2020 When the rebuild finishes run xfs_repair on that disk and post the output. Quote Link to comment
Matthew Kent Posted July 26, 2020 Author Share Posted July 26, 2020 1 minute ago, johnnie.black said: When the rebuild finishes run xfs_repair on that disk and post the output. Thanks, will do Quote Link to comment
Matthew Kent Posted July 26, 2020 Author Share Posted July 26, 2020 I had to run xfs_repair -L on the drive, everything's in lost+found xfs_repair -L /dev/mapper/md3 Phase 1 - find and verify superblock... sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 128 resetting superblock root inode pointer to 128 sb realtime bitmap inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap ino pointer to 129 sb realtime summary inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary ino pointer to 130 Phase 2 - using internal log - zero log... Log inconsistent (didn't find previous header) failed to find log head zero_log: cannot find log head/tail (xlog_find_tail=5) - scan filesystem freespace and inode maps... sb_icount 0, counted 378816 sb_ifree 0, counted 1556 sb_fdblocks 1220416779, counted 461720257 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 Metadata corruption detected at 0x435c33, xfs_inode block 0x80/0x4000 bad CRC for inode 128 Bad flags2 set in inode 128 bad CRC for inode 131 Bad flags2 set in inode 131 reflink flag set on non-file inode 131 bad CRC for inode 132 Bad flags2 set in inode 132 reflink flag set on non-file inode 132 bad CRC for inode 133 Bad flags2 set in inode 133 bad CRC for inode 134 Bad flags2 set in inode 134 bad CRC for inode 135 Bad flags2 set in inode 135 reflink flag set on non-file inode 135 bad CRC for inode 136 Bad flags2 set in inode 136 bad CRC for inode 137 Bad flags2 set in inode 137 reflink flag set on non-file inode 137 bad CRC for inode 138 Bad flags2 set in inode 138 bad CRC for inode 128, will rewrite Bad flags2 set in inode 128 fixing bad flags2. Bad mtime nsec 4096409347 on inode 128, resetting to zero cleared root inode 128 bad CRC for inode 131, will rewrite imap claims a free inode 131 is in use, correcting imap and clearing inode cleared inode 131 bad CRC for inode 132, will rewrite imap claims a free inode 132 is in use, correcting imap and clearing inode cleared inode 132 bad CRC for inode 133, will rewrite Bad flags2 set in inode 133 fixing bad flags2. Bad mtime nsec 1823503145 on inode 133, resetting to zero cleared inode 133 bad CRC for inode 134, will rewrite Bad flags2 set in inode 134 fixing bad flags2. Bad atime nsec 1409811472 on inode 134, resetting to zero Bad mtime nsec 1982958202 on inode 134, resetting to zero cleared inode 134 bad CRC for inode 135, will rewrite imap claims a free inode 135 is in use, correcting imap and clearing inode cleared inode 135 bad CRC for inode 136, will rewrite Bad flags2 set in inode 136 fixing bad flags2. Bad CoW extent size 0 on inode 136, resetting to zero Bad atime nsec 3222442049 on inode 136, resetting to zero Bad mtime nsec 1379801840 on inode 136, resetting to zero cleared inode 136 bad CRC for inode 137, will rewrite imap claims a free inode 137 is in use, correcting imap and clearing inode cleared inode 137 bad CRC for inode 138, will rewrite Bad flags2 set in inode 138 fixing bad flags2. Bad atime nsec 1306046837 on inode 138, resetting to zero Bad mtime nsec 1678034225 on inode 138, resetting to zero cleared inode 138 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 3 - agno = 4 - agno = 2 entry "cache" in shortform directory 8589934720 references free inode 132 - agno = 0 junking entry "cache" in directory inode 8589934720 - agno = 1 entry "kory-arielle" in shortform directory 8589934722 references free inode 135 junking entry "kory-arielle" in directory inode 8589934722 Cleared next_unlinked in inode 128 entry "atom" in shortform directory 8589934725 references free inode 137 junking entry "atom" in directory inode 8589934725 entry ".Trash-0" in shortform directory 128 references free inode 131 junking entry ".Trash-0" in directory inode 128 Cleared next_unlinked in inode 133 Cleared next_unlinked in inode 134 Cleared next_unlinked in inode 136 Cleared next_unlinked in inode 138 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... reinitializing root directory - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 174, moving to lost+found disconnected dir inode 934683985, moving to lost+found disconnected dir inode 1617389729, moving to lost+found disconnected inode 1625981332, moving to lost+found disconnected inode 1625981333, moving to lost+found disconnected inode 1625981334, moving to lost+found disconnected dir inode 2147483783, moving to lost+found disconnected dir inode 2685354793, moving to lost+found disconnected dir inode 4302849431, moving to lost+found disconnected dir inode 6442451072, moving to lost+found disconnected dir inode 7817690933, moving to lost+found Phase 7 - verify and correct link counts... resetting inode 8589934720 nlinks from 7 to 6 resetting inode 8589934722 nlinks from 8 to 7 resetting inode 8589934725 nlinks from 3 to 2 resetting inode 131 nlinks from 2 to 9 Maximum metadata LSN (4:2318) is ahead of log (1:2). Format log to cycle 7. done Quote Link to comment
Matthew Kent Posted July 26, 2020 Author Share Posted July 26, 2020 I’ve got some good news. I decided to clean the contacts on the PCB controller on the failing drive. It allowed me to get it connected to a Linux recovery system I built. I can see there’s a lot of data in the lost+found folder, prob from the multiple attempts to get the drive going again, and it won’t mount normally. But with a recovery program I decided to buy, I’ve been able to pull about 100g of data off so far with no read/write errors. Keeping my fingers crossed!! Do you guys have any tips on how to handle the lost+found data? Quote Link to comment
Matthew Kent Posted July 27, 2020 Author Share Posted July 27, 2020 Wow, I think I have even better news, I decided to actually look in the lost+found folders on the rebuilt drive and discovered most of my files look like they exist with their proper names and folder locations in a few randomly numbered folders, about 3tb worth, which I think is correct! I’m going to go ahead and move forward with this instead of the recovered files since the full recovery of the damaged drive looks like it might take days. Thanks @johnnie.black for all the help! 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.