eSATA drive won't mount. Wrong data rate ?

[linux guy]

Some of this was previously discussed in the "External eSATA drive
doesn't fdisk properly ? F8 eSATA hotplug ?" thread.

Computer: HP hdx9494.  T8100 processor, 4 GB RAM, running 32 bit Fedora
8.

Drive: Azio SATA/USB enclosure, Hitachi 500GB 3.5" hard drive.   The
drive works excellent under USB access.

$ uname -a
Linux localhost.localdomain 2.6.26.5-28.fc8 #1 SMP Sat Sep 20 09:32:58
EDT 2008 i686 i686 i386 GNU/Linux

If I shut the machine off, power up the external drive and then boot the
computer, I get the following in /var/logs/messages:

Oct  2 11:10:37 localhost kernel:  sdb: sdb1
Oct  2 11:10:37 localhost kernel: sd 2:0:0:0: [sdb] Attached SCSI disk
Oct  2 11:10:37 localhost kernel: ACPI: PCI Interrupt 0000:20:00.0[A] ->
GSI 19 (level, low) -> IRQ 19
Oct  2 11:10:37 localhost kernel: scsi3 : sata_sil24
Oct  2 11:10:37 localhost kernel: ata4: SATA max UDMA/100 host
m128@0xe0100000 port 0xe0102000 irq 19
Oct  2 11:10:37 localhost kernel: ata4: SATA link up 1.5 Gbps (SStatus
113 SControl 0)
Oct  2 11:10:37 localhost kernel: ata4.00: ATA-8: Hitachi
HDP725050GLA360, GM4OA52A, max UDMA/133
Oct  2 11:10:37 localhost kernel: ata4.00: 976773168 sectors, multi 0:
LBA48 NCQ (depth 31/32)
Oct  2 11:10:37 localhost kernel: ata4.00: configured for UDMA/100
Oct  2 11:10:37 localhost kernel: scsi 3:0:0:0: Direct-Access     ATA
Hitachi HDP72505 GM4O PQ: 0 ANSI: 5
Oct  2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] 976773168 512-byte
hardware sectors (500108 MB)
Oct  2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] Write Protect is off
Oct  2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] Write cache:
enabled, read cache: enabled, doesn't support DPO or FUA
Oct  2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] 976773168 512-byte
hardware sectors (500108 MB)
Oct  2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] Write Protect is off
Oct  2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] Write cache:
enabled, read cache: enabled, doesn't support DPO or FUA
Oct  2 11:10:37 localhost kernel:  sdc: sdc1
Oct  2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] Attached SCSI disk
Oct  2 11:10:37 localhost kernel: ACPI: PCI Interrupt 0000:00:1f.1[A] ->
GSI 16 (level, low) -> IRQ 16
Oct  2 11:10:37 localhost kernel: scsi4 : ata_piix
Oct  2 11:10:37 localhost kernel: scsi5 : ata_piix
Oct  2 11:10:37 localhost kernel: ata5: PATA max UDMA/100 cmd 0x1f0 ctl
0x3f6 bmdma 0x70a0 irq 14
Oct  2 11:10:37 localhost kernel: ata6: PATA max UDMA/100 cmd 0x170 ctl
0x376 bmdma 0x70a8 irq 15
Oct  2 11:10:37 localhost kernel: ata5.00: ATAPI: Optiarc BD ROM
BC-5500A, 1.86, max MWDMA2

If I run hwbrowser and look at it, it shows the drive under sdc with the
correct geometry and such, but without a partition, ie no sdc1 or file
sizes.

So it appears to be recognized by the computer on some level.

However, if I mount it with "mount /dev/sdc1 temp" or "mount
-text3 /dev/sdc1 temp", the console will hang for a minute or so before
returning without any errors.  However, the drive is unusable (ls
returns an empty directory) and /var/logs/messages shows the following:

