Jbed pw2 trashes file system of it crashes

barkas · 12-27-2014, 03:43 PM

When koreader or Kual crash, I had to reinstall both and copy my whole library onto the device again because much of it had vanished, being replaced by files with names like fsck0001.ren.
Any ideas what causes this and how I can prevent it?

Dr. Drib · 12-31-2014, 06:53 PM

Moved to the Kindle Dev. sub-forum.

Don
(Moderator)

knc1 · 12-31-2014, 07:17 PM

Quote:

Originally Posted by barkas

When koreader or Kual crash, I had to reinstall both and copy my whole library onto the device again because much of it had vanished, being replaced by files with names like fsck0001.ren.
Any ideas what causes this and how I can prevent it?

Hmm....

That almost sounds like you have reversed the cause and the effect.
I.E: The applications are crashing because of the file system errors.

The fsck* names are created during the file system (fs) check (ck) done during the reboot.

The root cause is whatever is creating the file system errors.
Most likely, hardware problems.

If still in warranty, return it as "broke" - it isn't practical to fix the hardware.

barkas · 01-01-2015, 03:53 AM

Quote:

Originally Posted by knc1

Hmm....

That almost sounds like you have reversed the cause and the effect.
I.E: The applications are crashing because of the file system errors.

The fsck* names are created during the file system (fs) check (ck) done during the reboot.

The root cause is whatever is creating the file system errors.
Most likely, hardware problems.

If still in warranty, return it as "broke" - it isn't practical to fix the hardware.

Interesting point, but I'm quite sure what crashed it, because I was trying different menu options in koreader and it crashed immediately on that, like accessing the history which was at that point empty.

Since then, it has not crashed again, and I have not had further fs corruption. I only fear if it happens again, it might trash the fs again, which is a bit inconvenient.

knc1 · 01-01-2015, 05:51 AM

Quote:

Originally Posted by barkas

Interesting point, but I'm quite sure what crashed it, because I was trying different menu options in koreader and it crashed immediately on that, like accessing the history which was at that point empty.

Since then, it has not crashed again, and I have not had further fs corruption. I only fear if it happens again, it might trash the fs again, which is a bit inconvenient.

What where you doing when KUAL crashed?

barkas · 01-01-2015, 06:53 AM

I had just installed that stuff and was trying what all the menu options are doing. I think one crash was in the history and the other one had to do with calibre integration.

Edit: I can not reproduce any of this.

knc1 · 01-01-2015, 07:45 AM

Quote:

Originally Posted by barkas

I had just installed that stuff and was trying what all the menu options are doing. I think one crash was in the history and the other one had to do with calibre integration.

Edit: I can not reproduce any of this.

Was the USB cable connected?
If so, was the device user storage mounted to a PC?

Prior to disconnecting the cable, had the user storage been un-mounted? (or in WinTerms - "safely remove" been executed?)

- - - - -

Do a cold (full) re-boot - several times.
That will run fsck each time on the file system and be fairly certain to find/fix all file system errors.

Running a FAT32 fsck program from the PC end of the cable **IS NOT** recommended.

When certain that no more file system errors are to be found, try to duplicate the crash(es) and keep detailed notes of how to reproduce them.

You did not say how old this device was, but you write as if it where new.
So it is possible it shipped with un-corrected file system errors.

It is also possible that the external PC (with or without user interference) caused the file system errors (slim chance, but possible).

barkas · 01-01-2015, 05:31 PM

USB cable was not connected, storage had been unmounted.
I rebooted once to be sure that the FS would be clean.

Then I did something that made koreader crash, kindle rebooted, and then all kinds of stuff was gone.

I bought the device a few weeks ago.

Unfortunately I can't get koreader to crash anymore ...

Anyway, thanks for the help, if it happens again, I'll try to keep better track of the circumstances and will hopefully be able to reproduce the problem.

hawhill · 01-03-2015, 07:58 AM

