Thread: Hacking SD card file system
View Single Post
Old 08-05-2016, 10:35 AM   #46
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by rtiangha View Post
That said, I wonder if it's possible to modify frostschutz's dosfsck script to either probe the partition to figure out what it's formatted with and run the proper utility, or to run e2fsck instead if dosfsck fails, so that way, it wouldn't matter to the device what file system that partition is formatted in (let the Kobo assume it's still FAT32) and will run the disk check whenever it needs to run a disk check under normal operations. Seems kind of silly to have a journaled file system if the device won't file check it every so often (assuming Kobo hard coded it to do that to the FAT32 partition once in a while), although to be fair, I don't know under what circumstances the Kobo would call dosfsck in the first place. Hopefully it would do it on regular intervals or whenever it detects issues with the file system.
Every time the device boots, the firmware runs:

Code:
dosfsck -a -w /dev/mmcblk0p3
And if it finds the file system is corrupt, it will prompt you to do a factory reset.
davidfor is offline   Reply With Quote