This problem is pretty odd, and I've tried everything I can think of to fix it --- I'm hoping someone can recognize it.
First, I've got an I3-530 machine I built myself, with gigabyte H55M-UD2H(running latest F10 bios), antec earthwatts 380w supply, two SATA hard drives (one seagate, one WD), and an LG DVD burner, integrated i3 graphics. Pretty standard.
I've done all my power supply calculations, and there's plenty of overall power, and plenty of power on each of the +5v and +12v rails.
I'm running Ubuntu 10.04.1 LTS. This machine has been up and running for almost a year with no real problems (outside of graphics compatibility with X and the i3 integrated graphics)
I'm rearranging my machines, am trying to move a SATA (everything in this thread is sata) 500g seagate barracuda 7200.11 drive(with SD1A latest firmware) which was windows formatted NTFS to this linux machine. The drive is perfectly readable from within windows, and mounts BY ITSELF(no other HDs in the system) within a linux live-cd environment just fine.
Whenever I attach this drive to the motherboard and try to boot up with the other two hard drives attached(+DVDRW), I get a myriad of problems. First, as soon as the machine is powered on, I start hearing a "ticking" sound coming from one of the OTHER drives. This "ticking" isn't like the hard-drive-death-ticking, but instead constant little accesses which sound like constant read-retries, separated by a pause of 1/4 second or so. All drives fsck clean.
Before I upgraded BIOS (it was F4), it would simply hang at the BIOS screen, or alternatively randomly not detect one or more of the attached drives. After the upgrade, all drives are detected, but when linux boots up, it does so INCREDIBLY SLOWLY, if I SSH in, and look at the logs, I see a bunch of drive errors.
When I look at dmesg and the like, I'm seeing a bunch of hard-drive related messages like read errors, DRDY errors, SMART command failures, media errors, unhandled sense codes, "atax: hard resetting link"s and so on.
I've tried multiple SATA cables, multiple SATA ports, (including using known working cables and ports) and the result is always the same.
It definitely reeks of some hardware incompatibility or issue. Which is why I upgraded the drive firmware and the BIOS to see if that would fix it.
While I'm not entirely sure if this practice is ok to do, I've hot-swapped harddrives before by applying sata power and data cable while the system is powered up. (offhand, I'd think an external e-sata setup would be a similar case) I normally get a few small errors, and then everything seems to come online and work just fine. In this particular case, when I attach the drive power cable (with the machine on), the other drive's power is definitely affected and the "ticking" starts IMMEDIATELY.
I've obviously tried powering everything down, attaching, and powering everything back up. It makes no difference, but the ticking starts immediately on power up (even before BIOS, I think!)
I've read my gigabyte mobo manual, and there's no mention of needing to enable ports in the BIOS, or jumpers to be set if port x is to be used, etc.
I've not tried upgrading the HD firmware of the other drives, but I'm not keen to do so because I'd rather not touch what isn't giving me problems.
It almost sounds like a drive power problem, where the seagate might be drawing too much current(maybe due to a hardware problem), and causes the overall rail voltage to drop, thereby affecting the other drive on the same power rail.
I've got the DVDRW and one harddrive on one run. And two harddrives(including the new one) on the other.
Am I going down the right path here? What else should I try?
Thanks
Keith
First, I've got an I3-530 machine I built myself, with gigabyte H55M-UD2H(running latest F10 bios), antec earthwatts 380w supply, two SATA hard drives (one seagate, one WD), and an LG DVD burner, integrated i3 graphics. Pretty standard.
I've done all my power supply calculations, and there's plenty of overall power, and plenty of power on each of the +5v and +12v rails.
I'm running Ubuntu 10.04.1 LTS. This machine has been up and running for almost a year with no real problems (outside of graphics compatibility with X and the i3 integrated graphics)
I'm rearranging my machines, am trying to move a SATA (everything in this thread is sata) 500g seagate barracuda 7200.11 drive(with SD1A latest firmware) which was windows formatted NTFS to this linux machine. The drive is perfectly readable from within windows, and mounts BY ITSELF(no other HDs in the system) within a linux live-cd environment just fine.
Whenever I attach this drive to the motherboard and try to boot up with the other two hard drives attached(+DVDRW), I get a myriad of problems. First, as soon as the machine is powered on, I start hearing a "ticking" sound coming from one of the OTHER drives. This "ticking" isn't like the hard-drive-death-ticking, but instead constant little accesses which sound like constant read-retries, separated by a pause of 1/4 second or so. All drives fsck clean.
Before I upgraded BIOS (it was F4), it would simply hang at the BIOS screen, or alternatively randomly not detect one or more of the attached drives. After the upgrade, all drives are detected, but when linux boots up, it does so INCREDIBLY SLOWLY, if I SSH in, and look at the logs, I see a bunch of drive errors.
When I look at dmesg and the like, I'm seeing a bunch of hard-drive related messages like read errors, DRDY errors, SMART command failures, media errors, unhandled sense codes, "atax: hard resetting link"s and so on.
I've tried multiple SATA cables, multiple SATA ports, (including using known working cables and ports) and the result is always the same.
It definitely reeks of some hardware incompatibility or issue. Which is why I upgraded the drive firmware and the BIOS to see if that would fix it.
While I'm not entirely sure if this practice is ok to do, I've hot-swapped harddrives before by applying sata power and data cable while the system is powered up. (offhand, I'd think an external e-sata setup would be a similar case) I normally get a few small errors, and then everything seems to come online and work just fine. In this particular case, when I attach the drive power cable (with the machine on), the other drive's power is definitely affected and the "ticking" starts IMMEDIATELY.
I've obviously tried powering everything down, attaching, and powering everything back up. It makes no difference, but the ticking starts immediately on power up (even before BIOS, I think!)
I've read my gigabyte mobo manual, and there's no mention of needing to enable ports in the BIOS, or jumpers to be set if port x is to be used, etc.
I've not tried upgrading the HD firmware of the other drives, but I'm not keen to do so because I'd rather not touch what isn't giving me problems.
It almost sounds like a drive power problem, where the seagate might be drawing too much current(maybe due to a hardware problem), and causes the overall rail voltage to drop, thereby affecting the other drive on the same power rail.
I've got the DVDRW and one harddrive on one run. And two harddrives(including the new one) on the other.
Am I going down the right path here? What else should I try?
Thanks
Keith