Reply
Kilobyte Kid
epsalmond
Posts: 5
Registered: ‎08-28-2013
0
Accepted Solution

m4 256gb msata read errors

Hey everyone,

I'm getting a lot of read errors on my m4. Winders reports a semaphore error, and cloning out my OS partition with DD just gave me some good old fashioned read io errors.

So my question is, is it normal to get unreadable sectors? On a magnetic drive I'd just rewrite all the sectors and let the reallocation firmware do its thing, but I'm not sure about ssd.

I'm not running the latest firmware. I just had the ISO ready to fire up with grub, and wouldn't you know it, another io error pops up. So I'm going to run badblocks on my boot partition and give this another shot tomorrow.

Is this normal? Should I just return the device? I've had quite a lot of files get murdered over the last year or so and it seems a bit odd. Does the firmware update fix this?

Thanks.
JEDEC Jedi
bogdan
Posts: 1,407
Registered: ‎09-26-2012
0

Re: m4 256gb msata read errors

in reply to epsalmond

Depending on how old is your drive and what firmware revision it has update could fix it - there is one well known bug in older firmwares. 

Could you dump SMART data of this drive? Just hide serial number prior to posting it.

______________________________________

FAQs and Top Forum Solutions
Did a user help you? Say thanks by giving Kudos!
How do I know what memory to buy?
Still need help? Contact Crucial Customer Service
Remember to regularly backup your important data!

SODIMM Sherpa
Holt
Posts: 122
Registered: ‎01-18-2012
0

Re: m4 256gb msata read errors

in reply to bogdan

If your m4 is still on a 0001, 0002 or 0009 FW version you should update to the 0309, for me still the best FW released for the m4, as later version had some issues and the mentioned ones hae a buf too.

 

0309 iso can still be found here: http://edge.crucial.com/firmware/m4/0309/Crucialm4_0309.zip

 

 Avoid using the Windows updater and if you already have  a later version, do not downgrade.

Kilobyte Kid
epsalmond
Posts: 5
Registered: ‎08-28-2013
0

Re: m4 256gb msata read errors

Here's what I did:

 

1) Installed latest firmware

2) Wrote /dev/zero to /dev/sda (entire disk) with dd  (actually with PV so I could watch it.  write speed was good all the way.)

3) rebuilt EFI partition, reinstalled grub and windows boot manager

4) re-imaged windows with dism

5) TRIM'ed everything up.

 

So far things seem OK.  I didn't have any write errors zero-ing the drive and I haven't had any read errors in about 4 days which is a record.  Will see if things continue to go well.

Memory Leak Geek
rus-transit
Posts: 4
Registered: ‎09-07-2013
0

Re: m4 256gb msata read errors

in reply to epsalmond

I have the same problem with Crucial M4 mSATA 256GB.

 

Over 20% space "read error" (by HD Tune).

Only 100 hour of device working (by SMART)

 

The firmware utility (07) no do anything (notebook Samsung 900x3c, W7).

 

I install mSATA in desktop.

Utility began, but don't show device in list.

After click "Continue" -> reboot and "Can't find grub loader" (approximate sense)

 

