View Single Post
Old 06-08-2024, 04:21 PM   #14
dhdurgee
Guru
dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.
 
Posts: 916
Karma: 3000002
Join Date: Jun 2010
Device: K3W, PW4
Quote:
Originally Posted by j.p.s View Post
Did you run fsck on the kindle or your PC? Running it on a mounted partition is a bad idea anytime, and it is my understanding that, at least in the case of a kindle, what shows up over usbfs is not the real partition.
Code:
[root@kindle root]# grep mmc /etc/fstab
/dev/mmcblk0p1    /             ext3   suid,exec,auto,nouser,async,rw,noatime,nodiratime 0      1
/dev/mmcblk1p1    /mnt/base-mmc vfat   defaults,noatime,nodiratime,utf8,noexec,shortname=mixed              0      0
fsp#/mnt/base-mmc /mnt/mmc      fuse   rw,max_write=65536,max_readahead=65536,noatime,exec,nosuid,nodev,nonempty     0      0
[root@kindle root]# grep mnt/us /etc/fstab
fsp#/mnt/base-us  /mnt/us       fuse   allow_other,umask=0,uid=0,gid=0,rw,max_write=65536,max_readahead=65536,noatime,noexec,nosuid,nodev,nonempty     0      0
/dev/mmcblk1p1 is the OS partition
/dev/mmcblk1p1 is the user store partition

Note the presence of the 2 fuse file systems.

If /dev/mmcblk1p1 is corrupted I guess you could disable usbfs by enabling usbnetworking and ssh in and unmount /mnt/us and /mnt/mmc and /mnt/base-mmc
then run fsck on /dev/mmcblk1p1

I have no idea how to run fsck on a fuse system.
I had looked through the mounts on the PW4 and found:

Code:
[root@kindle root]# mount | grep vfat
/dev/loop/0 on /mnt/base-us type vfat (rw,noexec,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
[root@kindle root]#
Given this I had been running my fsck.vfat on /dev/loop/o with the results you see above.

I get the following with the commands you used:

Code:
[root@kindle root]# grep mmc /etc/fstab
/dev/mmcblk0p1    /             ext3   suid,exec,auto,nouser,async,rw,noatime,nodiratime 0      1
/dev/mmcblk1p1    /mnt/base-mmc vfat   defaults,noatime,nodiratime,utf8,noexec,shortname=mixed              0      0
fsp#/mnt/base-mmc /mnt/mmc      fuse   rw,max_write=65536,max_readahead=65536,noatime,exec,nosuid,nodev,nonempty     0      0
[root@kindle root]# grep mnt/us /etc/fstab
fsp#/mnt/base-us  /mnt/us       fuse   allow_other,umask=0,uid=0,gid=0,rw,max_write=65536,max_readahead=65536,noatime,noexec,nosuid,nodev,nonempty,hard_remove     0      0
This appears to be identical, unless I am missing something.

I am using ssh via WiFi, so would it be sufficient to umount the three and then run the fsck.vfat?

Thank you for any further pointers you may have.

Dave
dhdurgee is offline   Reply With Quote