Tiny Core Linux
Tiny Core Base => TCB Talk => Topic started by: vinceASPECT on May 25, 2011, 03:54:32 AM
-
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.
-
What is the version number of your latest release?
-
Hello
it is version 3.6
Vince.
-
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.
-
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.
-
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.
-
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
-
@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.
-
I get a bunch of messages like this using tc3.5:
sr0: CDROM not ready. Make sure there is a disc in the drive.
..but this is a scsi cd drive
-
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.
-
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
-
Could you check whether they disappear with "nofstab"?
-
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
-
@Guy
The others got them from cd drives, from a hard disk it would indeed indicate failing hw.
-
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.
-
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?
No. And no.
e.g.: amongst other, TC is ideal for many cases of diskless PC's.
-
Using boot code nofstab I do not get the error messages during the boot process, of course it does not pickup my extensions on hdb1 or my restore file.
The boot code ide-core.nodma=0.0 had no effect, still got error messages during boot process.
-
Hi gwalther
That advice was for Guy. If you want to try it use ide-core.nodma=0.1 for hdb or ide-core.nodma=1.0
for hdc or ide-core.nodma=1.1 for hdd. You can try the libata advice as written if you wish.
-
Hi:
I also have this errors during boot (from CD) when I use a machine with winxp on it.
When I tried the new 3.7 rc1 even more errors show up during boot - but at the end the
system works.
I Installed TC 3.7rc1 to HD and see- the errors disappeared completely. Strange?
-
How is cdrom connected to system? pata / sata / usb self power hub/ external powered hub / ?
What does /etc/sysconfig/cdroms display?
After boot with device error messages, are the same messages displayed. if you open an xterm and run sudo /usr/sbin/rebuildfstab ?
-
Check if dmesg mentions libata, if it does then you could try
libata.dma=0 instead
.
It does and I did. It did not work. Thanks anyway.
I am wondering if the drive needs defragmenting.
I have installed Tiny Core on another hard drive, in case that one fails.
-
Defrag is completely unrelated.
-
Hello
has this "errors on boot screen during tcl CD disc boot" been fixed?
Did most people fix it manually? by entering a bootcode?
what did they enter?
what
-
Hi
I'm new to TinyCore so I'm likely to make dumb assumptions etc - please be kind!
I've downloaded TC 3.8.3 and I'm getting the kind of error messages mentioned in this thread. This happens whether I'm using a CD to boot my laptop or the original ISO file directly to boot a VirtualBox VM. In either case the machine starts after a few repetitions of the error.
But ... when I use the installer in MultiCore to put a bootable copy on a USB external drive I get the error messages (four times each attempt so far) and the machine appears to hang.
Did anyone come up with an explanation (and a fix please) for this?
Thanks (and hello)
Jeff
-
hello,
i am not sure what has happened about this thread subject.
I also use the latest TCL release 3.8.3 on CD disc and it still has the
same error messages while booting. The messages show up on any machine
i try it on.
They said it was not seriuos error and did not stop tcl from working.
However, i was
thinking that they may have repaired it. Since this thread began there have been
2 new releases of tcl but they still both contain the error.
i believe that some people were able to avoid the errors by using
certain bootcodes but it's not clear if that was favourable.
I imagine they are too busy to fix these errors.
Also the fact that they released the new
Multicore disc means that many people will actually "install" tcl to hard disc
and so less people will be booting off CD more than once. So the tcl team may be
less inclined to weed out the disc errors.
but you say your multicore disc does not boot at all...?
V.
-
I'm getting a bit confused having tried a number of options several times with different variations on the boot: selection (tc, tci etc). I think where I am is that a physical CD booting my laptop or an ISO booting a VM in VirtualBox throws errors but then works. An installation on a USB hard drive (produced from a VM booted using the MultiCore ISO) produced the same errors but hung completely.
I've checked my hardware by downloading another small distro and installing to the USB drive - which then works fine. I'd rather use TinyCore, or even MicroCore though because I really don't need much in the way of apps at all and I want this to work as fast as possible.
Cheers
Jeff
-
hello,
Yes. I also tested my hardware and found there isn't any problem
exhibited by other similar software tools.
Microcore may be ok. i never tried microcore.
I tried multicore and it installed fine onto hard drives without errors.
(never tried it onto USB sticks)
i am not sure what you are doing with the VM...
V.
-
Installing into a VM was just part of trying out different scenarios to see what worked. Using it to install on the USB HD was simply because that way the install routine didn't have access to my laptop hard drive - I'm paranoid about messing that up!
Jeff
-
hello
same here jeff
My laptop has a special tool on it called "hyperos" which has a bootloader that is
different to all other bootloaders. (or at least it seems that way)
i am paranoid about putting any kind of new bootloader near my laptop hard drive. Which really means paranoia about installing any new OS. It's silly really, but i don't want to have to rebuild the laptop.
The "hyperOS" tool i have is suppossed to deal with both win32 and Linux at the same time but it's not clear about how it does it.
VM's is the only answer in this situation, but even doing the testing inside
a VM will take me quite a while. I must install lots of stuff and test stuff.
i have only been given one real solution for sticking tcl onto my laptop hard drive
without affecting the current hard drive bootloader. That idea came from a guy on here who makes a special remix of tcl. He explained to me how to install tcl to it's own hard drive partition without including any bootloader involvement on the hard drive..... and then just use a floppy disc to boot into that hard drive version of tcl.
His idea only really works with his remaster of tcl. I notice many people are interested
in his remaster. "The Lite Core"
However, for him to come up with this solution, i had already told him in advance about
"hyperOS" and i think he studied the bootloader system that was involved.
(also guys RICH and JASON told me how to achieve my needs and use a floppy containing the Super Grub2 tool to boot into the hard drive tcl version).....[non of the existing
hard drive bootloader was affected"
I don't understand all this stuff, but it seams that some forum people also don't fully
understand it.
My broadband DSL is going nuts here now. i am shifting 100 gigs of data per month. Extreme
data usage but i am on an unlimited data account.
As for these errors on CD disc booting of tcl. It would be great if the tcl team fixed it
because it is a bad thing to see when using a computer tool. Newcomers to tcl won't
like it at all.
V.
-
Isn't this the error of the new optical driver?? Where booting with a cd in the drive produces pages of these error messages? I just open the cd try when booting since the issue has not been resolved.
-
hello
i'm having the same problem here also, since i started
using TC last 2 weeks i just ignore it the first week because
i thought this only happens on my test machine. when i run
on my home computer, it has the same problem. so, I start
wondering. i burned another copy (this time the multicore
before it was tinycore_3.8.2) but it has also the same. errors.
i don't think it has something to do with the hard disk or previous
operating system, because i tried booting without HD, the same
error is coming. yesterday i pulled my old pentium 2 and try to
boot from there, same problem on both cd ( tiny core and multi core.
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 21088
Buffer I/O error on device hdc, logical block 5272
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 21088
Buffer I/O error on device hdc, logical block 5272
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 21088
Buffer I/O error on device hdc, logical block 5272
Buffer I/O error on device hdc, logical block 5271
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
hdc: possibly failed opcode: 0xa0
ruel
-
could this be due to the size of cd?
maybe i will try a bussiness card size cd.
ruel
-
@ gwalther and ru60hz
Try burning a disc using the directions from this link and see if that helps.
http://www.troubleshooters.com/linux/coasterless.htm
-
hello
thanks for the link,that was very informative.
i would like to try that once i got all the tools needed
like cdrecord, isoinfo.
ruel
-
glad toknow that they are both in cdrtools.tcz :)
ruel
-
hello Rich,
no more errors!
thanks so much for the advice. so, now i've learned a very important lesson.
although i used cd record instead of rawread and i downloaded the
wrong iso (accedentally downloaded the current version 3.8.4) i think
it should work also in version 3.8.2.
i have not check yet with md5sum because it's too late now in the evening.
i'll do ti tomorrow.
Again thanks,
ruel
-
Hi ru60hz
You are quite welcome, glad I could help. CD record was the right thing to use. Rawread is for
creating an ISO file from a CD.
-
You may try libburn.tcz also. It contains command line tool 'cdrskin', a 'cdrecord' replacement.
-
Yay!
I followed the points in the link regarding burning CDs reliably and I now have a CD that boots OK and a USB HDD that works too :)
I still don't understand why the downloaded ISO produced the errors when used to boot a VM but hey, it is the USB HDD that I need.
Thanks all
Jeff
-
hello
sounds like my cd burning could be the problem....it's a cd re-writable disc....and i always
burn it at the max speed setting...
hmmm
i will follow the recommendations here
thanks
V.
-
Hi cast-fish
Please let us know how it works out. It would be nice if all these CD boot errors turn out to be
nothing but CD burn related errors.
-
@ bmarkus
thanks, i'll try that.
@ Rich
yes you were right, cdrecord is the right thing, i just
misunderstood the statement. anyway i was able to
use rawread for checking md5sum :)
Anyway, back to the subject. So, it means the real
cause of the problem was because improper iso burning
due cd burner not set up correctly, incorrect speed,
lack of the -dao, -pad or padsize= arguments to the
cdrecording program used and so on which a normal user
like me don't know and maybe some people knew but not
take it seriously.
also, it means IMHO that the latest TC realease is getting better
being able to detect errors that other distribution cannot or
ignoring,
by the way, catfish, i tried also burning using a cd re-writable last night
tried to set it at lower speed but cd recorder is auto. coming back to
maximum speed of 10. i don't know why. and the result is also good.
IMHO maybe you can try again? because here, it's working fine.
thanks
ruel
-
Hi ru60hz
Just be aware that re-writable CDs have a minimum write speed as well as a maximum write speed.
-
@ Rich
thanks for reminding, mine is 2 - 10x
@ cast-fish
BTW, did you issue this command also?
'cdrecord dev=0,0,0 speed=10 blank=fast padsize=63s -pad -dao -v -eject'
i think it's needed on a cd-rewritale cd
thanks
ruel
-
Blanking a re-writable CD before burning is probably a good idea.
-
I get these errors whenever booting tc with a cd/dvd in the drive. same results but not consistently with commercial disks or cdr. am going to revisit this issue asap
-
Blanking a re-writable CD before burning is probably a good idea.
Ru and Rich,
i have not actually tried burning TCL again just yet. But i will give it a go soon because
i don't like seeing those errors.
Ru was saying that his CD recording tool always defaults into the max speed
that a CD RW disc will support. Mine is similar and i am not sure if that speed
can be altered.
I will have to burn the CD from the Linux desktop and issue the command that
Ru has mentioned in this thread.
It looks pretty likely that my situation is similar to others in this thread...it's a badly
burned CDRW disc.
Having said this, i have been burning distros for 8 years and this has never happened
before ever. Even with this same hardware, but ofcourse, different media discs each time.
Just a note on this kind of topic that i am sure you are all aware of. Cheap blank CD discs can loose
the optical burn for no reason. It tends to happen after leaving the discs in darkness for a few weeks. They
gradually loose the optical burn and eventually fail to run. Externally the disc looks perfect without any
scratches or such like. You can't guess it's a faulty disc....you just eventually realize. This can be
tricky when you have already been successfully using the said "burned disc" for weeks.
V
-
Hi cast-fish
Just a note on this kind of topic that i am sure you are all aware of. Cheap blank CD discs can loose
the optical burn for no reason. It tends to happen after leaving the discs in darkness for a few weeks.
Nonsense. CDs are not sensitive to the presence or absence of light. Temperature extremes might
cause you problems. Heat generated by the LASER beam in your CD drive changes the reflectivity
in the disc by altering the color at the points you are writing to. So if a blank disc has all zeros, the
LASER heats the points where you want ones. CDRWs are the same except power levels, heating,
and cooling time are more critical. It is because of this last point that CDRWs also have a minimum
write speed. I have some 24x CDRWs, the minimum write speed listed on the package is 16x.
-
in that case Rich, is it possible that a CDr disc can have scratches
that are not visible by the naked eye, but scratches that can make the disc optically non readable?
V.
-
During last 20 years I have never seen CD's degrading in time, but have seen faulty, unrealible discs due to faulty CD writers having very short lifetime.
-
Hi cast-fish
I can't rule out the possibility, but I think it's unlikely. I had an old CD drive that was a bit hit and miss
when it came to burning CDs. After opening it up and carefully cleaning the LASER diode with cotton
swabs and alcohol it behaved normally again.
[EDIT]: Before the cleaning it was also a bit touchy about booting CDs.
-
Hello,
ah, so are you saying that an "older burning drive" could potentially begin to start creating
faulty burned discs and those discs "may or may not" continue to be effectively "readable"
in that drive...?
is there also a case, where a CDr disc that is burned in drive "a" also gets perfect
"reads" in drive "a" but may not be readable in other drives?
V.
-
yes rich
this is a hunch here. (could be gobley -gook ....but)
is it possible that "burning drives", like you say, can be temperamental.
Say for example, you burn a CDr disc with a Linux OS. Right away you
start reading that disc in the same drive and things are fine.
Weeks go by where you don't read that Disc. But also, you don't use the drive
to do any burning, just reading of other discs. The heads in the drive get dirty.
Later on you try the same Linux disc in the same drive and it fails to be "readable". You throw
the disc away and immediately "burn" a new disc using the same drive. But the burning process
somehow cleans the internal drive heads...so the drive now correctly reads the recently
burned disc.
V.
-
Hi cast-fish
In response to Reply#51
Yes and yes. If the LASER is weak or dirty it may not generate enough heat to write the bits properly.
By slowing the writing speed you can sometimes work around this, at least for a while. That's because
the disc spins slower and the LASER has more time to heat each bit.
In response to Reply#52
If the burn is marginal, anything can happen. A one may look like a one or a zero from one day to
another or one drive to another.
I think we've been off topic long enough on the inner workings of CD drives.
-
I think we've been off topic long enough on the inner workings of CD drives.
@Rich: perhaps this thread could be retitled to "inner workings of optical drives"
(since the current title is rather generic/non-descript)
sharing is caring
-
Hi gadget42
Since the point of the thread was not about the inner workings of optical drives, I came up with this instead.