Dying Kindle?

[leezer3]

Not a particularly happy bunny here
Attempted to transfer some more stuff onto my Kindle Paperwhite 10th generation, and Calibre keeps dumping IO errors.

Looking in the Windows error logs, and it keeps complaining about bad blocks and IO errors.
Chkdsk has frozen at 83%

Terminal?
Really irritating thing is that it's only 2 years old, and not bought from Amazon either.....
(Kobo died during Covid, and near impossible to get hold of anything)

[avni]

is your kindle jailbroken? do you have KUAL installed? do you have usb network hack installed? koreader?

if you answer this questions i might be able to help.

[leezer3]

Jailbroken, but no USB network or anything, only really the covers hack.

What were you thinking exactly?
SSH in and running badblocks from the device shell or something?

[avni]

i was thinking that if you had koreader you
could use its ssh function and ssh in via putty (or any client)
and execute the command 'imde reboot diags' and then command "reboot"
which will boot you into diags i think there might be something useful there.

[leezer3]

Hmm....
Diagnostics mode doesn't seem to want to work (although I'm pretty sure the command you intended was actually idme -d --bootmode diags )
The ENABLE_DIAGS blank file trick isn't doing anything either.

Badblocks running from the device has completed with zero bad blocks found, although I had to do that with the FS still mounted, which I don't like..... (With an unmounted FS, the whole thing crashes when it tries to enter sleep mode)

Changed the USB cable (just in case) and that hasn't done anything, Windows still dumped out with IO errors.

Now running a full fsck on the thing from USB networking to see if that helps at all.

Edit:
fsck via USB networking completed, and fixed a load of nasty stuff (inconsistancies between the two FATs, buch of corrupt files)
No bad clusters detected.
Another attempt to transfer stuff on via Windows, and it's still dumping exactly the same errors, and more issues.

I'd say the eMMC is not a happy bunny at this point.

Edit 2:
Factory reset, and tried again.
Problem surfaces when over 3gb on the internal memory, which is interesting, but not encouraging- Definitely a dud area on the flash.