alinkognito Posted August 12, 2022 Author Share Posted August 12, 2022 1 minute ago, JorgeB said: See if you can recover data form disk9 with ddrescue, then you'd do a new config with all the disks (including old disk2) and the clone from disk9, if successful. 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) Quote Link to comment
alinkognito Posted August 12, 2022 Author Share Posted August 12, 2022 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? Quote Link to comment
JorgeB Posted August 13, 2022 Share Posted August 13, 2022 See if it advances, what's the current status? Is the disk still doing the noise? Quote Link to comment
JorgeB Posted August 13, 2022 Share Posted August 13, 2022 If disk2 is mounting with UD you don't need XFS explorer, whatever that is. Quote Link to comment
itimpi Posted August 13, 2022 Share Posted August 13, 2022 1 hour ago, JorgeB said: XFS explorer, whatever that is Windows based disk recovery software. Quote Link to comment
alinkognito Posted August 13, 2022 Author Share Posted August 13, 2022 (edited) 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. Edited August 13, 2022 by alinkognito Quote Link to comment
alinkognito Posted August 13, 2022 Author Share Posted August 13, 2022 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 Quote Link to comment
JorgeB Posted August 13, 2022 Share Posted August 13, 2022 25 minutes ago, alinkognito said: I am starting to think there is no hope for these 2 disks. Wasn't disk2 mounting with UD? ddrescue is your best bet for disk9, if that doesn't work UFS explorer won't also, UFS explorer might help on the cloned disk if there are fs issues. Quote Link to comment
alinkognito Posted August 13, 2022 Author Share Posted August 13, 2022 1 minute ago, JorgeB said: Wasn't disk2 mounting with UD? ddrescue is your best bet for disk9, if that doesn't work UFS explorer won't also, UFS explorer might help on the cloned disk if there are fs issues. 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" ? Quote Link to comment
JorgeB Posted August 13, 2022 Share Posted August 13, 2022 10 minutes ago, alinkognito said: Disk2 is mounting in UD So why are you saiyn it's lost? Like mentioned just do a new config with it and the remaining disks. 10 minutes ago, alinkognito said: terminal was closed. Do I just run the same command again "ddrescue -f /dev/sdd /dev/sdac /boot/ddrescue.log" ? You can, it will resume from where it was. Quote Link to comment
alinkognito Posted August 13, 2022 Author Share Posted August 13, 2022 6 minutes ago, JorgeB said: So why are you saiyn it's lost? Like mentioned just do a new config with it and the remaining disks. You can, it will resume from where it was. 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) Quote Link to comment
alinkognito Posted August 14, 2022 Author Share Posted August 14, 2022 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. Quote Link to comment
JorgeB Posted August 14, 2022 Share Posted August 14, 2022 28 minutes ago, alinkognito said: I will be creating a new config without the 2 x failed drives Again, you can use old disk2 in the new array. Quote Link to comment
alinkognito Posted August 14, 2022 Author Share Posted August 14, 2022 Noted. Will do, saves me some time trying to recover it externally Thanks again. Quote Link to comment
Recommended Posts
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.