crolfe
asked on
Proliant ML350 tries to boot from ext USB drive before HDD
We have a number of ML350s and do our backups to disk. We have never had a problem until we upgraded the 500 GB Iomega external USB drives to 1 TB ones. At every server reboot (after updates for example) the server tries to boot from the external USB drive.
We have tried everything I can see in the BIOS. The boot order is for the RAID controller first, and boot drive order is C: then DROM then NIC then USB. The USB drive is recognized in the BIOS as C:, and I think this may we were the problem arises, but I see no way of changing this in the BIOS level the Iomega is listed as H: once the OS starts up.
The odd thing is that its not consistent, we have 12 identical servers with the same BIOS setups and Iomega drives, some will start up others not (or maybe on the third or fourth reboot). If I set the boot order to be CDROM then C:, then its guaranteed they will attempt to boot only from the Iomega.
We have the latest version of the BIOS on all computers. Any suggestions welcome!
We have tried everything I can see in the BIOS. The boot order is for the RAID controller first, and boot drive order is C: then DROM then NIC then USB. The USB drive is recognized in the BIOS as C:, and I think this may we were the problem arises, but I see no way of changing this in the BIOS level the Iomega is listed as H: once the OS starts up.
The odd thing is that its not consistent, we have 12 identical servers with the same BIOS setups and Iomega drives, some will start up others not (or maybe on the third or fourth reboot). If I set the boot order to be CDROM then C:, then its guaranteed they will attempt to boot only from the Iomega.
We have the latest version of the BIOS on all computers. Any suggestions welcome!
ASKER
Thanks, 2610 SA controllers all have the same BIOS that is the lastest version. I found the source of the 'inconsistency': cold boots are OK, warm boots not.
Cold reboot (power off totally) : the Proliant splash screen is displayed first (before the memory test). After the lengthy boot process, the F9 setup/F10/F12 menu is displayed on the screen (briefly). Then it says attempting to boot from C: and goes into windows as it should.
Warm reboot (restart from OS) : no Proliant splash screen
No F9 setup/F10/F12 menu
blinking cursor at the point where F9/F10/F12 should be coming up.
This is repeatable on all servers. The problem of course is that updates initiate a warm reboot.
Cold reboot (power off totally) : the Proliant splash screen is displayed first (before the memory test). After the lengthy boot process, the F9 setup/F10/F12 menu is displayed on the screen (briefly). Then it says attempting to boot from C: and goes into windows as it should.
Warm reboot (restart from OS) : no Proliant splash screen
No F9 setup/F10/F12 menu
blinking cursor at the point where F9/F10/F12 should be coming up.
This is repeatable on all servers. The problem of course is that updates initiate a warm reboot.
Try to get in your BIOS --> Advance options --> Option ROM loading sequence --> Load Embeded Device First
Reboot and let us know the result.
K
Reboot and let us know the result.
K
ASKER
Sounded good, but i don't have that option anywhere in the BIOS, under advanced I have:
MPS table
ROM selection (current or backup)
NVRASM erase
nmi debug
drive write cache
expansion card caching optimization
processor options legacy serrr
Boot controller order is:
1. PCI slot 3 RAID
2. HP integrated PCI IDE
3. Intel SATA
Boot order: IPL
1. HDD C:
2. CD ROM
3. Floppy
4. USB Drivekey (C:)
5. NIC
I am puzzled why is works OK from a cold boot, but not a warm boot
Thanks for the suggestions
Chris
MPS table
ROM selection (current or backup)
NVRASM erase
nmi debug
drive write cache
expansion card caching optimization
processor options legacy serrr
Boot controller order is:
1. PCI slot 3 RAID
2. HP integrated PCI IDE
3. Intel SATA
Boot order: IPL
1. HDD C:
2. CD ROM
3. Floppy
4. USB Drivekey (C:)
5. NIC
I am puzzled why is works OK from a cold boot, but not a warm boot
Thanks for the suggestions
Chris
Here is what you may try to do on Windows registry to disable USB boot
1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. Locate, and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\
4. In the right pane, double-click Start.
5. In the Value data box, type 4, click Hexadecimal (if it is not already
selected), and then click OK.
6. Reboot your server.
K
1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. Locate, and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\
4. In the right pane, double-click Start.
5. In the Value data box, type 4, click Hexadecimal (if it is not already
selected), and then click OK.
6. Reboot your server.
K
ASKER
Unfortunately this did not work either. The problem is that all this is happening before windows starts. After a warm boot, at the point when it should say F9 setup etc the cursor just sits there blinking. \
A cold boot works OK: sequence is as follows:
F9 setup F10etc
-- attempting to boot from drive C: -
starting windows
A cold boot works OK: sequence is as follows:
F9 setup F10etc
-- attempting to boot from drive C: -
starting windows
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The fact that it's not consistent would seem to indicate there is a difference and a difference in SA ROM could be it
Not a definite solution but maybe a first step
Andy