|
|
Thread Tools | Search this Thread |
03-26-2020, 04:48 PM | #1 |
Enthusiast
Posts: 36
Karma: 10
Join Date: Feb 2017
Device: Kobo Aura H2O
|
Can I stop a Kobo H2O from marking the file system as dirty short of a factory reset?
I have a Kobo Aura H2O with a file system that always shows up with the dirty bit set, so when I plug into a Linux computer, it's mounted as read-only, which makes it impossible to add books. I've run fsck on the file system and didn't find any errors, so I'm unconvinced there's anything actually wrong with it. I can manually unset the dirty bit and remount the file system read-write and successfully add books, but the moment I unplug it and plug it back in, the file system is set as dirty again and I have to go through the whole remount procedure to make it usable. I'm assuming the Kobo software is responsible for setting the dirty bit. Is there any to force it to stop doing that short of a factory reset?
This problem seems to have started when my ereader ran out of charge while I was temporarily unable to use it. |
03-26-2020, 06:31 PM | #2 |
BLAM!
Posts: 13,480
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Err, fix whatever mess is mounting stuff ro if the dirty bit is set, because that's definitely not standard.
EDIT: I would have naively assumed that'd be because of errors=remount-ro, but that's the default on FAT, and it's not tripped by a dirty bit on my system. ---- Is that an actual H2O, first of its name, or a v2? Because that'd be the first time I've seen this being reported on a H2O (it's usually far more prevalent on devices with an eMMc). I've certainly never seen it with mine (whereas it's fairly common on the Forma. Possibly slightly less so in newer FWs). Last edited by NiLuJe; 03-26-2020 at 10:12 PM. |
03-26-2020, 06:36 PM | #3 |
Resident Curmudgeon
Posts: 74,464
Karma: 129668758
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Try plugging the H2O into a Windows computer and if it thinks there is a problem, run check disk on it.
Always properly eject the H2O from the computer. You may have unplugged it without ejecting to get this issue. |
03-26-2020, 06:55 PM | #4 | ||
Enthusiast
Posts: 36
Karma: 10
Join Date: Feb 2017
Device: Kobo Aura H2O
|
Quote:
This is an original H2O. Quote:
I always do properly eject. In this case, the issue definitely started after I didn't recharge it awhile and it discharged completely. (I wasn't using it during this time.) I'm guessing that effectively caused a crash and that's why it's marking the disk as dirty. |
||
03-26-2020, 07:14 PM | #5 |
Resident Curmudgeon
Posts: 74,464
Karma: 129668758
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
So run fsck and fix the problem.
|
03-26-2020, 09:33 PM | #6 |
Grand Sorcerer
Posts: 24,906
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
At the moment, I'm noticing an error like this if after connecting either my Forma or Clara HD to my work Linux machine. When I get home, Windows will complain that the file system is dirty. The check doesn't find anything. I assume the Linux box isn't unmounting something properly, but, it isn't enough of an issue to chase down.
If it is happening all the time, it could be failing storage. Others have reported this and replacing the card fixed it. That is only possible if it is an original Aura H2O. But, you will need to break the waterproofing to do that. |
03-26-2020, 09:41 PM | #7 |
Grand Sorcerer
Posts: 12,236
Karma: 74000000
Join Date: Nov 2007
Location: Toronto
Device: Nexus 7, Clara, Touch, Tolino EPOS
|
For a long time I've experienced a dirty bit being left set when I dismount from a Chromebook. It doesn't cause an issue on the Chromebook but the next time I connect to windows the message is presented and requires a chkdsk to clear.
|
03-27-2020, 02:55 AM | #8 |
Member
Posts: 12
Karma: 10
Join Date: Sep 2010
Device: Libra 2
|
I had this every time with my Aura H2O 2nd edition even after running the windows check/fix. Eventually I tried the method in the link and no more problems!
https://www.raymond.cc/blog/manually...hout-chkdsk/2/ |
03-27-2020, 09:40 AM | #9 |
Resident Curmudgeon
Posts: 74,464
Karma: 129668758
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Sounds to me like a bug in Linux. This is yet another reason to use Windows.
|
03-27-2020, 06:41 PM | #10 |
Linux User
Posts: 2,279
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
|
the kobo uses "lazy umount" before USB export. unfortunately the way lazy umount works is that the filesystem "disappears" but in reality nothing is umounted at all if the filesystem is busy. so kobo ends up exporting the filesystem in dirty state.
in original unpatched kobo firmware this used to be the case when connecting it to USB out of a kepub book. but I haven't tested this condition recently so I don't know if this is still the case. if you modded the device it's possible for those mods/addons to block umount as well. I tried to make a debug utlity for this condition at some point https://www.mobileread.com/forums/sh...d.php?t=263674 but it probably won't work anymore in current firmware, haven't updated in ages |
03-28-2020, 06:44 AM | #11 |
the rook, bossing Never.
Posts: 11,437
Karma: 87454321
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper11
|
Wait till the Kobo ereader has removed the progress bar for updating content before unplugging USB.
I've had no problems in the last two years using Linux Mint with 3 models of Kobo, Nook, 5 models Kindle and two Sony models. I've occasionally plugged into a Win7 PC last year. |
03-28-2020, 07:03 AM | #12 | |
Resident Curmudgeon
Posts: 74,464
Karma: 129668758
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
|
|
03-28-2020, 07:49 AM | #13 | |
Grand Sorcerer
Posts: 24,906
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
And, if the device has shown the home screen, then it will be safe to disconnect the device. Waiting for the import to finish is only useful if you want to keep power to the device while it does the hard work of importing the books. |
|
03-28-2020, 10:15 AM | #14 |
BLAM!
Posts: 13,480
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
It's also irrelevant to the underlying issue, which is how *nickel* itself is handling the unmount in order to export the partition over USBMS (which happens to be the *start* of the USBMS session, not the end).
The only difference the OS the device gets plugged into makes is in how it chooses to deal with the dirty bit being set. ---- That doesn't invalidate what @davidfor just detailed about the recent (-ish) behavioral change re: how the import screen can be triggered and when an unplug becomes safe . Last edited by NiLuJe; 03-28-2020 at 10:20 AM. |
Tags |
aura h2o |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Aura H2O Help! NEED KOBO H2O factory sd image | edwardycn | Kobo Developer's Corner | 154 | 06-13-2018 07:42 AM |
Aura H2O After Factory Reset Cover Art For All File Formats Dosen't Appear | SJC-Caron | Kobo Reader | 6 | 04-14-2016 10:04 AM |
Factory reset K5 using file | ixtab | Kindle Developer's Corner | 22 | 10-15-2015 08:14 AM |
Question about factory reset on Aura H2O | howyoudoin | Kobo Reader | 5 | 05-02-2015 10:16 PM |
Kobo 1.9 Factory Reset | jahindy | Kobo Reader | 10 | 01-15-2012 03:59 PM |