p.H., I do remember and acknowledge that you had posted the first solution earlier. Thank you for the complete code-lines for the recovery process.
Code: Select all
dd if=/dev/sdc2 of=partition2.img bs=4k
Outputs:
Code: Select all
1286656+0 records in
1286656+0 records out
5270142976 bytes (5.3 GB) copied, 255.102 s, 20.7 MB/s
Outputs:
Code: Select all
e2fsck 1.42.5 (29-Jul-2012)
partition2.img: clean, 29666/321920 files, 731236/1286656 blocks
mounts normally in the /mnt directory. I've checked the files. They can be read.
Code: Select all
dd if=/dev/sdc1 of=partition1.img bs=4k
Outputs:
Code: Select all
2621692+0 records in
2621692+0 records out
10738450432 bytes (11 GB) copied, 538.849 s, 19.9 MB/s
The
won't work, as the partition is a fat32 partition, I remembered late
Outputs:
Code: Select all
dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN
There are differences between boot sector and its backup.
Differences: (offset:original/backup)
65:01/00
1) Copy original to backup
2) Copy backup to original
3) No action
? 3
Reclaimed 39 unused clusters (638976 bytes).
Free cluster summary wrong (133999 vs. really 134038)
1) Correct
2) Don't correct
? 3
Invalid input.
? ^C
I wasn't confident, so I did not damage the filesystem.
Strange, isn't it? The ext4 partition is alright, but unreadable. The fat32 partition has damaged data, but is unreadable!
Since the partition1 has a bad superblock how to recover the maximum possible data from the fat32 partition?
I attempted but changed nothing to the original partition1 in the pendrive:
Code: Select all
dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN
There are differences between boot sector and its backup.
Differences: (offset:original/backup)
65:01/00
1) Copy original to backup
2) Copy backup to original
3) No action
? 3
Reclaimed 39 unused clusters (638976 bytes).
Free cluster summary wrong (133999 vs. really 134038)
1) Correct
2) Don't correct
? 2
Leaving file system unchanged.
/dev/sdc1: 1839 files, 521063/655101 clusters
Please advise on the above step. Will this serve any purpose to recover the data that was there in the pendrive?
I read this post:
[SOLVED] No Boot, corrupt drive, any help welcome
I found specific clues:
Code: Select all
dumpe2fs /dev/sdb1| grep -i superblock
(I don't know about this, so I left this alone)
and
Code: Select all
/dev/sdc1: LABEL="STRONTIUM" UUID="201B-E085" TYPE="vfat"
Code: Select all
/dev/sdc2: UUID="be2a228a-cb20-4e31-8792-316835decbe4" TYPE="ext4"
So there is nothing unknown here!
I searched Google with the string, "e2fsck -b 8193". Finding nothing very informative immediately.
I tried with
and found this:
Found this:
-b superblock
Instead of using the normal superblock, use an alternative
superblock specified by superblock. This option is normally
used when the primary superblock has been corrupted. The loca‐
tion of the backup superblock is dependent on the filesystem's
blocksize. For filesystems with 1k blocksizes, a backup
superblock can be found at block 8193; for filesystems with 2k
blocksizes, at block 16384; and for 4k blocksizes, at block
32768.
Guess this code
won't work, as the partition in question is a vFAT partition!
But I am beyond my circle of awareness here. I will have to read the related materials.
Thank you, once again! FOSS still breathes for self-assured and confident people like you!
Freedom is impossible to conceive.
Books that help:
Dale Carnegie's How To Win Friends And Influence People and Emilie Post's Etiquette In Society, In Business, In Politics, And At Home