AHCI timeouts

[holzmann]

I am running the 1TB version: SAMSUNG EcoGreen F2 HD103SI

FW for the drive currently being scanned is 1AG01118. While I can find FW updates for the 2TB version, I am not seeing anything for the 1TB version.

 

[djoole]

The firmware issue was for the 2TB version (F4 EG).
So i don't see what your problem could be... an incompatibility between your sata controler, the hard drive model and Freenas?

 

[holzmann]

I just got done spending over 48 hours running ESTOOL on my four 1TB Samsung drives: no errors found.

I guess this leaves the SATA controller on the ASUS M4A88T-M LE motherboard featuring the AMD 880G / AMD SB710 (NB/SB).

 

[holzmann]

So I guess I either try FN7 or spend yet more money on a SATA controller card. I think I will try the former first.

 

[holzmann]

I ended up "downgrading" to FN7 (Nightly) and am no longer experiencing errors.

 

[gcooper]

I ended up "downgrading" to FN7 (Nightly) and am no longer experiencing errors.

I'll raise this to delphij's attention and we'll see what we can do about fixing this (sounds like an ahci/quirk issue).

 

[maarten]

HD204UI and IXP 700

Just for info:

Experienced the same issues with ahci timeouts almost at random for any of the 4 drives similar to:
ahcich2: Timeout on slot x port 0
ahcich2: is 00000000 cs 01000000 ss 00000000 rs 01000000 tfd x serr 00000000
ahcich2: AHCI reset: device not ready after 31000ms (tfd = xx )
ahcich2: Timeout on slot x port 0
ahcich2: is 00000000 cs 01000000 ss 00000000 rs 01000000 tfd xx serr ******
To reset needs a hard reset, shutdown stalls.

My config

storage: raidz,4x Samsung HD204UI 2TB version (F4 EG) wit latest firmware (1aq10003), 4k, Ran EStool on all 4 disks, all fine.
mobo: Asus E35M1-I Deluxe (IXP700 in AHCI mode)
memory: Kingston ValueRam 8GB(2x4GB) DDR3 1333MHz CL9
software: FreeNAS Build FreeNAS-8.0.3-RC1-x64 (9250)

Only way to overcome was by disabling smartd, otherwise trouble several times a week (with very low system usage).

I am happy to test any patches, make some more tests to investigate or to send log files, just drop a message.

Based on my experience I agree with the AHCI driver/smart quirks suggestion made earlier in this thread.

 

[holzmann]

maarten: sounds exactly like the issues I was having on very similar hardware/setup!!!

I am now running FN7 (Nightly) with no issues. SMART enabled, etc.

 

[Fab'z]

Same problem with two samsung hdd (HD154UI). JMicron JMB361

ahcich*: Timeout on slot...

 

[MrAnim8]

Same issue

I'm having the same issue - getting these timeouts when copying large amounts of files over to my newly built NAS. My setup:

Data Drives: 4 newly opened (they were sitting in a box) SAMSUNG EcoGreen F2 HD154UI 1.5TB.
Motherboard: Biostar TA880GU3+

I've tried all of the SATA modes on my motherboard, no dice.

Any suggestions? How do I use the older ata/ahciata driver? Do I have to downgrade from 8.0.2 to 7.x?

thanks!

 

[maarten]

MrAnim8: You could try to completly disable smart on the disks and on diskable the smartd service and post the results.

In my case that made the difference. If so that would be another pointer towards the smartd/ahci driver quirk. Googling around also gives me he impression the newer samsung drives appear to be affected over proportional, so there could also be an mismatch in the samsung smart implementation and the ahci drivers. I am not a developer so can not delve into the code myself but I am growing the impression of a pattern in this time-out issue.

 

[MrAnim8]

chipset?

In desperation I grabbed an old PCI-based SATA controller (Silicon Image 3114), and it seems fine now. The PCI bandwith (133MB/s, even if shared) should be plenty for a 4 drive RAIDZ array.
I'll continue playing with it to see if it actually corrects the problem, but if so it might be the AMD 880G/850SB chipset that's part of the problem chain.
Either that or it is a problem with the drives being overwhelmed by the driver, and my new solution is just too slow to trigger that. :)

 

[seeingwhite]

I'm having the same issue - getting these timeouts when copying large amounts of files over to my newly built NAS. My setup:

Data Drives: 4 newly opened (they were sitting in a box) SAMSUNG EcoGreen F2 HD154UI 1.5TB.
Motherboard: Biostar TA880GU3+

I've tried all of the SATA modes on my motherboard, no dice.

Any suggestions? How do I use the older ata/ahciata driver? Do I have to downgrade from 8.0.2 to 7.x?

thanks!

I have the same board, using the 2TB Samsung F4 EG, and having AHCI timeout issues at startup. Previously had no problems for months. From these posts, I am noticing a trend: Samsung drives combined with AMD 880G chipsets and freenas 8.

 

[seeingwhite]

I have the same board, using the 2TB Samsung F4 EG, and having AHCI timeout issues at startup. Previously had no problems for months. From these posts, I am noticing a trend: Samsung drives combined with AMD 880G chipsets and freenas 8.

Just some basic log messages:
Jan 8 22:29:11 freenas kernel: ahcich0: Timeout on slot 4 port 0
Jan 8 22:29:11 freenas kernel: ahcich0: is 00000002 cs 00000000 ss 00000000 rs 00000010 tfd 50 serr 00000000
Jan 8 22:29:13 freenas kernel: xptioctl: pass driver is not in the kernel
Jan 8 22:29:13 freenas kernel: xptioctl: put "device pass" in your kernel config file
Jan 8 22:29:35 freenas freenas[2116]: Popen()ing: zpool status Backup2T
Jan 8 22:29:41 freenas kernel: ahcich0: Timeout on slot 5 port 0
Jan 8 22:29:41 freenas kernel: ahcich0: is 00000008 cs 00000000 ss 00000000 rs 00000030 tfd 40 serr 00000000
Jan 8 22:29:43 freenas root: ZFS: zpool I/O failure, zpool=Backup2T error=6
Jan 8 22:29:43 freenas root: ZFS: vdev I/O failure, zpool=Backup2T path= offset= size= error=
Jan 8 22:29:49 freenas root: ZFS: zpool I/O failure, zpool=Backup2T error=6
Jan 8 22:29:49 freenas root: ZFS: vdev I/O failure, zpool=Backup2T path= offset= size= error=

 

[holzmann]

You guys seem to be having the same errors I was.

I was able to install/setup FN8 just fine. It would even run fine for a few days. Boot/reboot fine. My AHCI errors only came up when copying large amounts of data, say a few thousand RAW photos totaling over 100GBs. It would get 75% through the process and then AHCI errors galore from all drives.

Changing the BIOS settings from AHCI to IDE made no difference. Disabling SMART made no difference (in BIOS and FN8).

For all intents and purposes, I don't appear to have lost much, if at all, functionality by downgrading to FN7, but I certainly gained stability. I was able to copy about 500GBs of files from the old server to the new one with zero errors. Uptime is about two weeks now.

 

[seeingwhite]

I think I fixed the problem I was having. It has been running stable for almost a week now. In the BIOS for my Biostar board under the setting "SATA IDE Combined Mode", the default in "enabled." I changed this to "disabled" and now my F4 drive works again without any errors at all. For those of you that have this chipset, the setting is under Chipset > SouthBridge Configuration > SB SATA Configuration . Hope that helps.

 

[joeschmuck]

I started seeing this problem a few days ago. Unfortunately while away on work travel my main computer SSD died (crucial m4 firmware problem) and the NAS died. Seems too coincidental. The SSD was a real problem (dies after just over 5000 running hours, works for 1 hour increments after that) that was fixed with a firmware upgrade. The FreeNAS problem had the NAS computer locked up. My tag line has my hardware configuration and my hard drives are all firmware updated.

The error messages that started me looking into the issue (only appear for ahcich1) once I cycled power on the NAS to make it operational again.

Code:

Jan 29 07:00:59 freenas kernel: ahcich1: Timeout on slot 7 port 0
Jan 29 07:00:59 freenas kernel: ahcich1: is 00000000 cs 00010000 ss 0001ff80 rs 0001ff80 tfd 40 serr 01a80c01
Jan 29 07:01:30 freenas kernel: ahcich1: Timeout on slot 28 port 0
Jan 29 07:01:30 freenas kernel: ahcich1: is 04000000 cs 00000000 ss f000003f rs f000003f tfd 40 serr 00a80801
Jan 29 07:02:03 freenas kernel: ahcich1: Timeout on slot 1 port 0
Jan 29 07:02:03 freenas kernel: ahcich1: is 00000000 cs 00000002 ss 00000000 rs 00000002 tfd 1d0 serr 00880800
Jan 29 07:02:35 freenas kernel: ahcich1: Timeout on slot 13 port 0
Jan 29 07:02:35 freenas kernel: ahcich1: is 00000000 cs 00018000 ss 0001e000 rs 0001e000 tfd c0 serr 00880800

Here is my zpool status, I have cleared the error and scrubbed twice, received a clean bill of health but the errors keep coming. The ada1p1 drive no longer is listed as the GPTID number, prior to the crash it was similar to the others.

Code:

[Mark@freenas] /# zpool status
  pool: farm
 state: ONLINE
status: One or more devices has experienced an unrecoverable error.  An
        attempt was made to correct the error.  Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
        using 'zpool clear' or replace the device with 'zpool replace'.
   see: http://www.sun.com/msg/ZFS-8000-9P
 scrub: resilver completed after 3h19m with 0 errors on Sat Jan 28 16:52:19 2012
