alinkognito

Noted. Will do, saves me some time trying to recover it externally Thanks again.

I agree 😓 ce-la-vie I will be creating a new config without the 2 x failed drives I wil try recover the data externally (disk2 will be okay to do that on. disk9...well that will be another story (maybe a data recovery company for that). Thanks for you all for all your help.

Disk2 is showing in UD. Ran the command for ddrescue and getting this: GNU ddrescue 1.23 Press Ctrl-C to interrupt Initial status (read from mapfile) rescued: 2582 MB, tried: 108134 kB, bad-sector: 0 B, bad areas: 0 Current status ipos: 4181 MB, non-trimmed: 1700 MB, current rate: 0 B/s opos: 4181 MB, non-scraped: 0 B, average rate: 0 B/s non-tried: 15996 GB, bad-sector: 0 B, error rate: 1572 kB/s rescued: 2582 MB, bad areas: 0, run time: 16m 54s pct rescued: 0.01%, read errors: 24305, remaining time: n/a time since last successful read: n/a Copying non-tried blocks... Pass 5 (forwards)

Disk2 is mounting in UD Disk9 with ddrescue - terminal was closed. Do I just run the same command again "ddrescue -f /dev/sdd /dev/sdac /boot/ddrescue.log" ?

SIDE THOUGHT I am starting to think there is no hope for these 2 disks. Contemplating biting the bullet and removing disk2 and disk9 and replace them with the new drives and creating a new config (hopefully I can still access the data from all the other disks on the array. Then for the 2 x damaged disks, do some data recovery in windows with UFS Explorer and add those recovered files back to the array? What do you think? Or is there hope yet? Also, I will be getting a further drive so I can set up dual parity. Is it too early for a beer?! lol

Good morning. Hope everyone is well. signed in to the server this morning and terminal is blank. How do I bring up ddrescue? Do I use the same command again? ddrescue -f /dev/sdd /dev/sdac /boot/ddrescue.log Harddrive still making sounnds like it's trying to spin up, smin down, spin up loop.

blimey - it's going to take a long time... do you think it will speed up or is the disk dead? In the interum, i was thinking of taking disk2 though XFS Explorer to extract as much data from disk2 - what do you think?

okay, wish me luck. going to run ddrescue as per your link. Added brand new disk to server Running. root@Kraken:~# ddrescue -f /dev/sdd /dev/sdac /boot/ddrescue.log GNU ddrescue 1.23 Press Ctrl-C to interrupt Initial status (read from mapfile) rescued: 39845 kB, tried: 0 B, bad-sector: 0 B, bad areas: 0 Current status ipos: 66650 kB, non-trimmed: 0 B, current rate: 786 kB/s opos: 66650 kB, non-scraped: 0 B, average rate: 515 kB/s non-tried: 16000 GB, bad-sector: 0 B, error rate: 0 B/s rescued: 66650 kB, bad areas: 0, run time: 52s pct rescued: 0.00%, read errors: 0, remaining time: 380d 12h time since last successful read: 0s Copying non-tried blocks... Pass 1 (forwards)

damn sorry - anxiety kicked in, my bad terminal closed. so to back track... I can see the files in the mounted drive in UD

and as per your guide: stopped array disk2 set to no device Disk2 now showing un UD and mounted Contents of drive can be seen, but no option for a check filesystem in UD Ran xfs_repair -n /dev/sds in terminal Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... lots of . . . . . . . . . . . . . . . still going

cool array running in maintenance mode check filesystem run on Disk2 "Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now."

How shall I proceed? 1) add one of the new disks on the server (let;s call it diskA) 2) ddrescue Disk9 so it recover/clone as much data to the new diskA 2) replace Disk9 with the cloned disk (diskA) 3) then replace Disk2 with another new disk (diskB) then re-build? Apologies if I sound like a laman. Never had this problem before and ddrescue is also new to me. Thanks Al

disk2 is the old disk which was being re-build. stopped at 89% when unraid started saying 1000+ days to complete

just rebooted and it's showed up managed to get the array started in maintenance mode. Shall I still run the check filesystem on disk9 (which is not sounding very well btw)?

kraken-diagnostics-20220812-1807.zip