Disc errors when booting latest TC release from a CD

[vinceASPECT]

Hi,

i got the latest TC release on CD disc.

It shows errors concerning drives on any computer i try it on. Bootin errors
concerning hdb1 and things.

The computers tested are completely different machines. THe only thing
both computers have in common is they both have an internal hard drive
with windows XP installed on it. They both also have an optical drive
and rudimentary hardware. (cpu,ram,motherboard)

Nothing else is connected to either of the computers.

I will just check this again.

Why would TC show these hardware errors at boot?

thanks

Vince.

[bmarkus]

What is the version number of your latest release?

[vinceASPECT]

Hello

it is version 3.6

Vince.

[bmarkus]

Does it boot from CD and TC works? If it works, messages related to hdb1, etc are due to WIdnoes NTFS partitions and can be ignored safely.

Details on referred messages would help, for example output of dmesg after boot.

[vinceASPECT]

yes it boots fine from CD.

But does this mean every user sees these errors?

users must all have hard drives probably with windows XP or win 7 on them?...right?

VInce.

my windows installs are straight winXP installs on fresh hard drives. Nothing unusual.

have you had other people report this page or errors TC produces on it's boot screens?


thanks

VInce.

[vinceASPECT]

Actually the page of errors is referring to HDC1 also.

buffer io errors....Microsfot Joliet iso errors

these are all concerning the CD disc right?...

the disc i am using is a RE-writable 1 to 4 speed. The very first re-writable discs
and the optical drives here are old...maybe 7 years.

Vince.

[gwalther]

I get the same messages when booting from cd, on three different machines with version 3.6  I did not get these messages with version 3.3.  I even redownload 3.6 iso image and burnt it on another machine thinking it might be a burn issue, but got set of error messages.  The messages seem to be I/O issues with cdrom drive, buffer issues, etc.  I get about 20 of them, and then  Tc  finishes the boot and seems to run OK.  I had a similar issue when upgrading from 2.3 to 2.6 back  awhile ago..I reported it at that time here and it was addressed and fixed at that time...the messages this time are similar but not exactly the same.

Previous post:  http://forum.tinycorelinux.net/index.php?topic=4116.msg21546#msg21546

[Rich]

@vinceASPECT & @gwalther:
Open a terminal and type  dmesg > dmesg.txt, then post dmesg.txt on this thread. This way other
sets of eyes could see whats going on.

[Juanito]

I get a bunch of messages like this using tc3.5:

Code: [Select]

sr0: CDROM not ready.  Make sure there is a disc in the drive.
..but this is a scsi cd drive

[vinceASPECT]

ahh

so other people are experiencing this same "page of errors" on booting
of TC....?

i am surprised to see these errors on a product like Tinycore.

i will do the dmesg thing

thanks

Vince.

[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.