SATA2 HD Ticks/Squeaks?

[~LoKe]

To start; my operating system is Linux (Ubuntu) and not windows.

I'm trying to get this new Seagate SATA2 drive up and running, but once plugged in and connected, it either ticks or squeaks when I'm trying to boot up. I don't know if this is normal or not. My BIOS is not detecting the SATA2 drive.

Is there any way I can find out if it's a problem with the drive, my motherboard/BIOS or otherwise? I don't have another computer to test the drive in.

I see no /sda in /dev, either.
Edit/Delete Message

 

[unhappy_mage]

What sata controller are you using? Is there anything in 'dmesg' about the drive? What power supply are you using, and what other hardware? Does "fdisk -l" show anything? Do you have the MAKEDEV script?

 

[~LoKe]

Don't know what controlled I'm using, how can I check?

DMesg mentions SATA...

17179575.372000] SCSI subsystem initialized
[17179575.376000] libata version 1.20 loaded.
[17179575.376000] sata_via 0000:00:0f.0: version 1.1
[17179575.376000] ACPI: PCI Interrupt 0000:00:0f.0 -> GSI 20 (level, low) -> IRQ 209
[17179575.376000] PCI: Via IRQ fixup for 0000:00:0f.0, from 11 to 1
[17179575.376000] sata_via 0000:00:0f.0: routed to hard irq line 1
[17179575.376000] ata1: SATA max UDMA/133 cmd 0xEC00 ctl 0xE882 bmdma 0xE400 irq 209
[17179575.376000] ata2: SATA max UDMA/133 cmd 0xE800 ctl 0xE482 bmdma 0xE408 irq 209
[17179575.544000] scsi0 : sata_via
[17179575.712000] scsi1 : sata_via

loke@x04d:~$ dmesg|grep sata && dmesg|grep SATA
[17179575.376000] sata_via 0000:00:0f.0: version 1.1
[17179575.376000] sata_via 0000:00:0f.0: routed to hard irq line 1
[17179575.544000] scsi0 : sata_via
[17179575.712000] scsi1 : sata_via
[17179575.376000] ata1: SATA max UDMA/133 cmd 0xEC00 ctl 0xE882 bmdma 0xE400 irq 209
[17179575.376000] ata2: SATA max UDMA/133 cmd 0xE800 ctl 0xE482 bmdma 0xE408 irq 209

I've got a 350W Titan Power Supply.

Other Hardware...
Intel Core 2 Duo, E6300
ECS P4M890T-M2
XFX GeForce 7300 GT
1GB Corsair RAM
20GB WD IDE Drive
30GB WD IDE Drive

fdisk -l says nothing about a sata drive (sda, sdb, etc.), just IDE (hda, hdb).

I don't think I have the "MAKEDEV" script.
EDIT: Guess I do...

loke@x04d:~$ sudo /etc/init.d/makedev restart

Thanks for helping!

 

[unhappy_mage]

Try "cd /dev; MAKEDEV sda". And make sure the drive is plugged into the Via sata ports, if you've got more than one set. Since those seem to be working, might as well use 'em.

 

[~LoKe]

loke@x04d:/dev$ sudo MAKEDEV sda
udev active, devices will be created in /dev/.static/dev/
loke@x04d:/dev$ sudo fdisk -l

Disk /dev/hda: 30.0 GB, 30020272128 bytes
255 heads, 63 sectors/track, 3649 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 1 3649 29310561 83 Linux

Disk /dev/hdb: 20.0 GB, 20020396032 bytes
255 heads, 63 sectors/track, 2434 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdb1 * 1 2330 18715693+ 83 Linux
/dev/hdb2 2331 2434 835380 5 Extended
/dev/hdb5 2331 2434 835348+ 82 Linux swap / Solaris

Looking at my board and its manual, I've only got 2 SATA ports, and the drive is plugged into SATA1.

 

[~LoKe]

Any other ideas?

EDIT: I booted up a Windows installation CD and it didn't detect the SATA drive, either. It's gotta be dead.

 

[unhappy_mage]

Oh, I misread your first post. I thought the BIOS *was* detecting the drive.

Try connecting the 1.5gbps jumper, if there is one on that drive. Make sure the connections are snug. Is the drive spinning up?

 

[~LoKe]

Oh, I misread your first post. I thought the BIOS *was* detecting the drive.

Try connecting the 1.5gbps jumper, if there is one on that drive. Make sure the connections are snug. Is the drive spinning up?

According to the label on the hard drive, the jumper was already on the 1.5Gb/s pins (the two on the right). I've right with the jumper, without it, and with it on the left instead and the result was always the same.

Yep. it spins up when I boot and it attempts to detect the disks. The boot hangs when the drive is attached, but it eventually goes through and didn't detect the drive.