PW4 kindle mounting read-only on linux mint system

[dhdurgee]

Originally Posted by j.p.s

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.

[j.p.s]

I'm glad you figured it out.

It seems weird that a corrupted file sysyem can be repaired by deleting a directory and its files.

[dhdurgee]

Originally Posted by j.p.s

I'm glad you figured it out.

It seems weird that a corrupted file sysyem can be repaired by deleting a directory and its files.

I agree, but that appears to be the case. I am unsure how the corruption occurred, but given the location of the damaged sub-directory I suspect something happened while the PW4 was in the process of downloading a book from Amazon that left things corrupted in a way that Amazon did not anticipate.

Perhaps I did a restart of the PW4, which I do when the cover mode stops working and it was at just the absolute wrong time.

Dave

[j.p.s]

Would you mind sharing how you determined which directory was causing the problem?

I think the OP in this thread migght be having the same trouble:
https://www.mobileread.com/forums/sh...96#post4432796

[dhdurgee]

Originally Posted by j.p.s

Would you mind sharing how you determined which directory was causing the problem?

I think the OP in this thread migght be having the same trouble:
https://www.mobileread.com/forums/sh...96#post4432796

Look at the fsck.vfat output from an earlier post:

[root@kindle root]# fsck.vfat /dev/loop/0
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
Clearing dirty flag
Long filename fragment ":6eh:1BL:2bg:2ZI:E7v:9jb:4JF:DgE:B-j:FqH:2ot:EtR:81U" found outside a LFN sequence.
  (Maybe the start bit is missing on the last fragment)
1: Delete fragment
2: Leave it as it is.
3: Set start bit
? 1
/documents/Downloads/Items01/Holy Rebel_ Armed with Truth, Stand Your Ground, and Rebel Against Hell:20Ps Agenda._B0BM1XM884.sdr
  Has a large number of bad entries. (74/142)
Drop directory ? (y/n) y
Reclaimed 63 unused clusters (516096 bytes).
Free cluster summary wrong (598754 vs. really 598817)
1) Correct
2) Don't correct
? 1
Leaving file system unchanged.
/dev/loop/0: 20210 files, 218266/817083 clusters

This pointed me to a sub-directory of documents/Downloads/Items01 as a source of many problems.

As noted I then sftp mounted the PW4 and was able to delete that problematic sub-directory and then fsck.vfat gave clean results.

I am still a bit puzzled by the whole thing, as fsck.vfat offered to delete it for me but did not do so even when told to.

Hopefully this is helpful and never seen again.

Dave

[Quoth]

Originally Posted by j.p.s

I'm glad you figured it out.

It seems weird that a corrupted file sysyem can be repaired by deleting a directory and its files.

Not weird for FAT/DOS type file systems if the corruption isn't in the root.