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

 

[Pipeops]

here is what i have:

what do u think?


crw--w---- 1 root tty 4, 0 Jun 24 2004 /dev/tty0
crw------- 1 uucp uucp 4, 1 Sep 8 2007 /dev/tty1
crw------- 1 root root 4, 2 Oct 20 2006 /dev/tty2
crw------- 1 root root 4, 3 Jun 24 2004 /dev/tty3
crw------- 1 root root 4, 4 Jun 24 2004 /dev/tty4
crw------- 1 root root 4, 5 Jun 24 2004 /dev/tty5
crw------- 1 root root 4, 6 Jun 24 2004 /dev/tty6
crw--w---- 1 root tty 4, 7 Jun 24 2004 /dev/tty7
crw--w---- 1 root tty 4, 8 Jun 24 2004 /dev/tty8
crw--w---- 1 root tty 4, 9 Jun 24 2004
/dev/tty9

 

[Pipeops]

I forgot to mention once again - I am running RH 3.0

Thanks,
-I

 

[Annihilannic]

/dev entries look okay... any clues in /var/log/boot.log? I'm running low on ideas here...

Annihilannic.

 

[bdintegrations]

Are you sure that is the whole dmesg file?

dmesg > dmesg.txt

post contents of dmesg.txt

Shot in the dark...Try disabling as many devices in bios as possible: mouse, floppy, usb, ethernet, etc.


Business and Data Integrations

http://www.bdintegrations.com/

A Northern Virginia IT Service and Consulting Company

 

[danomac]

Are you sure that is the whole dmesg file?

It is possible that there is so much output from the kernel that the buffer can't contain it all... you would lose the beginning of it in that case. The only way to increase it would be to recompile the kernel. I know in 2.6 kernels there's a CONFIG_LOG_BUF_SHIFT setting that allows you to define the size of the kernel log buffer. I don't know about 2.4 kernels though.

 

[Pipeops]

Everyone,

Thank you very much for your input on this issue. There was a process which was running in the foreground and preventing the ttys to start. I will try to fix this by making it run in the background and will let you know about the outcome.

Thanks,
I

 

[Pipeops]

Everyone,

Thanks for all of your help. It did indeed turn out that I had a service running in the foreground and preventing the tty from starting. I fixed this by making the service run in the background. It was located in the rc3.d script.

Thanks,
-I