I would consider it a good thing that you can't crash it anymore :-)
Usually, it would almost never crash in a way that makes the device reboot. That would be a kernel error, I guess, rather than userspace software (though of course, userspace software can - by its behaviour - trigger the kernel error). And a hard reboot or poweroff might cause a corrupted filesystem, leading to a filesystem check, which leaves those funny named files.

barkas · 01-03-2015, 09:35 AM

Just got it to crash again. I was in KOReader Filebrowser and tried to connect to a nonexistent local Calibre catalog.

Kindle was nonresponsive for about 30 seconds, then rebooted.

/documents is still mostly intact, except the KUAL azw and a comics subfolder I had there.
/extensions is pretty much gone.
/koreader has quite a few missing (renamed) things.

So I basically had to reinstall everything KUAL related.

knc1 · 01-03-2015, 09:43 AM

Quote:

Originally Posted by barkas

Just got it to crash again. I was in KOReader Filebrowser and tried to connect to a nonexistent local Calibre catalog.
- - - - -

Now there is a similarity -
You mentioned that an earlier crash was when you accessed an empty history file.

- - - - -

Perhaps a missing error check when doing file access to a missing or empty file?

But I don't see how that could corrupt the file system (crash the application - maybe, trash the file system - not likely).

Someone with better knowledge than I of KOReader will have to look at this one.

hawhill · 01-03-2015, 11:38 AM

Not sure at all. As I said, when we manage to crash the whole device, the kernel is the culprit. However, we should probably avoid triggering kernel bugs. Will try to replicate, but am not sure when I'll get to do that.

NiLuJe · 01-05-2015, 08:54 AM

And even in the event of a kernel panic, it shouldn't trash the FS (to that extent, at least). VFAT sucks, true, but that sounds a bit extreme.

The only kpanic I ever triggered on a PW2 was mostly harmless. You might lose the date/time on some models, but that's it.

But, again, YMMV.

barkas · 01-05-2015, 01:58 PM

My thoughts exactly. It's only explainable by very aggressive caching of the fat itself, I think.
Does the kindle use weird mount options for /mnt/us?

I'd be up to debug this myself but I don't see how without some sort of text console.

Edit: do you really think this is a kernel panic? It seems to behave like some sort of watchdog reboot.

Edit2: could it be a good idea to update to 5.6.1?

NiLuJe · 01-05-2015, 04:31 PM

@barkas: Check dmesg (and/or the full logs (showlog)), the reboot reason is logged, and a watchdog reboot after a hang has a specific flavor that's logged

.

And, no, I'd stay away from 5.6.x, but that's just me

.

The userstore is originally mounted in a fairly straightforward manner, (/mnt/base-us) but it's then proxied through fuse (/mnt/us) to handle USBMS somewhat gracefully, so it's potentially unpredictable ^^.

12-27-2014, 03:43 PM	#1
barkas Member Posts: 12 Karma: 10 Join Date: Dec 2014 Device: Kindle pw2	Jbed pw2 trashes file system of it crashes When koreader or Kual crash, I had to reinstall both and copy my whole library onto the device again because much of it had vanished, being replaced by files with names like fsck0001.ren. Any ideas what causes this and how I can prevent it?

01-01-2015, 06:53 AM	#6
barkas Member Posts: 12 Karma: 10 Join Date: Dec 2014 Device: Kindle pw2	I had just installed that stuff and was trying what all the menu options are doing. I think one crash was in the history and the other one had to do with calibre integration. Edit: I can not reproduce any of this. Last edited by barkas; 01-01-2015 at 07:00 AM.

