Hi.  I'm wondering if someone can help me with how to proceed.  About a week ago, I saw on my dashboard that disk 1 in my array was reporting as a bad drive and that it was being emulated.  I've never seen this before and took it at face value and bought a new hard drive to replace it.  I replaced the drive and allowed it to rebuild overnight.  However, in the morning it still reported it as unmountable.  I then started it up in maintenance mode and ran the xfs_repair in the gui.  There's ton of issues that frankly I'm not too familiar with, I pasted a small segment of the end, but it always ends with that Assertion error. 

 

junking entry "Contents" in directory inode 26323979754
entry "Contents" in shortform directory 26323979756 references free inode 16251220
junking entry "Contents" in directory inode 26323979756
entry "Contents" in shortform directory 26323979758 references free inode 16251222
junking entry "Contents" in directory inode 26323979758
entry "Contents" in shortform directory 26323979760 references free inode 16251224
junking entry "Contents" in directory inode 26323979760
entry "Contents" in shortform directory 26323979762 references free inode 16251226
junking entry "Contents" in directory inode 26323979762
entry "Contents" in shortform directory 26323979764 references free inode 16251228
junking entry "Contents" in directory inode 26323979764
entry "Contents" in shortform directory 26323979766 references free inode 16251229
junking entry "Contents" in directory inode 26323979766
entry "Contents" in shortform directory 26323979768 references free inode 16251230
junking entry "Contents" in directory inode 26323979768
entry "Contents" in shortform directory 26323979770 references free inode 16251232
junking entry "Contents" in directory inode 26323979770
entry "Contents" in shortform directory 26323979772 references free inode 16251234
junking entry "Contents" in directory inode 26323979772
entry "Contents" in shortform directory 26323979774 references free inode 16251236
junking entry "Contents" in directory inode 26323979774
xfs_repair: rmap.c:701: mark_inode_rl: Assertion `!(!!((rmap->rm_owner) & (1ULL << 63)))' failed.

 

I don't think it's the drive that's bad anymore and perhaps the filesystem was corrupt and rebuilding it just rebuilt the corrupt filesystem.  I'm not sure how to proceed.  I've tried running xfs_repair many times and with the "-L" option but it always ends in that Assertion error.

 

Wondering what my options are?  It says my drive is being emulated but it looks like I'm missing some files.  

1) Are there any other things I can try to repair it?

 

2) If it's a lost cause at this point, is there anyway, I can just take the loss of that one disk and replace it?  (I have a 4 disk array - with one being parity and the other drives seems to be ok)

3) Do I have to wipe everything and start from scratch?

 

I attached the full xfs_repair output if that helps. 

Thanks in advance.  I appreciate any help.   

 

 

 

log.txt

xfs_repair is not able to repair that filesystem, which Unraid release are you running?

@JorgeB I’m running the latest release 6.12.10. 

You can try updating to 7.0.0-beta, it includes much newer xfs-progs, but note that running xfs_repair from the GUI is broken, so you would need to tun it manually, post back if you need the instructions.

Thanks for the reply @JorgeB.  I upgraded to 7.0.0-beta and ran xfs_repair with and without the "-L" option through the terminal but it still ends with the same assertion error.  Is it a lost cause at this point?

What would you recommend I do now in terms of just getting the system back up and running?  Should I try to grab whatever I can from the old disk through UD and then allow Unraid to format the disk?  Should I downgrade back to 6.12.10?  Thanks!

Edit: Actually never mind.  It can't mount in UD.  Gives me a error.
 

unassigned.devices: Mount of 'sde1' failed: 'mount: /mnt/disks/9MGX9A4J: mount system call failed: Structure needs cleaning.'

 

Edited July 7, 20241 yr by NulledGrayed
add more information

Try to repair the filesystem from the old disk with UD, if it's the same I'm afraid not many options, you can try UFS explorer, the free trial should show if it can recover any data.

Ok thanks.  I'll try that and see if I can recover whatever is left.   Is this just bad luck or is there a root cause for this type of corruption that I should be avoiding?

Unless you are getting multiple filesystem corruption issue I would assume just bad luck, it's not the first time I see xfs_repair failing to repair a filesystem.

Just to resolve this thread. I was ultimately unable to repair the filesystem. I ended up just formatting the disk and creating a new config with it back in the array. I WAS able to recover most of the contents on my old drive with UFS Explorer so thanks for that tip!  Thanks for the help!