You are not logged in.

#1 2016-01-16 10:14:12

Soukyuu
Member
Registered: 2014-04-08
Posts: 780

[NOT-SOLVED] Crucial m4 SSD suddenly only running in SATA3.0Gb/s mode

The device is a SATA6.0Gb/s capable device, and was running that last time I checked.

# smartctl -x /dev/sda| grep SATA
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)

The drive registers as SATA 3.0Gb/s on startup:

dmesg | grep ata
[    0.953381] libata version 3.00 loaded.
[    0.956380] scsi host0: pata_jmicron
[    0.957697] scsi host2: pata_jmicron
[    0.957738] ata1: PATA max UDMA/100 cmd 0xef00 ctl 0xee00 bmdma 0xeb00 irq 19
[    0.957740] ata2: PATA max UDMA/100 cmd 0xed00 ctl 0xec00 bmdma 0xeb08 irq 19
[    0.960320] ata3: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff100 irq 19
[    0.960323] ata4: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff180 irq 19
[    0.960325] ata5: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff200 irq 19
[    0.960327] ata6: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff280 irq 19
[    0.960329] ata7: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff300 irq 19
[    0.960331] ata8: SATA max UDMA/133 abar m1024@0xfdfff000 port 0xfdfff380 irq 19
[    0.971886] ata9: SATA max UDMA/133 abar m8192@0xfdbfe000 port 0xfdbfe100 irq 18
[    0.971889] ata10: SATA max UDMA/133 abar m8192@0xfdbfe000 port 0xfdbfe180 irq 18
[    1.268851] ata8: SATA link down (SStatus 0 SControl 300)
[    1.268885] ata5: SATA link down (SStatus 0 SControl 300)
[    1.268911] ata6: SATA link down (SStatus 0 SControl 300)
[    1.276897] ata9: SATA link down (SStatus 0 SControl 300)
[    1.276928] ata10: SATA link down (SStatus 0 SControl 300)
[    1.420043] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.420412] ata3.00: ATA-9: M4-CT128M4SSD2, 070H, max UDMA/100
[    1.420414] ata3.00: 250069680 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    1.420859] ata3.00: configured for UDMA/100
[    1.424096] ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.426088] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.430439] ata7.00: HPA detected: current 625140335, native 625142448
[    1.430498] ata7.00: ATA-7: SAMSUNG HD322HJ, 1AG01118, max UDMA7
[    1.430500] ata7.00: 625140335 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[    1.431461] ata4.00: ATA-7: SAMSUNG HD250HJ, FH100-06, max UDMA7
[    1.431464] ata4.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[    1.436884] ata4.00: configured for UDMA/133
[    1.436962] ata7.00: configured for UDMA/133
[    4.104188] systemd[1]: Listening on LVM2 metadata daemon socket.
[    4.215132] acpi-cpufreq: overriding BIOS provided _PSD data
[    4.451176] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: data=ordered

The two other drives are SATA 3.0Gb/s drives, so that's not a problem. The controller is capable of SATA6.0Gb/s, because another SATA6.0Gb/s device registers as such:

[  229.638997] ata5: exception Emask 0x10 SAct 0x0 SErr 0x40d0000 action 0xe frozen
[  229.639002] ata5: irq_stat 0x00400040, connection status changed
[  229.639005] ata5: SError: { PHYRdyChg CommWake 10B8B DevExch }
[  229.639011] ata5: hard resetting link
[  237.484286] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  237.485400] ata5.00: ATA-9: ST2000DM001-1ER164, CC26, max UDMA/133
[  237.485412] ata5.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[  237.486422] ata5.00: configured for UDMA/133
[  237.486439] ata5: EH complete

Currently on 4.3.3-2-ck, but using mainline doesn't seem to affect anything. Any idea why the drive suddenly only registering @3.0Gb/s? Is there a way to force it back to 6.0Gb/s?

