go69cars Posted June 19, 2018 Share Posted June 19, 2018 About 2 days ago I was watching something on Plex when Plex suddenly stopped working.  This has happened before so I did a reboot.  UnRaid didn't come back online so I left it until the next morning. I didn't have a monitor hooked up, but I couldn't log into UnRaid from a remote computer so I did a hard reset.  I then rebooted and UnRaid came back online. The first time it came back online there were a few discs it couldn't mount so I did a shutdown through UnRaid and restarted.  Now it comes back with only disc 1 unmountable and one of my parity drives.   I had a similar situation happen about 2 months ago.  At that time it turned out a couple discs were losing communication so I checked all my connections and it seemed to fix the issue.  I tried checking all my connections again, but haven't had any luck with fixing it.   I tried to run xfs repair on Disk 1 but it didn't fix the issue  My system has a 5 into 3 disc cage and has 2 LSI SAS 8 port cards. I suspect one of these 3 may be causing issues, but that's just a hunch.  I'd like to find out what the cause of these hiccups is and also how to recover from this one.  tower-diagnostics-20180619-1024.zip Link to comment
JorgeB Posted June 19, 2018 Share Posted June 19, 2018 Several ATA errors on ATA3/4, these should be the onboard SATA ports 3 and 4, check connections. Â As for disk1, run xfs_repair without -n and post the output if it's not fixed. Link to comment
go69cars Posted June 19, 2018 Author Share Posted June 19, 2018 I ran xfs again with this command  xfs_repair -v /dev/md1  That's the one I ran before as well  The output is so long I can't fit it all in here.  Here's the end of it.   bad hash table for directory inode 3395978616 (no data entry): rebuilding rebuilding directory inode 3395978616 entry ".." in directory inode 3395979534 points to non-existent inode 809910087, marking entry to be junked bad hash table for directory inode 3395979534 (no data entry): rebuilding rebuilding directory inode 3395979534 entry ".." in directory inode 3395979551 points to non-existent inode 809910087, marking entry to be junked bad hash table for directory inode 3395979551 (no data entry): rebuilding rebuilding directory inode 3395979551 entry ".." in directory inode 3395983625 points to non-existent inode 809914261, marking entry to be junked bad hash table for directory inode 3395983625 (no data entry): rebuilding rebuilding directory inode 3395983625 entry ".." in directory inode 3395983642 points to non-existent inode 809914261, marking entry to be junked bad hash table for directory inode 3395983642 (no data entry): rebuilding rebuilding directory inode 3395983642 entry ".." in directory inode 3395983659 points to non-existent inode 809920105, marking entry to be junked bad hash table for directory inode 3395983659 (no data entry): rebuilding rebuilding directory inode 3395983659 bad hash table for directory inode 3395983678 (no data entry): rebuilding rebuilding directory inode 3395983678 bad hash table for directory inode 3395985200 (no data entry): rebuilding rebuilding directory inode 3395985200 bad hash table for directory inode 3395985201 (no data entry): rebuilding rebuilding directory inode 3395985201 entry ".." in directory inode 3410664270 points to non-existent inode 809924147, marking entry to be junked bad hash table for directory inode 3410664270 (no data entry): rebuilding rebuilding directory inode 3410664270     - agno = 2 entry ".." in directory inode 5027846943 points to non-existent inode 804633806, marking entry to be junked bad hash table for directory inode 5027846943 (no data entry): rebuilding rebuilding directory inode 5027846943 entry ".." in directory inode 5027846965 points to non-existent inode 804633806, marking entry to be junked bad hash table for directory inode 5027846965 (no data entry): rebuilding rebuilding directory inode 5027846965 bad hash table for directory inode 5027847023 (no data entry): rebuilding rebuilding directory inode 5027847023 bad hash table for directory inode 5027847690 (no data entry): rebuilding rebuilding directory inode 5027847690 xfs_repair: phase6.c:1308: longform_dir2_rebuild: Assertion `done' failed. Aborted Link to comment
JorgeB Posted June 19, 2018 Share Posted June 19, 2018 Looks like the filesystem is beyond repair, you'll need to format and restore from backups or alternatively ask the help of a xfs maintainer on the xfs mailing list. Link to comment
go69cars Posted June 19, 2018 Author Share Posted June 19, 2018 Can't I rebuild from the Parity drive?  I can't seem to find the process for doing that  Link to comment
JorgeB Posted June 19, 2018 Share Posted June 19, 2018 3 hours ago, go69cars said: Can't I rebuild from the Parity drive? You can, but parity can't fix filesystem corruption. Â You also need to fix the underlying problem: 6 hours ago, go69cars said: This has happened before so I did a reboot. Â 6 hours ago, go69cars said: The first time it came back online there were a few discs it couldn't mount so I did a shutdown through UnRaid and restarted. This isn't normal, possibly caused by the ATA errors like those on ATA3 and 4, they could be happening on more disks other times, and if they are they are likely the cause of your problems. Link to comment
go69cars Posted June 20, 2018 Author Share Posted June 20, 2018 Thank you.   Once I figure out the underlying problem can you point me to a tutorial on how to recover the disc using the Parity drive.  Also one of the parity drives is offline as well. It doesn't say why though.  Is that because of this issue or is there yet another issue   Link to comment
itimpi Posted June 20, 2018 Share Posted June 20, 2018 3 hours ago, go69cars said: Thank you.   Once I figure out the underlying problem can you point me to a tutorial on how to recover the disc using the Parity drive.  Also one of the parity drives is offline as well. It doesn't say why though.  Is that because of this issue or is there yet another issue   If you have file system corruption then you can not recover the disk using the parity drive.  In such a scenario rebuilding the drive will just rebuild the corrupt file system. Link to comment
go69cars Posted June 20, 2018 Author Share Posted June 20, 2018 OK Thank you  I'm fairly new to linux in general and have only been building my own computers for a couple years.  Can someone point me in the direction of a good resource that can help me track down the cause of these ATA errors.  I'm assuming cables and MB would be possible culprits.  When I had issues before they were in discs that were in a 5 into 3 enclosure. I don't think SATA 3 and 4 are hooked up to that, but I'll be sure to rule that out.  Link to comment
JorgeB Posted June 20, 2018 Share Posted June 20, 2018 Start by replacing the cables, if the issues persist it might be a bad board, PSU, etc. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.