| 1 |
On 03/26 03:04, Bill Kenworthy wrote: |
| 2 |
> On 26/03/17 14:25, tuxic@××××××.de wrote: |
| 3 |
> > On 03/26 05:50, tuxic@××××××.de wrote: |
| 4 |
> > > On 03/26 11:21, Adam Carter wrote: |
| 5 |
> > > > Step 1: dd the contents into an image |
| 6 |
> > > > |
| 7 |
> > > > ddrescue is probably a better option than plain dd. |
| 8 |
> > > > |
| 9 |
> > > > step 2: put the sdcard to one side. |
| 10 |
> > > > > step 3: loopback mount a copy of the image (not the original) |
| 11 |
> > > > > step 4: try recovering the filesystem on the loopback, if it fails ... try |
| 12 |
> > > > > something else on another image copy |
| 13 |
> > > > |
| 14 |
> > > > |
| 15 |
> > > > Yep, once you've got the image mounted loopback, you can run |
| 16 |
> > > > testdisk/photorec depending on how bad it is. |
| 17 |
> > > |
| 18 |
> > > Hi all, |
| 19 |
> > > |
| 20 |
> > > thanks a lot for all help! :) |
| 21 |
> > > |
| 22 |
> > > Currently I am ddresucueing the flashcard to the harddisc. |
| 23 |
> > > Next I will try to mount the sdcard. |
| 24 |
> > > |
| 25 |
> > > What reliable sdcard-reader can one recommend ? |
| 26 |
> > > (...sorry if this sentence sounds harsh...I it by no means meant |
| 27 |
> > > that way...I am no native speaker... :) |
| 28 |
> > > |
| 29 |
> > > Cheers |
| 30 |
> > > Meino |
| 31 |
> > > |
| 32 |
> > > |
| 33 |
> > |
| 34 |
> > Hi, |
| 35 |
> > |
| 36 |
> > Is the assumption correct, that -- if ddrescue could read each |
| 37 |
> > partitions of the sdcard without stuttering, retries and errors -- |
| 38 |
> > the sdcard itsself is ok and "only" the logical structure |
| 39 |
> > (fs, superblock etc) got damaged? |
| 40 |
> > Or do I overlook something? |
| 41 |
> > |
| 42 |
> > (Background: I dont want to put a sdcard into the bin, if |
| 43 |
> > fdisking & reformatting that beast would gives me back an ok |
| 44 |
> > media...) |
| 45 |
> > |
| 46 |
> > Cheers |
| 47 |
> > Meino |
| 48 |
> > |
| 49 |
> > |
| 50 |
> > |
| 51 |
> > |
| 52 |
> |
| 53 |
> The dd gets you the best chance to work on the data before it completely |
| 54 |
> fails. In my experience the sdcard will only get worse ending with total |
| 55 |
> failure - if it hasn't already. |
| 56 |
> |
| 57 |
> If the dd dump comes up rubbish and cant be recovered, the actual sdcard |
| 58 |
> will be worse. You can run "strings" against the image to see if there is |
| 59 |
> any text in there (or even cat the /dev/sdcard node through strings) to see |
| 60 |
> if the bits are still there. |
| 61 |
> |
| 62 |
> I dont know of a cdparanoia type recovery utility for sdcards but I suspect |
| 63 |
> sdcard design means that approach wont work. |
| 64 |
> |
| 65 |
> BillK |
| 66 |
> |
| 67 |
> |
| 68 |
> |
| 69 |
|
| 70 |
Hi Bill, |
| 71 |
|
| 72 |
I got mixed results: There are three partitions on the sdcard from |
| 73 |
which I could fully recover (even mount it directly via loop device) |
| 74 |
the first and the third one. |
| 75 |
|
| 76 |
The second one is screwed up. |
| 77 |
|
| 78 |
Running fsch.ext4 against the image it starts with "bad superblock" |
| 79 |
and suggests two alternatives. |
| 80 |
|
| 81 |
I started fsch.ext4 again while using -b to define the alternate |
| 82 |
superblock and it starts to ask me *zillions of question, which |
| 83 |
I all answered with 'yes' in a first attempt (I have a backup of the |
| 84 |
image...). |
| 85 |
The result was an image, which I could mount again. |
| 86 |
But beside 'lost+found' with some small rests of something which |
| 87 |
may be files in a previous life nothing was there.... |
| 88 |
|
| 89 |
Currently it looks to me, that something has totally messed up the fs |
| 90 |
there. |
| 91 |
|
| 92 |
What do you think? |
| 93 |
|
| 94 |
Cheers |
| 95 |
Meino |
Archives