In2Photos

I installed the UD plugin and tried to mount the drive. On my console screen I get the following.

The filesystem check ran for hours and never found anything so I'll try UD.

No, it was from the webgui using maintenance mode.

I haven't done it. I'm hoping for others with more knowledge to lead me in the right direction. What do you suggest?

No luck on the file check. Do I try to run it again and repair it?

ddrescue is finished. here were the results. Filesystem check is still going, but here is what it looks like so far:

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?

When it finishes should I try to mount it? Or run a file check in maintenance mode first?

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?

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.

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).

Correct. So try again with the drive as reiserfs?

Same results as earlier today. Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval -1 fatal error -- Input/output error

OK, so that's not the reason, but I still can't run the check. The option isn't there for disk 1.

I can't run the check on disk 1 since it is not mountable.

I have not run filesystem check but I can. Are we absolutely sure the parity disk is bad?

Here you go. And a screenshot. mytower-diagnostics-20220617-1654.zip

No I don't believe I do. Here is where the system sits right now. I'm basically where I was this morning before checking for updates.

I have already installed a fresh OS on the flash drive and verified that it boots. I've done basic configuration of things like static IP. Just waiting for the new drives to arrive. Should I go into maintenance mode and check the disks?

The server had been working fine until today since 2015 when I did the conversion.

Well how would I know if they truly got converted other than unRAID reporting them as XFS?

After reading about ddrescue I see that what I planned to do will not be best since I need to clone the disk before it goes into the array. Instead I guess I need to do the following: Install 1 new drive in place of the parity drive Clone the 1.5 TB drive to this new drive. Install the other new drive and assign as parity and the other as a data drive Rebuild the array and parity Remove the 500GB drive using the method described here (clear drive then remove drive): https://wiki.unraid.net/Shrink_array

Got it. I also think I will remove the 500 GB drive from the array as I don't need it anymore with the replacement drive (1.5TB bad drive and 500 GB good drive replaced by new 3TB drive). I also only have 4 SATA ports on this old machine so in order to try and recover the files from the 1.5TB drive I need a free port. Here's the way I'm thinking of doing this. Install 2 new drives and the 2 good drives (3-3TB and 1-500GB) Assign 1 new drive as parity and the other as a data drive Rebuild the array and parity Remove the 500GB drive using the method described here (clear drive then remove drive): https://wiki.unraid.net/Shrink_array Install the 1.5TB bad drive and try to recover files using ddrescue Remove the 1.5TB drive

OK. Thanks for the help. I'll do some reading.

Trying from the command line and it says "command not found". I'm logged in as root. Is this not correct? Wow this has gone from bad to worse quickly. XFS is the file system. See screenshot from earlier.