I'm running a Scythe SY1225SL12HPVC - Slip Stream 120 PWM Adjustable which has a manual fan speed control as per HP Proliant MicroServer | silentpcreview.com, but I tried disabling the BIOS fan control option anyway to see it it made any difference.
I manually turned down the fan speed to 500k and the health LED (HP badge) went from blue to red, and it shut down soon after that, so no change in behaviour from normal.
Then I removed the fan plug completely, booted and it displayed a POST error and shut down.
So changing the fan control BIOS option doesn't seem to do anything for me.
this is all completely new to me so i have two questions...
i have downloaded the .rar file... what opens that type of file?
and i cant seem to find the txt file, how do i get it?
if its not too much can someone paste that on to the forum?
.... just tried google and its a zip file which makes sense...
i will try again tomoz when i have had less wine.
i put the wine down and manged this over the w/e... really straight forward in the end.
i have no idea technically what i have done but i am very thankful.
either way i now have a N40L 12TB homeserver running WHS for £650...
with the bios update does this now mean i could attach another hard drive to the rear SATA drive and increas it up to 15TB?
now to start loading it up with movies and buy a popcorn hour.
thanks again to all on here and especially TheBay.
Finally, should i be weary of updating any software now as could this affect the new bios?
Looking for help,
I have flashed my BIOS as followed in post 1 but my drives still show as IDE in BIOS and the WHS console. I set sata controller to ACHI mode before installing whs. I have 2 drives setup in the ODD bay (Main OS spare sata connection, extra HD on a sata card) and 4 drives in the lower bays.
Anyone have any ideas?
/proxy.php?image=http://dl.dropbox.com/u/60856466/1.jpg&hash=885f78c6bc63d56952df5375a7d79fc7
/proxy.php?image=http://dl.dropbox.com/u/60856466/2.jpg&hash=b136349214a52c835d6855e39d0f0f40
/proxy.php?image=http://dl.dropbox.com/u/60856466/DM.jpg&hash=8a60d3ca58554a40b977f0a7bf9c7221
I have used this BIOS update so I can use the eSATA port with my external SATA drive for the daily backup task and hot swap it with another in a rotation scheme. However, one morning I found that the server was down and when I power cycled it, it didn't load the OS (WHS 2011). It's headless, so I couldn't see what was going on. On a hunch, I powered down the external backup drive and it then booted OK.
What was happpening is that with the external drive powered on, it was completely missing the HP P410 RAID card in the boot sequence and trying to boot off the external drive. I later found that it rebooted in the night after applying some MS updates.
@ The Bay - Is this something that can be fixed in the updated BIOS?
Thanks.
Hi ya all,
I am also having the problem that challengedavid (post #123) is having with reboots and it is only hitting me on windows.
from my quick testing it is the rom, if I use the HP standard rom the machine reboots fine on 2008 R2 server, however if I use the thebay's rom it just hangs by the looks of it as it is about to reboot (the disks get safely stopped etc)
Any one got any suggestions?
I'm having the same issue where a shutdown is fine, but a restart hangs. I'm running WHS2011.
Is the hard drive that server 2008 is installed on in the odd bay?
is it not cause when you installed the os the sata port was in ata emulation mode and now it's in ahci mode
windows hates being changed modes after its been installed
the hdd is in the odd bay indeed data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7 (I want to use the 4 disks in the other bays for data)
Its a fresh install of windows (does it even during the install) and I have not changed the mode during install data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7
You've not changed the mode but The Bays BIOS has. That's what its designed to do. Change the sata port from ATA emulation to AHCI so the port runs at full speed
Hmmmmmm unsure why your having this problem during a fresh instal. It's common afterwards. Is it Server 2008 R2? Or just Server 2008. Maybe if it's the older version it may be a driver issue in which case you prob need to feed it a driver from CD or USB during install