Blinking cursor at bootup, cannot login

[Pipeops]

Hi Everyone,

I am not much of a Linux guru, but I am getting the following error at the bootup of the machine. I do not have anything external hooked up to the server(flash drive, external USB, etc. ) Does anyone know why I get this error? This prevents me from logging in and I get a blinking cursor.

Thanks,

-I



scsi2 : SCSI emulation for USB Mass Storage devices
Vendor: Dell Model: Virtual Floppy Rev: 123
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0
SCSI device sdb: 2097151 512-byte hdwr sectors (1074 MB)
sdb: I/O error: dev 08:10, sector 0
I/O error: dev 08:10, sector 0
unable to read partition table
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 5
USB Mass Storage support registered.
Attached scsi CD-ROM sr0 at scsi1, channel 0, id 0, lun 0
sr0: scsi-1 drive
SCSI device sdb: 2097151 512-byte hdwr sectors (1074 MB)
sdb: I/O error: dev 08:10, sector 0
I/O error: dev 08:10, sector 0
unable to read partition table

 

[Annihilannic]

It sounds like you have a DRAC (Dell Remote Administration/Access? Card) in the server.

The DRAC allows you to upload virtual media (floppies in earlier versions, CD-ROMs as well in later versions) so that you can remotely boot and install an OS or boot from rescue media.

I think you can sometimes avoid those messages by mounting and unmounting some virtual media. Also look into any available firmware updates for the DRAC on the Dell support site.

Otherwise you can safely ignore those messages.

Annihilannic.

 

[Pipeops]

So this is not the reason I cannot login at startup and have the blinking cursor on the black screen?

 

[Annihilannic]

Err... I overlooked that detail in your original post.

I doubt it is the cause. At what point in the boot process does it stop, immediately after those messages?

Annihilannic.

 

[Pipeops]

I really appreciate your help,
Here is my full log file in dmesg


usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 20:45:09 Jul 5 2006
usb-uhci.c: High bandwidth mode enabled
PCI: Setting latency timer of device 00:1d.0 to 64
usb-uhci.c: USB UHCI at I/O 0xdce0, IRQ 21
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Setting latency timer of device 00:1d.1 to 64
usb-uhci.c: USB UHCI at I/O 0xdcc0, IRQ 20
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Setting latency timer of device 00:1d.2 to 64
usb-uhci.c: USB UHCI at I/O 0xdca0, IRQ 21
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
PCI: Setting latency timer of device 00:1d.7 to 64
ehci-hcd 00:1d.7: PCI device 8086:268c (Intel Corp.)
ehci-hcd 00:1d.7: irq 21, pci mem f888a000
usb.c: new USB bus registered, assigned bus number 4
ehci-hcd 00:1d.7: enabled 64bit PCI DMA
PCI: 00:1d.7 PCI cache line size set incorrectly (0 bytes) by BIOS/FW.
PCI: 00:1d.7 PCI cache line size corrected to 128.
ehci-hcd 00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2003-Jan-22
hub.c: USB hub found
hub.c: 6 ports detected
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
hub.c: connect-debounce failed, port 1 disabled
hub.c: new USB device 00:1d.7-1, assigned address 2
hub.c: USB hub found
hub.c: 2 ports detected
hub.c: new USB device 00:1d.7-5, assigned address 3
hub.c: USB hub found
hub.c: 4 ports detected
hub.c: new USB device 00:1d.7-1.1, assigned address 4
input0: USB HID v1.10 Keyboard [Dell DRAC5] on usb4:4.0
input1: USB HID v1.10 Mouse [Dell DRAC5] on usb4:4.1
hub.c: new USB device 00:1d.7-1.2, assigned address 5
usb.c: USB device 5 (vend/prod 0x413c/0x1) is not claimed by any active driver.
hub.c: new USB device 00:1d.1-1, assigned address 2
input2: USB HID v1.10 Keyboard [CHESEN PS2 to USB Converter] on usb2:2.0
input3: USB HID v1.10 Mouse [CHESEN PS2 to USB Converter] on usb2:2.1
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,7), internal journal
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: Dell Model: Virtual CDROM Rev: 123
Type: CD-ROM ANSI SCSI revision: 02
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 5
scsi2 : SCSI emulation for USB Mass Storage devices
Vendor: Dell Model: Virtual Floppy Rev: 123
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0
SCSI device sdb: 2097151 512-byte hdwr sectors (1074 MB)
sdb: I/O error: dev 08:10, sector 0
I/O error: dev 08:10, sector 0
unable to read partition table
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 5
scsi2 : SCSI emulation for USB Mass Storage devices
Vendor: Dell Model: Virtual Floppy Rev: 123
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0
SCSI device sdb: 2097151 512-byte hdwr sectors (1074 MB)
sdb: I/O error: dev 08:10, sector 0
I/O error: dev 08:10, sector 0
unable to read partition table
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 5
USB Mass Storage support registered.
SCSI device sdb: 2097151 512-byte hdwr sectors (1074 MB)
sdb: I/O error: dev 08:10, sector 0
I/O error: dev 08:10, sector 0
unable to read partition table
SCSI device sdb: 2097151 512-byte hdwr sectors (1074 MB)
sdb: I/O error: dev 08:10, sector 0
I/O error: dev 08:10, sector 0
unable to read partition table
SCSI device sdb: 2097151 512-byte hdwr sectors (1074 MB)
sdb: I/O error: dev 08:10, sector 0
I/O error: dev 08:10, sector 0
unable to read partition table
SCSI device sdb: 2097151 512-byte hdwr sectors (1074 MB)
sdb: I/O error: dev 08:10, sector 0
I/O error: dev 08:10, sector 0
unable to read partition table
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,3), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,9), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,5), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,6), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,2), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,10), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding Swap: 2096440k swap-space (priority -1)
ide-floppy driver 0.99.newide
hda: attached ide-cdrom driver.
hda: ATAPI 24X DVD-ROM drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
hda: DMA disabled
IA-32 Microcode Update Driver: v1.13 <tigran@veritas.com>
microcode: No suitable data for cpu 2
microcode: No suitable data for cpu 1
microcode: No suitable data for cpu 0
microcode: No suitable data for cpu 3
Attached scsi CD-ROM sr0 at scsi1, channel 0, id 0, lun 0
sr0: scsi-1 drive
SCSI device sdb: 2097151 512-byte hdwr sectors (1074 MB)
sdb: I/O error: dev 08:10, sector 0
I/O error: dev 08:10, sector 0
unable to read partition table
Attached scsi generic sg0 at scsi0, channel 0, id 8, lun 0, type 13
inserting floppy driver for 2.4.21-47.ELsmp
floppy0: no floppy controllers found
Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v1.4.36b (January 19, 2006)
divert: allocating divert_blk for eth0
eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B1) PCI-X 64-bit 133MHz found at mem f8000000, IRQ 16, node addr 001372f7e282
divert: allocating divert_blk for eth1
eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B1) PCI-X 64-bit 133MHz found at mem f4000000, IRQ 16, node addr 001372f7e284
divert: freeing divert_blk for eth0
divert: freeing divert_blk for eth1
audit subsystem ver 0.1 initialized
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (8192 buckets, 65536 max) - 304 bytes per conntrack
Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v1.4.36b (January 19, 2006)
divert: allocating divert_blk for eth0
eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B1) PCI-X 64-bit 133MHz found at mem f8000000, IRQ 16, node addr 001372f7e282
divert: allocating divert_blk for eth1
eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B1) PCI-X 64-bit 133MHz found at mem f4000000, IRQ 16, node addr 001372f7e284
bnx2: eth0 NIC Link is Up, 100 Mbps full duplex
ipmi message handler version 35.13
IPMI System Interface driver version 35.13, KCS version 35.13, SMIC version 35.13, BT version 35.13
ipmi_si: Found SMBIOS-specified state machine at I/O address 0xca8
IPMI kcs interface initialized
ipmi device interface version 35.13
lp: driver loaded but no devices found
usb.c: registered new driver serial
usbserial.c: USB Serial support registered for Generic
usbserial.c: USB Serial Driver core v1.4
Fusion MPT base driver 2.06.16.02
Copyright (c) 1999-2005 LSI Logic
mptbase: 0 MPT adapters found, 0 installed.
Fusion MPT base driver 2.06.16.02
Copyright (c) 1999-2005 LSI Logic
mptbase: 0 MPT adapters found, 0 installed.
Fusion MPT base driver 2.06.16.02
Copyright (c) 1999-2005 LSI Logic
mptbase: 0 MPT adapters found, 0 installed.
Fusion MPT base driver 2.06.16.02
Copyright (c) 1999-2005 LSI Logic
mptbase: 0 MPT adapters found, 0 installed.
Fusion MPT base driver 2.06.16.02
Copyright (c) 1999-2005 LSI Logic
mptbase: 0 MPT adapters found, 0 installed.
Fusion MPT base driver 2.06.16.02
Copyright (c) 1999-2005 LSI Logic
mptbase: 0 MPT adapters found, 0 installed.
inserting floppy driver for 2.4.21-47.ELsmp
floppy0: no floppy controllers found
inserting floppy driver for 2.4.21-47.ELsmp
floppy0: no floppy controllers found
inserting floppy driver for 2.4.21-47.ELsmp
floppy0: no floppy controllers found
inserting floppy driver for 2.4.21-47.ELsmp
floppy0: no floppy controllers found
inserting floppy driver for 2.4.21-47.ELsmp
floppy0: no floppy controllers found
inserting floppy driver for 2.4.21-47.ELsmp
floppy0: no floppy controllers found
inserting floppy driver for 2.4.21-47.ELsmp
floppy0: no floppy controllers found
inserting floppy driver for 2.4.21-47.ELsmp
floppy0: no floppy controllers found
SCSI device sdb: 2097151 512-byte hdwr sectors (1074 MB)
sdb: I/O error: dev 08:10, sector 0
I/O error: dev 08:10, sector 0
unable to read partition table
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 256 ret -32
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 256 ret -32
usbdevfs: process 8198 (lsusb) did not claim interface 0 before use
usbdevfs: process 8198 (lsusb) did not claim interface 1 before use
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 256 ret -32
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 256 ret -32
usbdevfs: process 8198 (lsusb) did not claim interface 0 before use
usbdevfs: process 8198 (lsusb) did not claim interface 1 before use
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 256 ret -32
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 256 ret -32
usbdevfs: process 8208 (lsusb) did not claim interface 0 before use
usbdevfs: process 8208 (lsusb) did not claim interface 1 before use
usbdevfs: process 8198 (lsusb) did not claim interface 1 before use
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 256 ret -32
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 256 ret -32
usbdevfs: process 8208 (lsusb) did not claim interface 0 before use
usbdevfs: process 8208 (lsusb) did not claim interface 1 before use
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 256 ret -32
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 256 ret -32
usbdevfs: process 8208 (lsusb) did not claim interface 0 before use
usbdevfs: process 8208 (lsusb) did not claim interface 1 before use
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 256 ret -32
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 256 ret -32
usbdevfs: process 8212 (lsusb) did not claim interface 0 before use
usbdevfs: process 8212 (lsusb) did not claim interface 1 before use
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 256 ret -32
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 256 ret -32
usbdevfs: process 8212 (lsusb) did not claim interface 0 before use
usbdevfs: process 8212 (lsusb) did not claim interface 1 before use
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 256 ret -32
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 256 ret -32
usbdevfs: process 8216 (lsusb) did not claim interface 0 before use
usbdevfs: process 8216 (lsusb) did not claim interface 1 before use
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 256 ret -32
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 256 ret -32
usbdevfs: process 8216 (lsusb) did not claim interface 0 before use
usbdevfs: process 8216 (lsusb) did not claim interface 1 before use
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 256 ret -32
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 256 ret -32
usbdevfs: process 8220 (lsusb) did not claim interface 0 before use
usbdevfs: process 8220 (lsusb) did not claim interface 1 before use
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 256 ret -32
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 256 ret -32
usbdevfs: process 8220 (lsusb) did not claim interface 0 before use
usbdevfs: process 8220 (lsusb) did not claim interface 1 before use
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 256 ret -32
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 256 ret -32
usbdevfs: process 8224 (lsusb) did not claim interface 0 before use
usbdevfs: process 8224 (lsusb) did not claim interface 1 before use
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 256 ret -32
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 256 ret -32
usbdevfs: process 8224 (lsusb) did not claim interface 0 before use
usbdevfs: process 8224 (lsusb) did not claim interface 1 before use

 