Oct  2 11:16:49 localhost kernel: ata4.00: qc timeout (cmd 0xec)
Oct  2 11:16:49 localhost kernel: ata4.00: failed to IDENTIFY (I/O
error, err_mask=0x4)
Oct  2 11:16:49 localhost kernel: ata4.00: revalidation failed
(errno=-5)
Oct  2 11:16:49 localhost kernel: ata4: failed to recover some devices,
retrying in 5 secs
Oct  2 11:16:54 localhost kernel: ata4: hard resetting link
Oct  2 11:16:56 localhost kernel: ata4: SATA link up 1.5 Gbps (SStatus
113 SControl 0)
Oct  2 11:17:26 localhost kernel: ata4.00: qc timeout (cmd 0xec)
Oct  2 11:17:26 localhost kernel: ata4.00: failed to IDENTIFY (I/O
error, err_mask=0x4)
Oct  2 11:17:26 localhost kernel: ata4.00: revalidation failed
(errno=-5)
Oct  2 11:17:26 localhost kernel: ata4: failed to recover some devices,
retrying in 5 secs
Oct  2 11:17:31 localhost kernel: ata4: hard resetting link
Oct  2 11:17:33 localhost kernel: ata4: SATA link up 1.5 Gbps (SStatus
113 SControl 0)
Oct  2 11:18:03 localhost kernel: ata4.00: qc timeout (cmd 0xec)
Oct  2 11:18:03 localhost kernel: ata4.00: failed to IDENTIFY (I/O
error, err_mask=0x4)
Oct  2 11:18:03 localhost kernel: ata4.00: revalidation failed
(errno=-5)
Oct  2 11:18:03 localhost kernel: ata4.00: disabled
Oct  2 11:18:04 localhost kernel: ata4: hard resetting link
Oct  2 11:18:06 localhost kernel: ata4: SATA link up 1.5 Gbps (SStatus
113 SControl 0)
Oct  2 11:18:06 localhost kernel: ata4: EH complete
Oct  2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Oct  2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
sector 976767935
Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 488383936
Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 488383937
Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 488383938
Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 488383939
Oct  2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Oct  2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
sector 976767935
Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 488383936
Oct  2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Oct  2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
sector 976767937
Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 488383937
Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 488383938
Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 488383939
Oct  2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Oct  2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
sector 63
Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 0
Oct  2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Oct  2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
sector 65
Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
logical block 1
Oct  2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Oct  2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
sector 63
Oct  2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Oct  2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
sector 65
Oct  2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Oct  2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
sector 65
Oct  2 11:18:06 localhost kernel: hfs: unable to find HFS+ superblock
Oct  2 11:23:03 localhost kernel: sd 3:0:0:0: [sdc] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Oct  2 11:23:03 localhost kernel: end_request: I/O error, dev sdc,
sector 65
Oct  2 11:23:03 localhost kernel: EXT3-fs: unable to read superblock

One thing that sticks out for me in all this is the SATA data rate.
Both the computer and the drive are supposed to be 3.0Gb/s devices.  Yet
the driver wants to connect at 1.5 Gbps.

The Serial ATA Controller is listed as ahci in hwbrowser.

# /sbin/lsmod | grep sat
sata_sil24             16069  0
libata                131937  3 ata_piix,sata_sil24,ahci

How should I proceed to get my external drive working ?

Thanks

[Craig White]