edit: it also ran in 3.0Gb/s mode on windows, according to smartmontools. I have then changed the cable and it booted to 6.0Gb/s in windows. The drive is NOT being detected AT ALL in linux now, though?! All I get is "a start job is running for device <number sequence>" then it drops me to a recovery shell. Lsblk doesn't list the SSD.

edit: it seems I have a choice between a bootable archlinux @ 3.0Gb/s + windows @ 3.0Gb/s (cable A) and an unbootable archlinux + windows @ 6.0Gb/s (cable B).
In case B, the SSD is visible in BIOS and libata actually registers it @ 6.0Gb/s, but lsblk doesn't list it.

edit: well, cable C seems to have done the trick. Both OSes boot now @6.0Gb/s
Why would my cable A suddenly go bad though, without me touching it for years (or transporting the PC anywhere)?

Last edited by Soukyuu (2016-01-23 16:11:35)


[ Arch x86_64 | linux-ck-k10 | Custom-built | AMD Phenom II X4@3,5Ghz | nVidia 260 GTX | 12GB RAM | Main w/ Win 10 x64 dualboot ]
[ Arch x86_64 | linux-ck-core2 | Zepto 6625WD | Intel C2D T7250@2,0GHz | nVidia 8600m GT | 4GB RAM | Backup/Experimental]
[ Arch x86_64 | linux-ck-bobcat | Zotac AD02 | AMD Zacate e-350@1,2GHz | Radeon 6310 | 4GB RAM | Home Server ]

Offline

#2 2016-01-16 13:05:42

graysky
Member
From: /run/user/1000
Registered: 2008-12-01
Posts: 8,611
Website

Re: [NOT-SOLVED] Crucial m4 SSD suddenly only running in SATA3.0Gb/s mode

Soukyuu wrote:

Why would my cable A suddenly go bad though, without me touching it for years (or transporting the PC anywhere)?

https://www.youtube.com/watch?v=YeBGZMj49fo


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#3 2016-01-23 16:12:10

Soukyuu
Member
Registered: 2014-04-08
Posts: 780

Re: [NOT-SOLVED] Crucial m4 SSD suddenly only running in SATA3.0Gb/s mode

So we're back to

[    1.306011] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.306380] ata3.00: ATA-9: M4-CT128M4SSD2, 070H, max UDMA/100
[    1.306382] ata3.00: 250069680 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    1.306828] ata3.00: configured for UDMA/100

Is this thing mocking me?


[ Arch x86_64 | linux-ck-k10 | Custom-built | AMD Phenom II X4@3,5Ghz | nVidia 260 GTX | 12GB RAM | Main w/ Win 10 x64 dualboot ]
[ Arch x86_64 | linux-ck-core2 | Zepto 6625WD | Intel C2D T7250@2,0GHz | nVidia 8600m GT | 4GB RAM | Backup/Experimental]
[ Arch x86_64 | linux-ck-bobcat | Zotac AD02 | AMD Zacate e-350@1,2GHz | Radeon 6310 | 4GB RAM | Home Server ]

Offline

#4 2016-01-24 03:56:59

R00KIE
Forum Moderator
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 3,282

Re: [NOT-SOLVED] Crucial m4 SSD suddenly only running in SATA3.0Gb/s mode

Soukyuu wrote:

Is this thing mocking me?

I keep saying "feed the gremlins inside your computer well, you don't want them to get upset" but no one ever listens ...

On a more serious note, have you changed anything lately? Maybe updated firmware/bios/uefi, change bios/uefi options, add more drives or addon cards? Did you add anything new around your computer or at home, something that might use a considerable amount of power or create interference.

If you can get the drive to get recognized at 6Gbps can you "benchmark" it with 'hdparm -t /dev/sdX' from the arch boot iso? What do you get from dmesg in this case if it fails/succeeds? Also try checking the output of 'smartctl -x /dev/sdX' as it provides some more info and there might be some clues there.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#5 2016-01-24 10:05:03

