NOTE: The shutdown I mention in original post happened as I was
preparing a remaster of installed puppylinux... the partial file
generated when the process broke was the problem... after
removing the broken puppylivecdbuild file, everything returned to
normal, and the second remaster succeeded
original article:
After an abrupt shutdown, I cannot load any of several savefiles which
appear in puppy menu at startup
I know all the listed savefiles are good... after a fresh boot with
puppy pfix=ram I can click/load any savefile and read/copy
contents... so the savefiles themselves are intact... it is whatever
connects savefiles to boot process where the breakage seems
to be... how can I fix this ?
NOTE: the computer itself /does/ boot fine to full debian installs
(I have two of them)... so Im hesitant to say "my boot sector is broken",
its only when trying to boot a wheezypup savefile that the computer
writes ten lines of code, and then stalls.
SOLVED cannot boot any savefile ? SOLVED
SOLVED cannot boot any savefile ? SOLVED
Last edited by soundNICK on Fri 01 May 2015, 00:47, edited 2 times in total.
Try to boot the save file with boot option "puppy pfix=fsck" to control its integrity. You can insert the "pfix=fsck" in the grub menu entry. I suppose a not encrypted savefile. If the savefile is encrypted then it's another story.
SECOND THOUGHT: read:
http://bkhome.org/blog/?viewDetailed=0144
You can try to put a /fsckme.err empty file in your partition.
SECOND THOUGHT: read:
http://bkhome.org/blog/?viewDetailed=0144
You can try to put a /fsckme.err empty file in your partition.