[Annihilannic]

How were you able to get dmesg output if you aren't able to log in?

I still don't fully understand at what point it is stopping, is it immediately after the messages you listed above?

Annihilannic.

 

[Pipeops]

Hi there,

That is exactly what is happening. It happens immediately after the messages above. My other guess if this has to do anything with mingetty. Could that be the reason for the blinking cursor?

Thanks,

-I

 

[Pipeops]

It looks like it is trying to find an update for the 2.4.21-47 kernel update on the floppy. How can I specify to make it look somewhere else?

 

[Pipeops]

usb.c: registered new driver serial
usbserial.c: USB Serial support registered for Generic
usbserial.c: USB Serial Driver core v1.4
Fusion MPT base driver 2.06.16.02
Copyright (c) 1999-2005 LSI Logic
mptbase: 0 MPT adapters found, 0 installed.
Fusion MPT base driver 2.06.16.02
Copyright (c) 1999-2005 LSI Logic
mptbase: 0 MPT adapters found, 0 installed.
Fusion MPT base driver 2.06.16.02
Copyright (c) 1999-2005 LSI Logic
mptbase: 0 MPT adapters found, 0 installed.
Fusion MPT base driver 2.06.16.02
Copyright (c) 1999-2005 LSI Logic
mptbase: 0 MPT adapters found, 0 installed.
Fusion MPT base driver 2.06.16.02
Copyright (c) 1999-2005 LSI Logic
mptbase: 0 MPT adapters found, 0 installed.
Fusion MPT base driver 2.06.16.02
Copyright (c) 1999-2005 LSI Logic
mptbase: 0 MPT adapters found, 0 installed.
inserting floppy driver for 2.4.21-47.ELsmp
floppy0: no floppy controllers found
inserting floppy driver for 2.4.21-47.ELsmp
floppy0: no floppy controllers found

 

