Squall Leonhart Posted January 5, 2017 Share Posted January 5, 2017 I recently picked up an MX300 and a number of smart fields are listed as <Vendor - specific>. These fields don't seem much unchanged from the mx200, From the MX200 ID Attribute Description Threshold Value Worst Data Status 01 Raw Read Error Rate 0 100 100 0 OK: Always passes 05 Reallocated Sector Count 10 100 100 0 OK: Value is normal 09 Power-On Hours Count 0 100 100 15047 OK: Always passes 0C Power Cycle Count 0 100 100 83 OK: Always passes AB Program Fail Count 0 100 100 0 OK: Always passes AC Erase Fail Count 0 100 100 0 OK: Always passes AD Wear Leveling Count 0 95 95 177 OK: Always passes AE Unexpected Power Loss Count 0 100 100 75 OK: Always passes B4 Unused Reserve (Spare) NAND Blocks 0 0 0 2586 OK: Always passes B7 SATA Interface Downshift 0 100 100 15 OK: Always passes B8 Error Correction Count 0 100 100 0 OK: Always passes BB Reported Uncorrectable Errors 0 100 100 0 OK: Always passes C2 Enclosure Temperature 0 62 49 51, 24, 38 OK: Always passes C4 Re-allocation Event Count 0 100 100 0 OK: Always passes C5 Current Pending Sector Count 0 100 100 0 OK: Always passes C6 SMART Off-line Scan Uncorrectable Error Count 0 100 100 0 OK: Always passes C7 Ultra DMA CRC Error Rate 0 100 100 4695 OK: Always passes CA Percentage Of The Rated Lifetime Used 1 95 95 5 OK: Value is normal CE Write Error Rate 0 100 100 0 OK: Always passes D2 Successful RAIN Recovery Count 0 100 100 0 OK: Always passes F6 Total Host Sector Writes 0 100 100 22.77 TB OK: Always passes F7 Host Program Page Count 0 100 100 1528632514 OK: Always passes F8 FTL Program Page Count 0 100 100 281716231 OK: Always passes From the MX300 ID Attribute Description Threshold Value Worst Data Status 01 Raw Read Error Rate 0 100 100 0 OK: Always passes 05 Reallocated Sector Count 10 100 100 0 OK: Value is normal 09 Power-On Time Count 0 100 100 1 OK: Always passes 0C Power Cycle Count 0 100 100 8 OK: Always passes AB <vendor-specific> 0 100 100 0 OK: Always passes AC <vendor-specific> 0 100 100 0 OK: Always passes AD <vendor-specific> 0 100 100 1 OK: Always passes AE <vendor-specific> 0 100 100 5 OK: Always passes B4 Host Program Page Count 0 100 100 1528632514 OK: Always passes B7 <vendor-specific> 0 100 100 0 OK: Always passes B8 End-to-End Error 0 100 100 0 OK: Always passes BB Reported Uncorrectable Errors 0 100 100 0 OK: Always passes C2 Temperature 0 60 60 40, 27, 40 OK: Always passes C4 Reallocation Event Count 0 100 100 0 OK: Always passes C5 Current Pending Sector Count 0 100 100 0 OK: Always passes C6 Offline Uncorrectable Sector Count 0 100 100 0 OK: Always passes C7 Ultra ATA CRC Error Rate 0 100 100 0 OK: Always passes CA Data Address Mark Errors 1 100 100 0 OK: Value is normal CE Flying Height 0 100 100 0 OK: Always passes < this field is named wrong for some reason, its the same as the writer error rate field on the mx200. D2 FTL Program Page Count 0 100 100 281716279 OK: Always passes F6 <vendor-specific> 0 100 100 8116072 OK: Always passes F7 <vendor-specific> 0 0 0 1936 OK: Always passes F8 Ramp Load Value 0 100 100 0 OK: Always passes Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 5, 2017 Share Posted January 5, 2017 Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery Quote Link to comment Share on other sites More sharing options...
Squall Leonhart Posted January 5, 2017 Author Share Posted January 5, 2017 Here you go Fiery. smartdump.txt Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 5, 2017 Share Posted January 5, 2017 Thank you. We'll implement advanced support for MX300 SSDs in the next AIDA64 beta update due next week Quote Link to comment Share on other sites More sharing options...
Squall Leonhart Posted January 11, 2017 Author Share Posted January 11, 2017 I see you have added the mx300 in the new beta I am seeing some odd GUI behaviour though when switching between the two ssd's though involving the smart fields If i select a HDD and then the MX200 or MX300 i see this mx200 ID Attribute Description Threshold Value Worst Data Status 01 Raw Read Error Rate 0 100 100 0 OK: Always passes 05 Reallocated Sector Count 10 100 100 0 OK: Value is normal 09 Power-On Hours Count 0 100 100 15201 OK: Always passes 0C Power Cycle Count 0 100 100 84 OK: Always passes AB Program Fail Count 0 100 100 0 OK: Always passes AC Erase Fail Count 0 100 100 0 OK: Always passes AD Wear Leveling Count 0 95 95 178 OK: Always passes AE Unexpected Power Loss Count 0 100 100 76 OK: Always passes B4 Unused Reserve (Spare) NAND Blocks 0 0 0 2586 OK: Always passes B7 SATA Interface Downshift 0 100 100 15 OK: Always passes B8 Error Correction Count 0 100 100 0 OK: Always passes BB Reported Uncorrectable Errors 0 100 100 0 OK: Always passes C2 Enclosure Temperature 0 63 49 51, 24, 37 OK: Always passes C4 Re-allocation Event Count 0 100 100 0 OK: Always passes C5 Current Pending Sector Count 0 100 100 0 OK: Always passes C6 SMART Off-line Scan Uncorrectable Error Count 0 100 100 0 OK: Always passes C7 Ultra DMA CRC Error Rate 0 100 100 4695 OK: Always passes CA Percentage Of The Rated Lifetime Used 1 95 95 5 OK: Value is normal CE Write Error Rate 0 100 100 0 OK: Always passes D2 Successful RAIN Recovery Count 0 100 100 0 OK: Always passes F6 Total Host Sector Writes 0 100 100 22.84 TB OK: Always passes F7 Host Program Page Count 0 100 100 1533394129 OK: Always passes F8 FTL Program Page Count 0 100 100 282356913 OK: Always passes mx300 ID Attribute Description Threshold Value Worst Data Status 01 Raw Read Error Rate 0 100 100 0 OK: Always passes 05 Reallocated Sector Count 10 100 100 0 OK: Value is normal 09 Power-On Hours Count 0 100 100 154 OK: Always passes 0C Power Cycle Count 0 100 100 8 OK: Always passes AB Program Fail Count 0 100 100 0 OK: Always passes AC Erase Fail Count 0 100 100 0 OK: Always passes AD Wear Leveling Count 0 100 100 3 OK: Always passes AE Unexpected Power Loss Count 0 100 100 5 OK: Always passes B4 Unused Reserve (Spare) NAND Blocks 0 0 0 1936 OK: Always passes B7 SATA Interface Downshift 0 100 100 0 OK: Always passes B8 Error Correction Count 0 100 100 0 OK: Always passes BB Reported Uncorrectable Errors 0 100 100 0 OK: Always passes C2 Enclosure Temperature 0 67 51 49, 27, 33 OK: Always passes C4 Re-allocation Event Count 0 100 100 0 OK: Always passes C5 Current Pending Sector Count 0 100 100 0 OK: Always passes C6 SMART Off-line Scan Uncorrectable Error Count 0 100 100 0 OK: Always passes C7 Ultra DMA CRC Error Rate 0 100 100 0 OK: Always passes CA Percentage Of The Rated Lifetime Used 1 100 100 0 OK: Value is normal CE Write Error Rate 0 100 100 0 OK: Always passes D2 Successful RAIN Recovery Count 0 100 100 0 OK: Always passes F6 Total Host Sector Writes 0 100 100 860.07 GB OK: Always passes F7 Host Program Page Count 0 100 100 56394814 OK: Always passes F8 FTL Program Page Count 0 100 100 16334715 OK: Always passes However, if i switch from SSD to SSD, it will do this mx200 ID Attribute Description Threshold Value Worst Data Status 01 Raw Read Error Rate 0 100 100 0 OK: Always passes 05 Reallocated Sector Count 10 100 100 0 OK: Value is normal 09 Power-On Hours Count 0 100 100 15201 OK: Always passes 0C Power Cycle Count 0 100 100 84 OK: Always passes AB Program Fail Count 0 100 100 0 OK: Always passes AC Erase Fail Count 0 100 100 0 OK: Always passes AD Wear Leveling Count 0 95 95 178 OK: Always passes AE Unexpected Power Loss Count 0 100 100 76 OK: Always passes B4 Host Program Page Count 0 100 100 1533394129 OK: Always passes B7 SATA Interface Downshift 0 100 100 15 OK: Always passes B8 Error Correction Count 0 100 100 0 OK: Always passes BB Reported Uncorrectable Errors 0 100 100 0 OK: Always passes C2 Enclosure Temperature 0 63 49 51, 24, 37 OK: Always passes C4 Re-allocation Event Count 0 100 100 0 OK: Always passes C5 Current Pending Sector Count 0 100 100 0 OK: Always passes C6 SMART Off-line Scan Uncorrectable Error Count 0 100 100 0 OK: Always passes C7 Ultra DMA CRC Error Rate 0 100 100 4695 OK: Always passes CA Percentage Of The Rated Lifetime Used 1 95 95 5 OK: Value is normal CE Host Program Page Count 0 100 100 56394814 OK: Always passes D2 FTL Program Page Count 0 100 100 282357425 OK: Always passes F6 Total Host Sector Writes 0 100 100 22.84 TB OK: Always passes F7 Host Program Page Count 0 100 100 1533394129 OK: Always passes F8 FTL Program Page Count 0 100 100 282357425 OK: Always passes mx300 ID Attribute Description Threshold Value Worst Data Status 01 Raw Read Error Rate 0 100 100 0 OK: Always passes 05 Reallocated Sector Count 10 100 100 0 OK: Value is normal 09 Power-On Hours Count 0 100 100 154 OK: Always passes 0C Power Cycle Count 0 100 100 8 OK: Always passes AB Program Fail Count 0 100 100 0 OK: Always passes AC Erase Fail Count 0 100 100 0 OK: Always passes AD Wear Leveling Count 0 100 100 3 OK: Always passes AE Unexpected Power Loss Count 0 100 100 5 OK: Always passes B4 Host Program Page Count 0 100 100 1533394129 OK: Always passes B7 SATA Interface Downshift 0 100 100 0 OK: Always passes B8 Error Correction Count 0 100 100 0 OK: Always passes BB Reported Uncorrectable Errors 0 100 100 0 OK: Always passes C2 Enclosure Temperature 0 67 51 49, 27, 33 OK: Always passes C4 Re-allocation Event Count 0 100 100 0 OK: Always passes C5 Current Pending Sector Count 0 100 100 0 OK: Always passes C6 SMART Off-line Scan Uncorrectable Error Count 0 100 100 0 OK: Always passes C7 Ultra DMA CRC Error Rate 0 100 100 0 OK: Always passes CA Percentage Of The Rated Lifetime Used 1 100 100 0 OK: Value is normal CE Write Error Rate 0 100 100 0 OK: Always passes D2 FTL Program Page Count 0 100 100 282357489 OK: Always passes F6 Host Program Page Count 0 100 100 56394814 OK: Always passes F7 Unused Reserve (Spare) NAND Blocks 0 0 0 1936 OK: Always passes F8 Successful RAIN Recovery Count 0 100 100 0 OK: Always passes Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 11, 2017 Share Posted January 11, 2017 Thank you for the feedback. Which drive of yours is the first one in the list of drives on the Storage / SMART page of AIDA64? Quote Link to comment Share on other sites More sharing options...
Squall Leonhart Posted January 14, 2017 Author Share Posted January 14, 2017 The MX200 is the first in the list Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 18, 2017 Share Posted January 18, 2017 Thank you. Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Quote Link to comment Share on other sites More sharing options...
Squall Leonhart Posted January 19, 2017 Author Share Posted January 19, 2017 it hasn't, im guessing it might be the controller doing it Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 20, 2017 Share Posted January 20, 2017 19 hours ago, Squall Leonhart said: it hasn't, im guessing it might be the controller doing it Thank you. Quite puzzling, since we've used SMART device emulation to verify the whole thing, but it works properly on our -- albeit emulated -- system. Would it be possible to record a video of the issue and upload it to Youtube or send us directly, so we could see what exactly are you clicking through (how exactly you navigate on the AIDA64 user interface), and what exactly is shown? In our efforts of trying to replicate the issue, maybe we're not doing what you're doing... Quote Link to comment Share on other sites More sharing options...
Squall Leonhart Posted January 21, 2017 Author Share Posted January 21, 2017 All im doing is selecting the MX300 after the MX200 and vice versa and the smart fields come back wrong, some of them duplicated or missing. This could just be a Jmicron glitch, or one that only occurs when used with MSAHCI drivers, jmicron drivers are slower and buggy, and don't work with SSD tools well at all. Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 23, 2017 Share Posted January 23, 2017 What kind of JMicron SATA controller do you have your SSDs hooked at? Quote Link to comment Share on other sites More sharing options...
Squall Leonhart Posted January 26, 2017 Author Share Posted January 26, 2017 JMB363, 1 esata, 1 internal sata, and a pata port for 2 devices. Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 26, 2017 Share Posted January 26, 2017 7 hours ago, Squall Leonhart said: JMB363, 1 esata, 1 internal sata, and a pata port for 2 devices. Thank you. Does it mean you've got only one of those SSDs connected to the JMB363 controller, and you've got the other one connected to the internal SATA controller of your chipset? Quote Link to comment Share on other sites More sharing options...
Squall Leonhart Posted February 2, 2017 Author Share Posted February 2, 2017 both are connected to the JMB chip presently, one connected to the rear esata port, and another connected on the case esata port. both of these will be going internal when my new build is ready. Quote Link to comment Share on other sites More sharing options...
Fiery Posted February 2, 2017 Share Posted February 2, 2017 5 hours ago, Squall Leonhart said: both are connected to the JMB chip presently, one connected to the rear esata port, and another connected on the case esata port. both of these will be going internal when my new build is ready. Thank you. Please let us know when your new build is ready. Let's hope it will solve this issue. If not, we'll keep hunting for the bug Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.