Re: boot problem after compiling kernel 2.6.4
From: Drew Kroft (dkroft_at_mindless.com)
Date: 04/30/04
- Next message: mjt: "Re: URGENT HELP needed"
- Previous message: Ron Gibson: "Re: make xconfig documentation ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 29 Apr 2004 15:08:11 -0700
for what it's worth, i've stumbled through similar situations -
particularly when alternating between RedHat and generic kernels.
you MAY be seeing a combination of issues:
- devfs enabling/disabling - /dev entries appear/disappear if/when devfs
turns on/off. /dev/null missing indicates that.
- kernel module ext3 being locaded/built-into-the-kernel/not in the
initrd image. if hda1 is an ext3 formatted drive, missing this
functionality can trigger a slew of mount errors/fsck repairs. similar
with reiserfs formatted devices.
somtimes regenerating the initrd.....img in /boot can help load any
missing modules.
or, init'ing into single-user mode (kernel param "single" or "1") can
give you the opportunity
to load missing modules as you go along the boot process.
there are bootparams (man bootparam) to control devfs and ext3 loading.
hope that helps,
d-
Tim Buchanan wrote:
> Hey all,
>
> Just compiled the kernel 2.6.4 and now my system won't boot. I backed
> up the old kernel and I have restored it but the same thing still
> happens. Everything goes fine until the following appears:
>
> (I'm not sure how much of this is relevant)
>
> ERROR: Couldn't open /dev/null (Read-only file system)
> fsck.ext2: No such file or directory while trying to open /dev/hda1
> /dev/hda1: The superblock could not be read or does not describe a
> correct ext2 filesystem. If the device is valid and it really contains
> an ext2 filesystem (and not swap or ufs or something else), then the
> superblock is corrupt, and you might try running e2fsck with an
> alternate superblock: e2fsck -b 8183 <device>
>
> ...
>
> INIT: Entering runlevel: 3
> -- /etc/rc.d/rc.mu --
> [Pauses for approx 1 minute]
> INIT: Id "c1" respawning too fast: disables for 5 minutes
> INIT: Id "c2" respawning too fast: disables for 5 minutes
> INIT: Id "c3" respawning too fast: disables for 5 minutes
> INIT: no more processes left in this runlevel
>
> Does anyone know what this all means? any help would be appreciated
>
> Cheers
> Tim
>
>
- Next message: mjt: "Re: URGENT HELP needed"
- Previous message: Ron Gibson: "Re: make xconfig documentation ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
