Timeline for Recover a reiserfs hard disk
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2020 at 12:04 | history | edited | CommunityBot | Commonmark migration | |
| Apr 18, 2019 at 12:10 | history | edited | Rui F Ribeiro | CC BY-SA 4.0 | deleted 17 characters in body |
| Jun 13, 2012 at 20:42 | vote | accept | pjv | ||
| Jun 10, 2012 at 17:10 | comment | added | killermist | If an offset seems "more right", maybe try that first. | |
| Jun 10, 2012 at 17:03 | comment | added | killermist | After imaging the drive, I'd try the default methods, including some of the tricks in the links (rewriting the drive from the image if anything gets too damaged in an attempt), and then get more creative if necessary until you get a result. It could be that one of the superblocks got damaged, and that is why some things detect properly and others don't. I'd say do a little trial and error (restoring from the image if anything appears to do catastrophic damage, and go again) | |
| Jun 10, 2012 at 16:55 | comment | added | pjv | Yeah, I've been through it myself a few times over the last decade. But what with the offset? Should I just go and do a --rebuild-sb and --rebuild-tree without setting that straight? Or does it have no meaning? (Again, can't take an image and rather lose my data then.) | |
| Jun 10, 2012 at 16:33 | history | answered | killermist | CC BY-SA 3.0 |