Tiny Core Base > TCB Talk

Disc errors when booting latest TC release from a CD

<< < (3/12) > >>

gwalther:
For me the error  messages are similar but not identical on three different machins all booting from a cdrom

This is a partial copy of my error messages:

hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
hdc: possibly failed opcode: 0xa0
end_request: I/O error, dev hdc, sector 21704
Buffer I/O error on device hdc, logical block 5426
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
hdc: possibly failed opcode: 0xa0
end_request: I/O error, dev hdc, sector 21704
Buffer I/O error on device hdc, logical block 5426
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
hdc: possibly failed opcode: 0xa0
end_request: I/O error, dev hdc, sector 21704
Buffer I/O error on device hdc, logical block 5426
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
hdc: possibly failed opcode: 0xa0

These error messages start during the boot process right after the "timezone message.." 
there are about 40 of them...
they finish.... then the boot message "Possible swap partion...."

then Tinycore boots normally

curaga:
Could you check whether they disappear with "nofstab"?

Guy:
I get similar messages when booting from a hard drive on one computer, not on all computers.

The number of error messages varies each time I boot.

I was wondering if the hard drive was failing, or it was a bug.

I have not lost any data yet.

Tiny Core runs with no problems.


hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: possibly failed opcode: 0xca
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: possibly failed opcode: 0xca
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: possibly failed opcode: 0xca
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: possibly failed opcode: 0xca

curaga:
@Guy

The others got them from cd drives, from a hard disk it would indeed indicate failing hw.

Rich:
Hi Guy
Maybe Linux is using too high a DMA setting for your drive. Try the boot code  ide-core.nodma=0.0
and see if the errors go away. Check if dmesg mentions  libata, if it does then you could try
libata.dma=0 instead.

Navigation

[0] Message Index

[#] Next page

[*] Previous page