June 17, 20224 yr Author 1 minute ago, trurl said: That is with xfs I assume. That might indicate that the disk isn't xfs. Correct. So try again with the drive as reiserfs? Edited June 17, 20224 yr by In2Photos
June 17, 20224 yr Community Expert 6 hours ago, JorgeB said: cloning disk1 to a new disk with ddrescue to try and recover as much data as possible Maybe this is the way forward. At least we would have a good disk to try repair on.
June 17, 20224 yr Author And changing it to reiserfs I got this: reiserfsck 3.6.27 Will read-only check consistency of the filesystem on /dev/md1 Will put log info to 'stdout' The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (2): (Input/output error).
June 18, 20224 yr Author Well, only 1 of the 2 drives showed up tonight. I'm running ddrescue now, cloning the 1.5TB drive. This might take a while. It's been running for almost 2 hours and is only 8.5% complete on Pass 1.
June 18, 20224 yr Community Expert 9 hours ago, trurl said: -- Input/output error This indicates that xfs_repair is aborting due to a disk read error, xfs_repair won't work in a failing disk, you can clone the disk first with ddrescue then run xfs_repair.
June 18, 20224 yr Author Woke up this morning and expected it to be much further away from completion. Also expected a lot more errors. I realize it's only pass 1 but 0 bad areas and only 3 read errors? Edited June 18, 20224 yr by In2Photos spelling
June 18, 20224 yr Author When it finishes should I try to mount it? Or run a file check in maintenance mode first?
June 18, 20224 yr Author The replacement is showing as a new disk. Should I remove the bad disk from the array before starting maintenance mode and checking the filesystem on the new disk?
June 18, 20224 yr Community Expert While there's no parity it's not a problem, if you then need to remove a disk just do a new config, note that after parity is assigned any new data disk will be cleared (erased) first.
June 18, 20224 yr Author ddrescue is finished. here were the results. Filesystem check is still going, but here is what it looks like so far:
June 19, 20224 yr Author 51 minutes ago, JorgeB said: Please post the full command did you used to run xfs_repair. I haven't done it. I'm hoping for others with more knowledge to lead me in the right direction. What do you suggest?
June 19, 20224 yr Community Expert Sorry, that was a stupid question, you're not using the command line, is that filesystem check screenshot from UD?
June 19, 20224 yr Author 15 minutes ago, JorgeB said: Sorry, that was a stupid question, you're not using the command line, is that filesystem check screenshot from UD? No, it was from the webgui using maintenance mode.
June 19, 20224 yr Community Expert Cloned disk won't mount in the array because it's larger than the original, but a filesystem check will still work, let it finish to see if it can find a backup superblock, strange if all are damaged, failing that unassign the disk and try to mount it with UD to see what fs error you get.
June 19, 20224 yr Author 30 minutes ago, JorgeB said: Cloned disk won't mount in the array because it's larger than the original, but a filesystem check will still work, let it finish to see if it can find a backup superblock, strange if all are damaged, failing that unassign the disk and try to mount it with UD to see what fs error you get. The filesystem check ran for hours and never found anything so I'll try UD.
June 19, 20224 yr Author I installed the UD plugin and tried to mount the drive. On my console screen I get the following.
June 19, 20224 yr Community Expert Result will likely be the same but try checking filesystem again, with UD, click on the highlighted area:
June 20, 20224 yr Community Expert That's better, at least there's a fix option, click on "run with correct flag"
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.