99.99% recovered is a great result, the other commands are only needed if you want to see if/which files had read errors, it's optional, but if you would like to do it, just copy/paste those commands into a terminal window in order, if the cloned drive is sdc, the 2nd one would be:

 

ddrescue -f --fill=- ~/fill.txt /dev/sdc /boot/ddrescue.log

 

for the last one, you need to mount the drive first, use the UD plugin in read only mode then type the command with the correct path, if you don't know, post the diagnostics after the disk is mounted

 

 

20 minutes ago, JorgeB said:

99.99% recovered is a great result, the other commands are only needed if you want to see if/which files had read errors, it's optional, but if you would like to do it, just copy/paste those commands into a terminal window in order, if the cloned drive is sdc, the 2nd one would be:

 

ddrescue -f --fill=- ~/fill.txt /dev/sdc /boot/ddrescue.log

 

for the last one, you need to mount the drive first, use the UD plugin in read only mode then type the command with the correct path, if you don't know, post the diagnostics after the disk is mounted

 

 

So I don't need to do it? then now I have to mount it all as the array before?
parity
disk1
disk2
disk3 emulated (no spare drive yet)
disk4,
then start new configuration?

Edited April 11, 20251 yr by jolma

Since the emulated disk3 wasn't mounting, the next step would be to clone old disk3, then rebuild parity with original disks 1 and 2, and cloned disks 3 a 4.

 

 

6 minutes ago, JorgeB said:

Since the emulated disk3 wasn't mounting, the next step would be to clone old disk3, then rebuild parity with original disks 1 and 2, and cloned disks 3 a 4.

 

 

Noted, I'll wait for spare drives to arrive and clone disk3..

ddrescue on going but it took more than 10 days... what if I just start the array, it is okay if I lost data from disk 3, what is the next step I would do?
plug in all back

new configuration
parity 12TB
disk1

disk2

disk3? (should i assign my spare disk or not)
disk4 (newly cloned using ddrescue)

start the array?

 

I'll use ddrescue on another machine to try saving data from disk3.

 

Thank you

Edited April 11, 20251 yr by jolma

If you don't mind losing the data from disk3, at least for now, you can do a new config without it and use the new disk4, then  resync parity.

 

If you have another spare you can use it as the new disk3, then copy the data from the clone, if you don't have one, don't assign a disk3 for now, you can add it later, but it will require doing another new config and resyncing parity, you cannot just add to a parity protected array, or it will be cleared (wiped).

 

You could also see if disk3 can now be emulated again with the new disk4, but based on previous results, it should not work, and will need another spare to do it, but can post the instruction if you like to try.

 

 

11 hours ago, JorgeB said:

If you don't mind losing the data from disk3, at least for now, you can do a new config without it and use the new disk4, then  resync parity.

 

If you have another spare you can use it as the new disk3, then copy the data from the clone, if you don't have one, don't assign a disk3 for now, you can add it later, but it will require doing another new config and resyncing parity, you cannot just add to a parity protected array, or it will be cleared (wiped).

 

You could also see if disk3 can now be emulated again with the new disk4, but based on previous results, it should not work, and will need another spare to do it, but can post the instruction if you like to try.

 

 

Thank you, Seeing that ddrescue time fluctuated, I will wait ddrescue first, then post the result after it finished,

after 7 days ddrescue cloning disk3 there is this notification (4TB to 4TB Drive)..
what should I do or what is the command? Thanks

Edited April 18, 20251 yr by jolma

Looks like that disk is really toast, but you can reboot and try again, if you use the same log file, it will resume.

18 minutes ago, JorgeB said:

Looks like that disk is really toast, but you can reboot and try again, if you use the same log file, it will resume.

Thank you, I restarted again and the progress resume...
I upload progress from beginning of the ddrescure, and 2nd pic is ddrescue progress now..
Will updated again, Thank you again
 

Edited April 18, 20251 yr by jolma

That looks much better, almost 98% recovered, and this includes free space.

while doing cloning, the last successfull read time growing longer...

can i just stop the progress and continue to next step or wait for it to finish?

The last few sectors can take a long time, since it has already recovered 99.99%, you may choose to stop there.

41 minutes ago, JorgeB said:

The last few sectors can take a long time, since it has already recovered 99.99%, you may choose to stop there.

Noted, I'll wait, thanks

it took longer than I thougt, so i just stop ddrescue, and new configuration again?
Thanks

IIRC, and you want to add that disk as a new array disk, yes, you need a new config and then resync parity, but it may be worth testing to see if the disk is mounting first using the UD plugin.

Disk3 failed to mount on UD plugin

Post the current diags.

4 minutes ago, JorgeB said:

Post the current diags.

here is the current diagnostics.. just try it after stopping ddrescue (only two HDD connected

tower-diagnostics-20250424-2144.zip

10 minutes ago, jolma said:

Disk3 failed to mount on UD plugin

A little confusing to call it disk3 when it isn't assigned.

 

Are you sure you didn't try to mount the bad disk in UD?

3 minutes ago, trurl said:

A little confusing to call it disk3 when it isn't assigned.

 

Are you sure you didn't try to mount the bad disk in UD?

sorry, I try mounting sdb (dev1 ) which is the new drive, the bad disk is WD EARX (dev 2), Thank you

Edited April 24, 20251 yr by jolma

OK, I see. That bad disk is still attached and cluttering up the syslog.

 

You will have to check filesystem on Dev 1. Not unexpected.

Diags are spammed with what, I assume, are the old disk errors, disconnect that disk, reboot, try to mount with UD, post new diags.

8 minutes ago, JorgeB said:

Diags are spammed with what, I assume, are the old disk errors, disconnect that disk, reboot, try to mount with UD, post new diags.

Done, try mounting and still fail, here is the new diagnostic, thanks

tower-diagnostics-20250424-2207.zip

13 minutes ago, trurl said:

You will have to check filesystem on Dev 1. Not unexpected.