05-05-2018 05:22 PM
I have a Intel SSD 535 - SSDSC2BW480H6. It has begun to fail on my motherboard, started happening about 4 months ago. It worked fine for about a year and a half but about 4 months ago it started to not show up on my motherboard. Initially I had to install a new ssd hard drive, however it showed up on the bios screen one time. Now it goes off and on randomly. I have to do several reboots in order for it to come back on line. I did run the Intel Solid State Drive Tool box for a full diagnostic Scan but nothing failed. Just started a second scan right now. Checked for a new firmware but no update showed, so now I have the following questions:
Any help would be appreciated.
Thanks,
05-07-2018 07:47 AM
Hi eforonda,
Thank you for posting in the Intel® communities.The issue you are describing has similar symptoms of an issue reported with the DevSleep feature of some SSDs (including the Intel® SSD 535 Series). The DevSleep feature allows the device to go into a low power "device sleep" state, but sometimes the motherboard does not signal to wake up the SSD back.It may be possible to solve the issue without the need of an RMA, so let's first try the following in order to recover the drive.The first recommendation is to update the BIOS version of your motherboard to the latest one, as it may not support the DevSleep feature in the current BIOS version. However, if there are no updates available for the BIOS, we can try to disable the DevSleep feature on the SSD by following the steps below:05-08-2018 01:17 AM
Hello Diego,
Thank you for the information, I have updated the bios. However, I am not sure if it the new version supports Devsleep, there is no mention of the new bios supporting Devsleep in the release notes. I did try updating the firmware on the SSD, and have been unsuccessful in getting to the update firmware tool. I boot to the usb stick however the boot stops with the following error:
couldn't find an input interrupt endpoint giving up. unable to connecto X server: Connection refused server error.
I did the legacy only mode but I get the same error. The motherboard I am using is a Gigabyte g1 gaming ga-z170mx-gaming 5 firmware/bios version: F22f. In case you can look into the settings I need to change.
How large does the USB stick have to be? Any guidance would be greatly appreciated.
Also is there maybe another reason for the issue given that the ssd never had an issue for about a year and a half?
Thanks,
05-08-2018 06:49 AM
Heya, I have done this with 1GB NanoFlash. Also Rfus ask me how to write ISO, I use ISO recommended mode, but you can try other "DD" mode. With this FW will be RG2P /sounds, like performance I hope/ Also with that USB can switch between 2 versions of firmware.
05-08-2018 10:57 AM
Hi eforonda,
I've just tried to boot from the USB flash drive to see if I got the same message as you did, but it worked fine for me.I used a 16GB USB flash drive. I formatted it before creating the bootable unit. Regarding to the BIOS settings, I only had to change in the Boot menu the option of booting from storage devices to "Legacy Only", and set the USB flash drive as the first drive to boot from and everything worked fine.Could you please try to create the bootable unit once again and try it one more time? This is how I created the bootable unit:Please try it again and let me know if you get the same error message again.
Regarding to the issue itself, it usually start happening after some time of using the drive which is the same scenario that you described. That's why it seems to be related to the DevSleep feature. Although there is also the chance that the drive has another issue. We can check the health of the drive by checking the SMART attributes. In order to get this information, please run the Intel® SSD Toolbox and get the SMART attributes report of the drive. You can download the Intel® SSD Toolbox from this site: https://downloadcenter.intel.com/download/27656/Intel-Solid-State-Drive-Toolbox https://downloadcenter.intel.com/download/27656/Intel-Solid-State-Drive-Toolbox
Have a nice day.
Regards,
Diego V.