Quote:
Originally Posted by NiLuJe
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 with mine (whereas it's fairly common on the Forma. Possibly slightly less so in newer FWs).
|
errors=remount-ro is what's triggering the load as read-only, I've assumed. That's set in mtab, IIRC. You mean the dirty bit isn't sufficient to trigger errors=remount-ro? Is there a way to figure out what
is triggering it to go read-only, then?
This is an original H2O.
Quote:
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.
|
I don't have a Windows computer. fsck is the Linux equivalent to checkdisk, AFAIK.
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.