March 26, 20197 yr Hi guys, we’ve had a power cut, and on starting my server one of my drives is now unmountable... (i will be investing in a UPS as soon as possible). There are some files on here that i dont have backed up, but they are not as important. i have started in maintenance mode and ran xfs repair with -n option. phase 1 states find and verify superblock... and nothing else. Phase 2 gives an alert saying that the filesystem has metadata changes in a log which is being ignored. after that several folders and files are listed as referencing non-existent inode. now are these the only files it can find or the only ones it has an issue with? Thanks in advance M0zz Edited March 26, 20197 yr by M0zza
March 27, 20197 yr Community Expert 8 hours ago, M0zza said: and ran xfs repair with -n option. run it without -n
March 27, 20197 yr Author So just run without the -n and i can expect to lose just those mentioned in the -n verbage? or should i expect total annihilation of disc? documentation on this tool i have found seems to assume some preknowledge.
March 27, 20197 yr Community Expert You might not lose anything, you might lose some or a lot, depends on how corrupt the filesystem is, most times there is no significant data loss, and the dry run output most times doesn't mean much.
March 27, 20197 yr Author Well then... when i get home from work i will run xfs_repair and update the post on how it went.
March 30, 20197 yr Author Right. Well it is now the weekend and I have had a chance to look into this... tried to run xfs-repair with no options and got the following... 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 to repair. Now the drive is mostly full and had only just started being written to again... is this what i can expect to lose of will the log contain long term data?
March 30, 20197 yr Community Expert 32 minutes ago, M0zza said: Now the drive is mostly full and had only just started being written to again... is this what i can expect to lose of will the log contain long term data? Nearly always using the -L option causes absolutely no data loss at all. In the worst case it is only likely to affect the last file that was written.
March 30, 20197 yr Author Bollox! ran with -L and ended with ’xfs_repair: phase6.c:1376: longform_dir2_rebuild: assertion ‘done’ failed.’
March 31, 20197 yr Community Expert Which version of Unraid? You may have a version that doesn't have the most recent version of xfs_repair.
March 31, 20197 yr Community Expert 13 hours ago, M0zza said: ’xfs_repair: phase6.c:1376: longform_dir2_rebuild: assertion ‘done’ failed.’ That's a xfs bug, you'd need to update to v6.7rc or manually update xfsprogs.
March 31, 20197 yr Author Updated to 6.7 and rerun xfs_repair. it looks like not much if anything was lost, but i do have a bit of tidying up to do as a hundred or so files and folders in lost+found. Thank you all for your help with this. Couldnt have done it with out you. M0zz
Archived
This topic is now archived and is closed to further replies.