slobberybeast Posted March 21, 2017 Share Posted March 21, 2017 Hello all, I am having an issue with a disk that is unmountable. Smart check comes back okay so I ran an xfs_repair -n on it and this is what I get - See Attached file please Then I ran a check -L thinking it would fix it like it did a few versions back (Was unmountable a few versions back and the repair -L fixed it right up and I was able to mount it again) and I now get this - See Attached file please Not sure where else to go without mucking it up more as it seems from reading about this is way over my head. Any help is appreciated. xfs_repair -L.txt xfs_repair -n.txt Quote Link to comment
RobJ Posted March 21, 2017 Share Posted March 21, 2017 Please see Need help? Read me first!, and attach the diagnostics zip. Quote Link to comment
slobberybeast Posted March 21, 2017 Author Share Posted March 21, 2017 40 minutes ago, RobJ said: Please see Need help? Read me first!, and attach the diagnostics zip. Thanks for the link! Here you go, as well as a smart Status on that drive. diagnostics-20170320-2006.zip smart-20170320-2007.zip Quote Link to comment
JorgeB Posted March 21, 2017 Share Posted March 21, 2017 (edited) That looks like a very corrupt file system, try with -v to see if any more info is displayed: xfs_repair -v /dev/mdX If it needs -L again use: xfs_repair -vL /dev/mdX Edited March 21, 2017 by johnnie.black Quote Link to comment
slobberybeast Posted March 21, 2017 Author Share Posted March 21, 2017 10 hours ago, johnnie.black said: That looks like a very corrupt file system, try with -v to see if any more info is displayed: xfs_repair -v /dev/mdX If it needs -L again use: xfs_repair -vL /dev/mdX Here are the outputs of these two commands xfs_repair -v.txt xfs_repair -vL.txt Quote Link to comment
slobberybeast Posted March 21, 2017 Author Share Posted March 21, 2017 Would wiping the disk and rebuilding help? I have a valid parity as of 19 days ago or would the data be corrupted there too? Quote Link to comment
trurl Posted March 21, 2017 Share Posted March 21, 2017 10 minutes ago, slobberybeast said: Would wiping the disk and rebuilding help? I have a valid parity as of 19 days ago or would the data be corrupted there too? No, absolutely not. Parity cannot fix filesystem corruption, and wiping the disk will just make parity think you have a wiped disk. Quote Link to comment
JorgeB Posted March 21, 2017 Share Posted March 21, 2017 (edited) It's the first time I see xfs_repair failing to repair a filesystem, but like I said before, it looks very corrupt. Unless someone else has a different suggestion your only options are waiting for a new xfs_repair release and hope it will work or use xfs_metadump and send it to a xfs maintainer, see here. Also, and unless you're using ECC, I would run memtest for a few hours to make sure your RAM is OK. Edited March 21, 2017 by johnnie.black Quote Link to comment
slobberybeast Posted March 21, 2017 Author Share Posted March 21, 2017 Well dang, so It looks like I am out of options for now. Unless someone else has any ideas? I will run Memtest for a bit to see if there are RAM issues. I have been meaning to wipe and rebuild clean for awhile now I just don't have the time right now. I am not super worried about the data loss as I have backups in place that are known good. Quote Link to comment
slobberybeast Posted March 21, 2017 Author Share Posted March 21, 2017 Memtest is a going... Quote Link to comment
slobberybeast Posted March 21, 2017 Author Share Posted March 21, 2017 First pass came up clean with no errors. Letting it run for another pass. I'm thinking my drive is screwed... Quote Link to comment
RobJ Posted March 22, 2017 Share Posted March 22, 2017 The reason I asked for diagnostics was there were so many things wrong with the file system structures, that I was afraid that either he had tried to repair the drive instead of the partition (sde instead of sde1 or md4), or it wasn't an XFS drive, but a drive with a similar file system, enough to find file system pieces and try to construct an XFS file system. I'm afraid the damage is so severe that it's too much for the current xfs_repair, and it's crashing. I really hope you have a backup for the data. I'm a bit intrigued by your statement of a 19 day old parity copy, but didn't understand what you mean by that. Is that a *separate* disk that you can put back in? And was Disk 4 fine at that time? What exactly do you have from 19 days ago? Quote Link to comment
RobJ Posted March 22, 2017 Share Posted March 22, 2017 Also, you have IDE emulation turned on for your onboard SATA drives. When you next boot, go into the BIOS settings and look for the SATA mode, and change it to a native SATA mode, preferably AHCI if available, anything but IDE emulation mode. It should be slightly faster, and a little safer. You have Disk 4 and Disk 5 on the same IDE channel, at limited speed. Quote Link to comment
slobberybeast Posted March 22, 2017 Author Share Posted March 22, 2017 4 hours ago, RobJ said: The reason I asked for diagnostics was there were so many things wrong with the file system structures, that I was afraid that either he had tried to repair the drive instead of the partition (sde instead of sde1 or md4), or it wasn't an XFS drive, but a drive with a similar file system, enough to find file system pieces and try to construct an XFS file system. I'm afraid the damage is so severe that it's too much for the current xfs_repair, and it's crashing. I really hope you have a backup for the data. I'm a bit intrigued by your statement of a 19 day old parity copy, but didn't understand what you mean by that. Is that a *separate* disk that you can put back in? And was Disk 4 fine at that time? What exactly do you have from 19 days ago? No worries, I can't expect anyone to help me fix my broken shit without giving them as much info as I possibly can. :-) As far as the data goes I am at no loss as I have a backup on another system (QNAP running a raid 5, as well as a back up of that to a couple of 8TB drives not in a raid). Haha yea I'm a bit paranoid... I have a parity drive in the unRaid that says its 19 days old. Am I understanding the parity wrong? I thought it was there so if a drive died it could re-build it, unless it has the file system corruption is on it as well. Should I be running the parity check more often? At any rate i will stick it out and try and fix this, otherwise I will start from scratch and rebuild - although I really don't want to do that. I have backups of my system configs I need just in case but transferring that amount of data takes so much time. Memtest did 2 passes with no errors so I'm going to say it is the file system on Drive 4. Here is a screen from the Memtest that has been running most of the day - Here is a screen from unRaid that shows the Parity was last checked 20 days ago with no errors. As far as I know everything was up and running then. I did an update a few days ago and that is when I got the Un-mountable Disk. I tried to run a check on that disk in maintenance mode and then I ran one with -L and here I am now. I really do appreciate all the help, love the community here! Quote Link to comment
slobberybeast Posted March 22, 2017 Author Share Posted March 22, 2017 3 hours ago, RobJ said: Also, you have IDE emulation turned on for your onboard SATA drives. When you next boot, go into the BIOS settings and look for the SATA mode, and change it to a native SATA mode, preferably AHCI if available, anything but IDE emulation mode. It should be slightly faster, and a little safer. You have Disk 4 and Disk 5 on the same IDE channel, at limited speed. Ah yes, I must have missed that a few weeks ago when resetting my BIOS settings. My rig ''somehow'' lost all its BIOS settings (Battery is good). I think they got reset when I ''maybe'' bumped the clear CMOS button replacing the parity drive a few weeks back. Thanks for catching that. They are set to AHCI now. :-) Quote Link to comment
trurl Posted March 22, 2017 Share Posted March 22, 2017 7 hours ago, slobberybeast said: As far as the data goes I am at no loss as I have a backup on another system (QNAP running a raid 5, as well as a back up of that to a couple of 8TB drives not in a raid). Haha yea I'm a bit paranoid... You might be surprised at the number of people who think unRAID parity means they don't need a backup. Quote Link to comment
slobberybeast Posted March 22, 2017 Author Share Posted March 22, 2017 4 minutes ago, trurl said: You might be surprised at the number of people who think unRAID parity means they don't need a backup. That is like saying Raid 5 is a backup..... never a good idea. :-) Quote Link to comment
trurl Posted March 22, 2017 Share Posted March 22, 2017 3 minutes ago, slobberybeast said: That is like saying Raid 5 is a backup..... never a good idea. :-) Agreed, even though unRAID is probably more robust than RAID5, since each disk is independent. Quote Link to comment
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.