BIOS does only sees one SATA drive but boot menu sees all 5

Zoinks

Senior member
Oct 11, 1999
826
0
76
AsRock Taichi X399 - latest BIOS - stopped booting to my windows drive after a BSOD. Strangely the BIOS does not see the drive to let me choose it as the boot drive. But if I press F11 I can choose and of the 5 drives from the menu and windows boots fine.

I tried clearing CMOS. What next, reflash the BIOS?
 

Indus

Lifer
May 11, 2002
13,549
9,417
136
Ugh that's an asrock bios thingy. Annoying at first.

What it is currently doing is that after a bios update, it usually ignores all drives except 1 that it picks randomly.

Go into bios, into boot, and change the #1, #2, #3 and its selection in depth menu. You'll be able to see them all there.

I know its a pain in the ass but that's how you fix it.
 

Zoinks

Senior member
Oct 11, 1999
826
0
76
Where exactly?

Under advanced--storage they are all listed but just info, can't make any changes.

Under boot, just the one drive - the wrong one - is listed under boot devices! I think this is what you are referring to, but what I'm saying is only one drive is listed here!
 

Zoinks

Senior member
Oct 11, 1999
826
0
76
I moved the boot drive to SATA1. The BIOS now only offers SATA3 as a boot drive. Limping along with the F11 boot menu. Kind of a PITA.
 

dlerious

Golden Member
Mar 4, 2004
1,999
824
136
After selecting the drive using F11, can you boot back into BIOS before Windows loads (don't have that motherboard to try)?
 

atc_advisor

Junior Member
Apr 3, 2019
1
1
6
I encountered this issue with this same MB but it had nothing to do with any BSOD, and behaved the same using both P3.30 and P3.50 bios versions; regardless of how the sata drives were connected. I discovered that the issue is dependent upon how the “Boot\Hard Drive BBS Priorities” options are used. If you select the “NVme 970” as boot option 1 (pic: NVme selected in BBS.jpg), you cannot select any other drive in the main boot selection dialog. In fact there are two instances of the same drive; one prefixed with AHCI and another with NVME (pic: only EVO 970 allowed.jpg).

However if you select the 860 EVO 1TB in the lower BBS Priority menu (pic: 860 selected in BBS.jpg), you are now able to select either drive in the main boot priority menu (pic: either drive can boot.jpg).

It is always possible to use the F11 boot override option when booting to select any of the available drives, but I had issue with having the 860 SSD drive boot by default when working with a native install of Ubuntu or Windows for validating the build and running the performance benchmarks. This really is somewhat of a moot point since it will boot to ProxMox running on the NVme drive by default when in production. It is notable that the SSD 970 Pro 512GB appears twice in this menu showing both the UEFI and NVME prefixes. I am not aware of any differences when selecting one or the other (pic: f11 boot menu_all drives available.jpg).

There may some other root cause or workaround but this worked satisfactorily for me. Love the Taichi x399 with the Threadripper 2950!
 

Attachments

  • NVme selected in BBS.jpg
    NVme selected in BBS.jpg
    72.8 KB · Views: 8
  • only EVO 970 allowed.jpg
    only EVO 970 allowed.jpg
    78.5 KB · Views: 6
  • 860 selected in BBS.jpg
    860 selected in BBS.jpg
    71.1 KB · Views: 5
  • either drive can boot.jpg
    either drive can boot.jpg
    75.5 KB · Views: 5
  • f11 boot menu_all drives available.jpg
    f11 boot menu_all drives available.jpg
    60.8 KB · Views: 5
  • Like
Reactions: UsandThem

VirtualLarry

No Lifer
Aug 25, 2001
56,570
10,200
126
Yeah, I think @atc_advisor nailed it.

I was going to mention, that there's the "Boot Priority" Menu, that largely lets you choose Boot priority, between different "classes" of devices, and then, there's the BBS/HDD Boot Order menu, that allows you to order the SATA drives "within" that class of device.

I know, kinda wonky, having to use two different menu sections to select your boot device ultimately, but ... BIOS hasn't always been easy or intuitive to configure.