Direkt zum Inhalt

New SSD restore - Bios not recognizing SSD until after entering Bios and saving every cold boot - Solved

Thread needs solution

Installed Sandisk Extreme 11 240Gb, copied partitions over using Acronis Home (without the recovery partition) restore from backup, Win 7 64bit. Used Pat L and Grover H (guides very helpful), and manual for guidance. Partitions in order, no boots between steps, and last step was MBR 0 and Disk Signature.

Boot failed first several restarts - No boot device found, went into Bios........No SSD but exiting bios and auto reboot, booted to Win 7!

In other words, the bios on a cold start or reboot does not recognize the SSD, however after entering the bios and F10 exit (SSD not recognized - None for drive), the system recognizes the SSD on self boot (Serial ATA Port 0: Sandisk SDS....)! Also if bios is immediately re-entered upon reboot after F10 exit the SSD shows up in the bios.

Very odd behavior. Updated bios from 1.05 to 1.11, no difference. No similar posts on this forum or found on internet. SSD, current firmware R1311.

Only thing different from original Hitachi Hdd is I did not include recovery partition....but this is very flaky...

Any help would be appreciated!

floydo

0 Users found this helpful

Is this a UEFI & GPT setup? If yes, that could be a problem with the secure boot as you eliminated a boot device by removing the recovery partition.

Anyway, I would eliminate the variables.

First, I would restore the disk as is, with the recovery partition and see if that makes any difference.
If the problem is still there, I would install Windows and see if the SSD behaves normally.
If the problem exists with a fresh install, I would change the SSD. IF the problem exists with another SSD, you have a BIOS issue. If the problem disappears with another SSD, your SSD has some obscure issue. if the problem disappears with a fresh install, you have a problem with your image.

The drive was initialized as is an MBR.

Next step after your helpful comments was acronis add new disk and delete the partitions to unallocated space.
Booting in that configuration resulted in not recognizing the drive on cold boot, same as before.
A quick fresh W7 install resulted in the same characteristics

Thanks for the thoughts, since I was not sure if I was missing something that relates Acronis partitioning to bios drive initial recognition. Since the SSD is remains recognized on a reboot, it seems the bios stays in contact with the drive during reboot of the OS. When the power up on a cold boot there is some initialization/recognition of the drive that is not happening until after bios is entered and exited even though the bios does not show the drive...weird...

It is headed for an RMA, but may try it in another computer as a last ditch curiosity prior to sending the drive back.
Thanks again!

Update: The problem was not an Acronis issue. Talking to Sandisk tech support extensively, they concluded the SSD Extreme II SSD is probably "not compatible" with the Acer One AO722 laptop.

This has to be a firmware issue, and they suggested in so many words to return it from where I bought it for a refund....They did offer to send a replacement, but without much hope of it working. Geesh. Interestingly the same laptop has seen successful installs of the Sandisk Extreme as has been reported on the web.
Thx for the Acronis help Pat!