[knc1]

Phooey!
That bad block is part of the file system meta-data, leaving a corrupted file system.

- - - -

Give the factory initial firmware a chance, it might be programmed to deal with that kind of error.

Note that if it does, it will be a slow process -

On this flash memory, the build of e2fsck the Kindle uses has to start over after mapping out each bad block.
So keep the Kindle on a charger while it is trying to recover the file system, it may take a few days (really).

If it doesn't auto-recover, we will have to force it.

We aren't ready for the "Erase All" big hammer (yet).
There are less drastic things to try if "#2" doesn't do the job.

= = = =

Note:
Even when everything is normal, it is a tricky business to install an update image that is larger than available memory (and without swap enabled also).

We may, eventually, have to treat this as a blank eMMC - -
Search for a fairly recent (this summer) thread with 'fastboot' in the title.
It also has a lot of capture logs attached to the posts to serve as reference information.

Don't be concerned if the thread you find isn't about the PW-2, the procedure will be the same.

Ah, and yes, we did recover from a blank eMMC - -
Which reminds me, we need to make a copy of the Diags system before doing an "erase all" on the Kindle.

geekmaster is probably following this thread, he may have some other reference threads to suggest.