FedoraForum.org - Fedora Support Forums and Community
Results 1 to 13 of 13
  1. #1
    Join Date
    Oct 2011
    Location
    UK
    Posts
    469

    Help my sata drive runs at udma33

    Because of other issues I had turned on all the kernel messages on boot up and discovered that my SATA drives were complaining that they have 40-wire cables and would run at UDMA33. I am running F17 fully updated.

    Code:
    ata9.01: ATA-8: Hitachi HDP725016GLAT80, GMBOA4CA, max UDMA/133
    ata9.01: 312581808 sectors, multi 16: LBA48 
    ata9.00: limited to UDMA/33 due to 40-wire cable
    ata9.01: limited to UDMA/33 due to 40-wire cable
    ata9.00: configured for UDMA/33
    ata9.01: configured for UDMA/33
    Can anyone please explain why my disks are not running at SATA speeds? My BIOS has the SATA controller in AHCI mode.

    Stuart

  2. #2
    Join Date
    Dec 2006
    Posts
    2,088

    Re: Help my sata drive runs at udma33

    There is no such thing as a 40 wire sata cable. Try

    Code:
    hdparm -t -T /dev/sdX
    with the appropriate drive letter instead of "X" and if you get more than 30 MiB/sec you should be fine.

  3. #3
    Join Date
    Oct 2011
    Location
    UK
    Posts
    469

    Re: Help my sata drive runs at udma33

    Well this raises two things, first why is the kernel saying this, and second my two SATA disks come up at 68.77 MB/sec and 133.97 MB/sec for buffered reads. I dont understand why the difference though as they are similar disks.

    Stuart

    ---------- Post added at 05:59 PM ---------- Previous post was at 05:12 PM ----------

    Just done some more timings:-

    /dev/sda: SATA disk
    Timing cached reads: 4350 MB in 2.00 seconds = 2175.47 MB/sec
    Timing buffered disk reads: 404 MB in 3.00 seconds = 134.53 MB/sec

    /dev/sdb: SATA disk
    Timing cached reads: 4606 MB in 2.00 seconds = 2303.26 MB/sec
    Timing buffered disk reads: 206 MB in 3.01 seconds = 68.51 MB/sec

    /dev/sdc: PATA disk
    Timing cached reads: 4618 MB in 2.00 seconds = 2309.79 MB/sec
    Timing buffered disk reads: 166 MB in 3.02 seconds = 54.92 MB/sec

    /dev/sdd: PATA disk
    Timing cached reads: 4668 MB in 2.00 seconds = 2334.35 MB/sec
    Timing buffered disk reads: 224 MB in 3.01 seconds = 74.39 MB/sec

    Can someone explain why sdb a SATA disk is slower that sdd a PATA disk? Both sda and sdb are SATAII drives.

    Stuart
    Last edited by broadstairs; 13th April 2013 at 06:01 PM. Reason: Correct typo

  4. #4
    stevea Guest

    Re: Help my sata drive runs at udma33

    SATA/PATA does not determine the actual transfer rate of data off the disks, the bus type and UDMA merely set an upper bound. So it's entirely possible that "hdparm -t ..." (sequential read test) for your sdb [a SATA] is 68.51 MB/sec and your sdd [a PATA] is 74.39 MB/sec.

    [I don't know why George_T asks for '-t' cache speed, but sadly amid good comments he often asks for irrelevant scatter-shot info]

    If you look up the exact model of disk and google for performance reports (storagereview.com is good) you should see the relationship.

    ===

    UDMA has no relevance to SATA (only PATA & IDE), except that udma6 us used to designate SATA1.0.
    In any case you are not getting UDMA33 speeds (33MB/sec) your slowest drive transfers at least an avg 54.92MB/s, well above 33MB/s.

    The message abt 40-wire limits from from the kernel driver ...
    .../linux/drivers/ata/libata-core.c,
    which is included in kernel directly, but the problem is that one of the sata/pata chip coontrol modules for your interface chip incorrectly identified the cable type as 40pin vs the
    ATA_CBL_PATA40 instead of ATA_CBL_SATA .

    You might try to
    sudo hdparm -I /dev/sd{a,b,c,d} | grep -i udma
    and you'll likely see
    Code:
    	DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
    type lines for the SATA drives.

    ---------- Post added at 05:35 PM ---------- Previous post was at 05:30 PM ----------

    FWIW since there is a real bug here inthe driver, you might want to use
    lspci -nnk
    to list the devices and related drivers for your specific interface.


    So I get lines line-sets like ...
    Code:
    00:1f.2 SATA controller [0106]: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller [8086:3b22] (rev 06)
    	Subsystem: Giga-byte Technology Device [1458:b005]
    	Kernel driver in use: ahci
    ...
    02:00.0 SATA controller [0106]: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller [197b:2363] (rev 02)
    	Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard [1458:b000]
    	Kernel driver in use: ahci
    02:00.1 IDE interface [0101]: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller [197b:2363] (rev 02)
    	Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard [1458:b000]
    	Kernel driver in use: pata_jmicron
    Where pata_jmicron.ko might be the problem driver.

  5. #5
    Join Date
    Aug 2009
    Posts
    8,464

    Re: Help my sata drive runs at udma33

    Ummm.. a Hitachi HDP725016GLAT80 happens to be a 160GB PATA drive, not a SATA drive.

    Edit:
    You may want to double check your device assignments. They can change, and may not necessarily be in the order you think they are supposed to be.

  6. #6
    Join Date
    Oct 2011
    Location
    UK
    Posts
    469

    Re: Help my sata drive runs at udma33

    Yes thats correct, I picked the wrong one

    ata9.00: ATA-8: Hitachi HDS721050CLA362, JP2OA3MA, max UDMA/133
    ata9.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    ata9.00: limited to UDMA/33 due to 40-wire cable
    ata9.00: configured for UDMA/33

    and
    ata9.01: SAMSUNG SP2504C, VT100-41, max UDMA7
    ata9.01: 488397168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    ata9.01: limited to UDMA/33 due to 40-wire cable
    ata9.01: configured for UDMA/33

    plus the PATA drive does have a 40-wire cable installed, and just to be sure I replaced it with a new one.

    Something funny is going on here.

    Stuart

    ---------- Post added at 12:14 PM ---------- Previous post was at 08:19 AM ----------

    I tried running without libata.force=80c on in grub and the disk speeds for the PATA drive do drop below 33Mb/sec so there is a bug at least there which says the driver is misinterpreting the data from the drive because as I said I did install a new 80 wire cable in place of the old 80 wire cable and it made no difference. It is also misleading to get the same messages about SATA drives.

    This PC dual boots to XP and in that the drive speeds are the same (SATA and PATA) as they are in Linux when forcing the 80-wire bit so the cable IS 80 wire or XP would get rubbish speeds. So I guess my Samsung drive is just not very fast.

    Stuart

  7. #7
    Join Date
    Aug 2009
    Posts
    8,464

    Re: Help my sata drive runs at udma33

    That is interesting. As someone said above.. There is no 40 pin cable for a SATA drive. Do you by chance have a VIA chipset in that machine? I seem to recall seeing a bug in the via ata drivers that required the libata.force=80c on the kernel line due to something similar to this.

    But, everything I have found on your Samsung SATA drive tells me that you are getting about what you should from it. Benchmarks I have seen average 50-58 MB/sec with max throughput hitting almost 70 MB/sec.

    Edit:

    Refer to stevea's post above to determine what module is being loaded. If it loads via_pata, then you are getting hit with the bug I mentioned, and it's pretty much a bug in the driver, and not much you can do except to force it as you have been doing.

    Edit:
    The driver is pata_via, not via_pata that I specified above. My memory is starting to go.. I need more coffee

  8. #8
    Join Date
    Oct 2011
    Location
    UK
    Posts
    469

    Re: Help my sata drive runs at udma33

    It has two SATA controllers, one Marvell SE9120 which is disabled as I dont currently have anything connected to it and one AMD SB850 which is the one in use and both are SATAIII. The motherboard is an ASRock 890FX Deluxe5.

    You can see why I was a tad confused by all these messages. There must be two bugs, one in the PATA driver which is not detecting the 80-wire correctly and the other in the SATA driver putting out these spurious messages.

    Yes the Samsung is performing as well as expected from what I've seen, the Hitachi one is much better at 130Mb/sec. Sadly my Linux system is installed on the Samsung at present.

  9. #9
    Join Date
    Aug 2009
    Posts
    8,464

    Re: Help my sata drive runs at udma33

    You can try putting your SATA drives on the other controller.

    Also, ASRock has released quite a few BIOS updates for that board, none that show any changes for the SATA controllers, though (unless they are lumped into the fixes for Win 8 shutdown)

    You could try updating the BIOS and see if that helps things, though.

  10. #10
    Join Date
    Oct 2011
    Location
    UK
    Posts
    469

    Re: Help my sata drive runs at udma33

    I could try using the Marvell controller although there is a warning about having to set it bootable and this 'can' slow booting, dont know why. I will also look at the BIOS to see if I already have the updates installed.

    Stuart

  11. #11
    Join Date
    Dec 2006
    Posts
    2,088

    Re: Help my sata drive runs at udma33

    Adding or enabling additional sata host adapters can and will slow down the boot process, because they will have to search for (bootable) devices that are connected to these host adapters and display an information screen. Some of these will even ask you to press a key.

  12. #12
    stevea Guest

    Re: Help my sata drive runs at udma33

    Is AHCI enabled in the BIOS for the interface ?
    Fergodsakes tell us which driver is loaded.

  13. #13
    Join Date
    Oct 2011
    Location
    UK
    Posts
    469

    Re: Help my sata drive runs at udma33

    Yes AHCI IS enabled in BIOS and SATA driver is ahci, PATA driver is pata_via. Forcing 80-wire does speed up the PATA hdds.

    Log currently shows on last boot for the SATA drives:-

    Code:
    Apr 16 09:00:22 fedora17 kernel: [    1.429796] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Apr 16 09:00:22 fedora17 kernel: [    1.430530] ata5: FORCE: cable set to 80c
    Apr 16 09:00:22 fedora17 kernel: [    1.430810] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Apr 16 09:00:22 fedora17 kernel: [    1.431152] ata5.00: ATA-8: Hitachi HDS721050CLA362, JP2OA3MA, max UDMA/133
    Apr 16 09:00:22 fedora17 kernel: [    1.431287] ata5.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
    Apr 16 09:00:22 fedora17 kernel: [    1.432499] ata5.00: configured for UDMA/133
    Apr 16 09:00:22 fedora17 kernel: [    1.433936] ata6: FORCE: cable set to 80c
    Apr 16 09:00:22 fedora17 kernel: [    1.434267] ata6.00: ATA-7: SAMSUNG SP2504C, VT100-41, max UDMA7
    Apr 16 09:00:22 fedora17 kernel: [    1.434413] ata6.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
    Apr 16 09:00:22 fedora17 kernel: [    1.460257] ata6.00: configured for UDMA/133
    This is after installing the latest BIOS for this motherboard.

    Stuart

    Just tested without forcing 80-wire and all it changes is the pata disks speed, the same messages for the sata disks appear.

    Just tested my other system which is F18 fully up to date with one SATA disk and that shows similar messages about UDMA/133. This has a different older motherboard/chipset/cpu.
    Last edited by broadstairs; 16th April 2013 at 01:06 PM. Reason: add info

Similar Threads

  1. Replies: 1
    Last Post: 26th March 2013, 12:48 PM
  2. Making a drive image that runs on anything?
    By hallikainen in forum Installation, Upgrades and Live Media
    Replies: 1
    Last Post: 22nd June 2008, 08:05 AM
  3. Replies: 12
    Last Post: 19th June 2008, 02:33 AM
  4. Lock up with SATA drive - SATA driver problem?
    By stodge in forum Hardware & Laptops
    Replies: 0
    Last Post: 3rd April 2005, 07:28 PM
  5. SATA drive - SATA or UDMA cable?
    By stodge in forum Hardware & Laptops
    Replies: 3
    Last Post: 27th December 2004, 08:13 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •