September 30, 20205 yr I was using the Parity swap method to replace a bad drive with a larger than parity drive so I followed the guide. I "copied" to the new parity and after that was done, it was doing a data rebuild on the Old parity drive (in the bad disks slot) and now it shows this: I attached my Diag. EDIT: I should also point out that the Unmountable Disk was my old Parity drive (that I thought was still good) but I do have a new 4tb drive I had planned to replace that disk (disk1) with after this process was finished. Don't know if thats still an option or if I lost everything on disk1 already. EDIT2: Did an XFSRepair in Maintence Mode with the -n switch and this was the output: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... agf_freeblks 29078110, counted 29078240 in ag 0 agf_freeblks 6819842, counted 6819974 in ag 2 agf_freeblks 4968062, counted 4937793 in ag 1 agf_freeblks 18856952, counted 18857398 in ag 3 agi_freecount 24, counted 107 in ag 0 agi_freecount 24, counted 107 in ag 0 finobt agi_freecount 95, counted 94 in ag 1 agi_freecount 95, counted 94 in ag 1 finobt agi_freecount 113, counted 122 in ag 2 agi_freecount 113, counted 122 in ag 2 finobt sb_fdblocks 59198793, counted 59693421 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 Metadata CRC error detected at xfs_dir3_data block 0x50/0x1000 corrupt block 0 in directory inode 102 would junk block no . entry for directory 102 no .. entry for directory 102 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 3 - agno = 2 corrupt block 0 in directory inode 102 would junk block no . entry for directory 102 no .. entry for directory 102 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... Metadata CRC error detected at xfs_dir3_data block 0x50/0x1000 wrong FS UUID, directory inode 102 block 80 bad hash table for directory inode 102 (no data entry): would rebuild would create missing "." entry in dir ino 102 entry "Science Fair" in dir ino 3221225570 doesn't have a .. entry, will set it in ino 102. wrong FS UUID, directory inode 102 block 80 would create missing "." entry in dir ino 102 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 130, would move to lost+found disconnected inode 131, would move to lost+found disconnected inode 132, would move to lost+found disconnected inode 133, would move to lost+found disconnected inode 134, would move to lost+found disconnected inode 135, would move to lost+found disconnected inode 136, would move to lost+found disconnected inode 137, would move to lost+found disconnected inode 138, would move to lost+found disconnected inode 139, would move to lost+found disconnected inode 140, would move to lost+found disconnected inode 141, would move to lost+found disconnected inode 142, would move to lost+found disconnected inode 143, would move to lost+found disconnected inode 144, would move to lost+found disconnected inode 145, would move to lost+found disconnected inode 146, would move to lost+found disconnected inode 147, would move to lost+found disconnected inode 148, would move to lost+found disconnected inode 149, would move to lost+found disconnected inode 150, would move to lost+found disconnected inode 151, would move to lost+found disconnected inode 152, would move to lost+found disconnected inode 153, would move to lost+found disconnected inode 154, would move to lost+found disconnected inode 155, would move to lost+found disconnected inode 156, would move to lost+found disconnected inode 157, would move to lost+found disconnected inode 158, would move to lost+found disconnected inode 159, would move to lost+found disconnected inode 1088992, would move to lost+found disconnected inode 1088993, would move to lost+found disconnected inode 1088994, would move to lost+found disconnected inode 1088995, would move to lost+found disconnected inode 1088996, would move to lost+found disconnected inode 1088997, would move to lost+found disconnected inode 1088998, would move to lost+found disconnected inode 1088999, would move to lost+found disconnected inode 1089000, would move to lost+found disconnected inode 1089001, would move to lost+found disconnected inode 1089002, would move to lost+found disconnected inode 1089003, would move to lost+found disconnected inode 1089004, would move to lost+found disconnected inode 1089005, would move to lost+found disconnected inode 1089006, would move to lost+found disconnected inode 1089007, would move to lost+found disconnected inode 1089008, would move to lost+found disconnected inode 1089009, would move to lost+found disconnected inode 1089010, would move to lost+found disconnected inode 1089011, would move to lost+found disconnected inode 1089012, would move to lost+found disconnected inode 1089013, would move to lost+found disconnected inode 1089014, would move to lost+found disconnected inode 1089015, would move to lost+found disconnected inode 1089016, would move to lost+found disconnected inode 1089017, would move to lost+found disconnected inode 1089018, would move to lost+found disconnected inode 1089019, would move to lost+found disconnected inode 1089020, would move to lost+found disconnected inode 1089021, would move to lost+found disconnected inode 1089022, would move to lost+found disconnected inode 1089023, would move to lost+found disconnected inode 1089024, would move to lost+found disconnected inode 1089025, would move to lost+found disconnected inode 1089026, would move to lost+found disconnected inode 1089027, would move to lost+found disconnected inode 1089028, would move to lost+found disconnected inode 1089029, would move to lost+found disconnected inode 1089030, would move to lost+found disconnected inode 1089031, would move to lost+found disconnected inode 1089032, would move to lost+found disconnected inode 1089033, would move to lost+found disconnected inode 1089034, would move to lost+found disconnected inode 1089035, would move to lost+found disconnected inode 1089036, would move to lost+found disconnected inode 1089037, would move to lost+found disconnected inode 1089038, would move to lost+found disconnected inode 1089039, would move to lost+found disconnected inode 1089040, would move to lost+found disconnected inode 1089041, would move to lost+found disconnected inode 1089042, would move to lost+found disconnected inode 1089043, would move to lost+found disconnected inode 1089044, would move to lost+found disconnected inode 1089045, would move to lost+found disconnected inode 1089046, would move to lost+found disconnected inode 1089047, would move to lost+found disconnected inode 1089048, would move to lost+found disconnected inode 1089049, would move to lost+found disconnected inode 1089050, would move to lost+found disconnected dir inode 2149391464, would move to lost+found Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. Thanks, Scott unraid-diagnostics-20200930-1517.zip Edited September 30, 20205 yr by scottw
October 1, 20205 yr Community Expert Run it again without -n or nothing will be done, if it asks for -L use it.
October 1, 20205 yr Author Thank you, thank you, thank you! I think I am finally back up. My docker was dead but I was able to delete and re-create it and just restore from Previous Apps. Thanks again! Scott
Archived
This topic is now archived and is closed to further replies.