Results 1 to 8 of 8

Thread: AB9 QuadGT eSATA failure

  1. #1
    Registered+
    Join Date
    Apr 2007
    Posts
    52
    Thanks
    6
    Thanked
    1 time in 1 post
    • Old_Biker's system
      • Motherboard:
      • Gigabyte GA-Z77X-UD5H
      • CPU:
      • Intel Core i5 3570K with Noctua NH-C14 cooler
      • Memory:
      • CML16GX3M4A1600C9B - 16GB (4x4GB) Corsair DDR3 Vengeance LP
      • Storage:
      • 120GB Samsung 830 SSD + 2 * WD 640GB
      • Graphics card(s):
      • 2GB XFX Radeon HD 6950
      • PSU:
      • Corsair HX650W
      • Case:
      • Coolermaster Cosmos
      • Operating System:
      • Windows 7
      • Monitor(s):
      • HP LP2475w
      • Internet:
      • 16MB ADSL

    AB9 QuadGT eSATA failure

    I use a Vantec USB/eSATA external backup drive across several PC's and have experienced some issues with eSATA data transfers on the AB9 QuadGT board.

    1. Windows explorer file copying in XP Pro (SP2) hangs with large files and locks system totally, requiring mains power switch-off to restart system.

    2. Some smaller, transferred textual data files, show corruption of text when examined.

    Transfer of the same files via the USB port seems to be free of both problems.

    Does anyone know any action that I could take to overcome this issue?

  2. #2
    Resident abit mourner BUFF's Avatar
    Join Date
    Jul 2003
    Location
    Sunny Glasgow
    Posts
    8,067
    Thanks
    7
    Thanked
    181 times in 171 posts
    which JMicron driver version are you using?

    MSI P55-GD80, i5 750
    abit A-S78H, Phenom 9750,

    My HEXUS.trust abit forums

  3. #3
    Registered+
    Join Date
    Apr 2007
    Posts
    52
    Thanks
    6
    Thanked
    1 time in 1 post
    • Old_Biker's system
      • Motherboard:
      • Gigabyte GA-Z77X-UD5H
      • CPU:
      • Intel Core i5 3570K with Noctua NH-C14 cooler
      • Memory:
      • CML16GX3M4A1600C9B - 16GB (4x4GB) Corsair DDR3 Vengeance LP
      • Storage:
      • 120GB Samsung 830 SSD + 2 * WD 640GB
      • Graphics card(s):
      • 2GB XFX Radeon HD 6950
      • PSU:
      • Corsair HX650W
      • Case:
      • Coolermaster Cosmos
      • Operating System:
      • Windows 7
      • Monitor(s):
      • HP LP2475w
      • Internet:
      • 16MB ADSL
    Quote Originally Posted by BUFF View Post
    which JMicron driver version are you using?
    Hi BUFF,

    Thanks for your interest in my problem.

    I am using version 1.17.11.2 of the JMicron drivers.

    Since posting this thread, I have received feedback from a duplicate thread that I posted on the [forum.abit-usa.com/showthread.php?t=122638] thread (I haven't clocked up 5 posts yet so can't send you the link properly).

    Mr. RICHH seemed to have similar thoughts to your own and suggested a BIOS change to B06R as a possible fix.

    I just need to obtain the binary file and have sent a private message to him as advised in the Abit USA thread on that BIOS.

    Then all I need to do is take the plunge with my first BIOS flash!

  4. #4
    Registered+
    Join Date
    Apr 2007
    Posts
    52
    Thanks
    6
    Thanked
    1 time in 1 post
    • Old_Biker's system
      • Motherboard:
      • Gigabyte GA-Z77X-UD5H
      • CPU:
      • Intel Core i5 3570K with Noctua NH-C14 cooler
      • Memory:
      • CML16GX3M4A1600C9B - 16GB (4x4GB) Corsair DDR3 Vengeance LP
      • Storage:
      • 120GB Samsung 830 SSD + 2 * WD 640GB
      • Graphics card(s):
      • 2GB XFX Radeon HD 6950
      • PSU:
      • Corsair HX650W
      • Case:
      • Coolermaster Cosmos
      • Operating System:
      • Windows 7
      • Monitor(s):
      • HP LP2475w
      • Internet:
      • 16MB ADSL
    Quote Originally Posted by Old_Biker View Post
    Then all I need to do is take the plunge with my first BIOS flash!
    While waiting for the BIOS upgrade file and plucking up enough courage to risk flashing the chip, I tried my eSATA drive successfully by connecting to a spare Intel SATA socket on the motherboard and using a backplane adapter supplied with the Vantec drive unit.

    The only snag with this approach was that I had to power up the Vantec external drive before booting my QuadGT so that it was detected as a new system drive. It could not be recognised if hot-plugged in the socket after QuadGT boot-up.

    I feel a BIOS flash coming on.

  5. #5
    Resident abit mourner BUFF's Avatar
    Join Date
    Jul 2003
    Location
    Sunny Glasgow
    Posts
    8,067
    Thanks
    7
    Thanked
    181 times in 171 posts
    Quote Originally Posted by Old_Biker View Post
    It could not be recognised if hot-plugged in the socket after QuadGT boot-up.
    hmm, did you install as AHCI?
    if not & it's running as a basic native drive afaik hot swapping isn't supported.

    MSI P55-GD80, i5 750
    abit A-S78H, Phenom 9750,

    My HEXUS.trust abit forums

  6. #6
    Registered+
    Join Date
    Apr 2007
    Posts
    52
    Thanks
    6
    Thanked
    1 time in 1 post
    • Old_Biker's system
      • Motherboard:
      • Gigabyte GA-Z77X-UD5H
      • CPU:
      • Intel Core i5 3570K with Noctua NH-C14 cooler
      • Memory:
      • CML16GX3M4A1600C9B - 16GB (4x4GB) Corsair DDR3 Vengeance LP
      • Storage:
      • 120GB Samsung 830 SSD + 2 * WD 640GB
      • Graphics card(s):
      • 2GB XFX Radeon HD 6950
      • PSU:
      • Corsair HX650W
      • Case:
      • Coolermaster Cosmos
      • Operating System:
      • Windows 7
      • Monitor(s):
      • HP LP2475w
      • Internet:
      • 16MB ADSL
    Quote Originally Posted by BUFF View Post
    hmm, did you install as AHCI?
    if not & it's running as a basic native drive afaik hot swapping isn't supported.
    Hi BUFF,

    I installed SATA as IDE in BIOS rather than AHCI.

    This is my first install on any mobo with SATA and I didn't read all about AHCI before I started.

    I'll have to read up on AHCI and see if I can change the setting or need to completely reinstall.

  7. #7
    Registered+
    Join Date
    Apr 2007
    Posts
    52
    Thanks
    6
    Thanked
    1 time in 1 post
    • Old_Biker's system
      • Motherboard:
      • Gigabyte GA-Z77X-UD5H
      • CPU:
      • Intel Core i5 3570K with Noctua NH-C14 cooler
      • Memory:
      • CML16GX3M4A1600C9B - 16GB (4x4GB) Corsair DDR3 Vengeance LP
      • Storage:
      • 120GB Samsung 830 SSD + 2 * WD 640GB
      • Graphics card(s):
      • 2GB XFX Radeon HD 6950
      • PSU:
      • Corsair HX650W
      • Case:
      • Coolermaster Cosmos
      • Operating System:
      • Windows 7
      • Monitor(s):
      • HP LP2475w
      • Internet:
      • 16MB ADSL
    Hi BUFF (and anyone else who may have a view on this problem),

    I have now flashed my BIOS to version 1.1 and later to B06R and changed my ICH8R chipset drivers in XP Pro to AHCI from IDE mode* in an effort cure the problem. These actions have all failed, the copying lockup failure still occurs. (I have not yet checked again for small file corruption).

    * If anyone wants to know how I achieved this 'impossible' task please ask and I'll open another thread to explain (unless there is already a thread detailing this operation, that I have failed to find).


    eSATA failure symptoms: -


    Situation 1. (Original)

    BIOS 1.0

    ICH8R and JMicron SATA controllers in IDE mode.

    When copying from eSATA to internal SATA via JMicron port, windows explorer fails to release the file after copying it and fails to close copy progress dialog window. XP Pro tolerates this for some minutes before crashing unless machine is turned off first. (eSATA drive cannot be closed down as it is 'still in use' and normal shutdown does not complete due to file remaining open)

    Some small text files that were copied later found to be corrupted, but this could not definitely be attributed to the eSATA copy process.

    Large and small files were later copied from same USB/eSATA drive via USB port with no problem.

    All files copied correctly over Vantec eSATA backplane adapter using mobo (ICH8R controlled) SATA port.

    Situation 2. - BIOS changed to ver. 1.1 - Windows Explorer 'lock-up' remains for eSATA copying via JMicron

    controller. Small file corruption not checked as main problem still unsolved.

    Situation 3. - BIOS changed to B06R - same result as 2.

    Situation 4. - BIOS B06R, JMicron driver changed to 1.17.10.5 - same result as 2.

    Situation 5. - BIOS B06R, ICH8R now converted from IDE to AHCI mode, JMicron still IDE - same result as 2.

    Situation 6. - BIOS b06R, ICH8R and JMicron now AHCI, - same result as 2.

    I am running out of ideas!

    My current analysis leads me to suspect some flaw in the way that my Vantec drive enclosure interfaces with the JMicron controller, or an operating system problem caused by some of my software or a Microsoft update.

    I plan a vanilla install of XP Pro on another drive and to boot from this to see if windows explorer eSATA copying works correctly before other software and Microsoft's updates are added to the basic OS.

    Other than that, I propose to cycle through the various flavours of JMicron XP drivers that I have to see if that fixes the problem.

    Your further suggestions for fixing this problem are most welcome.

  8. #8
    Registered+
    Join Date
    Apr 2007
    Posts
    52
    Thanks
    6
    Thanked
    1 time in 1 post
    • Old_Biker's system
      • Motherboard:
      • Gigabyte GA-Z77X-UD5H
      • CPU:
      • Intel Core i5 3570K with Noctua NH-C14 cooler
      • Memory:
      • CML16GX3M4A1600C9B - 16GB (4x4GB) Corsair DDR3 Vengeance LP
      • Storage:
      • 120GB Samsung 830 SSD + 2 * WD 640GB
      • Graphics card(s):
      • 2GB XFX Radeon HD 6950
      • PSU:
      • Corsair HX650W
      • Case:
      • Coolermaster Cosmos
      • Operating System:
      • Windows 7
      • Monitor(s):
      • HP LP2475w
      • Internet:
      • 16MB ADSL

    Thumbs up

    Thanks for your suggestions they have certainly made me think about the way current systems work.

    However, I must now report that I have completed the transfer of my WD4000AAKS drive to the eSATA enclosure as a swap for the SP2504C that is now in my PC. I am delighted to report that this change has COMPLETELY SOLVED THE COPY FAILURE PROBLEM!:biggrin:

    The file copy process now works as it should in both directions with either eSATA port, transferring a 1GB file in about 15 secs. The same file was consistently failed when the drives were in the reverse positions.

    I do not understand how this miracle has been achieved, but I can certainly live with the outcome!:smile:

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. AB9 QuadGT or P5B Deluce Wifi?
    By Mutley in forum PC Hardware and Components
    Replies: 31
    Last Post: 07-03-2007, 08:42 AM
  2. AB9 QuadGT
    By dave24 in forum abit.care@HEXUS
    Replies: 7
    Last Post: 25-02-2007, 03:00 AM
  3. AB9 QuadGT Availability
    By EtheAv8r in forum abit.care@HEXUS
    Replies: 0
    Last Post: 02-01-2007, 11:25 PM

Posting Permissions

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