> On Thu, 6 Feb 2003, Andrew Morton wrote:
>
> > > I'm still not seeing your messages.
> > >
> > > Part of the problem is I'm only seeing part of the boot sequence. The
> > > last thing I see is the infamous:
> > >
> > > Uncompressing Linux... OK booting the kernel
> > >
> > > Something is going on behind the scenes, though. The drive light seems to
> > > be doing its usual thing. The system responds to alt-sysrq keys, but not
> > > to ctrl-alt-del.
> >
> > eh? But that sounds like something totally different from
> > your original report?
> >
> > You're not getting any console output at all?
> >
> > Make sure that you're not booting with the `quiet' option.
> >
> > If you're using any fancy video options, framebuffers, etc then disabled them.
Further on this problem. I did a system restore to a disk on /dev/hdb,
fixed up fstab and other files so I could boot from /dev/hdb1. I got
results similar to the original. However, this time I did get log
messages.
I'm also attaching a copy of the configuration used to build this kernel.
What might be a good next step in debugging this?
When I booted up I got the following on the console:
Booting 'tom's test'
root (hd1,0)
Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz-2.5.59-0207 ro root=/dev/hdb1
[Linux-bzImage, setup=0x1400, size= 0xec89c]
Uncompressing Linux... OK booting the kernel
at which time I ceased seeing messages on the console. However, I
continued to see drive light activity. When that ceased, I booted back
into a stock RedHat 8.0 kernel and did an fsck on the affected drive. I
got the following:
[root@dad root]# e2fsck -d -f -v /dev/hdb1
e2fsck 1.27 (8-Mar-2002)
/dev/hdb1: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
106211 inodes used (9%)
83 non-contiguous inodes (0.1%)
# of inodes with ind/dind/tind blocks: 4994/29/0
777861 blocks used (33%)
0 bad blocks
0 large files
80812 regular files
4661 directories
2523 character device files
15884 block device files
1 fifo
2265 links
2318 symbolic links (2315 fast symbolic links)
3 sockets
--------
108467 files
In /var/log/messages I got the following interesting stuff:
Feb 7 13:20:36 dad kernel: Journalled Block Device driver loaded
(how can that be, considering the initial message on the console?)
then I started seeing some of these:
Feb 7 13:20:36 dad keytable: /etc/rc3.d/S17keytable: line 26: /dev/tty0:
No such device
Feb 7 13:20:36 dad keytable: Couldnt get a file descriptor referring to
the console
Feb 7 13:20:36 dad kernel: Warning: unable to open an initial console.
Feb 7 13:20:43 dad gpm[724]: oops() invoked from gpn.c(125)
Feb 7 13:20:43 dad gpm[724]: /dev/console: No such device
Feb 7 13:20:43 dad gpm: gpm: oops() invoked from gpn.c(125)
Feb 7 13:20:43 dad gpm: /dev/console: No such device
Feb 7 13:20:43 dad gpm: gpm startup failed
Feb 7 13:20:43 dad crond: crond startup succeeded
Feb 7 13:20:44 dad xfs: listening on port 7100
Feb 7 13:20:44 dad xfs: xfs startup succeeded
Feb 7 13:20:44 dad anacron: anacron startup succeeded
Feb 7 13:20:44 dad atd: atd startup succeeded
Feb 7 13:20:44 dad xfs: ignoring font path element
/usr/X11R6/lib/X11/fonts/cyrillic (unreadable)
Feb 7 13:20:44 dad kernel: warning: process `update' used the obsolete
bdflush system call
Feb 7 13:20:44 dad kernel: Fix your initscripts?
Feb 7 13:20:44 dad /sbin/mingetty[799]: /dev/tty5: cannot open tty: No
such device
Feb 7 13:20:44 dad /sbin/mingetty[795]: /dev/tty1: cannot open tty: No
such device
Feb 7 13:20:44 dad /sbin/mingetty[796]: /dev/tty2: cannot open tty: No
such device
Feb 7 13:20:44 dad /sbin/mingetty[797]: /dev/tty3: cannot open tty: No
such device
Feb 7 13:20:44 dad /sbin/mingetty[800]: /dev/tty6: cannot open tty: No
such device
Feb 7 13:20:44 dad /sbin/mingetty[798]: /dev/tty4: cannot open tty: No
such device
Feb 7 13:20:44 dad /sbin/mingetty[809]: /dev/tty1: cannot open tty: No
such device
Feb 7 13:20:44 dad /sbin/mingetty[810]: /dev/tty2: cannot open tty: No
such device
Feb 7 13:20:44 dad /sbin/mingetty[811]: /dev/tty3: cannot open tty: No
such device
Feb 7 13:20:44 dad /sbin/mingetty[812]: /dev/tty4: cannot open tty: No
such device
Feb 7 13:20:44 dad /sbin/mingetty[813]: /dev/tty5: cannot open tty: No
such device
Feb 7 13:20:44 dad /sbin/mingetty[814]: /dev/tty6: cannot open tty: No
such device
etc., etc., etc.
followed finally by:
Feb 7 13:20:45 dad init: Id "1" respawning too fast: disabled for 5
minutes
Feb 7 13:20:45 dad /sbin/mingetty[907]: /dev/tty6: cannot open tty: No
such device
Feb 7 13:20:45 dad /sbin/mingetty[906]: /dev/tty4: cannot open tty: No
such device
Feb 7 13:20:45 dad init: Id "5" respawning too fast: disabled for 5
minutes
Feb 7 13:20:45 dad init: Id "4" respawning too fast: disabled for 5
minutes
Feb 7 13:20:45 dad /sbin/mingetty[911]: /dev/tty3: cannot open tty: No
such device
Feb 7 13:20:45 dad /sbin/mingetty[913]: /dev/tty6: cannot open tty: No
such device
Feb 7 13:20:45 dad /sbin/mingetty[905]: /dev/tty2: cannot open tty: No
such device
Feb 7 13:20:45 dad init: Id "6" respawning too fast: disabled for 5
minutes
Feb 7 13:20:45 dad init: Id "2" respawning too fast: disabled for 5
minutes
Feb 7 13:20:45 dad /sbin/mingetty[915]: /dev/tty3: cannot open tty: No
such device
Feb 7 13:20:45 dad init: Id "3" respawning too fast: disabled for 5
minutes
Feb 7 13:20:45 dad init: no more processes left in this runlevel
You get the idea.
This archive was generated by hypermail 2b29 : Fri Feb 07 2003 - 22:00:24 EST