Timeline for DDRescue - Did I do the wrong command which is causing it to take longer then expected
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Apr 10, 2017 at 7:08 | history | suggested | Chindraba |
Tag cleanup
|
|
| Apr 10, 2017 at 6:25 | review | Suggested edits | |||
| S Apr 10, 2017 at 7:08 | |||||
| Aug 7, 2014 at 17:21 | audit | Suggested edits | |||
| Aug 7, 2014 at 17:23 | |||||
| Jul 22, 2014 at 19:46 | answer | added | Frank Thomas | timeline score: 4 | |
| Jul 22, 2014 at 18:36 | comment | added | Jason | All I noticed was Windows had a problem mounting to show files and even on Linux I would get long delays. Nothing mechanical sounding like clicking. Might just be bad firmware as I remember the drive being pretty brand new. shrug I've done drives before with actual mechanical issues and they cloned faster. | |
| Jul 22, 2014 at 18:15 | comment | added | Frank Thomas | ddrescue takes DAYS for seriously damaged drives. Did you look at the smart stats on the drive before attempting to recover the data? The exact type of failure may indicate a shorter\longer recovery time. | |
| Jul 22, 2014 at 17:36 | history | asked | Jason | CC BY-SA 3.0 |