I have exactly same issue. I thought it was my laptop and I even reinstalled my os.
My laptop is Macbook Pro 2010 Mid. After I completely shutting down the computer, I was able to boot. But if I try restarting from the os it fails.
Just bought the SSD two days ago and was quite excited at beginning. Now I am so disappointed. Guess I have to return the SSD.
This problem is not chipset related. Several of the contributors to this thread have systems using other chipsets and our internal testing has shown the problem on other chipsets as well.
The problem is simply an inconsistency in the SATA features supported by the system BIOS and the SATA features implemented in the 530.
The symptom of not being seen after an OS shutdown is very different from the problem others are reporting on this thread.
I've started a new thread to track your symptom. Please use this thread for continuing the discussion.
Same Problem with HP ProBook 470 G1 Notebook (E9Y75EA#ABD).
and Intel SSDSC2BW240A401 240GB
- Cold boot, everything is fine
- Warm boot, as in reboot from windows, leads to no boot device found
Update of latest Intel RST did not help, uninstalling the complete RST neither. Legacy mode is enabled in UEFI.
Latest Driver/BIOS installed (through HP Support Manager)
Just purchased and migrated data from an Intel 520 120GB to my new Intel 530 240GB and can confirm on my HP 8570P with BIOS F.45 (latest) I am having the same restart issue. Cold boot is perfect, Restart prompts with "No Boot Device Found".
Looking forward to the firmware update soon.
@Intel, I didn't skim all 8 pages, but what parameter in the drive is causing the issue only on restart?
Having the same issue here. HP Probook 6460b and a Probook 6570b. The 6570b and ssd disk is brand new.
Tryed lots of different options in bios until I fell over this thread. And it's a 530 series with dc12 firmware.
Both laptops have newest bios revision.
Hope a new firmware is released for the hdd soon!
I'm wondering if this issue can explain my problems in booting a xen dom0 domain on a 530 drive (gigabyte z87x-ud5h mainboard).
I can boot the linux installation (without xen) and everything works fine except failure to detect drive at reboot.
Booting xen hypervisor works but the ssd drive is not detected when the dom0 linux kernel boots. I have verified that the sata controller is using the ahci kernel module. The only problem seems to be that the drive can't be detected. A bit interesting since it was detected a couple of seconds earlier when the hypervisor was able to read both kernel and initial ramdisk from the drive.
Could it be that the handover of the disk from hypervisor boot to linux dom0 kernel follows a similar process as a reboot, hence making it impossible to boot (even cold boot)? I can wait for a little while to have this fixed but not for long since the computer is bricked until the issue is fixed.
Is it likely that I have run into the same issue or is this something else that won't be fixed in the december update? Trying to decide if I should send the drive back or not.
I looked a bit further into this. The gigabyte board has 6 SATA ports from z87 chipset and 4 SATA port connected to a Marvell 88SE9230 chip. The detection only fails when the disk is connected to the Marvell controller. I can boot if I connect it to the intel controlled SATA ports. Problem is that I need to passthrough that pcie controller to a virtual machine.
It seems most likely that this is a problem with the driver and/or firmware related to the Marvell controller.