8 hours ago, Bartok27 said:

Really hoping this is just the bad sectors and it speeds up at some point.

It could, at least, no errors so far.

The remaining time is still bounces between 3000-4200 days remaining.  Still not saying any read errors in ddrescue? However the smart info  now states "Failing now"  in the raw read error rate row. 

ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL   RAW_VALUE
  1 Raw_Read_Error_Rate     PO-R--         012    012         016    NOW  4294942212

and ddrescue is showing

 

GNU ddrescue 1.29.1
Press Ctrl-C to interrupt
     ipos:  174516 MB, non-trimmed:        0 B,   current rate:   43690 B/s
     opos:  174516 MB, non-scraped:        0 B,   average rate:    582 kB/s
non-tried:   11825 GB,  bad-sector:        0 B,     error rate:       0 B/s
  rescued:  174516 MB,   bad areas:          0,       run time:  3d 11h 12m
pct rescued:    1.45%, read errors:          0, remaining time:   3690d 10h
                               time since last successful read:          0s
Copying non-tried blocks... Pass 1 (forwards)    

 

So i assume the drive is done and probably time to give up on ddrescue?

At this point i'm assume the drive is lost but thinking i will pull it and drop it in an external dock and see if i can pull anything off just to see what happens.

 

If we assume the drive is dead and now there is no way to restore the emulated drive 5.  Can we assume drive 5 (8TB) is good.  It only contains media and some backups so i think i can just loose any changes that were made to the emulation.

 

So can i add the remaining 4 drives to an array without loosing the data and the new 14TB drive to the array and rebuild the parity.   If so could you point me to the correct steps to follow so i dont screw up anything else.   

 

 

tower-diagnostics-20250415-1313.zip

 

 

 

Also Just for my information if i have any future issue.  I wanted to confirm i took the correct steps for running ddrescue.

 

I took the array offline (did not restart the server),  set disc3 to no device so that the 12 TB drive showed up under  "Unassigned Disk Device"  and ran the command below (attached the current stats of the running command)

 

root@Tower:~# ddrescue -f /dev/sdc /dev/sdb /boot/ddrescue.log

 

On thing i did notice that was a bit weird is the drive is label dev2  and the other two devices are labelled Dev 1 and Dev 2.  I assume that is just naming and has not impact but looks weird.

 

 

 

12 minutes ago, Bartok27 said:

So i assume the drive is done and probably time to give up on ddrescue?

Probably.

 

14 minutes ago, Bartok27 said:

If we assume the drive is dead and now there is no way to restore the emulated drive 5.  Can we assume drive 5 (8TB) is good.

SMART looks OK at least, so it should be.

 

15 minutes ago, Bartok27 said:

So can i add the remaining 4 drives to an array without loosing the data and the new 14TB drive to the array and rebuild the parity.   If so could you point me to the correct steps to follow so i dont screw up anything else.   

 

You can with a new config (Tools - New config), keep all assignments and assign any missing/new drives, then start array to sync parity.

 

16 minutes ago, Bartok27 said:

I assume that is just naming and has not impact but looks weird.

You can ignore that.

Do i need to clear or format the new 14 TB before assigning it to the disk 3 spot.  Not sure what state it is in after a partial ddrescue restore.

 

 

I really dont want to make anything worse at this point.   can i safely shutdown and restart the server to remove the old 12TB.   Or should i do the new config and parity rebuild first.  Dont know if its better to pull it first or rebuild then shutdown and pull it

 

You can include the new disk in the new config, and format it during or after parity build.

Just wanted to close this off.   Thanks the parity has been rebuilt and everything is working.   Seem the one drive was bad and the rest is ok.   I can still mount the drive on my laptop via a usb dock so will do some more research on if i can recovery any of the data.     But my unraid server is back up and working thanks everyone.