On Thu, 16 Oct 2003 21:00:56 GMT,
a?n?g?e?lrigrevol.moc.com (The little lost angel) wrote:
I always create a /boot volume of about 50-75M as a primary partition
first thing: then you NEVER have that problem....
A "kernel panic" generally means that you're stopped cold. Also,
"init" is the first process (process id 1); so if something is trying
to kill init, you should be stopped cold there, too.
A power tip: press Shift-PgUp and Shift-PgDown to go back and forth.
If you switch virtual terminals (with Alt-F1 and Alt-F2 and so on)
then the "buffer" disappears and you can't get what went before you
switched (so don't...)
"Bad super block" sometimes means that the format of the volume is
unrecognized; for instance, if you are using the XFS filesystem on the
root volume and the kernel has no internal XFS support.
The Shift-PgUp and Shift-PgDown should help...
That has more to do with the number of partitions on the drive and
possibly where they are located in the partition table. Since it is
/dev/hda5, I'd say that that was the first volume in the extended
partition. You can have (generally speaking) any number of
partitions. If you have more than three primary partitions, then one
of the partitions will be contained within an extended partition
(which occupies one "partition slot").
If you look at the bootup, I'm guessing you'll see something like
this, which would be the format I'm talking of:
hda: hda1 hda2 hda3 hda4 < hda5 >
hda1 through hda3 are your disk volumes, hda4 is the extended
partition, which contains hda5...