[mrregan]

Is your floppy listed as a boot device in your
firmware?

 

[Pipeops]

There is no floppy device that is physically attached. There is no virtual floppy disk as well in the firmware.

 

[mrregan]

Nevermind, I think I was on the wrong track here.

 

[donb01]

I'm trying to figure out how the thing is booting in the first place. It's obviously telling you that SCSI Disk B has failed, so either you have another SCSI disk in there it's booting off of, sda perhaps, or an IDE drive, or there is a CD in the CD drive it is booting from....

As an earlier poster asked - if your console is locking up how are you getting this information? Are you able to login remotely vis telnet or SSL or something?

If your boot manager comes up and asks you which version to boot, have you tried the failsafe version? Does that work?

 

[Pipeops]

I am able to SSH into the server. I will try to boot from the failsafe version

 

[Annihilannic]

How about if you go to the alternative consoles using Alt-F2, Alt-F3, etc., are there login prompts displayed on those?

What kind of login is the server set up for normally, graphical or text?

Your guess about mingetty has some merit alright, can you see it running when you log in via ssh?

Also, what flavour of Linux are looking at here?

Annihilannic.

 

[Pipeops]

I just checked and the mingetty process is not running. mingetty is designed to be a minimal getty for the virtual terminals on the the workstation's monitor and keyboard. Now I am stuck, because it is actually in the innitab file. Any suggestions?

Thanks,
-I

 

[Annihilannic]

Is the mingetty executable where it should be? Can you run it manually?

Annihilannic.

 

[Pipeops]

I am not able to start mingetty for some apparent reason. I tried the respawn command. I also compared mingetty to the backup server to make sure nothing is corrupted and it is in fact the same file. The mingetty executable is in the inittab folder.

Thanks,
-I

 

[Pipeops]

Here is what i get in the messages log when i manually try to run it:

mingetty[11663]: tty1: no controlling tty: Operation not permitted

Any Ideas?

 

[Annihilannic]

Does the output of ls -l /dev/tty? look sane? Here's a sample from a system near me:

# ls -l /dev/tty?
crw--w--w-  1 root root 4, 0 Jan 30  2007 /dev/tty0
crw-rw----  1 root tty  4, 1 May  2 23:06 /dev/tty1
crw-rw----  1 root tty  4, 2 May  2 23:06 /dev/tty2
crw-rw----  1 root tty  4, 3 May  2 23:06 /dev/tty3
crw-rw----  1 root tty  4, 4 May  2 23:06 /dev/tty4
crw-rw----  1 root tty  4, 5 May  2 23:06 /dev/tty5
crw-rw----  1 root tty  4, 6 May  2 23:06 /dev/tty6
crw--w----  1 root root 4, 7 May  2 23:05 /dev/tty7
crw--w----  1 root tty  4, 8 Jun  5  2007 /dev/tty8
crw--w----  1 root tty  4, 9 Nov 18  2005 /dev/tty9

Also, please answer my previous question about the particular flavour of Linux you are running?

Annihilannic.