Encrypting Save gives Kernel Panic on next boot

[2joe]

Fresh Precise install to USB, first save, selected heavy crypto, next boot had kernel panic. Do I need to wipe the USB and start over? or is there another way to fix this?

[bigpup]

What version of Precise?
Is it the latest version?
http://bkhome.org/blog2/?viewDetailed=00346

[2joe]

yes precise 5.7.1
I used unetbootin on ubuntu 12.04 to make the bootable usb.
I entered the password and it successfully mounts. then it copies puppy_precise_5.7.1.sfs main file to ram. Then this:

Code: Select all

[   27.176950] Kernel panic - not syncing: Attempting to kill init! exitcode=0x00000200
[   27.176950]
[   27.177013] Pid :1, comm:init Not tainted 3.9.11
[   27.177063] Call Trace;
[   27.177116] [<c1365826>] ? panic+0x7b/0x159
[   27.177166] [<c1020196>] ? do_exit+0x3b4/0x747
[   27.177216] [<c10205f5>] ? sys_exit+0x11/0x11 
[   27.177267] [<c136a1c0>] ? syscall_call+0x7/0xb

[Flash]

The NSA OVERLORD program in your computer's BIOS does not know Puppy's encryption protocol.

Just kidding, I really have no idea.

[rcrsn51]

When you set up an encrypted savefile, make sure that you select ext2 as the file format.

[Flash]

Does that require that the partition where the Save file will be located must be formatted ext2, or can the Save file have an internal ext2 filesystem separate from the partition's filesystem?

[rcrsn51]

The ext2 requirement refers to the savefile's internal structure, not the destination partition.

[Flash]

Thank you, I didn't know that.