On Thu, 2008-10-02 at 11:34 -0400, Linuxguy123 wrote:
> Some of this was previously discussed in the "External eSATA drive
> doesn't fdisk properly ? F8 eSATA hotplug ?" thread.
>
> Computer: HP hdx9494.  T8100 processor, 4 GB RAM, running 32 bit Fedora
> 8.
>
> Drive: Azio SATA/USB enclosure, Hitachi 500GB 3.5" hard drive.   The
> drive works excellent under USB access.
>
> $ uname -a
> Linux localhost.localdomain 2.6.26.5-28.fc8 #1 SMP Sat Sep 20 09:32:58
> EDT 2008 i686 i686 i386 GNU/Linux
>
> If I shut the machine off, power up the external drive and then boot the
> computer, I get the following in /var/logs/messages:
>
> Oct  2 11:10:37 localhost kernel:  sdb: sdb1
> Oct  2 11:10:37 localhost kernel: sd 2:0:0:0: [sdb] Attached SCSI disk
> Oct  2 11:10:37 localhost kernel: ACPI: PCI Interrupt 0000:20:00.0[A] ->
> GSI 19 (level, low) -> IRQ 19
> Oct  2 11:10:37 localhost kernel: scsi3 : sata_sil24
> Oct  2 11:10:37 localhost kernel: ata4: SATA max UDMA/100 host
> m128@0xe0100000 port 0xe0102000 irq 19
> Oct  2 11:10:37 localhost kernel: ata4: SATA link up 1.5 Gbps (SStatus
> 113 SControl 0)
> Oct  2 11:10:37 localhost kernel: ata4.00: ATA-8: Hitachi
> HDP725050GLA360, GM4OA52A, max UDMA/133
> Oct  2 11:10:37 localhost kernel: ata4.00: 976773168 sectors, multi 0:
> LBA48 NCQ (depth 31/32)
> Oct  2 11:10:37 localhost kernel: ata4.00: configured for UDMA/100
> Oct  2 11:10:37 localhost kernel: scsi 3:0:0:0: Direct-Access     ATA
> Hitachi HDP72505 GM4O PQ: 0 ANSI: 5
> Oct  2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] 976773168 512-byte
> hardware sectors (500108 MB)
> Oct  2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] Write Protect is off
> Oct  2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] Write cache:
> enabled, read cache: enabled, doesn't support DPO or FUA
> Oct  2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] 976773168 512-byte
> hardware sectors (500108 MB)
> Oct  2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] Write Protect is off
> Oct  2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] Write cache:
> enabled, read cache: enabled, doesn't support DPO or FUA
> Oct  2 11:10:37 localhost kernel:  sdc: sdc1
> Oct  2 11:10:37 localhost kernel: sd 3:0:0:0: [sdc] Attached SCSI disk
> Oct  2 11:10:37 localhost kernel: ACPI: PCI Interrupt 0000:00:1f.1[A] ->
> GSI 16 (level, low) -> IRQ 16
> Oct  2 11:10:37 localhost kernel: scsi4 : ata_piix
> Oct  2 11:10:37 localhost kernel: scsi5 : ata_piix
> Oct  2 11:10:37 localhost kernel: ata5: PATA max UDMA/100 cmd 0x1f0 ctl
> 0x3f6 bmdma 0x70a0 irq 14
> Oct  2 11:10:37 localhost kernel: ata6: PATA max UDMA/100 cmd 0x170 ctl
> 0x376 bmdma 0x70a8 irq 15
> Oct  2 11:10:37 localhost kernel: ata5.00: ATAPI: Optiarc BD ROM
> BC-5500A, 1.86, max MWDMA2
>
> If I run hwbrowser and look at it, it shows the drive under sdc with the
> correct geometry and such, but without a partition, ie no sdc1 or file
> sizes.
>
> So it appears to be recognized by the computer on some level.
>
> However, if I mount it with "mount /dev/sdc1 temp" or "mount
> -text3 /dev/sdc1 temp", the console will hang for a minute or so before
> returning without any errors.  However, the drive is unusable (ls
> returns an empty directory) and /var/logs/messages shows the following:
>
> Oct  2 11:16:49 localhost kernel: ata4.00: qc timeout (cmd 0xec)
> Oct  2 11:16:49 localhost kernel: ata4.00: failed to IDENTIFY (I/O
> error, err_mask=0x4)
> Oct  2 11:16:49 localhost kernel: ata4.00: revalidation failed
> (errno=-5)
> Oct  2 11:16:49 localhost kernel: ata4: failed to recover some devices,
> retrying in 5 secs
> Oct  2 11:16:54 localhost kernel: ata4: hard resetting link
> Oct  2 11:16:56 localhost kernel: ata4: SATA link up 1.5 Gbps (SStatus
> 113 SControl 0)
> Oct  2 11:17:26 localhost kernel: ata4.00: qc timeout (cmd 0xec)
> Oct  2 11:17:26 localhost kernel: ata4.00: failed to IDENTIFY (I/O
> error, err_mask=0x4)
> Oct  2 11:17:26 localhost kernel: ata4.00: revalidation failed
> (errno=-5)
> Oct  2 11:17:26 localhost kernel: ata4: failed to recover some devices,
> retrying in 5 secs
> Oct  2 11:17:31 localhost kernel: ata4: hard resetting link
> Oct  2 11:17:33 localhost kernel: ata4: SATA link up 1.5 Gbps (SStatus
> 113 SControl 0)
> Oct  2 11:18:03 localhost kernel: ata4.00: qc timeout (cmd 0xec)
> Oct  2 11:18:03 localhost kernel: ata4.00: failed to IDENTIFY (I/O
> error, err_mask=0x4)
> Oct  2 11:18:03 localhost kernel: ata4.00: revalidation failed
> (errno=-5)
> Oct  2 11:18:03 localhost kernel: ata4.00: disabled
> Oct  2 11:18:04 localhost kernel: ata4: hard resetting link
> Oct  2 11:18:06 localhost kernel: ata4: SATA link up 1.5 Gbps (SStatus
> 113 SControl 0)
> Oct  2 11:18:06 localhost kernel: ata4: EH complete
> Oct  2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> Oct  2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
> sector 976767935
> Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
> logical block 488383936
> Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
> logical block 488383937
> Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
> logical block 488383938
> Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
> logical block 488383939
> Oct  2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> Oct  2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
> sector 976767935
> Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
> logical block 488383936
> Oct  2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> Oct  2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
> sector 976767937
> Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
> logical block 488383937
> Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
> logical block 488383938
> Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
> logical block 488383939
> Oct  2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> Oct  2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
> sector 63
> Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
> logical block 0
> Oct  2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> Oct  2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
> sector 65
> Oct  2 11:18:06 localhost kernel: Buffer I/O error on device sdc1,
> logical block 1
> Oct  2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> Oct  2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
> sector 63
> Oct  2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> Oct  2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
> sector 65
> Oct  2 11:18:06 localhost kernel: sd 3:0:0:0: [sdc] Result:
> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> Oct  2 11:18:06 localhost kernel: end_request: I/O error, dev sdc,
> sector 65
> Oct  2 11:18:06 localhost kernel: hfs: unable to find HFS+ superblock
> Oct  2 11:23:03 localhost kernel: sd 3:0:0:0: [sdc] Result:
> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> Oct  2 11:23:03 localhost kernel: end_request: I/O error, dev sdc,
> sector 65
> Oct  2 11:23:03 localhost kernel: EXT3-fs: unable to read superblock
>
> One thing that sticks out for me in all this is the SATA data rate.
> Both the computer and the drive are supposed to be 3.0Gb/s devices.  Yet
> the driver wants to connect at 1.5 Gbps.
>
> The Serial ATA Controller is listed as ahci in hwbrowser.
>
> # /sbin/lsmod | grep sat
> sata_sil24             16069  0
> libata                131937  3 ata_piix,sata_sil24,ahci
>
> How should I proceed to get my external drive working ?

