[Nook Touch Android Development] LastSilmaril:
How do we actually *read* the images we just created?

Hi all,

So I've made a few backup images of my nook and want to be able to access the files on there without problems. I'm not the most knowledgeable Linux guy but have a Kubuntu VirtualBox image lying around for when I decide to compile Rockbox and such. I've also got Cygwin installed, but never expect it to do anything correctly, really. I haven't really come across any Windows tools that'll do the trick for me, so I want to know what I'm doing wrong with my parameters for the 'mount' command in Linux. What I really want right now is to get into the the system partition (#5).

Now I don't really know how to use mount beyond a little bit of googling, so I likely missed something here, but anyway, this is what I did:

I ran

fdisk -l nook_1.0.0_backup.img

and got this:

Disk nook_1.0.0_backup.img: 1958 MB, 1958739968 bytes

128 heads, 32 sectors/track, 934 cylinders, total 3825664 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

Device Boot Start End Blocks Id System

nook_1.0.0_backup.img1 * 32 155647 77808 c W95 FAT32 (LBA)

nook_1.0.0_backup.img2 155648 188415 16384 c W95 FAT32 (LBA)

nook_1.0.0_backup.img3 188416 577535 194560 83 Linux

nook_1.0.0_backup.img4 577536 3792895 1607680 5 Extended

nook_1.0.0_backup.img5 577568 1167359 294896 83 Linux

nook_1.0.0_backup.img6 1167392 1658879 245744 c W95 FAT32 (LBA)

nook_1.0.0_backup.img7 1658912 2150399 245744 83 Linux

nook_1.0.0_backup.img8 2150432 3792895 821232 83 Linux
​

I multiplied 577568 by 512 to get an offset of 295698432, and knew that the system partition uses ext2 by running 'mount' in the nook's shell, so then I ran:

mount -o loop,offset=295698432 -t ext2 nook_1.0.0_backup.img /media/n2e

and keep getting this error message:

wrong fs type, bad option, bad superblock on /dev/loop0,

missing codepage or helper program, or other error

In some cases, useful info is found in syslog - try

dmesg | tail or so​

trying dmesg | tail yielded this gibberish:

[ 6690.080964] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2

[ 6690.081015] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2

[ 6690.081081] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2

[ 6690.081131] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2

[ 6690.081181] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2

[ 6690.081231] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2

[ 6690.081286] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2

[ 6690.081337] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2

[ 6690.081387] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2

[ 6690.081437] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2​

I also tried using dd to extract that partition (which I also did correctly if you go by file size, which is identical to the file size listed when I extract it via 7-zip in Windows) and then tried to mount that, but got the same message. I'm thinking this is all a simple syntactical error...any ideas? roustabout? ros87?

---------- Post added at 07:26 PM ---------- Previous post was at 07:05 PM ----------

Wait, so this piece of software does the trick in Windows:

http://www.diskinternals.com/linux-reader/

But I'd still like to know how to mount correctly.