Very dissapointed : (((

 

Not any Crucial ssd for me. Forever!

Kilobyte Kid
epsalmond
Posts: 5
Registered: ‎08-28-2013
0

Re: m4 256gb msata read errors

in reply to rus-transit

"Not any <insert name of company> for me. Forever!"

 

If I had a nickel...

 

Try the "manual install" method.  It comes with an ISO.  Burn it to a CD and give that a shot.  That's more or less what I had to do.  Since writing 0's to the drive (aka "low level format") it's been great.

Kilobyte Kid
epsalmond
Posts: 5
Registered: ‎08-28-2013
0

Re: m4 256gb msata read errors

in reply to bogdan

Here is my smart data.  You can see the read errors that were logged before my firmware upgrade and wipe.  Haven't logged anything new since.

 

smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.38-std231-amd64] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model: M4-CT256M4SSD3
Serial Number: 00000000<snip>
LU WWN Device Id: <snip this too>
Firmware Version: 07MH
User Capacity: 256,060,514,304 bytes [256 GB]
Sector Size: 512 bytes logical/physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 6
Local Time is: Fri Aug 30 02:22:35 2013 UTC
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: (0x80) Offline data collection activity
was never started.
Auto Offline Data Collection: Enabled.
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: ( 1190) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
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: ( 19) minutes.
Conveyance self-test routine
recommended polling time: ( 3) minutes.
SCT capabilities: (0x003d) 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 050 Pre-fail Always - 16
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
9 Power_On_Hours 0x0032 100 100 001 Old_age Always - 905
12 Power_Cycle_Count 0x0032 100 100 001 Old_age Always - 605
170 Unknown_Attribute 0x0033 100 100 010 Pre-fail Always - 0
171 Unknown_Attribute 0x0032 100 100 001 Old_age Always - 2
172 Unknown_Attribute 0x0032 100 100 001 Old_age Always - 0
173 Unknown_Attribute 0x0033 100 100 010 Pre-fail Always - 6
174 Unknown_Attribute 0x0032 100 100 001 Old_age Always - 99
181 Program_Fail_Cnt_Total 0x0022 100 100 001 Old_age Always - 2104539087269
183 Runtime_Bad_Block 0x0032 100 100 001 Old_age Always - 0
184 End-to-End_Error 0x0033 100 100 050 Pre-fail Always - 0
187 Reported_Uncorrect 0x0032 100 100 001 Old_age Always - 55503
188 Command_Timeout 0x0032 100 100 001 Old_age Always - 0
189 High_Fly_Writes 0x000e 100 100 001 Old_age Always - 87
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 0
195 Hardware_ECC_Recovered 0x003a 100 100 001 Old_age Always - 47710
196 Reallocated_Event_Count 0x0032 100 100 001 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 001 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 001 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 100 100 001 Old_age Always - 0
202 Data_Address_Mark_Errs 0x0018 100 100 001 Old_age Offline - 0
206 Flying_Height 0x000e 100 100 001 Old_age Always - 2

SMART Error Log Version: 1
Warning: ATA error count 0 inconsistent with error log pointer 3

ATA Error Count: 0
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:smileyfrustrated:S.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 0 occurred at disk power-on lifetime: 904 hours (37 days + 16 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 50 80 68 f5 cd 40 at LBA = 0x00cdf568 = 13497704

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 03 80 00 f5 cd 40 00 37d+16:37:00.000 READ FPDMA QUEUED
2f 00 01 10 00 00 e0 00 37d+16:37:00.000 READ LOG EXT
60 00 80 00 f5 cd 40 00 37d+16:37:00.000 READ FPDMA QUEUED
2f 00 01 10 00 00 e0 00 37d+16:37:00.000 READ LOG EXT
60 00 80 00 f5 cd 40 00 37d+16:37:00.000 READ FPDMA QUEUED

Error -1 occurred at disk power-on lifetime: 904 hours (37 days + 16 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 50 80 68 f5 cd 40 at LBA = 0x00cdf568 = 13497704

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 80 00 f5 cd 40 00 37d+16:37:00.000 READ FPDMA QUEUED
2f 00 01 10 00 00 e0 00 37d+16:37:00.000 READ LOG EXT
60 00 80 00 f5 cd 40 00 37d+16:37:00.000 READ FPDMA QUEUED
2f 00 01 10 00 00 e0 00 37d+16:37:00.000 READ LOG EXT
60 00 80 00 f5 cd 40 00 37d+16:37:00.000 READ FPDMA QUEUED

Error -2 occurred at disk power-on lifetime: 904 hours (37 days + 16 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 50 80 68 f5 cd 40 at LBA = 0x00cdf568 = 13497704

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 80 00 f5 cd 40 00 37d+16:37:00.000 READ FPDMA QUEUED
2f 00 01 10 00 00 e0 00 37d+16:37:00.000 READ LOG EXT
60 00 80 00 f5 cd 40 00 37d+16:37:00.000 READ FPDMA QUEUED
2f 00 01 10 00 00 e0 00 37d+16:37:00.000 READ LOG EXT
60 02 80 00 f5 cd 40 00 37d+16:37:00.000 READ FPDMA QUEUED

Error -3 occurred at disk power-on lifetime: 904 hours (37 days + 16 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 50 80 68 f5 cd 40 at LBA = 0x00cdf568 = 13497704

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 80 00 f5 cd 40 00 37d+16:37:00.000 READ FPDMA QUEUED
2f 00 01 10 00 00 e0 00 37d+16:37:00.000 READ LOG EXT
60 02 80 00 f5 cd 40 00 37d+16:37:00.000 READ FPDMA QUEUED
60 03 80 80 f5 cd 40 00 37d+16:37:00.000 READ FPDMA QUEUED
2f 00 01 10 00 00 e0 00 37d+16:37:00.000 READ LOG EXT

Error -4 occurred at disk power-on lifetime: 904 hours (37 days + 16 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 50 80 68 f5 cd 40 at LBA = 0x00cdf568 = 13497704

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 02 80 00 f5 cd 40 00 37d+16:37:00.000 READ FPDMA QUEUED
60 03 80 80 f5 cd 40 00 37d+16:37:00.000 READ FPDMA QUEUED
2f 00 01 10 00 00 e0 00 37d+16:37:00.000 READ LOG EXT
60 00 80 80 f5 cd 40 00 37d+16:37:00.000 READ FPDMA QUEUED
60 00 80 00 f5 cd 40 00 37d+16:37:00.000 READ FPDMA QUEUED

SMART 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 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.

 

Memory Leak Geek
rus-transit
Posts: 4
Registered: ‎09-07-2013
0

Re: m4 256gb msata read errors

in reply to epsalmond

 


epsalmond wrote:

 

Try the "manual install" method.  It comes with an ISO


Thanks.

 

But there are no ISO image "07MH"  firmware for M4 [u]mSATA[/u].

I would be afraid to apply the "crucial-03093l.iso"

 

Now I install Crucial mSATA to NUC.

Its was no detected : (((

 

Memory Leak Geek
rus-transit
Posts: 4
Registered: ‎09-07-2013
0

Re: m4 256gb msata read errors

[ Edited ]
in reply to epsalmond

After some time Crucial M4 mSATA was detected in NUC.

 

Win8.1  was installed.

 

Firmware update utility was finished with crash.

Problem signatire :
  Name                  : APPCRASH
...
  Version               : 1.0.0.42
  Application timestamp : 513faf39
  Error module name     : MicronIOLib-DllInterface.dll
  Error module version  : 0.0.0.0
  Error module timestamp: 513faf38
  Exception code        : c00000fd
  Exception offset      : 0001c7f7
  OS version            : 6.3.9431.2.0.0.256.48
---
-= Quick translated  =-

 But FW was updated.

 

RESULT

 

 

HD Tune Pro: M4-CT256M4SSD3 Error Scan

Scanned data &colon; 212 gB
Damaged Blocks : 22.8 %
Elapsed Time : 28:31
1 Error at 244 MB (LBA 501714)
2 Error at 1135 MB (LBA 2325891)
3 Error at 1186 MB (LBA 2429059)
. . .
570 Error at 174377 MB (LBA 357124241)

 

 

 

Kilobyte Kid
epsalmond
Posts: 5
Registered: ‎08-28-2013
0

Re: m4 256gb msata read errors

in reply to epsalmond
Did you write zeros to the drive, or does it still have your old data? That's what I had to with mine (pv /dev/zero > /dev/sda) to get it reading properly (pv /dev/sda > /dev/null) again.

Badblocks, DD or PV are tools I normally use for this sort of thing. I'm not familiar with HD tune.