Printable Version of Topic
Click here to view this topic in its original format
Scientific Linux Forum.org > Hardware > Unable to boot: Buffer I/O problem


Posted by: hooberman May 22 2017, 07:14 PM
Hello,

Upon bootup, I'm received the errors below which repeat continuously, and I'm unable to get a command line prompt. Any help would be appreciated!

Cheers,
Ben



end_request: I/O error, dev sda, sector 9416960
Buffer I/O error on device dm-0, logical block 1048608
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 forzen
ata3.00: failed command: WRITE DMA
ata3.00: cmd ca/00:08:48:d0:8f/00:00:00:00:00/e0 tag0 dma 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3:00: status: { DRDY }

Posted by: hooberman May 22 2017, 09:59 PM
I suspect that this is due a problem with the file system. I want to run fsck or smartmontools, but I am unable to get a command line prompt or run in recovery mode.

If I press a key to enter GRUB during bootup, I get these 3 options:

Scientific Linux CERN SLC (2.6.32-642.13.1.e16.x86_64)
Scientific Linux CERN SLC (2.6.32-642.11.1.e16.x86_64)
Scientific Linux CERN SLC (2.6.32-642.6.2.e16.x86_64)

I don't have an option there for any recovery mode, and I don't know how to get from here to force a command line prompt.

I can type "c" to get a GRUB command line, but I can't run fsck there.

Any help would be GREATLY appreciated!


Posted by: burakkucat May 23 2017, 02:24 PM
Interrupt the boot process whilst the Grub splash screen is displayed, move the "shadow bar" to select a kernel with the <UpArrow> or <DownArrow> keys, press the A key, the <Space Bar>, the S key and the <Enter> key.

The system should then boot in single user mode and ultimately display a # prompt.

Posted by: hooberman May 23 2017, 06:35 PM
Thank you for very much for the response! Unfortunately it does not resolve the problem.

When I hit the "A" key, I get a screen saying

[Minimal BASH-like line editing is supported. ]

grub append> ro root=/dev/mapper/VolGroup-lv-root rd_NO_LUKS LAN=en_US.UTF-8 rd_NO_MD rd_LVM_LV=VolGroup/lv_swap rd_LVM_LV=VolGroup/lv_root SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet crashkernel=auto

I tried hitting spacebar and S as suggested, but this brings me back to the continuously looping errors:

ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 forzen
ata3.00: failed command: WRITE DMA
ata3.00: cmd ca/00:08:48:d0:8f/00:00:00:00:00/e0 tag0 dma 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3:00: status: { DRDY }


Do you know what causes this? Is there another way to get a command line prompt?

Cheers,
Ben





Posted by: burakkucat May 24 2017, 12:14 PM
Unfortunately it appears that the physical disk has a serious fault / is virtually dead.

You may be able to recover the data by booting a LiveCD / LiveDVD (or even the installation DVD) and seeing if it is possible to access the defective disk.

'
Powered by Invision Power Board (http://www.invisionboard.com)
© Invision Power Services (http://www.invisionpower.com)