9
0
My new SSD Corsair CSSD-F60 actually works - using it for boot and system disk (Windows 7 64-bit). But when first (cold-) booting the PC it's not properly found by BIOS and Intel ICH9R Controller. The first boot attempt always fails. When I wait for about 1-2 minutes, and retry using CTRL + ALT + DEL it's getting recognized and everything works as expected from now on - until the next boot from a turned-off state. I'm also running a RAID-5 SATA set in this machine, this was my previous system partition.
Some screenshots describe the problem:
Turning PC on, initialization, shows up like this. The problem is: While it's recognized at "Port 00", it doesn't appear in the Physical Disks section:
Error because boot disk was not found:
When I'd press CTRL + ALT + DEL instantly, the procedure likely will repeat from (1). But after about 1-2 minutes have passed from the first start, it's certain that I get the following screen. From now on, everything works fine! Note that now the SSD appears in the Physical Disks section:
Interestingly, when going to BIOS during the first period, I'm not able to select the SSD as my boot device because it simply doesn't appear in the list. After it was recognized, I can select it from the list.
(This is the working version, during the first period there is only my Intel RAID device listed)
Usually, I turn on my PC, wait two minutes and press CTRL + ALT + DEL to get it booted - this always works.
What could this be?
Here some facts:
- Phoenix BIOS up-to-date (Manufacturer ABIT doesn't provide any support for mainboards anymore, this is the IX38 QuadGT with Intel X38-ICH9R)
- Storage Controller/Bus running in RAID mode which supposedly include AHCI (have to run in RAID mode because of the existing RAID set)
- Switching ports (hardware) and exchanging cables didn't help
Any clues?
EDIT 1:
My PSU is the following: Corsair TX650W from summer of 2007.
EDIT 2:
Bad news guys, I've pulled off the power connectors from all three hard disks (Ports 01, 03 and 05) and from the DVD-ROM drive (Port 04) so there was only the SSD plugged in - same effect, I wasn't able to boot from cold start state but minutes later. I also exchanged the port to 04 for a single test, no success.
thomasjaworski.com
Posted 2011-07-28T19:15:01.500
Reputation: 191
2This might be a power issue. Can you successfully cold-boot without the other hard drives connected? – sblair – 2011-07-28T19:27:02.030
@sblair Thanks, good catch, will try that soon - while my power supply is scaled sufficiently, the hard disks are all hanging on the same cable (for lengths reasons you know.. :). The SSD is not the last one though, its one of the RAID disks. – thomasjaworski.com – 2011-07-28T22:38:11.233
2The order of the drives on the daisy-chained power connector shouldn't matter much, each drive should get the same voltages. If possible, it would be interesting to measure those voltages during the first minute or so after booting. I'm speculating wildly here, but the SSD may be sensitive to even slight voltage dips, whereas the HDDs can ride-through. How old is the PSU? – sblair – 2011-07-28T23:08:32.997
@sblair: That was my first inclination. Power. You should put that is as an answer. – surfasb – 2011-07-29T00:06:37.297
@sblair The order might actually matter. The more current that flows through the wire, the lower the voltage on the other end.
– Breakthrough – 2011-07-29T02:44:45.957You can sometimes find in your BIOS where there is a delay setting to allow devices to get power and boot up. I had some regular harddrives that had this issue. I told the BIOS to allow the sata devices to have a change to boot and then I would be able to do a cold boot without the annoyance of having to reboot – kobaltz – 2011-07-29T02:48:52.320
1@Breakthrough Yes, I'm familiar with Ohm's law :) But, I don't understand what you mean. Each SATA device will be connected to the various voltage rails in parallel. Ignoring the tiny cable impedance, the voltages must be the same for each device, regardless of order, and regardless of current. – sblair – 2011-07-29T10:47:18.910
@sblair Yes, but the more devices you have on that rail, the more current flows along it, and the more the voltage sags at each connection point (moreso after the first junction). While it usually doesn't make a difference, if you have three hard drives going all-out, it could make a difference. It all depends on the cable, though. Either way, I would recommend to not use more then two SATA devices on a single power cable to see if that's the issue here. – Breakthrough – 2011-07-29T12:50:34.937
@kobaltz yes I have such option but unfortunately I can set it up from 0 to 15 seconds only. I've tried that but 15 seconds were not long enough. I have some time on weekend, gonna examine the possible power issues. – thomasjaworski.com – 2011-07-29T20:53:48.993
@sblair See my EDIT 1 regarding the PSU – thomasjaworski.com – 2011-07-29T20:58:07.320
Also, try updating your bios – kobaltz – 2011-07-29T22:45:04.603
@sblair +@Breakthrough Thanks people for the suggestions unfortunately my power connection tests were not successful as described in EDIT 2 – thomasjaworski.com – 2011-07-30T10:24:06.623
2I also have a Corsair SSD (a P3 128GB). Sometimes when I reboot or cold start the computer I experience this issue too. Letting it sit there for a while and then rebooting again always makes it reappear. I've also suspected it to be a power issue, but I have a well-sized PSU (also from Corsair!), but it's been shown not likely. I suggest contacting Corsair. They're usually very personal with their customers. – jesper – 2011-07-30T10:54:16.843
Have you tried a firmware update? – Sean87 – 2011-07-31T17:48:55.030
@Sean87 thanks but it appears that it runs the newest available firmware (2.0). Now I'm trying to update the Intel Chipset drivers if possible... – thomasjaworski.com – 2011-07-31T20:16:37.620
I don't think it is a chipset driver problem since the chipset driver is not going to load while booting. Also check for a new bios for you mainboard. – Sean87 – 2011-07-31T20:33:34.220
I think the problem is in the drive itself. I guess it's possible that your firmware froze up during a cold boot. Maybe it's handling some bad block relocation or maybe some internal configuration got corrupted. You'd better check the SMART info and see if you're low on reserved blocks. – billc.cn – 2011-08-01T00:30:23.780
Unfortunately it looks like I have pretty new drivers everywhere... @billc.cn the SMART status shows all OK. Meanwhile, I've checked the Corsair forums where people seem to have similar, but not exactly the same problem. I'll try to find out more there. Thanks for your suggestions so far, really appreciate it! – thomasjaworski.com – 2011-08-01T18:29:02.003
Have you tried disabling and/or disconnecting your RAID array, changing the controller to AHCI pass-through, and trying to start the system with only the SSD connected? – Breakthrough – 2011-08-05T10:38:36.183
@Breakthrough maybe this is worth another try, but which conclusion would you come to if it would work or not work? – thomasjaworski.com – 2011-08-07T21:12:29.170