config:

        NAME                                            STATE     READ WRITE CKSUM
        farm                                            ONLINE       0     0     0
          raidz1                                        ONLINE       0     0     0
            gptid/4004da37-0d40-11e1-9d47-50e549b78964  ONLINE       0     0     0
            ada1p1                                      ONLINE      45 14.2K     0  39.2G resilvered
            gptid/405d2497-0d40-11e1-9d47-50e549b78964  ONLINE       0     0     0
            gptid/408a1ff1-0d40-11e1-9d47-50e549b78964  ONLINE       0     0     0

errors: No known data errors
[Mark@freenas] /#

And my Smart test results, both short and long. Note that item 199 UDMA_CRC_Error_Count is incrementing slowly.

Code:

[Mark@freenas] /# smartctl -a -d auto /dev/ada1
smartctl 5.41 2011-06-09 r3365 [FreeBSD 8.2-RELEASE-p6 amd64] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     SAMSUNG SpinPoint F4 EG (AFT)
Device Model:     SAMSUNG HD204UI
Serial Number:    S2H7J1AZC08730
LU WWN Device Id: 5 0024e9 0047c3f46
Firmware Version: 1AQ10001
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 6
Local Time is:    Sun Jan 29 09:13:26 2012 EST

==> WARNING: Using smartmontools or hdparm with this
drive may result in data loss due to a firmware bug.
****** THIS DRIVE MAY OR MAY NOT BE AFFECTED! ******
Buggy and fixed firmware report same version number!
See the following web pages for details:
http://www.samsung.com/global/business/hdd/faqView.do?b2b_bbs_msg_id=386
http://sourceforge.net/apps/trac/smartmontools/wiki/SamsungF4EGBadBlocks

SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (19320) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 255) minutes.
SCT capabilities:              (0x003f) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   051    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0026   056   056   000    Old_age   Always       -       17565
  3 Spin_Up_Time            0x0023   068   044   025    Pre-fail  Always       -       9797
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       612
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       2016
 10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   252   252   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       248
181 Program_Fail_Cnt_Total  0x0022   098   098   000    Old_age   Always       -       43859379
191 G-Sense_Error_Rate      0x0022   100   100   000    Old_age   Always       -       8
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   064   064   000    Old_age   Always       -       29 (Min/Max 16/41)
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   252   252   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   100   100   000    Old_age   Always       -       454
200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       1
223 Load_Retry_Count        0x0032   252   252   000    Old_age   Always       -       0
225 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       1634

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%      2012         -
# 2  Short offline       Completed without error       00%      2011         -

Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run
SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Completed [00% left] (0-65535)
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

[Mark@freenas] /#

My current action is I'm backup up my NAS data to my backup NAS and it should be done soon. Once complete I will verify my hardware connections are okay to the drive. It's an open case and it's possible one of the animals hit it but I'm not holding my breath that will fix it. I just don't see the correlation between the CRC Error and the zpool status errors since i would think the CRC errors would be automatically fixed.

Here is a definition of UDMA CRC Error Count: Low value of this attribute typically indicates that something is wrong with the connectors and/or cables. Disk-to-host transfers are protected by CRC error detection code when Ultra-DMA 66 or 100 is used. So if the data gets garbled between the disk and the host machine, the receiving controller senses this and the retransmission is initiated. Such a situation is called "UDMA CRC error". Once the problem is rectified (typically by replacing a cable), the attribute value returns to the normal levels pretty quick.

If re-seating the SATA cable doesn't fix it, I'll swap the SATA cable with a new cable. If that fails I will swap the SATA cable ports trying to see if it's the hard drive or MB port. If it remains with the hard drive then I hope it's still under warranty.

So my only real problem once I have this all backed up will be to get the GPTID back to normal, if that is at all possible without blowing away my entire pool. I've never had to replace a drive in a pool before so I'll be learning something new.

Also, this problem never presented itself before and I've been running this version of FreeNAS for a short while.

This is really a PITA coming home from a work trip only to be greeted with two computer issues. All I can say is thank god it wasn't my wife's computer, I could never have fixed it from across the country.

 

[joeschmuck]

UPDATE: I disconnected and remated the SATA connector on the drive and no more achi errors nor UDMA CRC Errors. At the end of a scrub I found a few dozen sumcheck errors. I cleared the errors via zpool clear command and have rebooted the system and it all looks good but we will see how it looks tomorrow. I still think I need to do some more testing as I'd really like to test the drive with some tools and I do want to get the drive recognized under the GPTID again.

 

[maarten]

For your information and refering to my earlier post. I upgraded to FreeNAS-8.0.3-RELEASE-p1-x64 (9591) and it ran stable for some weeks. Then I did enable smart again and all seems stable so far. Anyone with similar experience?

 

[lingyunzjdt]

Same Timeout errors here: msi e350ia-e45, samsung 1.5T drive. FreeNas 8.0.3p1 64bit. It is my first home NAS, this Samsung HD works well in USB enclosure. The other two Seagate HDD works well under FN8.0.3p1.

When the terminal has "Time out", system hangs even I type 10/11 to reboot/shutdown. Read/Write also hangs.