I have a feeling this is probably because the software is designed for hard drive diagnostics rather than there being a problem with the drive, but wanted to ask to be sure. The drive seems to work fine, but when viewing the SMART status using Western Digital Data Lifeguard Diagnostics it shows a FAIL for ID B4(hex value) which has the attribute name "End to End Error Rate". I'll contact Crucial support (there's still warranty left) and tell you if the replacement worked.I recently purchased a crucial MX500 500gb 2.5inch sata ssd new from amazon to increase my system storage. This might be a bad programmed controller. It actually looks like the BX100 from Crucial gets bricked if you add a security password over Linux. And i'm pretty sure they are right and that this applies to my drive - Crucial BX100 -, too. According to the answers there, it could be a bad programmed controller, viz. Info: Both UEFI(BIOS) and Linux recognizes the SSDįlashing the firmware over a USB-boot-drive -> not working:ĬMD_Status: Command aborted by the drive | STATUS_CODE: 13Ģ) As i've written in my opening post (in the "Edit March 1-st"-section), i've found this thread.both "Storage Executive" and Windows don't recognize the SSD (not even Windows Disk Management).Installing "Crucial Storage Executive" on Windows and trying to secure erase it using the function "PSID revert" (like the Crucial support told me to) -> didn't work switch SATA-Option in UEFI/BIOS between IDE and AHCI.plug SSD to another SATA-Port on Mainboard.Hdparm -user-master m -security-set-pass NEWPASS /dev/sda all possible commands in the Linux terminal (see above) - including Royce' command:.It's connected directly to the motherboard via SATA-connection.Įxplanation for my assumption it's a hardware problem:ġ) I've tried everything that is possible on the software-level - and nothing worked for the ssd: > No, it's not conected via USB-to-SATA. (Explanation for this in this post further wouldn't happen to be attaching the drive via USB-to-SATA, would you? If so, can you try with a direct SATA connection? I will contact Crucial to - hopefully - get the SSD replaced. I think there's no doubt that it is a hardware problem. *In a general service mail that i sent before the staff was very helpful, even by mentioning Linux. Just say it doesn't work with Windows 10, and you are good to go. SO - my tip: if you send it back just don't mention something about using it with Linux (at least in the actual replacement request*). I got the impression that they tried to blame me, instead of listening to my statement that i did nothing wrong and it has to be a hardware failure. And actually one guy told me something like "the drive is not beeing replaced if the drive got bricked whilst using Linux". They said something like: "we don't support Linux" (which is - in my opinion - idiocy and not to heard to). My experience: - Crucial tries to get rid of you (at least on telephone) when you say you use this drive with Linux and then the problem occured. Ok guys, the replacement WORKED! I encourage everyone who runs into the same problem to send Crucial a warranty replacement request. Maybe i'll confront Crucial with that info in the next days.Īnd for further information: I've tried the following commands, too: hdparm -user-master m - security-disable NULL /dev/sdaĪnd hdparm -user-master m -security-erase-enhanced NULL /dev/sda In his case - they assume - there are controller-problems. I've found this thread today where someone has the exact same problem. I’m a little bit desperate right here, hope you can help. Maybe that led to the locked-state? I don’t know. I solved that by putting the system in Sleep Mode. Maybe important to know: Before that my drive has been frozen. Hdparm -user-master u -security-erase PASS /dev/sdaīut it said the following with some and some more 00’s) at the end: Bad/missing sense data, sb: 70 00 05 00 00 00 00 0a 51 e0 00 21 04 … I've booted from a Knoppix Live CD and used the command: hdparm -user-master u -security-set-pass PASS /dev/sdaĪfter that I wanted to actually secure erase it with: ![]() ![]() Or maybe someone knows another solution that could unlock my SSD.īackground: I wanted to secure erase my SSD drive. I want to use the command: hdparm -user-master m -security-unlock PASS /dev/sda Does someone know the ATA master password for Crucial drives? Unfortunately I haven’t found the master ATA password for Crucial drives on the internet. So I’ve searched all over google, and read in a thread that I should try to unlock it with the master password. I can’t unlock it with the correct (!) user password.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |