Stable SATA pci card for FreeBSD 6.x/7.0
Sebastiaan van Erk
sebster at sebster.com
Tue Aug 5 13:16:43 UTC 2008
Sorry for forgetting to paste the smart details. Pressed send too quickly.
However, when I did check the smart stats again, I noticed I'd been
smartctling the wrong disk (duh), and smart was not enabled on the new
disks. I enabled it now, and it comes with a bunch of warnings and other
Considering it wasn't enabled, maybe the errors wouldn't show up anyway,
but here's the output of the smartctl command just in somebody sees
something to worry about in it... (The ECC recovery count looks rather
high, I tried -F samsung and -F samsung2 but that didn't help).
root at piglet(ttyp3:59:0):~# smartctl -a /dev/ad4
smartctl version 5.37 [i386-portbld-freebsd6.3] Copyright (C) 2002-6
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: SAMSUNG HD103UJ
Serial Number: S13PJ1BQ606865
Firmware Version: 1AA01112
User Capacity: 1,000,204,886,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: Not recognized. Minor revision code: 0x52
Local Time is: Tue Aug 5 15:15:20 2008 CEST
==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for
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:
Self-test execution status: ( 0) The previous self-test routine
without error or no self-test
Total time to complete Offline
data collection: (11811) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection
Suspend Offline collection upon new
Offline surface scan supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
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: ( 198) minutes.
Conveyance self-test routine
recommended polling time: ( 21) minutes.
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 0x000f 253 253 051 Pre-fail
Always - 0
3 Spin_Up_Time 0x0007 090 090 011 Pre-fail
Always - 4050
4 Start_Stop_Count 0x0032 100 100 000 Old_age
Always - 4
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail
Always - 0
7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail
Always - 0
8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail
Offline - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age
Always - 230
10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail
Always - 0
11 Calibration_Retry_Count 0x0012 100 100 000 Old_age
Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age
Always - 4
13 Read_Soft_Error_Rate 0x000e 253 253 000 Old_age
Always - 0
183 Unknown_Attribute 0x0032 100 100 000 Old_age Always
184 Unknown_Attribute 0x0033 100 100 099 Pre-fail Always
187 Unknown_Attribute 0x0032 100 100 000 Old_age Always
188 Unknown_Attribute 0x0032 100 100 000 Old_age Always
190 Temperature_Celsius 0x0022 056 056 000 Old_age Always
194 Temperature_Celsius 0x0022 052 052 000 Old_age Always
- 48 (Lifetime Min/Max 0/12324)
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age
Offline - 0
199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always
200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always
201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 0
Warning: ATA Specification requires self-test log structure revision
number = 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective Self-Test Log Data Structure Revision Number (0) should be 1
SMART Selective self-test log data structure revision number 0
Warning: ATA Specification requires selective self-test log data
structure revision number = 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
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.
root at piglet(ttyp3:60:0):~#
Jeremy Chadwick wrote:
> On Tue, Aug 05, 2008 at 12:28:40PM +0200, Sebastiaan van Erk wrote:
>> However, a lot of disk activity on the drives will often cause the
>> machine to crash and spontaneously reboot. I checked out which chipset
>> was on the card with pciconf -lv and I found it was the Sil 3512.
>> Googling showed me that I'm not the only one with problems using this
> Yes, most of the Silicon Image ICs I've read about have odd driver
> problems or general issues (even under Windows). The system rebooting
> is an odd one; you sure your PSU can handle two disks?
>> Does anybody have experience with a (preferably not too expensive)
>> 2-port SATA expansion card which does not have any issues running under
>> FreeBSD 6.3/7.0?
> Promise makes some consumer-priced cards which work very well under
> FreeBSD (sos@ has full documentation on their cards).
> Their RAID controllers (the consumer-level ones) **do not** require that
> you use RAID; they support JBOD, and the disks will show up under
> FreeBSD as ad(4) devices. (If you choose to use the RAID, you'll still
> see the ad(4) disks, but you'll also see an ar(4) device too. This has
> the added advantage of you being able to monitor SMART stats on the
> disks themselves directly, etc...
>> [pciconf -lv output]
>> atapci0 at pci0:10:0: class=0x018000 card=0x35121095 chip=0x35121095
>> vendor = 'Silicon Image Inc (Was: CMD Technology Inc)'
>> device = 'Sil 3512 SATALink/SATARaid Controller'
>> class = mass storage
>> [/var/log/messages before the crash]
>> Aug 5 11:16:14 piglet kernel:
>> g_vfs_done():mirror/gm1s1e[WRITE(offset=111376236544, length=16384)] error = 6
>> Aug 5 11:16:17 piglet last message repeated 9 times
> Are you sure this is being caused by the controller? Have you checked
> SMART statistics on both disks? Assuming error == errno, errno 6 is
> "Device not configured".
> There's been recent discussion of such messages being caused by the use
> of gmirror or gjournal, when the mirror/journal is improperly set up.
> (In one users' case, he was receiving similar errors, as well as the
> filesystem failing during fsck. Turns out he incorrectly configured
> journalling, which nuked the last ~1MB of his UFS filesystem.)
> I'm not saying this is the reason for the messages you see, but it's
> something to keep in mind.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3315 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080805/392530bb/smime.bin
More information about the freebsd-stable