01-05-2015, 01:58 PM	#14
barkas Member Posts: 12 Karma: 10 Join Date: Dec 2014 Device: Kindle pw2	My thoughts exactly. It's only explainable by very aggressive caching of the fat itself, I think. Does the kindle use weird mount options for /mnt/us? I'd be up to debug this myself but I don't see how without some sort of text console. Edit: do you really think this is a kernel panic? It seems to behave like some sort of watchdog reboot. Edit2: could it be a good idea to update to 5.6.1? Last edited by barkas; 01-05-2015 at 03:10 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Troubleshooting Extremely frequent crashes on brand new PW2	Animec	Amazon Kindle	10	08-04-2014 01:24 PM
Sigil file crashes Sony software	Quiss	Sigil	12	08-14-2012 08:04 PM
Calibre crashes my system(Ubuntu)	Grey Pearl	Devices	12	02-01-2012 08:11 PM
Pogue trashes the Cool-ER	discourse	Interead COOL-ER	44	06-03-2009 07:10 AM
how to clean more disk space in root file system to upgrade system	chinaet	iRex	1	12-18-2006 03:54 PM

12-31-2014, 06:53 PM	#2
Dr. Drib Grand Sorcerer Posts: 45,441 Karma: 59592133 Join Date: Jan 2007 Location: Peru Device: KINDLE: Oasis 3, Scribe (1st), Matcha; KOBO: Libra 2, Libra Colour	Moved to the Kindle Dev. sub-forum. Don (Moderator)

01-01-2015, 05:31 PM	#8
barkas Member Posts: 12 Karma: 10 Join Date: Dec 2014 Device: Kindle pw2	USB cable was not connected, storage had been unmounted. I rebooted once to be sure that the FS would be clean. Then I did something that made koreader crash, kindle rebooted, and then all kinds of stuff was gone. I bought the device a few weeks ago. Unfortunately I can't get koreader to crash anymore ... Anyway, thanks for the help, if it happens again, I'll try to keep better track of the circumstances and will hopefully be able to reproduce the problem.

01-03-2015, 07:58 AM	#9
hawhill Wizard Posts: 1,379 Karma: 2155307 Join Date: Nov 2010 Location: Goettingen, Germany Device: Kindle Paperwhite, Kobo Mini	I would consider it a good thing that you can't crash it anymore :-) Usually, it would almost never crash in a way that makes the device reboot. That would be a kernel error, I guess, rather than userspace software (though of course, userspace software can - by its behaviour - trigger the kernel error). And a hard reboot or poweroff might cause a corrupted filesystem, leading to a filesystem check, which leaves those funny named files.

01-03-2015, 09:35 AM	#10
barkas Member Posts: 12 Karma: 10 Join Date: Dec 2014 Device: Kindle pw2	Just got it to crash again. I was in KOReader Filebrowser and tried to connect to a nonexistent local Calibre catalog. Kindle was nonresponsive for about 30 seconds, then rebooted. /documents is still mostly intact, except the KUAL azw and a comics subfolder I had there. /extensions is pretty much gone. /koreader has quite a few missing (renamed) things. So I basically had to reinstall everything KUAL related.

01-03-2015, 11:38 AM	#12
hawhill Wizard Posts: 1,379 Karma: 2155307 Join Date: Nov 2010 Location: Goettingen, Germany Device: Kindle Paperwhite, Kobo Mini	Not sure at all. As I said, when we manage to crash the whole device, the kernel is the culprit. However, we should probably avoid triggering kernel bugs. Will try to replicate, but am not sure when I'll get to do that.

01-05-2015, 08:54 AM	#13
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	And even in the event of a kernel panic, it shouldn't trash the FS (to that extent, at least). VFAT sucks, true, but that sounds a bit extreme. The only kpanic I ever triggered on a PW2 was mostly harmless. You might lose the date/time on some models, but that's it. But, again, YMMV.

01-05-2015, 04:31 PM	#15
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@barkas: Check dmesg (and/or the full logs (showlog)), the reboot reason is logged, and a watchdog reboot after a hang has a specific flavor that's logged . And, no, I'd stay away from 5.6.x, but that's just me . The userstore is originally mounted in a fairly straightforward manner, (/mnt/base-us) but it's then proxied through fuse (/mnt/us) to handle USBMS somewhat gracefully, so it's potentially unpredictable ^^.

Advert

Advert