The specific problem referred to above is within this system context:
Supermicro X10SLH-F; Xeon E3 1231v3; 2 x 4GB DDR3; WS2012 R2; AMI BIOS
Function: MUSIC SERVER - 3 Drives: SSD - OS and pertinent programs (Audio Optimizer, JRMC v21, etc) only.
OPTICAL - solely for Ripping Cd's
HDD - Music Files only, for playback
Specific Context: Am about to introduce linear psu's to power the system, one of which MUST drive both the SSD & HDD . No problem; EXCEPT, they must NOT be BOOTED in sequence.
Therefore, in the AMI BIOS, using Boot Priority Device, I thought I could set the sequence to meet the requirement, BUT.... only the SSD and OPTICAL are contained therein. Consequently, have set the Boot Priority sequence as follows:
1) SSD 2) UEFI: Built-in EFI Shell 3) Optical Drive 4) Network: IBA GE SLOT 0400 v1404 5) USB Hard Disk [there is none in the system] 6) Removable [ditto]
I'm hoping that this sequence FORCES the HDD to be booted afterwards, but that is something I Do Not Know For Sure - since I am not able to see, thus "command" the hdd!
Obviously, the hdd is "floating" around somewhere; PC's are not arbitrary, meaning it will engage the boot for the hdd somewhere, and in a predictable, repeated order - question is where?? Because...... if PC "decides" to initiate the hdd's boot just ahead of the Boot Priority Device sequence, then the hdd & ssd WILL BE booted sequentially!!
Can anyone confirm, DEFINITIVELY, if the supposition above, i.e. HDD forced to be booted last, is correct???
If that is not correct, how can I ensure that the SSD & HDD are NOT booted in sequence? Where IS the hdd?
Disclosure: I am not a tech or even well versed in the science, by geek standards. Yes, the server is home-built, and has been working flawlessly from the get-go, but geek I ain't - just slow 'n meticulous :-)