Boot Priority AMI Bios

canoosa

Reputable
Feb 2, 2015
22
0
4,520
Although the system is server based, using Supermicro X10SLH-F board, Intel Xeon E3 1231v3 cpu, and WS2012 R2, its function is solely as a dedicated MUSIC SERVER.

There are 3 Drives: SSD, HDD, Optical.
The SSD holds the OS. The HDD only stores files for playback. The Optical is used solely for ripping cd’s.

The Supermicro board uses AMI BIOS.

It is imperative that the BOOT sequence NOT boot the SSD & HDD DIRECTLY IN SEQUENCE!
At this time, I am in a position to do with the Bios as I like, i.e. set it up to incorporate the above requisite.
To be clear: just because I built this server, does NOT mean I’m a PC Tech or IT Specialist :) , far from it; and entering the BIOS to effect changes is always done with a degree of trepidation and anxiety!

WHAT’S DONE, SO FAR:
Via the Aptio SETUP UTILITY, I proceeded to BOOT. From BOOT, entered BOOT PRIORITY and, there, for the first two options set: 1st Boot Device as the SSD (P5)
set: 2nd Boot Device as the OPTICAL (P3)

The next 4 entries in the category, are not helpful to the purpose, it seems: 3rd BOOT DEVICE = USB hard Disk; 4th BOOT DEVICE= Removable; 5th BOOT DEVICE= Network: IBA...; 6th BOOT DEVICE= UEFI: Windows Boot....

However, I never seem to be able to see all three drives listed together to ensure that the SSD and HDD are booted with SOMETHING/ANYTHING in between them, e.g. Optical Drive. My concern/fear therefore is, that with the GIVEN BOOT PRIORITY (above – SSD followed by Optical), perhaps the HDD is booted JUST PRIOR to the SSD within the general Boot Sequence (I think I’m concocting a term here), such that the HDD is booted DIRECTLY PRIOR to the sequence that initiates the DEVICE BOOT SEQUENCE, meaning that the HDD would, by that conjecture, be in DIRECT SEQUENCE with the following SSD Boot Priority; and that MUST NOT happen!

It doesn't matter HOW this is accomplished, perhaps the HDD can be booted on AFTER everything else, or the very first of all things, as long as it is NOT IN DIRECT SEQUENCE with the SSD. And, just maybe, by the above-listed "BOOT PRIORITY" I've managed to accomplish that, but WHERE is the HDD in all this?
Can someone set me straight on this – definitively?
Many Thanks.
 
