HD Problem don't allow boot

Questions about problems with your hardware. For example, if you the kernel hangs during boot because of an hardware failure or if you have a problem with a driver not working or missing.
BarataPT
Posts: 1
Joined: 22 Jul 2009, 11:22

HD Problem don't allow boot

Postby BarataPT » 22 Jul 2009, 11:33

Hi,

My HD has many bad sectors, from what i can tell from a chkdsk that i made.

I was trying to boot with RescueCd but every time i try to do that an error appear and don't allow to boot:

ata1: BMDA stat: 0x24
status: {DRDY ERR}
error: {UNC}

I tried altker32 and rescuecd but this error occurs in all boot options.

Is there some way to avoid this? Cause this is the last thing i want to try before i change HD :?

noboots
Posts: 2
Joined: 05 Jul 2014, 05:12

Re: HD Problem don't allow boot

Postby noboots » 05 Jul 2014, 05:17

I have this same problem as well. I can't boot to run the ddrescue command to copy the faulty HD's data to another HD.

An endless loop of:

status: {DRDY ERR}
error: {UNC}
hard resetting link
link is slow to respond, please be patient (ready=0)
softreset failed (device not ready)

or it just locks up during boot.

But I could boot into Hiren's Mini XP and run "HDD Raw Copy Tool" to raw copy the HD data to another HD.

Why can it be done in XP and not Linux? It is a Seagate HD and SeaTools can see the HD and do checks on it. But linux systemrescueCD refuses to even load.

gernot
Posts: 1127
Joined: 07 Apr 2010, 16:19

Re: HD Problem don't allow boot

Postby gernot » 05 Jul 2014, 05:36

sysrcd search all devices for sysrcd.dat.
If you boot from CD then the CD is the first probed device.

Many Bios name a boot USB stick /dev/sdb. sysrcd scan then first /dev/sda and find the files on /dev/sdb1.

You can boot if you add skipmount=/dev/sda1 skipmount=/dev/sda2 at the boot command for all freezing partitions.

Gernot

noboots
Posts: 2
Joined: 05 Jul 2014, 05:12

Re: HD Problem don't allow boot

Postby noboots » 05 Jul 2014, 21:06

My SystemRescueCD is on a YUMI usb stick.

It looks frozen at the "Loading kernel modules" line after the screen switches resolutions.

But, then it says "udevadm timeout after 180 seconds..." and continues on to fail at dmraid stuff and other things.

So I use params: dodebug nodmraid nomdadm skipmount=/dev/sda skipmount=/dev/sda1 skipmount=/dev/sda2

It still looks frozen at the "Loading Kernel modules line", but I wait longer.

In dmesg a long loop of the same error:

[ 7.463469] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 7.463475] ata2.00: BMDMA stat 0x5
[ 7.463481] ata2.00: failed command: READ DMA EXT
[ 7.463489] ata2.00: cmd 25/00:08:00:66:54/00:00:57:00:00/e0 tag 0 dma 4096 in
res 51/40:00:00:66:54/40:00:57:00:00/00 Emask 0x9 (media error)
[ 7.463494] ata2.00: status: { DRDY ERR }
[ 7.463497] ata2.00: error: { UNC }
[ 7.572539] ata2.00: configured for UDMA/133
[ 7.572561] sd 1:0:0:0: [sda] Unhandled sense code
[ 7.572565] sd 1:0:0:0: [sda]
[ 7.572568] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 7.572572] sd 1:0:0:0: [sda]
[ 7.572575] Sense Key : Medium Error [current] [descriptor]
[ 7.572580] Descriptor sense data with sense descriptors (in hex):
[ 7.572582] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 7.572593] 57 54 66 00
[ 7.572599] sd 1:0:0:0: [sda]
[ 7.572604] Add. Sense: Unrecovered read error - auto reallocate failed
[ 7.572608] sd 1:0:0:0: [sda] CDB:
[ 7.572611] Read(10): 28 00 57 54 66 00 00 00 08 00
[ 7.572621] end_request: I/O error, dev sda, sector 1465148928
[ 7.572626] Buffer I/O error on device sda, logical block 183143616
[ 7.572651] ata2: EH complete

...

[ 405.908651] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 405.908658] ata2.00: BMDMA stat 0x5
[ 405.908663] ata2.00: failed command: READ DMA EXT
[ 405.908671] ata2.00: cmd 25/00:08:e8:66:54/00:00:57:00:00/e0 tag 0 dma 4096 in
res 51/40:00:e8:66:54/40:00:57:00:00/00 Emask 0x9 (media error)
[ 405.908676] ata2.00: status: { DRDY ERR }
[ 405.908679] ata2.00: error: { UNC }
[ 406.024644] ata2.00: configured for UDMA/133
[ 406.024673] sd 1:0:0:0: [sda] Unhandled sense code
[ 406.024677] sd 1:0:0:0: [sda]
[ 406.024680] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 406.024683] sd 1:0:0:0: [sda]
[ 406.024687] Sense Key : Medium Error [current] [descriptor]
[ 406.024692] Descriptor sense data with sense descriptors (in hex):
[ 406.024694] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 406.024705] 57 54 66 e8
[ 406.024711] sd 1:0:0:0: [sda]
[ 406.024716] Add. Sense: Unrecovered read error - auto reallocate failed
[ 406.024720] sd 1:0:0:0: [sda] CDB:
[ 406.024723] Read(10): 28 00 57 54 66 e8 00 00 08 00
[ 406.024733] end_request: I/O error, dev sda, sector 1465149160
[ 406.024738] Buffer I/O error on device sda, logical block 183143645
[ 406.024770] ata2: EH complete



I guess if I knew it would timeout I would have initially waited longer at at the "Loading Kernel Modules" message, but I just was giving up and rebooting... It should be outputting something instead of looking like a locked up system even with dodebug it didn't output anything.

Eventually it booted and I got to a prompt.

gernot
Posts: 1127
Joined: 07 Apr 2010, 16:19

Re: HD Problem don't allow boot

Postby gernot » 06 Jul 2014, 05:36

Sometime, but not anytime "ctrl c" helped in this case.
You can increase the loglevel with "alt sysreq 6"

Gernot


Return to “Hardware and drivers”

Who is online

Users browsing this forum: No registered users and 2 guests