View Single Post
Old 06-08-2024, 04:56 PM   #16
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: 911
Karma: 3000002
Join Date: Jun 2010
Device: K3W, PW4
Quote:
Originally Posted by j.p.s View Post
I don't know. I have no experience with running fsck on loop devices or fuse file systems, and have no idea what complicated scheme is used to map the /dev/mmcblk1p1 device eventually to /mnt/us
In that case I guess I can only try it and see. Should it suffice to issue a "mount -a" once the fsck.vfat completes? If not, I guess I can issue a reboot.

Dave

PS:

Looks like I won't have to try this. I noticed that all the problems reported were in a single sub-directory. I sfpt mounted the device and found that I was able to remove the problem sub-directory. After doing so fsck.vfat reports no problems and Calibre now mounts the PW4 properly. So the problem appears solved.

Last edited by dhdurgee; 06-08-2024 at 05:04 PM.
dhdurgee is offline   Reply With Quote