Date: Mon, 13 Feb 2012 08:28:10 -0800 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: Willem Jan Withagen <wjw@digiware.nl> Cc: "stable@freebsd.org" <stable@freebsd.org> Subject: Re: Troube with SSD Message-ID: <20120213162810.GA75832@icarus.home.lan> In-Reply-To: <4F39372E.5030105@digiware.nl> References: <4F2940C1.10901@digiware.nl> <20120201143942.GA96012@icarus.home.lan> <4F2960A7.8040705@digiware.nl> <20120201163556.GA97343@icarus.home.lan> <4F297FD5.7090809@digiware.nl> <4F39372E.5030105@digiware.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 13, 2012 at 05:15:42PM +0100, Willem Jan Withagen wrote: > On 2012-02-01 19:09, Willem Jan Withagen wrote: > > On 2012-02-01 17:35, Jeremy Chadwick wrote: > > Hi Jeremy, > > Took a little longer, since "holidays got in the way". > But even in the original server connected to regular intel sataports, > the device is not known and 2 commands failed. > > Flash SSD is connected for about 1 hour now. > > --WjW > > > >>> The output of the first one command, but it contains some real weird > >>> values.....?? > >> > >> All the values below look fine to me. I will try my best to explain. > > > >>> SMART Attributes Data Structure revision number: 10 > >>> 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 082 082 050 Pre-fail Always - 897651373777 > >>> 5 Reallocated_Sector_Ct 0x0033 100 100 003 Pre-fail Always - 0 > >>> 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 121242631799621 > >>> 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 31 > >>> 171 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 0 > >>> 172 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 0 > >>> 174 Unknown_Attribute 0x0030 000 000 000 Old_age Offline - 19 > >>> 177 Wear_Leveling_Count 0x0000 000 000 000 Old_age Offline - 0 > >>> 181 Program_Fail_Cnt_Total 0x0032 000 000 000 Old_age Always - 0 > >>> 182 Erase_Fail_Count_Total 0x0032 000 000 000 Old_age Always - 0 > >>> 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 > >>> 194 Temperature_Celsius 0x0022 026 035 000 Old_age Always - 26 (Min/Max 21/35) > >>> 195 Hardware_ECC_Recovered 0x001c 120 120 000 Old_age Offline - 897651373777 > >>> 196 Reallocated_Event_Count 0x0033 100 100 003 Pre-fail Always - 0 > >>> 201 Soft_Read_Error_Rate 0x001c 120 120 000 Old_age Offline - 897651373777 > >>> 204 Soft_ECC_Correction 0x001c 120 120 000 Old_age Offline - 897651373777 > >>> 230 Head_Amplitude 0x0013 100 100 000 Pre-fail Always - 429496729700 > >>> 231 Temperature_Celsius 0x0013 100 100 010 Pre-fail Always - 0 > >>> 233 Media_Wearout_Indicator 0x0000 000 000 000 Old_age Offline - 1260 > >>> 234 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 1925 > >>> 241 Total_LBAs_Written 0x0032 000 000 000 Old_age Always - 1925 > >>> 242 Total_LBAs_Read 0x0032 000 000 000 Old_age Always - 1032 > > >>>> * smartctl -l devstat /dev/whatever > >>>> * smartctl -l sataphy /dev/whatever > >>>> * smartctl -l ssd /dev/whatever > > > > It'll have to wait until later this evening, before I able to swap the > > disk back in the old box. > > [~wjw] root@zfs.digiware.nl# smartctl -l devstat /dev/ada2 > smartctl 5.42 2011-10-20 r3458 [FreeBSD 8.2-STABLE amd64] (local build) > Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net > > Device Statistics (GP Log 0x04) not supported > [~wjw] root@zfs.digiware.nl# smartctl -l sataphy /dev/ada2 > smartctl 5.42 2011-10-20 r3458 [FreeBSD 8.2-STABLE amd64] (local build) > Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net > > SATA Phy Event Counters (GP Log 0x11) > ID Size Value Description > 0x0001 4 0 Command failed due to ICRC error > 0x0003 4 0 R_ERR response for device-to-host data FIS > 0x0004 4 0 R_ERR response for host-to-device data FIS > 0x0006 4 0 R_ERR response for device-to-host non-data FIS > 0x0007 4 0 R_ERR response for host-to-device non-data FIS > 0x0008 4 0 Device-to-host non-data FIS retries > 0x0009 4 0 Transition from drive PhyRdy to drive PhyNRdy > 0x000a 4 11 Device-to-host register FISes sent due to a COMRESET > 0x000f 4 0 R_ERR response for host-to-device data FIS, CRC > 0x0010 4 0 R_ERR response for host-to-device data FIS, non-CRC > 0x0012 4 0 R_ERR response for host-to-device non-data FIS, CRC > 0x0013 4 0 R_ERR response for host-to-device non-data FIS, non-CRC > 0x0002 4 0 R_ERR response for data FIS > 0x0005 4 0 R_ERR response for non-data FIS > 0x000b 4 0 CRC errors within host-to-device FIS > 0x000d 4 0 Non-CRC errors within host-to-device FIS > > [~wjw] root@zfs.digiware.nl# smartctl -l ssd /dev/ada2 > smartctl 5.42 2011-10-20 r3458 [FreeBSD 8.2-STABLE amd64] (local build) > Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net > > Device Statistics (GP Log 0x04) not supported The SATA PHY counters for the disk, kept in GP log area 0x11, look perfectly fine. The 11 you see at offset 0xa are completely fine; nothing to worry about there. Sadly the SSD does not support GP log area 0x04. Overall I see no real problems with the drive itself given the information above, which is literally all I can go off of. Sorry I can't be of more assistance past this point; honestly your drive looks fine given what I can tell. Only Corsair would be able to help at this point, but it's unlikely any Tier 1 individual would know how to troubleshoot this kind of thing. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120213162810.GA75832>