Matthews Posted June 3, 2020 Posted June 3, 2020 Hi, Can anyone perhaps explain what does this mean for the drive? I had a weird situation where the drive that was in the array was only read. I assumed I reached my max limit of critical utilization (90%) when dl files. After I changed it to 95 % the drive somehow failed and stopped the array and got the "Unmountable: No file system". Thus I came to the forum and found out that I should run the repair command -nv if the output was okay, i should run the -nL command, which I havent yet since the problem is I do not understand the output. I only ran the xfs_repair command -nv and got the following status/response posted below. Can anyone tell me what does it mean? Disk ded or just corrupted? P.s. Disk has 187 - Reported uncorrect 5 (Raw value). I am assuming I will have to replace the drive very soon since this is the second time this exact drive has got me in this mess. Thank you for any suggestions and help! Phase 1 - find and verify superblock... - block cache size set to 731784 entries Phase 2 - using internal log - zero log... zero_log: head block 2726329 tail block 2721272 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... Metadata CRC error detected at 0x43cc6d, xfs_allocbt block 0x130642a8/0x1000 btree block 0/39897173 is suspect, error -74 bad magic # 0x241a9c92 in btbno block 0/39897173 agi unlinked bucket 7 is 1114354311 in ag 1 (inode=3261837959) agf_btreeblks 33, counted 32 in ag 0 agi unlinked bucket 47 is 1136892079 in ag 0 (inode=1136892079) agi unlinked bucket 54 is 1136892086 in ag 0 (inode=1136892086) sb_ifree 46690, counted 46754 sb_fdblocks 126075810, counted 129340729 - 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 0x458c79, xfs_dir3_block block 0x13064298/0x1000 bad directory block magic # 0x241a9c92 in block 0 for directory inode 268517514 corrupt block 0 in directory inode 268517514 would junk block no . entry for directory 268517514 no .. entry for directory 268517514 problem with directory contents in inode 268517514 would have cleared inode 268517514 - 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 = 2 - agno = 3 bad directory block magic # 0x241a9c92 in block 0 for directory inode 268517514 corrupt block 0 in directory inode 268517514 would junk block no . entry for directory 268517514 no .. entry for directory 268517514 problem with directory contents in inode 268517514 would have cleared inode 268517514 entry "n" in shortform directory 505388108 references free inode 268517514 would have junked entry "n" in directory inode 505388108 entry ".." at block 0 offset 80 in directory inode 5454144722 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 1134627659 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 7324966922 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 1134627684 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 7324966966 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 7324967061 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 3261836359 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 3261836502 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 3261836540 references free inode 268517514 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 entry "n" in shortform directory inode 505388108 points to free inode 268517514 would junk entry entry ".." in directory inode 1134627659 points to free inode 268517514, would junk entry bad hash table for directory inode 1134627659 (no data entry): would rebuild entry ".." in directory inode 1134627684 points to free inode 268517514, would junk entry bad hash table for directory inode 1134627684 (no data entry): would rebuild - agno = 1 entry ".." in directory inode 3261836359 points to free inode 268517514, would junk entry bad hash table for directory inode 3261836359 (no data entry): would rebuild entry ".." in directory inode 3261836502 points to free inode 268517514, would junk entry bad hash table for directory inode 3261836502 (no data entry): would rebuild entry ".." in directory inode 3261836540 points to free inode 268517514, would junk entry bad hash table for directory inode 3261836540 (no data entry): would rebuild - agno = 2 entry ".." in directory inode 5454144722 points to free inode 268517514, would junk entry bad hash table for directory inode 5454144722 (no data entry): would rebuild - agno = 3 entry ".." in directory inode 7324966922 points to free inode 268517514, would junk entry bad hash table for directory inode 7324966922 (no data entry): would rebuild entry ".." in directory inode 7324966966 points to free inode 268517514, would junk entry bad hash table for directory inode 7324966966 (no data entry): would rebuild entry ".." in directory inode 7324967061 points to free inode 268517514, would junk entry bad hash table for directory inode 7324967061 (no data entry): would rebuild - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 985625184, would move to lost+found disconnected inode 1134627388, would move to lost+found disconnected inode 1134627399, would move to lost+found disconnected inode 1134627403, would move to lost+found disconnected inode 1134627421, would move to lost+found disconnected inode 1134627424, would move to lost+found disconnected inode 1134627426, would move to lost+found disconnected inode 1134627526, would move to lost+found disconnected inode 1134627527, would move to lost+found disconnected inode 1134627528, would move to lost+found disconnected dir inode 1134627530, would move to lost+found disconnected inode 1134627532, would move to lost+found disconnected inode 1134627533, would move to lost+found disconnected inode 1134627534, would move to lost+found disconnected inode 1134627535, would move to lost+found disconnected inode 1134627539, would move to lost+found disconnected inode 1134627540, would move to lost+found disconnected inode 1134627541, would move to lost+found disconnected inode 1134627542, would move to lost+found disconnected inode 1134627543, would move to lost+found disconnected dir inode 1134627544, would move to lost+found disconnected dir inode 1134627659, would move to lost+found disconnected inode 1134627679, would move to lost+found disconnected inode 1134627680, would move to lost+found disconnected inode 1134627681, would move to lost+found disconnected inode 1134627682, would move to lost+found disconnected dir inode 1134627684, would move to lost+found disconnected inode 1134627696, would move to lost+found disconnected inode 1134627697, would move to lost+found disconnected inode 1134627698, would move to lost+found disconnected inode 1134627700, would move to lost+found disconnected inode 1134627701, would move to lost+found disconnected inode 1134627703, would move to lost+found disconnected inode 1134627704, would move to lost+found disconnected inode 1134627705, would move to lost+found disconnected inode 1136892079, would move to lost+found disconnected inode 1136892086, would move to lost+found disconnected dir inode 3261836356, would move to lost+found disconnected dir inode 3261836358, would move to lost+found disconnected dir inode 3261836359, would move to lost+found disconnected dir inode 3261836502, would move to lost+found disconnected dir inode 3261836540, would move to lost+found disconnected inode 3261837959, would move to lost+found disconnected dir inode 5454144722, would move to lost+found disconnected dir inode 5454158679, would move to lost+found disconnected dir inode 5556624766, would move to lost+found disconnected dir inode 5556624773, would move to lost+found disconnected dir inode 7324966916, would move to lost+found disconnected dir inode 7324966922, would move to lost+found disconnected dir inode 7324966966, would move to lost+found disconnected dir inode 7324967061, would move to lost+found Phase 7 - verify link counts... would have reset inode 505388108 nlinks from 6 to 5 would have reset inode 3261837959 nlinks from 0 to 1 would have reset inode 1136892079 nlinks from 0 to 1 would have reset inode 1136892086 nlinks from 0 to 1 No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Wed Jun 3 20:46:28 2020 Phase Start End Duration Phase 1: 06/03 20:45:44 06/03 20:45:44 Phase 2: 06/03 20:45:44 06/03 20:45:46 2 seconds Phase 3: 06/03 20:45:46 06/03 20:46:18 32 seconds Phase 4: 06/03 20:46:18 06/03 20:46:18 Phase 5: Skipped Phase 6: 06/03 20:46:18 06/03 20:46:28 10 seconds Phase 7: 06/03 20:46:28 06/03 20:46:28 Total run time: 44 seconds Quote
itimpi Posted June 3, 2020 Posted June 3, 2020 That is saying that there is a significant level of corruption so expect some files to either be lost or (more likely) end up in the lost+found folder with names that are not the original names making them hard to recognise. you might as well run the repair option as it should make the drive mountable again with the majority of files intact. do you have backups of any important data that is on the array? Quote
Matthews Posted June 4, 2020 Author Posted June 4, 2020 So the drive got corrupted. I only have parity, no backup. I have some files, hopefully those are unaffected, but it is hard to say. So run the -nL command or just -L command. Can I do it in the "Check Filesystem Status" under the drive that shows that is unmountable or use the terminal with xfs_repair -nL /dev/disk4? Quote
Matthews Posted June 4, 2020 Author Posted June 4, 2020 I just ran the -nL command and got these results. Should i go out of maintenance mode and run the array? 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... Metadata CRC error detected at 0x43cc6d, xfs_allocbt block 0x130642a8/0x1000 btree block 0/39897173 is suspect, error -74 bad magic # 0x241a9c92 in btbno block 0/39897173 agi unlinked bucket 7 is 1114354311 in ag 1 (inode=3261837959) agf_btreeblks 33, counted 32 in ag 0 agi unlinked bucket 47 is 1136892079 in ag 0 (inode=1136892079) agi unlinked bucket 54 is 1136892086 in ag 0 (inode=1136892086) sb_ifree 46690, counted 46754 sb_fdblocks 126075810, counted 129340729 - 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 0x458c79, xfs_dir3_block block 0x13064298/0x1000 bad directory block magic # 0x241a9c92 in block 0 for directory inode 268517514 corrupt block 0 in directory inode 268517514 would junk block no . entry for directory 268517514 no .. entry for directory 268517514 problem with directory contents in inode 268517514 would have cleared inode 268517514 - 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 = 2 - agno = 1 - agno = 3 bad directory block magic # 0x241a9c92 in block 0 for directory inode 268517514 corrupt block 0 in directory inode 268517514 would junk block no . entry for directory 268517514 no .. entry for directory 268517514 problem with directory contents in inode 268517514 would have cleared inode 268517514 entry "n" in shortform directory 505388108 references free inode 268517514 would have junked entry "n" in directory inode 505388108 entry ".." at block 0 offset 80 in directory inode 5454144722 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 7324966922 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 7324966966 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 7324967061 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 1134627659 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 1134627684 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 3261836359 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 3261836502 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 3261836540 references free inode 268517514 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... entry "n" in shortform directory inode 505388108 points to free inode 268517514 would junk entry entry ".." in directory inode 1134627659 points to free inode 268517514, would junk entry bad hash table for directory inode 1134627659 (no data entry): would rebuild entry ".." in directory inode 1134627684 points to free inode 268517514, would junk entry bad hash table for directory inode 1134627684 (no data entry): would rebuild entry ".." in directory inode 3261836359 points to free inode 268517514, would junk entry bad hash table for directory inode 3261836359 (no data entry): would rebuild entry ".." in directory inode 3261836502 points to free inode 268517514, would junk entry bad hash table for directory inode 3261836502 (no data entry): would rebuild entry ".." in directory inode 3261836540 points to free inode 268517514, would junk entry bad hash table for directory inode 3261836540 (no data entry): would rebuild entry ".." in directory inode 5454144722 points to free inode 268517514, would junk entry bad hash table for directory inode 5454144722 (no data entry): would rebuild entry ".." in directory inode 7324966922 points to free inode 268517514, would junk entry bad hash table for directory inode 7324966922 (no data entry): would rebuild entry ".." in directory inode 7324966966 points to free inode 268517514, would junk entry bad hash table for directory inode 7324966966 (no data entry): would rebuild entry ".." in directory inode 7324967061 points to free inode 268517514, would junk entry bad hash table for directory inode 7324967061 (no data entry): would rebuild - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 985625184, would move to lost+found disconnected inode 1134627388, would move to lost+found disconnected inode 1134627399, would move to lost+found disconnected inode 1134627403, would move to lost+found disconnected inode 1134627421, would move to lost+found disconnected inode 1134627424, would move to lost+found disconnected inode 1134627426, would move to lost+found disconnected inode 1134627526, would move to lost+found disconnected inode 1134627527, would move to lost+found disconnected inode 1134627528, would move to lost+found disconnected dir inode 1134627530, would move to lost+found disconnected inode 1134627532, would move to lost+found disconnected inode 1134627533, would move to lost+found disconnected inode 1134627534, would move to lost+found disconnected inode 1134627535, would move to lost+found disconnected inode 1134627539, would move to lost+found disconnected inode 1134627540, would move to lost+found disconnected inode 1134627541, would move to lost+found disconnected inode 1134627542, would move to lost+found disconnected inode 1134627543, would move to lost+found disconnected dir inode 1134627544, would move to lost+found disconnected dir inode 1134627659, would move to lost+found disconnected inode 1134627679, would move to lost+found disconnected inode 1134627680, would move to lost+found disconnected inode 1134627681, would move to lost+found disconnected inode 1134627682, would move to lost+found disconnected dir inode 1134627684, would move to lost+found disconnected inode 1134627696, would move to lost+found disconnected inode 1134627697, would move to lost+found disconnected inode 1134627698, would move to lost+found disconnected inode 1134627700, would move to lost+found disconnected inode 1134627701, would move to lost+found disconnected inode 1134627703, would move to lost+found disconnected inode 1134627704, would move to lost+found disconnected inode 1134627705, would move to lost+found disconnected inode 1136892079, would move to lost+found disconnected inode 1136892086, would move to lost+found disconnected dir inode 3261836356, would move to lost+found disconnected dir inode 3261836358, would move to lost+found disconnected dir inode 3261836359, would move to lost+found disconnected dir inode 3261836502, would move to lost+found disconnected dir inode 3261836540, would move to lost+found disconnected inode 3261837959, would move to lost+found disconnected dir inode 5454144722, would move to lost+found disconnected dir inode 5454158679, would move to lost+found disconnected dir inode 5556624766, would move to lost+found disconnected dir inode 5556624773, would move to lost+found disconnected dir inode 7324966916, would move to lost+found disconnected dir inode 7324966922, would move to lost+found disconnected dir inode 7324966966, would move to lost+found disconnected dir inode 7324967061, would move to lost+found Phase 7 - verify link counts... would have reset inode 505388108 nlinks from 6 to 5 would have reset inode 3261837959 nlinks from 0 to 1 would have reset inode 1136892079 nlinks from 0 to 1 would have reset inode 1136892086 nlinks from 0 to 1 No modify flag set, skipping filesystem flush and exiting. Quote
itimpi Posted June 4, 2020 Posted June 4, 2020 You have to remove the 'n' option or it will only be a check and not a repair. Quote
Matthews Posted June 4, 2020 Author Posted June 4, 2020 Cant mount the disk with -v command. I am using the -L command now to see if that will work. Phase 1 - find and verify superblock... - block cache size set to 731784 entries Phase 2 - using internal log - zero log... zero_log: head block 2726329 tail block 2721272 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. Quote
Matthews Posted June 4, 2020 Author Posted June 4, 2020 I just figured it out this morning, that -n doesnt execute it just checks. Just finished the -L command and this is the output. Im running another -n command to check if all is okay. Then mounting the array out of maintenance. Is that safe to do? 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 destroyed because the -L option was used. - scan filesystem freespace and inode maps... Metadata CRC error detected at 0x43cc6d, xfs_allocbt block 0x130642a8/0x1000 btree block 0/39897173 is suspect, error -74 bad magic # 0x241a9c92 in btbno block 0/39897173 agf_btreeblks 33, counted 32 in ag 0 agi unlinked bucket 7 is 1114354311 in ag 1 (inode=3261837959) agi unlinked bucket 47 is 1136892079 in ag 0 (inode=1136892079) agi unlinked bucket 54 is 1136892086 in ag 0 (inode=1136892086) sb_ifree 46690, counted 46754 sb_fdblocks 126075810, counted 129340729 - 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 CRC error detected at 0x458c79, xfs_dir3_block block 0x13064298/0x1000 bad directory block magic # 0x241a9c92 in block 0 for directory inode 268517514 corrupt block 0 in directory inode 268517514 will junk block no . entry for directory 268517514 no .. entry for directory 268517514 problem with directory contents in inode 268517514 cleared inode 268517514 - 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 = 2 - agno = 1 - agno = 3 entry "n" in shortform directory 505388108 references free inode 268517514 junking entry "n" in directory inode 505388108 entry ".." at block 0 offset 80 in directory inode 5454144722 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 7324966922 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 7324966966 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 7324967061 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 1134627659 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 1134627684 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 3261836359 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 3261836502 references free inode 268517514 entry ".." at block 0 offset 80 in directory inode 3261836540 references free inode 268517514 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... entry ".." in directory inode 1134627659 points to free inode 268517514 bad hash table for directory inode 1134627659 (no data entry): rebuilding rebuilding directory inode 1134627659 entry ".." in directory inode 1134627684 points to free inode 268517514 bad hash table for directory inode 1134627684 (no data entry): rebuilding rebuilding directory inode 1134627684 entry ".." in directory inode 3261836359 points to free inode 268517514 bad hash table for directory inode 3261836359 (no data entry): rebuilding rebuilding directory inode 3261836359 entry ".." in directory inode 3261836502 points to free inode 268517514 bad hash table for directory inode 3261836502 (no data entry): rebuilding rebuilding directory inode 3261836502 entry ".." in directory inode 3261836540 points to free inode 268517514 bad hash table for directory inode 3261836540 (no data entry): rebuilding rebuilding directory inode 3261836540 entry ".." in directory inode 5454144722 points to free inode 268517514 bad hash table for directory inode 5454144722 (no data entry): rebuilding rebuilding directory inode 5454144722 entry ".." in directory inode 7324966922 points to free inode 268517514 bad hash table for directory inode 7324966922 (no data entry): rebuilding rebuilding directory inode 7324966922 entry ".." in directory inode 7324966966 points to free inode 268517514 bad hash table for directory inode 7324966966 (no data entry): rebuilding rebuilding directory inode 7324966966 entry ".." in directory inode 7324967061 points to free inode 268517514 bad hash table for directory inode 7324967061 (no data entry): rebuilding rebuilding directory inode 7324967061 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 985625184, moving to lost+found disconnected inode 1134627388, moving to lost+found disconnected inode 1134627399, moving to lost+found disconnected inode 1134627403, moving to lost+found disconnected inode 1134627421, moving to lost+found disconnected inode 1134627424, moving to lost+found disconnected inode 1134627426, moving to lost+found disconnected inode 1134627526, moving to lost+found disconnected inode 1134627527, moving to lost+found disconnected inode 1134627528, moving to lost+found disconnected dir inode 1134627530, moving to lost+found disconnected inode 1134627532, moving to lost+found disconnected inode 1134627533, moving to lost+found disconnected inode 1134627534, moving to lost+found disconnected inode 1134627535, moving to lost+found disconnected inode 1134627539, moving to lost+found disconnected inode 1134627540, moving to lost+found disconnected inode 1134627541, moving to lost+found disconnected inode 1134627542, moving to lost+found disconnected inode 1134627543, moving to lost+found disconnected dir inode 1134627544, moving to lost+found disconnected dir inode 1134627659, moving to lost+found disconnected inode 1134627679, moving to lost+found disconnected inode 1134627680, moving to lost+found disconnected inode 1134627681, moving to lost+found disconnected inode 1134627682, moving to lost+found disconnected dir inode 1134627684, moving to lost+found disconnected inode 1134627696, moving to lost+found disconnected inode 1134627697, moving to lost+found disconnected inode 1134627698, moving to lost+found disconnected inode 1134627700, moving to lost+found disconnected inode 1134627701, moving to lost+found disconnected inode 1134627703, moving to lost+found disconnected inode 1134627704, moving to lost+found disconnected inode 1134627705, moving to lost+found disconnected inode 1136892079, moving to lost+found disconnected inode 1136892086, moving to lost+found disconnected dir inode 3261836356, moving to lost+found disconnected dir inode 3261836358, moving to lost+found disconnected dir inode 3261836359, moving to lost+found disconnected dir inode 3261836502, moving to lost+found disconnected dir inode 3261836540, moving to lost+found disconnected inode 3261837959, moving to lost+found disconnected dir inode 5454144722, moving to lost+found disconnected dir inode 5454158679, moving to lost+found disconnected dir inode 5556624766, moving to lost+found disconnected dir inode 5556624773, moving to lost+found disconnected dir inode 7324966916, moving to lost+found disconnected dir inode 7324966922, moving to lost+found disconnected dir inode 7324966966, moving to lost+found disconnected dir inode 7324967061, moving to lost+found Phase 7 - verify and correct link counts... resetting inode 268517514 nlinks from 2 to 19 resetting inode 505388108 nlinks from 6 to 5 Maximum metadata LSN (2:2726326) is ahead of log (1:2). Format log to cycle 5. done Quote
Matthews Posted June 4, 2020 Author Posted June 4, 2020 Running the -n command gave me this output. Seems all is okay and go check the lost+found folder. 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 - 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 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. Quote
Matthews Posted June 4, 2020 Author Posted June 4, 2020 Drive mounted after running the -L command. It would seem only one folder was affected(not important files), since all files in lost+found are from the same folder. The rest it would seem its intact, so far at least. I will try and check if anything important is corrupted or missing. Thank you for your help! This forum rocks!! Quote
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.