Quote:
Originally Posted by NiLuJe
Huh, that's what I was afraid of... Seems like something is wonky with the whole userstore mount thing (Which is kind of complicated, and I'm honestly not sure I perfectly understand why it's done that way [If I remember correctly, there's like the original FAT32 partition, then a loop device, and then another crazy custom amazon fuse module on top... o_O]). There's a chance it could be recovered from with a SSH/Serial access, but your easiest bet might be a simple RMA if it's still under warranty.
Just in case, try another restart/check if the log file managed to pop in the documents folder.
What exactly did you do in the first place/have tried to do since?
|
The startup script comments mention an 8192 userstore offset, so I did this:
mount -o loop,noatime,ro,offset=8192 /dev/mmcblk0p4 /mnt/mmc
Hey, what do you know? loop mounting a
device with offset works! My k3 USB drive is mounted right there in /mnt/mmc on my k3 right now. Of course you can change to "ro" option to "rw" if you want to write to it.
The actual FAT32 partition has 8192 bytes of OTHER data in front of it in /dev/mmcblk0p4 on the k3. And you can treat a block device as an image file and loop mount it with offset. This could be useful...
And remember to add -d to the umount when you unmount any loop device, or you can use up all your loop devices and need to reboot to loop mount anything again. Some of the kindles to no free loop devices without supplying the -d option to umount (even if they are listed in /etc/mtab). Yet another kindle bug...
umount -d /mnt/mmc