----
what do you get when you (as root) do

fdisk -l /dev/sdc

I have no knowledge that eSATA is a hot-plug technology as the only
experience I have had with eSATA was with an Explorer 8300HD cable box
and that clearly wasn't hot plug but required a full power off to
connect or disconnect.

Craig

[linux guy]

On Thu, 2008-10-02 at 10:44 -0700, Craig White wrote:
> > How should I proceed to get my external drive working ?
>
> what do you get when you (as root) do
>
> fdisk -l /dev/sdc

It returns nothing.

It works for other drives.

# /sbin/fdisk -l /dev/sdb

Disk /dev/sdb: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xc2deb5a2

Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       38913   312568641   83  Linux

[Craig White]

On Thu, 2008-10-02 at 12:55 -0400, Linuxguy123 wrote:
> On Thu, 2008-10-02 at 10:44 -0700, Craig White wrote:
> > > How should I proceed to get my external drive working ?
> >
> > what do you get when you (as root) do
> >
> > fdisk -l /dev/sdc
>
> It returns nothing.
>
> It works for other drives.
>
> # /sbin/fdisk -l /dev/sdb
>
> Disk /dev/sdb: 320.0 GB, 320072933376 bytes
> 255 heads, 63 sectors/track, 38913 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Disk identifier: 0xc2deb5a2
>
> Device Boot      Start         End      Blocks   Id  System
> /dev/sdb1               1       38913   312568641   83  Linux

----
perhaps try booting a different kernel

I just don't know of eSATA is supported but I sort of expected that it
would be supported.

