Seagate 7200.8 drive. Well, all went well for a week or two, but then the drive
began to make strange noises, and i got some weird messages
from dmesg output...
I feared a drive failure, so I made a full Seagate diagnoses
of the disk, but no errors...
Well, maybe I got bad luck with that drive, so I decided to
get another one. I took another Seagate, 250Go, 7200.10 this time.
I put this new Seagate (let's call it S_new, the other being
S_old) to the first connector of the Sil 3112a chip, and put
the "old" one on the second connector : thus I have sda for
S_new, and sdb for S_old...
What is really surprising, is that i still got issues with
sda, but none with sdb... so the believed faulty drive is not,
as i got no dmesg errors from sdb...
thus i suspect either a faulty controller, or a problem with
the driver (sata_sil) i use...(or even something with IRQ as I
don't understand anything with IRQ...)
I tried to put both disks numbers in the "blacklist" in
sata_sil.c, but apart from a degraded speed, it didn't do
anything...
The other observation I made, was that these problems happens
only when the computer is still "cold" : I mean, after an hour
or two, no problem with this... and even if i reboot (I really
mean reboot, not halt and restart : when the power still turns
on), i got no problem...
Well since I use my computer for Desktop, it really is an
issue for me at the moment, especially when the disk is making
a noise...
I'm on Linux for about 2 or 3 years now, under Debian/SID,
with kernel 2.6.17.13 from kernel.org (self-compiled)
Here is the output of dmesg if it helps...
I can provide any information you would find useful, even make
some tests, but if you could be not too technical, that would
really be great, as I'm a real noob with Hardware problems...
Any help/links/infos/hints would really be appreciated!
I've already googled a lot and found that Seagate/sil3112a is
a problematic couple, but i didn't find any solution for that...
I'll try this evening with an older kernel (if you have any
suggestion for a kernel version...) to see if it's not related
to a kernel upgrade...
EXT3-fs: unable to read superblock
ata1: command 0xec timeout, stat 0xd0 host_stat 0x0
ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ
0xb/47/00
ata1: status=0xd0 { Busy }
ata1: command 0xec timeout, stat 0xd0 host_stat 0x0
ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ
0xb/47/00
ata1: status=0xd0 { Busy }
ata1: command 0xb0 timeout, stat 0xd0 host_stat 0x0
ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ
0xb/47/00
ata1: status=0xd0 { Busy }
ata1: command 0xb0 timeout, stat 0xd0 host_stat 0x0
ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ
0xb/47/00
ata1: status=0xd0 { Busy }
ata1: command 0xec timeout, stat 0xd0 host_stat 0x0
ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ
0xb/47/00
ata1: status=0xd0 { Busy }
ata1: command 0xec timeout, stat 0xd0 host_stat 0x0
ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ
0xb/47/00
ata1: status=0xd0 { Busy }
ata1: command 0xb0 timeout, stat 0xd0 host_stat 0x0
ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ
0xb/47/00
ata1: status=0xd0 { Busy }
ata1: command 0xb0 timeout, stat 0xd0 host_stat 0x0
ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ
0xb/47/00
ata1: status=0xd0 { Busy }