Solution
So, I found my own DEFINITIVE answer: when we built this server, my wife was in charge of "software"; she had correctly selected the hdd in Hard Disk Drive BBS Priorities with the Option: Disabled - because it would only contain music files, nothing to boot WITH ! [She's currently away, on assignment]
Hence, the hdd could not be found under Boot Priority Device - duh....

I guess that, at least, any learning experience is worthwhile !

I'm a bit confused as to why you would need to have the two drives, SSD (OS) and HDD (music), separated by a different device? Could you please explain in more detail why this is a prerequisite?

Normally you would use (your) 6th device labeled UEFI: Windows boot manager as the first initialization drive. While this is the same exact drive as your SSD doing so adds features that will help and among them allow for a 4TB HDD to be used as a boot device without having to set partitions.

Next if you want to separate the two drives, SSD and HDD, you will use a drive that is always attached. As an example, like you are already doing, using the Optical drive and not a removable thumb drive.

If there is no option for your HDD to be put in the third boot position then you can usually leave it up to the BIOS to place the remaining drives in any order that it wishes. Normally the only time you really need to watch the boot order, after initial setup, is if you want to boot from a different device like a thumb drive or CD/DVD ect..

Setting things this way should give you the desired effect you are looking for... Though my curiosity is peaked as to why you would need it to be set this way.
 

canoosa

Reputable
Feb 2, 2015
22
0
4,520
Hello bgunner!
I agree - the prerequisite is a bit unusual.
I am about to power the system using Linear PSU's, one for mobo + optical, the other for the hdd + ssd. The latter lpsu is borderline limit for current delivery during boot - 5V @ 3A, but optimal for audio fidelity; the two drives - Samsung SSD 850Pro and WD40EZRZ would total ~ 4.9A if driven simultaneously, which is my concern. True, they aren't EXACTLY booted together, but might be SEEN as such by the lpsu, given that the interval between the two boots would be VERY small - which is my assumption! As long as they are separated, during boot, that possible/probable problem would be eliminated entirely; hence my NEED to ensure that something comes in between the two drives during boot.
So, do you know a way this requirement can be effected?
 
As you seem to be already aware that the boot process for each drive is very short, you also need to be aware that one device in between the 2 data drives really wont make that much of a difference.

Since SSD's are so quick there power draw over time is short. The HDD's are the ones that take a fare amount of time and energy to spin up and be read to initialize. My suggestion would be to add as many non removable devices between the drives as you can to separate them a bit more. As long as you have quality linear PSU's they should have protection for Over Power/Load Protection (OPP/OLP) that will shut the PSU down and force you to turn the PSU off and unplug from the wall to reset. If yours have this then try the set up I mentioned in my first post. If not try the method I mentioned in this post by adding as much as you can between the drives to take up more time.

In your case the biggest issue is the first second or three as everything powers up. There is not to much that I am aware of, other than getting better PSU's, that will help in this situation.
 

canoosa

Reputable
Feb 2, 2015
22
0
4,520
Because I'm not well versed in the intricacies of boot & bios, your reply is a tad too vague, unfortunately.
Sounds good to: "add as many non removable devices between the drives as you can to separate them a bit more" - but that's the problem as stated, isn't it, because I don't seem to be able to find a way in the bios to set up any kind of list/order of sequence beyond the "SET BOOT PRIORITY" previously referred to, which provides no DEFINITE view as to where the hdd is in the sequence; fine if the hdd then followed at the END of the BOOT PRIORITY sequence, bad if it precedes it.

So, how can I tell?
 
Many different manufactures call these following options slightly different things but usually stay close to the same type of wording:

IN my AMI BIOS for my Asus Sabertooth board I have Boot Option Priority this is where you would tell the BIOS what boot and in what order for drives. For me I have 3 slots I can set to tell the BIOS what to boot in what order.

Hard drive BBS Priority also known as Hard Drive BIOS Boot Specification. This to you can change and set the devices you want to boot first. For me I have 4 options in this one that I can set for drive boot order.
 

canoosa

Reputable
Feb 2, 2015
22
0
4,520
Sorry for the major delay - Satellite IP down.
Yes, I've been into the Boot Priority Device, even before I posted. My final conclusion was to set it in terms of having as many items in between the ssd and hdd as you suggested - and had been pondering that, anyway, while trying to negotiate the murkiness of my mental concept for all this.

So: !st = SSD; 2nd=UEFI: Built-In EFI Shell; 3rd=OPTICAL DRIVE; 4th=NETWORK: IBA GE Slot 0400 v1404; 5th=USB Hard Disk (there is none in this system); 6th=Removable (ditto).

HOWEVER..... My original question STILL stands: Where in this sequence is the hdd??? In other words, is the hdd now FORCED into last position - and that is what I want to happen - or can/will the system place the hdd at the HEAD of the sequence - which I doubt, but DO NOT KNOW FOR CERTAIN ???

 

canoosa

Reputable
Feb 2, 2015
22
0
4,520
So, I found my own DEFINITIVE answer: when we built this server, my wife was in charge of "software"; she had correctly selected the hdd in Hard Disk Drive BBS Priorities with the Option: Disabled - because it would only contain music files, nothing to boot WITH ! [She's currently away, on assignment]
Hence, the hdd could not be found under Boot Priority Device - duh....

I guess that, at least, any learning experience is worthwhile !

 
Solution