Craig

[Fred Silsbee]

--- On Thu, 10/2/08, Craig White  wrote:
> From: Craig White 
> Subject: Re: eSATA drive won't mount.  Wrong data rate ?
> To: "Community assistance, encouragement, and advice for using Fedora." 
> Date: Thursday, October 2, 2008, 7:09 PM
> On Thu, 2008-10-02 at 12:55 -0400, Linuxguy123 wrote:
> > On Thu, 2008-10-02 at 10:44 -0700, Craig White wrote:
> > > > How should I proceed to get my external
>
> drive working ?
> > > what do you get when you (as root) do
> > >
> > > fdisk -l /dev/sdc
> >
> > It returns nothing.
> >
> > It works for other drives.
> >
> > # /sbin/fdisk -l /dev/sdb
> >
> > Disk /dev/sdb: 320.0 GB, 320072933376 bytes
> > 255 heads, 63 sectors/track, 38913 cylinders
> > Units = cylinders of 16065 * 512 = 8225280 bytes
> > Disk identifier: 0xc2deb5a2
> >
> > Device Boot      Start         End      Blocks   Id
>
> System
> > /dev/sdb1               1       38913   312568641   83
> Linux
>
> perhaps try booting a different kernel
>
> I just don't know of eSATA is supported but I sort of
> expected that it
> would be supported.
>
> Craig

see "man fdisk" bugs section other versions avail
> -- 
> fedora-list mailing list
> [e-mail]
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines:
> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Steve Siegfried]

Linuxguy123 wrote:
<SNIP>
> One thing that sticks out for me in all this is the SATA data rate.
> Both the computer and the drive are supposed to be 3.0Gb/s devices.  Yet
> the driver wants to connect at 1.5 Gbps.
>
> The Serial ATA Controller is listed as ahci in hwbrowser.
>
> # /sbin/lsmod | grep sat
> sata_sil24             16069  0
> libata                131937  3 ata_piix,sata_sil24,ahci
>
> How should I proceed to get my external drive working ?

Check the manual that came with your motherboard (or the hardware manual
that came with your computer).  3.0GB/s SATA is otherwise known as "SATA
II", "SATA 3.0" and/or "SATA/300".  If it just sez "SATA", it's 1.5Gbs 
"SATA-I" and you either need a controller card or a new motherboard to
use the 3.0GB/s drives.  Sadly some SATA-II drives don't automagically
downshift to SATA-I mode nicely... you may have one of these.

Found out the hard way when I bought 2 VelociRaptor drives'idly,

-S

[linux guy]

On Thu, 2008-10-02 at 16:45 -0500, Steve Siegfried wrote:
> Linuxguy123 wrote:
>
> <SNIP>
> > 
> > One thing that sticks out for me in all this is the SATA data rate.
> > Both the computer and the drive are supposed to be 3.0Gb/s devices.  Yet
> > the driver wants to connect at 1.5 Gbps.
> > 
> > The Serial ATA Controller is listed as ahci in hwbrowser.
> > 
> > # /sbin/lsmod | grep sat
> > sata_sil24             16069  0
> > libata                131937  3 ata_piix,sata_sil24,ahci
> > 
> > 
> > How should I proceed to get my external drive working ?
> >
>
> Check the manual that came with your motherboard (or the hardware manual
> that came with your computer).  3.0GB/s SATA is otherwise known as "SATA
> II", "SATA 3.0" and/or "SATA/300".  If it just sez "SATA", it's 1.5Gbs 
> "SATA-I" and you either need a controller card or a new motherboard to
> use the 3.0GB/s drives.  Sadly some SATA-II drives don't automagically
> downshift to SATA-I mode nicely... you may have one of these.

The shiny HP advertising brochure says "eSATA Port.  Blazing next
generation 3Gb/sec data transfer to an external HDD."

So unless the marketing department got it wrong and the engineers never
read the brochures, its probably a 3Gb/sec port.  I think that Linux
somehow gets the speed wrong.

Is it time to report this as a bug ?

LG

[Craig White]

