[canoosa]

Greetings All,

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 :-)

 

Cheers.

 

[Advertisements]

Hi
 
Sorry I don't know what you mean by

NOT be BOOTED in sequence.

 
The Boot Priority sequence means that the BIOS/UEFI will try "passing the boot sequence" to the devices in the other you set, the first in the order that have the required information to boot (boot sector, OS boot manager, etc.) is the one used, the BIOS/UEFI will not try to boot from the next device unless the first isn't recognized as bootable.

[SleepyDude]

Hi
 
Sorry I don't know what you mean by

NOT be BOOTED in sequence.

 
The Boot Priority sequence means that the BIOS/UEFI will try "passing the boot sequence" to the devices in the other you set, the first in the order that have the required information to boot (boot sector, OS boot manager, etc.) is the one used, the BIOS/UEFI will not try to boot from the next device unless the first isn't recognized as bootable.

[canoosa]

Hi
 
Sorry I don't know what you mean by

NOT be BOOTED in sequence.

 
The Boot Priority sequence means that the BIOS/UEFI will try "passing the boot sequence" to the devices in the other you set, the first in the order that have the required information to boot (boot sector, OS boot manager, etc.) is the one used, the BIOS/UEFI will not try to boot from the next device unless the first isn't recognized as bootable.

 

What I meant is that the ssd and hdd must not be seen by the lpsu as (more or less) booting together, such that....if at the beginning of the Boot Priority Device sequence the hdd WERE to be booted ahead of that sequence (if that is possible) then there's a good possibility that the lpsu would see them as one amperage draw, too much in this instance.

However, it just now occurred to me that what you're saying is that BECAUSE the hdd has no requirement  to be booted in the first place, that therefore it will NEVER be booted, per se, it will simply be ON, and when prompted to work, will do that.

Is THAT right?

[SleepyDude]

However, it just now occurred to me that what you're saying is that BECAUSE the hdd has no requirement  to be booted in the first place, that therefore it will NEVER be booted, per se, it will simply be ON, and when prompted to work, will do that.
Is THAT right?

 

The HDD will start spinning from the moment you power on the machine. I think newer HDD's don't always work at maximum rotation speed only when accessed. SSD's are know for low power consumption are you sure that the power supply specs are so low that it can't handle an SSD + HDD?

[canoosa]

 

However, it just now occurred to me that what you're saying is that BECAUSE the hdd has no requirement  to be booted in the first place, that therefore it will NEVER be booted, per se, it will simply be ON, and when prompted to work, will do that.
Is THAT right?

 

The HDD will start spinning from the moment you power on the machine. I think newer HDD's don't always work at maximum rotation speed only when accessed. SSD's are know for low power consumption are you sure that the power supply specs are so low that it can't handle an SSD + HDD?

 

What concerns me is the amperage demanded for BOOT on the psu, the working (spinning) read/write values are no problem. However, I'm coming to the conclusion that the hdd will never BOOT, anyways, because there's nothing ON IT to make it usable as a means for booting, unlike the Optical, which at least can have a disc-for-booting placed on it.

Am waiting for a DEFINITIVE answer to the question of whether or not the hdd WILL BOOT. I'll post once I get it.

[SleepyDude]

Am waiting for a DEFINITIVE answer to the question of whether or not the hdd WILL BOOT. I'll post once I get it.

 

It will not boot. In terms or power I don't think it makes a big difference.

 

Many machines when you turn them on all the coolers, etc. will start spinning very fast and after some seconds they will calm down, this makes a spike on the power consumption for a few seconds.

[canoosa]

 

Am waiting for a DEFINITIVE answer to the question of whether or not the hdd WILL BOOT. I'll post once I get it.

 

It will not boot. In terms or power I don't think it makes a big difference.

 

Many machines when you turn them on all the coolers, etc. will start spinning very fast and after some seconds they will calm down, this makes a spike on the power consumption for a few seconds.

 

I agree. 

I think I was too deep in the trees to see the forest! Began to google "Boot" & "Boot Sequence"; best sites I found:

 

http://pcsupport.abo...nge.htm#showall

 

http://www.engineers...ter-pc-boots-up

 

They confirm that the hdd will not be recognized as a source for booting, simply because it contains nothing to boot with, only Music Files.

 

I do believe the "problem" of Where's the hdd? has been resolved.

As for the amperage draw: Have to run both ssd & hdd at 5V with the Lpsu; their combined amps, if booted in direct sequence and possibly seen as one draw, would have been ~ 4.9A, too high for the unit. However, that "problem" doesn't actually exist, now.

 

Thanks for your help.

[canoosa]

 

 

Am waiting for a DEFINITIVE answer to the question of whether or not the hdd WILL BOOT. I'll post once I get it.

 

It will not boot. In terms or power I don't think it makes a big difference.

 

Many machines when you turn them on all the coolers, etc. will start spinning very fast and after some seconds they will calm down, this makes a spike on the power consumption for a few seconds.

 

I agree. 

I think I was too deep in the trees to see the forest! Began to google "Boot" & "Boot Sequence"; best sites I found:

 

http://pcsupport.abo...nge.htm#showall

 

http://www.engineers...ter-pc-boots-up

 

They confirm that the hdd will not be recognized as a source for booting, simply because it contains nothing to boot with, only Music Files.

 

I do believe the "problem" of Where's the hdd? has been resolved.

As for the amperage draw: Have to run both ssd & hdd at 5V with the Lpsu; their combined amps, if booted in direct sequence and possibly seen as one draw, would have been ~ 4.9A, too high for the unit. However, that "problem" doesn't actually exist, now.

 

Thanks for your help.

 

So, found my own DEFINITIVE answer. Turns out that my wife (currently away, on assignment), who was in charge of "software" when we built the server, correctly designated the hdd under Hard Disk Drive BBS Priorities with the option: DISABLED - because it contains nothing but music files, and nothing to boot WITH !!

 

[ BBS = Bios Boot Specification]

 

Consequently, the hdd couldn't be listed under Boot Priority Device !

 

Cheers.