Soukyuu
Member
Registered: 2014-04-08
Posts: 780

Re: [NOT-SOLVED] Crucial m4 SSD suddenly only running in SATA3.0Gb/s mode

I can, with complete confidence, say that I didn't change anything hardware related (or software related), simply because I lately have no spare time. About the only thing I did was installing ruby-1.9 and messing with my sshfs fstab entries, but I don't see how that could have affected something.

I haven't been able to get it to run in 6.0 mode again so far, except in windows.

smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.3.3-2-ck] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Crucial/Micron RealSSD m4/C400/P400
Device Model:     M4-CT128M4SSD2
Serial Number:    
LU WWN Device Id: 5 00a075 10319ed17
Firmware Version: 070H
User Capacity:    128,035,676,160 bytes [128 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sun Jan 24 11:03:09 2016 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: 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:                (  595) 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:        (   9) 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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   100   100   050    -    0
  5 Reallocated_Sector_Ct   PO--CK   100   100   010    -    0
  9 Power_On_Hours          -O--CK   100   100   001    -    14853
 12 Power_Cycle_Count       -O--CK   100   100   001    -    4219
170 Grown_Failing_Block_Ct  PO--CK   100   100   010    -    0
171 Program_Fail_Count      -O--CK   100   100   001    -    101
172 Erase_Fail_Count        -O--CK   100   100   001    -    69
173 Wear_Leveling_Count     PO--CK   097   097   010    -    113
174 Unexpect_Power_Loss_Ct  -O--CK   100   100   001    -    46
181 Non4k_Aligned_Access    -O---K   100   100   001    -    3444 934 2510
183 SATA_Iface_Downshift    -O--CK   100   100   001    -    0
184 End-to-End_Error        PO--CK   100   100   050    -    0
187 Reported_Uncorrect      -O--CK   100   100   001    -    0
188 Command_Timeout         -O--CK   100   100   001    -    0
189 Factory_Bad_Block_Ct    -OSR--   100   100   001    -    85
194 Temperature_Celsius     -O---K   100   100   000    -    0
195 Hardware_ECC_Recovered  -O-RCK   100   100   001    -    0
196 Reallocated_Event_Count -O--CK   100   100   001    -    0
197 Current_Pending_Sector  -O--CK   100   100   001    -    0
198 Offline_Uncorrectable   ----CK   100   100   001    -    0
199 UDMA_CRC_Error_Count    -O--CK   100   100   001    -    1
202 Perc_Rated_Life_Used    ---RC-   097   097   001    -    3
206 Write_Error_Rate        -OSR--   100   100   001    -    101
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O     51  Comprehensive SMART error log
0x03       GPL     R/O  16383  Ext. Comprehensive SMART error log
0x04       GPL,SL  R/O    255  Device Statistics log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O   3449  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  SATA NCQ Queued Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa0       GPL     VS    2000  Device vendor specific log
0xa0       SL      VS     208  Device vendor specific log
0xa1-0xbf  GPL,SL  VS       1  Device vendor specific log
0xc0       GPL     VS      80  Device vendor specific log
0xc1-0xdf  GPL,SL  VS       1  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (16383 sectors)
No Errors Logged

SMART Extended Self-test Log size 3449 not supported

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.

SCT Status Version:                  3
SCT Version (vendor specific):       1 (0x0001)
SCT Support Level:                   0
Device State:                        Active (0)
Current Temperature:                  0 Celsius
Power Cycle Max Temperature:          0 Celsius
Lifetime    Max Temperature:          0 Celsius

SCT Temperature History Version:     2
Temperature Sampling Period:         10 minutes
Temperature Logging Interval:        10 minutes
Min/Max recommended Temperature:      0/70 Celsius
Min/Max Temperature Limit:           -5/75 Celsius
Temperature History Size (Index):    478 (395)

Index    Estimated Time   Temperature Celsius
 396    2016-01-21 03:30     ?  -
 ...    ..(476 skipped).    ..  -
 395    2016-01-24 11:00     ?  -

SCT Error Recovery Control:
           Read:     40 (4.0 seconds)
          Write:     40 (4.0 seconds)

Device Statistics (GP Log 0x04)
Page  Offset Size        Value Flags Description
0x01  =====  =               =  ===  == General Statistics (rev 2) ==
0x01  0x008  4            4219  ---  Lifetime Power-On Resets
0x01  0x010  4           14853  ---  Power-on Hours
0x01  0x018  6     20705231092  ---  Logical Sectors Written
0x01  0x020  6       388257782  ---  Number of Write Commands
0x01  0x028  6     32273522732  ---  Logical Sectors Read
0x01  0x030  6       511890600  ---  Number of Read Commands
0x04  =====  =               =  ===  == General Errors Statistics (rev 1) ==
0x04  0x008  4               0  ---  Number of Reported Uncorrectable Errors
0x04  0x010  4               0  ---  Resets Between Cmd Acceptance and Completion
0x05  =====  =               =  ===  == Temperature Statistics (rev 1) ==
0x05  0x008  1               0  ---  Current Temperature
0x05  0x010  1               0  ---  Average Short Term Temperature
0x05  0x018  1               0  ---  Average Long Term Temperature
0x05  0x020  1               0  ---  Highest Temperature
0x05  0x028  1               0  ---  Lowest Temperature
0x05  0x030  1               0  ---  Highest Average Short Term Temperature
0x05  0x038  1               0  ---  Lowest Average Short Term Temperature
0x05  0x040  1               0  ---  Highest Average Long Term Temperature
0x05  0x048  1               0  ---  Lowest Average Long Term Temperature
0x05  0x050  4               -  ---  Time in Over-Temperature
0x05  0x058  1              70  ---  Specified Maximum Operating Temperature
0x05  0x060  4               -  ---  Time in Under-Temperature
0x05  0x068  1               0  ---  Specified Minimum Operating Temperature
0x06  =====  =               =  ===  == Transport Statistics (rev 1) ==
0x06  0x008  4             184  ---  Number of Hardware Resets
0x06  0x010  4               0  ---  Number of ASR Events
0x06  0x018  4               1  ---  Number of Interface CRC Errors
0x07  =====  =               =  ===  == Solid State Device Statistics (rev 1) ==
0x07  0x008  1               4  N--  Percentage Used Endurance Indicator
                                |||_ C monitored condition met
                                ||__ D supports DSN
                                |___ N normalized value

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  4            0  Command failed due to ICRC error
0x000a  4            8  Device-to-host register FISes sent due to a COMRESET

edit: turns out it's now not running in 6.0 on windows, either. *sigh*

Last edited by Soukyuu (2016-01-24 21:49:30)


[ Arch x86_64 | linux-ck-k10 | Custom-built | AMD Phenom II X4@3,5Ghz | nVidia 260 GTX | 12GB RAM | Main w/ Win 10 x64 dualboot ]
[ Arch x86_64 | linux-ck-core2 | Zepto 6625WD | Intel C2D T7250@2,0GHz | nVidia 8600m GT | 4GB RAM | Backup/Experimental]
[ Arch x86_64 | linux-ck-bobcat | Zotac AD02 | AMD Zacate e-350@1,2GHz | Radeon 6310 | 4GB RAM | Home Server ]

Offline

#6 2016-01-24 15:15:13

R00KIE
Forum Moderator
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 3,282

Re: [NOT-SOLVED] Crucial m4 SSD suddenly only running in SATA3.0Gb/s mode

I don't see anything that looks out of place in the output of smartctl. If you have time try to connect the drive to one of the ports that now works at 6Gbps and see what happens. Try to connect only one drive at a time. Check for dust on the motherboard, dust and humidity could be a reason to make it work slower (unlikely but still worth checking).

Little tip, you may want to use 'smartctl -q noserial' to avoid disclosing your drive's serial number.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#7 2016-01-24 21:50:07

Soukyuu
Member
Registered: 2014-04-08
Posts: 780

Re: [NOT-SOLVED] Crucial m4 SSD suddenly only running in SATA3.0Gb/s mode

What would someone do with my drive's serial number? o_O


[ Arch x86_64 | linux-ck-k10 | Custom-built | AMD Phenom II X4@3,5Ghz | nVidia 260 GTX | 12GB RAM | Main w/ Win 10 x64 dualboot ]
[ Arch x86_64 | linux-ck-core2 | Zepto 6625WD | Intel C2D T7250@2,0GHz | nVidia 8600m GT | 4GB RAM | Backup/Experimental]
[ Arch x86_64 | linux-ck-bobcat | Zotac AD02 | AMD Zacate e-350@1,2GHz | Radeon 6310 | 4GB RAM | Home Server ]

Offline

#8 2016-01-24 23:57:13

R00KIE
Forum Moderator
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 3,282

Re: [NOT-SOLVED] Crucial m4 SSD suddenly only running in SATA3.0Gb/s mode

Soukyuu wrote:

What would someone do with my drive's serial number? o_O

I don't know but here [1] it says to report new drives with the -q noserial option, I suppose there must be a reason for that.

[1] https://www.smartmontools.org/wiki/FAQ# … tddatabase


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#9 2016-01-25 20:36:42

Soukyuu
Member
Registered: 2014-04-08
Posts: 780

Re: [NOT-SOLVED] Crucial m4 SSD suddenly only running in SATA3.0Gb/s mode

Connected it to another port, booted up as 6.0Gbps. hdparm -t says:

Timing buffered disk reads: 1226 MB in  3.00 seconds = 408.67 MB/sec

smartctl also says it's running at 6.0Gbps:

smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.3.3-2-ck] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Crucial/Micron RealSSD m4/C400/P400
Device Model:     M4-CT128M4SSD2
Firmware Version: 070H
User Capacity:    128,035,676,160 bytes [128 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Jan 25 21:35:33 2016 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: 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:                (  595) 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:        (   9) 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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   100   100   050    -    0
  5 Reallocated_Sector_Ct   PO--CK   100   100   010    -    0
  9 Power_On_Hours          -O--CK   100   100   001    -    14866
 12 Power_Cycle_Count       -O--CK   100   100   001    -    4222
170 Grown_Failing_Block_Ct  PO--CK   100   100   010    -    0
171 Program_Fail_Count      -O--CK   100   100   001    -    101
172 Erase_Fail_Count        -O--CK   100   100   001    -    69
173 Wear_Leveling_Count     PO--CK   097   097   010    -    113
174 Unexpect_Power_Loss_Ct  -O--CK   100   100   001    -    46
181 Non4k_Aligned_Access    -O---K   100   100   001    -    3445 934 2511
183 SATA_Iface_Downshift    -O--CK   100   100   001    -    0
184 End-to-End_Error        PO--CK   100   100   050    -    0
187 Reported_Uncorrect      -O--CK   100   100   001    -    0
188 Command_Timeout         -O--CK   100   100   001    -    0
189 Factory_Bad_Block_Ct    -OSR--   100   100   001    -    85
194 Temperature_Celsius     -O---K   100   100   000    -    0
195 Hardware_ECC_Recovered  -O-RCK   100   100   001    -    0
196 Reallocated_Event_Count -O--CK   100   100   001    -    0
197 Current_Pending_Sector  -O--CK   100   100   001    -    0
198 Offline_Uncorrectable   ----CK   100   100   001    -    0
199 UDMA_CRC_Error_Count    -O--CK   100   100   001    -    1
202 Perc_Rated_Life_Used    ---RC-   097   097   001    -    3
206 Write_Error_Rate        -OSR--   100   100   001    -    101
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O     51  Comprehensive SMART error log
0x03       GPL     R/O  16383  Ext. Comprehensive SMART error log
0x04       GPL,SL  R/O    255  Device Statistics log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O   3449  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  SATA NCQ Queued Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa0       GPL     VS    2000  Device vendor specific log
0xa0       SL      VS     208  Device vendor specific log
0xa1-0xbf  GPL,SL  VS       1  Device vendor specific log
0xc0       GPL     VS      80  Device vendor specific log
0xc1-0xdf  GPL,SL  VS       1  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (16383 sectors)
No Errors Logged

SMART Extended Self-test Log size 3449 not supported

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.

SCT Status Version:                  3
SCT Version (vendor specific):       1 (0x0001)
SCT Support Level:                   0
Device State:                        Active (0)
Current Temperature:                  0 Celsius
Power Cycle Max Temperature:          0 Celsius
Lifetime    Max Temperature:          0 Celsius

SCT Temperature History Version:     2
Temperature Sampling Period:         10 minutes
Temperature Logging Interval:        10 minutes
Min/Max recommended Temperature:      0/70 Celsius
Min/Max Temperature Limit:           -5/75 Celsius
Temperature History Size (Index):    478 (398)

Index    Estimated Time   Temperature Celsius
 399    2016-01-22 14:00     ?  -
 ...    ..(476 skipped).    ..  -
 398    2016-01-25 21:30     ?  -

SCT Error Recovery Control:
           Read:     40 (4.0 seconds)
          Write:     40 (4.0 seconds)

Device Statistics (GP Log 0x04)
Page  Offset Size        Value Flags Description
0x01  =====  =               =  ===  == General Statistics (rev 2) ==
0x01  0x008  4            4222  ---  Lifetime Power-On Resets
0x01  0x010  4           14866  ---  Power-on Hours
0x01  0x018  6     20710824420  ---  Logical Sectors Written
0x01  0x020  6       388369512  ---  Number of Write Commands
0x01  0x028  6     32303171313  ---  Logical Sectors Read
0x01  0x030  6       512219598  ---  Number of Read Commands
0x04  =====  =               =  ===  == General Errors Statistics (rev 1) ==
0x04  0x008  4               0  ---  Number of Reported Uncorrectable Errors
0x04  0x010  4               0  ---  Resets Between Cmd Acceptance and Completion
0x05  =====  =               =  ===  == Temperature Statistics (rev 1) ==
0x05  0x008  1               0  ---  Current Temperature
0x05  0x010  1               0  ---  Average Short Term Temperature
0x05  0x018  1               0  ---  Average Long Term Temperature
0x05  0x020  1               0  ---  Highest Temperature
0x05  0x028  1               0  ---  Lowest Temperature
0x05  0x030  1               0  ---  Highest Average Short Term Temperature
0x05  0x038  1               0  ---  Lowest Average Short Term Temperature
0x05  0x040  1               0  ---  Highest Average Long Term Temperature
0x05  0x048  1               0  ---  Lowest Average Long Term Temperature
0x05  0x050  4               -  ---  Time in Over-Temperature
0x05  0x058  1              70  ---  Specified Maximum Operating Temperature
0x05  0x060  4               -  ---  Time in Under-Temperature
0x05  0x068  1               0  ---  Specified Minimum Operating Temperature
0x06  =====  =               =  ===  == Transport Statistics (rev 1) ==
0x06  0x008  4             184  ---  Number of Hardware Resets
0x06  0x010  4               0  ---  Number of ASR Events
0x06  0x018  4               1  ---  Number of Interface CRC Errors
0x07  =====  =               =  ===  == Solid State Device Statistics (rev 1) ==
0x07  0x008  1               4  N--  Percentage Used Endurance Indicator
                                |||_ C monitored condition met
                                ||__ D supports DSN
                                |___ N normalized value

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  4            0  Command failed due to ICRC error
0x000a  4            3  Device-to-host register FISes sent due to a COMRESET

It also booted about 3 seconds faster.

I haven't saved the results in 3.0Gbps, but it was something around 275MB/sec.

edit: now it also runs in 6.0 mode on the old port again. I will monitor the thing for a while.
Tried blowing out any dust that might have gotten into the SATA port, but I'm not sure how it would have gotten there considering I never removed the cable since I out the SSD in there. The first time I did was after the trouble started...

Last edited by Soukyuu (2016-01-25 20:46:42)


[ Arch x86_64 | linux-ck-k10 | Custom-built | AMD Phenom II X4@3,5Ghz | nVidia 260 GTX | 12GB RAM | Main w/ Win 10 x64 dualboot ]
[ Arch x86_64 | linux-ck-core2 | Zepto 6625WD | Intel C2D T7250@2,0GHz | nVidia 8600m GT | 4GB RAM | Backup/Experimental]
[ Arch x86_64 | linux-ck-bobcat | Zotac AD02 | AMD Zacate e-350@1,2GHz | Radeon 6310 | 4GB RAM | Home Server ]

Offline

#10 2016-01-29 21:37:13

Soukyuu
Member
Registered: 2014-04-08
Posts: 780

Re: [NOT-SOLVED] Crucial m4 SSD suddenly only running in SATA3.0Gb/s mode

Back to 3.0 without me changing, or moving anything again. Btw, hdparm says

Timing buffered disk reads: 774 MB in  3.00 seconds = 257.80 MB/sec

[ Arch x86_64 | linux-ck-k10 | Custom-built | AMD Phenom II X4@3,5Ghz | nVidia 260 GTX | 12GB RAM | Main w/ Win 10 x64 dualboot ]
[ Arch x86_64 | linux-ck-core2 | Zepto 6625WD | Intel C2D T7250@2,0GHz | nVidia 8600m GT | 4GB RAM | Backup/Experimental]
[ Arch x86_64 | linux-ck-bobcat | Zotac AD02 | AMD Zacate e-350@1,2GHz | Radeon 6310 | 4GB RAM | Home Server ]

Offline

#11 2016-01-29 21:47:20

slithery
Member
Registered: 2013-12-01
Posts: 790

Re: [NOT-SOLVED] Crucial m4 SSD suddenly only running in SATA3.0Gb/s mode

Bit of a shot in the dark but are you overclocking your computer?

Last edited by slithery (2016-01-29 21:47:59)

Online

#12 2016-01-29 22:01:59

mich41
Member
Registered: 2012-06-22
Posts: 592

Re: [NOT-SOLVED] Crucial m4 SSD suddenly only running in SATA3.0Gb/s mode

I suppose it may be caused by some components on the motherboard or SSD going out-of-spec with time. Can you get another 6G device to test this motherboard? Many magnetic disks support 6G even if they are dog slow and few years old.

Noisy voltage outputs from the PSU could be another suspect. At least maybe theoretically, I'm not sure if it actually happens.

Also, avoid tightly bending SATA cables (any high speed cables, really) and routing them close to power cables, PSUs, GPUs, basically any high-power electric stuff.

Last edited by mich41 (2016-01-29 22:19:25)

Offline

#13 2016-01-29 23:11:48

R00KIE
Forum Moderator
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 3,282

Re: [NOT-SOLVED] Crucial m4 SSD suddenly only running in SATA3.0Gb/s mode

I second what mich41 says about handling and routing of sata cables. Regarding the power supply I though about saying something about that before but it could be a red herring given that nothing else seems affected.

I have seen a bad power supply cause stability problems only when creating tar.gz files, which seemed to point to a hard disk problem when the disk was just fine. If you have an extra known good power supply with can test with then maybe you can try, otherwise it's hard to justify buying a new one and later find out the problem is something else.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#14 2016-01-29 23:54:35

mich41
Member
Registered: 2012-06-22
Posts: 592

Re: [NOT-SOLVED] Crucial m4 SSD suddenly only running in SATA3.0Gb/s mode

Yep, swapping PSU should really be last-ditch effort, after making sure that all other hardware is in working order but before hiring an exorcist wink

Last edited by mich41 (2016-01-30 11:44:42)

Offline

#15 2016-01-30 11:00:49

Soukyuu
Member
Registered: 2014-04-08
Posts: 780

Re: [NOT-SOLVED] Crucial m4 SSD suddenly only running in SATA3.0Gb/s mode

I'm not overclocking, unless you count the factory OC of my GPU. The SATA cables do pass close to the main PSU cable that provides power to the mainboard, but moving the one connected to my SSD doesn't solve the issue. I've also tried all ports now, and it's still only running in 3.0Gbps on all of them. However, my archive HDD is running in 6.0Gbps as it should. It is located on top of my CoolerMaster 690 II, in the HDD docking bay. I've moved my SSD there to test it, and no dice, still 3.0Gbps only.

I had a bad HDD that caused exceptions in dmesg after which it went from 6.0 -> 3.0 -> 1.5, pulling everything else 6.0->3.0, but it's long gone, and there are no errors in dmesg. Despite S.M.A.R.T saying only 3% of it's life time is used, I'm starting to suspect it's trying to give out on me...

Last edited by Soukyuu (2016-01-30 11:01:02)


[ Arch x86_64 | linux-ck-k10 | Custom-built | AMD Phenom II X4@3,5Ghz | nVidia 260 GTX | 12GB RAM | Main w/ Win 10 x64 dualboot ]
[ Arch x86_64 | linux-ck-core2 | Zepto 6625WD | Intel C2D T7250@2,0GHz | nVidia 8600m GT | 4GB RAM | Backup/Experimental]
[ Arch x86_64 | linux-ck-bobcat | Zotac AD02 | AMD Zacate e-350@1,2GHz | Radeon 6310 | 4GB RAM | Home Server ]

Offline

#16 2016-01-30 12:06:51

mich41
Member
Registered: 2012-06-22
Posts: 592

Re: [NOT-SOLVED] Crucial m4 SSD suddenly only running in SATA3.0Gb/s mode

"Remaining lifetime" refers to flash memory wearout and is unrelated to the SATA port of the controller. The controller isn't really supposed to degrade with time, although sometimes it does happen that chips fail.

Did you try it in another machine? Is this temperature-related in any way?
I suppose the SSD is sitting in its case and there is no way for junk to end up on the PCB?

Last edited by mich41 (2016-01-30 12:07:36)

Offline

#17 2016-01-30 14:19:56

Soukyuu
Member
Registered: 2014-04-08
Posts: 780

Re: [NOT-SOLVED] Crucial m4 SSD suddenly only running in SATA3.0Gb/s mode

Yes, I know it refers to the flash memory cycle, I thought that maybe the performance drop could be related somehow.

On the other PC, which incidentally has an identical SSD running at 6.0Gbps (but otherwise completely different hardware), this one also runs at 3.0Gbps only.
Of course after returning it to this PC it suddenly booted up at 6.0Gbps again. The first test today was done on a cold boot, then it ran for a few hours (made a backup of the OS, updated via pacman...) then I plopped it into another PC.

So I don't think it's related to temperature. I'm starting to think it's the SATA controller on the SSD, as well.


[ Arch x86_64 | linux-ck-k10 | Custom-built | AMD Phenom II X4@3,5Ghz | nVidia 260 GTX | 12GB RAM | Main w/ Win 10 x64 dualboot ]
[ Arch x86_64 | linux-ck-core2 | Zepto 6625WD | Intel C2D T7250@2,0GHz | nVidia 8600m GT | 4GB RAM | Backup/Experimental]
[ Arch x86_64 | linux-ck-bobcat | Zotac AD02 | AMD Zacate e-350@1,2GHz | Radeon 6310 | 4GB RAM | Home Server ]

Offline

Board footer

Powered by FluxBB