On Thu, 2008-10-02 at 16:07 -0400, Linuxguy123 wrote:
> On Thu, 2008-10-02 at 16:45 -0500, Steve Siegfried wrote:
> > Linuxguy123 wrote:
> >
> > <SNIP>
> > > 
> > > One thing that sticks out for me in all this is the SATA data rate.
> > > Both the computer and the drive are supposed to be 3.0Gb/s devices.  Yet
> > > the driver wants to connect at 1.5 Gbps.
> > > 
> > > The Serial ATA Controller is listed as ahci in hwbrowser.
> > > 
> > > # /sbin/lsmod | grep sat
> > > sata_sil24             16069  0
> > > libata                131937  3 ata_piix,sata_sil24,ahci
> > > 
> > > 
> > > How should I proceed to get my external drive working ?
> > >
> >
> > Check the manual that came with your motherboard (or the hardware manual
> > that came with your computer).  3.0GB/s SATA is otherwise known as "SATA
> > II", "SATA 3.0" and/or "SATA/300".  If it just sez "SATA", it's 1.5Gbs 
> > "SATA-I" and you either need a controller card or a new motherboard to
> > use the 3.0GB/s drives.  Sadly some SATA-II drives don't automagically
> > downshift to SATA-I mode nicely... you may have one of these.
>
> The shiny HP advertising brochure says "eSATA Port.  Blazing next
> generation 3Gb/sec data transfer to an external HDD."
>
> So unless the marketing department got it wrong and the engineers never
> read the brochures, its probably a 3Gb/sec port.  I think that Linux
> somehow gets the speed wrong.
>
> Is it time to report this as a bug ?

----
Is it a type II cable? Is it a type II interface in your 'combo' hard
drive case?

Craig

[linux guy]

On Thu, 2008-10-02 at 15:14 -0700, Craig White wrote:
> > Is it time to report this as a bug ?
>
> Is it a type II cable? Is it a type II interface in your 'combo' hard
> drive case?

Here is the drive.  It came with an eSATA cable.   It says up to 3
Gb/sec.
http://www.aziocorp.com/product_detail/ENC311SU31.php

[linux guy]

I was playing around with this drive today, hooking and unhooking it
from the eSATA port.   Somehow it doesn't work with the USB port
anymore.  fdisk /dev/sdc doesn't see a drive anymore.

Luckily the drive didn't have any data on it.

[Fred Silsbee]

--- On Thu, 10/2/08, Linuxguy123  wrote:
> From: Linuxguy123 
> Subject: Re: eSATA drive won't mount.  Wrong data rate ?
> To: "Community assistance, encouragement, and advice for using Fedora." 
> Date: Thursday, October 2, 2008, 11:27 PM
> I was playing around with this drive today, hooking and
> unhooking it
> from the eSATA port.   Somehow it doesn't work with the
> USB port
> anymore.  fdisk /dev/sdc doesn't see a drive anymore.
>
> Luckily the drive didn't have any data on it.

Earlier you gave the site for the drive maker but I didn't save it.

Where was the drive made?

10 years ago I got stuck with a 1 gig SparQ cartridge drive from a company named SyQuest that went out of business.
> -- 
> fedora-list mailing list
> [e-mail]
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines:
> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[linux guy]

On Thu, 2008-10-02 at 18:47 -0700, Fred Silsbee wrote:
> --- On Thu, 10/2/08, Linuxguy123  wrote:
> > From: Linuxguy123 
> > Subject: Re: eSATA drive won't mount.  Wrong data rate ?
> > To: "Community assistance, encouragement, and advice for using Fedora." 
> > Date: Thursday, October 2, 2008, 11:27 PM
> > I was playing around with this drive today, hooking and
> > unhooking it
> > from the eSATA port.   Somehow it doesn't work with the
> > USB port
> > anymore.  fdisk /dev/sdc doesn't see a drive anymore.
> >
> > Luckily the drive didn't have any data on it.
>
> Earlier you gave the site for the drive maker but I didn't save it.

This is the enclosure its mounted in.
http://www.aziocorp.com/product_detail/ENC311SU31.php

The drive itself is a 500GB Hitachi.
> Where was the drive made?

The enclosure is made by AZIO.
> 10 years ago I got stuck with a 1 gig SparQ cartridge drive from a company named SyQuest that went out of business.

They are still in business as far as I know.