boosted

Rebuild completed without errors. It does not appear that I have lost any file, at least that I can tell. As long as the loss is the whole file and not chunks of it. That'd just corrupt the whole file without me knowing it for a long while. Spare HD ordered as well. Thanks again trurl for your help on this.

12 more hours til rebuild is done. I'll pick up some drives during this BF sale if possible as spares. Prices have gone down since when I built it.

Extended SMARTS test finally finished. Both said completed without error. Here are their reports. I think I'm ok to proceed. But I'm not sure if some the attributes numbers are good. Most say "old age" eventhough it's just 2 years old. unraid-smart-20201124-1215-disk3.zip unraid-smart-20201124-1215-disk5.zip

Thank you!

One more question, can I rebuild both drives at the same time? The wiki didn't say whether that's advisable or possible.

Ok, I will do that. Extended smart test, then stop array, unassign disks, start array, stop array, assign disk back then start to rebuild. According to the wiki. Thank you again.

Thank you for helping me get this far! I honestly don't think I lost anything, but I will see over time, I can most likely recover the last 2 month, i think that's how long they've been down. So does no lost+found mean nothing was lost? Or that nothing that was lost can be recovered? What is the rebuilding process from this point? The wiki didn't say what to do to rebuild after a repair. I don't want to assume anything. As for what happened, can you speculate anything? Maybe those 2 drives lost power at some point and corrupted the data? Should I still trust these 2 drives or should I get replacements for them?

The data that were gone in maintenance mode are back, mainly the things I copied over the past month or so. But I don't know if I'm missing anything though.

disk 3 and 5 show emulated with red X and no unmountable labeling for 3 and 5. Nothing in the unassigned section. here's the diagnostic. unraid-diagnostics-20201123-1928.zip

I did not

ok I ran -vL on disk 3. Phase 1 - find and verify superblock... - block cache size set to 120736 entries sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 96 resetting superblock root inode pointer to 96 sb realtime bitmap inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 97 resetting superblock realtime bitmap ino pointer to 97 sb realtime summary inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 98 resetting superblock realtime summary ino pointer to 98 Phase 2 - using internal log - zero log... zero_log: head block 487811 tail block 487807 ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... sb_icount 0, counted 18112 sb_ifree 0, counted 334 sb_fdblocks 1952984865, counted 1064388454 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 0 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (1:487789) is ahead of log (1:2). Format log to cycle 4. XFS_REPAIR Summary Mon Nov 23 19:10:33 2020 Phase Start End Duration Phase 1: 11/23 19:07:53 11/23 19:07:53 Phase 2: 11/23 19:07:53 11/23 19:08:42 49 seconds Phase 3: 11/23 19:08:42 11/23 19:08:44 2 seconds Phase 4: 11/23 19:08:44 11/23 19:08:44 Phase 5: 11/23 19:08:44 11/23 19:08:44 Phase 6: 11/23 19:08:44 11/23 19:08:45 1 second Phase 7: 11/23 19:08:45 11/23 19:08:45 Total run time: 52 seconds done still says unmountable. I ran disk3 with -n again just to see if there's more repairs needed. maybe there are? Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - 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 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - 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 = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting.

I'm still in maintenance mode. do I take it out of maintenance mode to see if disk5 is mountable? Currently it still says both disk 3 and 5 are not mountable in maintenance mode.

disk 5 is much different Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock - block cache size set to 120736 entries sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 96 resetting superblock root inode pointer to 96 sb realtime bitmap inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 97 resetting superblock realtime bitmap ino pointer to 97 sb realtime summary inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 98 resetting superblock realtime summary ino pointer to 98 Phase 2 - using internal log - zero log... zero_log: head block 163 tail block 163 - scan filesystem freespace and inode maps... sb_icount 0, counted 64 sb_ifree 0, counted 60 sb_fdblocks 1952984865, counted 1952984857 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - 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 = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Note - stripe unit (0) and width (0) were copied from a backup superblock. Please reset with mount -o sunit=,swidth= if necessary XFS_REPAIR Summary Mon Nov 23 18:00:47 2020 Phase Start End Duration Phase 1: 11/23 18:00:47 11/23 18:00:47 Phase 2: 11/23 18:00:47 11/23 18:00:47 Phase 3: 11/23 18:00:47 11/23 18:00:47 Phase 4: 11/23 18:00:47 11/23 18:00:47 Phase 5: 11/23 18:00:47 11/23 18:00:47 Phase 6: 11/23 18:00:47 11/23 18:00:47 Phase 7: 11/23 18:00:47 11/23 18:00:47 Total run time: done

here's disk 3 with -v Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock - block cache size set to 120736 entries sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 96 resetting superblock root inode pointer to 96 sb realtime bitmap inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 97 resetting superblock realtime bitmap ino pointer to 97 sb realtime summary inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 98 resetting superblock realtime summary ino pointer to 98 Phase 2 - using internal log - zero log... zero_log: head block 487811 tail block 487807 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.

Had to finish up some stuff. Here are the results. I put it in maintenance mode, added verbose to options to make it -nv and ran the test for both drives. drive 3 took a while, and I clicked refresh to get the result. disk 5 took no time at all, almost as if it didn't run? disk3 Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now. disk5 Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now.