Quote:
Originally Posted by frostschutz
I think I'll leave it at that - sorry I couldn't come up with a better method - looking forward to what Kobo's fix will look like.
|
I tried your fatpatch.exe but it couldn't find the Kobo filesystem. I then tried v4 but it does same as before, ramains on black clown and doesn't fix the problem.
I then went back through your posts, particularly post #107. I then mounted my N905B on Linux and ran fsck.fat. I found my version of fsck.fat is v3.0.27 while yours is 4.0, which probably explains why I had to do things slightly differnently. I found the dirty bit was set and I had to use fsck.fat -a (automatically repair the filesystem) to fix that, then I had to use fsck.fat -r (interactively repair the filesystem) to run it interactively before it would allow me to copy the backup boot sector to the original and perform the change. The result was:
Quote:
mypc:/home/grahamc# fsck.fat -a /dev/sdc
fsck.fat 3.0.27 (2014-11-12)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automatically removing dirty bit.
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset: original/backup)
494:30/ff, 495:3d/00, 496:61/00, 497:8a/00, 498:f0/00, 499:b2/00, 500:6f/00
, 501:15/00, 502:5b/00, 503:35/00, 504:fd/00, 505:8c/00, 506:07/00
, 507:3d/00, 508:6e/00, 509:ea/00
Not automatically fixing this.
Performing changes.
/dev/sdc: 2623 files, 107816/348630 clusters
mypc:/home/grahamc# fsck.fat -r /dev/sdc
fsck.fat 3.0.27 (2014-11-12)
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset: original/backup)
494:30/ff, 495:3d/00, 496:61/00, 497:8a/00, 498:f0/00, 499:b2/00, 500:6f/00
, 501:15/00, 502:5b/00, 503:35/00, 504:fd/00, 505:8c/00, 506:07/00
, 507:3d/00, 508:6e/00, 509:ea/00
1) Copy original to backup
2) Copy backup to original
3) No action
? 2
Perform changes ? (y/n) y
/dev/sdc: 2623 files, 107816/348630 clusters
mypc:/home/grahamc#
|
I then unmounted and connected to Windows 10 AU (build 10393) and found, not surprisingly given your experience, that it works and I can now read the filesystem from Windows 10 AU. However what is surprising is that rebooting it did not disable it. This is possibly because since I upgraded the firmware to 3.19.5761 I can't power it off, I can only reboot it. Still, surprising, but there you go. I rebooted several times and I can still connect it to Windows 10 AU and see the files. Calibre also sees it fine.
Then I repeated the exercise with my wife's N905C and found that it also worked and I could read it on Windows 10 AU. However this one can be powered off and when I did so and restarted, it was as you found, the problem had returned.
I am quite happy with this though, because it is for me a simple and well-defined procedure for me to fix it via fsck.fat, and that's good enough for me, I am going to leave it like that. We rarely power our Kobos off and if the N905C is, it's easy to recover from. Down the track a bit I will check back in a while and see if Kobo come up with a fix for it, and see if I can work out a reliable fix, but I don't have the time right now. I could of course use the Minitool solution and reformat the drive and restore from backup, but I would really rather preserve my current files because I never know what the wretched DRM is going to do if I restore ePub files - I don't trust it not to decide I'm not allowed to read them any more.
This is considerable progress for me. I want to thank you, frostshutz, for your considerable efforts with this, it gave me quite a bit of information that was in the end enough to get me to a reliable working state.