Won't boot after bad shutdown (battery went dead)

[lulrich]

I installed the latest puppy version the other day to my computer, total install, I didn't partition the hd, it has been working good except for my internet connection which remains a mystery to me, as it connects via my pmccia aircard, sierra wireless 881, the blue light comes on indicating 3g, but I cannot access the web, but now another problem I have is that I didn't shut down normal the last time, (my battery went dead) and now when I try to boot up it starts but only goes so far and gives this message line after line,"EXT2-fs (sda 1) error:ext2_look up:deleted inode reference, 2281108"

while I was writing this I tried again and this time it went thru this again but then I hit enter several times and it actually booted, so I shut it down right and restarted and here it did the same thing again, "strange"
do I have something configured wrong in the bootup or somewhere?
sorry and thanks again for all your help!

[Flash]

This should be two different topics. Let's fix the booting problem in this one. You can start a new thread in the Wireless section for your wireless problem.

It might help if you could tell us which version of Puppy you installed and more detail about how you installed it, but anyway I think there is something you can enter at the boot prompt that will repair your ext2 filesystem. I've never used it so I'll leave the details for someone who knows what he's talking about.

[Sylvander]

1.

I didn't shut down normal the last time, (my battery went dead) and now when I try to boot up it starts but only goes so far

(a) I'm no Puppy super-expert, but...

(b) This was an "improper-power-off"...
That tends to corrupt the partition_file_system of the partition that was hosting the OS at the time.
Each/every time [if ever] this happens...
At next restart, you aught to REPAIR that partition_file_system before going any further.
How best to do this?...

(c) Well...
If this were a "live" install, and you were booting the main OS from files held on an incorruptible optical disk...
You would know that the basic Puppy OS was guaranteed to function, and be able to fix the problem with the puppy pfix-fsck command at startup.
But...
Because this is a full install...
And the OS is not guaranteed to function...
You cannot be sure it will be able to reliably fix the problem.
SO...

(d) Methinks it best to:
Boot a "live" Puppy CD. [In such a way that no suspect pupsave file is used]
Then, run Gparted, and use it to "check" the suspect partition.
[Know how to do that?]

[lulrich]

I´ll try, am still pretty new at this

[bigpup]

Most of the time, when Puppy does a hard crash, the file system gets corrupted.
This check will find and correct the problem.

Boot with the Puppy live CD
Use boot option puppy pfix=ram
Select console on desktop
Run a file system check on partition Puppy is installed to.

File system check at terminal
Drive to be checked must be unmounted.
Drive id to reflect what drive to check.

e2fsck /dev/sda1

Reboot after running file system check.
( because running Puppy from live CD it will ask about making save file. Say no )