ML150 G3 embedded SATA Raid problem

[J. Muurling]

I will try the update next Saturday but I might not take the risk about rebuilding the mirror because the system had to go into production.
We have to deliver more servers soon but I might try to find another server from another brand.

[Oleg Koroz]

From F8
Once type of Array designed and selected, it's new Install and you don't have any data - Method to create array select only: CLEAR.

From BIOS
1. Software and Hardware dogwatch disable
2. There will few more options for Action on the different Event all of them set as NO ACTION NEEDED
3. OS Install Timeout set for 100

Can few of you try once again and report back.

BTW: I had tried on the few systems with different BIOS Rev, and it won't make any difference as settings in it.


http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00474317/c00474317.pdf

[Datanet]

Same problem.

Building up a new ML150 G3 dual CPU 2GB ram unit for a client and it still willnot build or clear the array.

I have updated the Bios to 1.8.0, dated 02/Oct/2006, and still cannot build or clear an array without the server re-booting at the 15 to 20% mark.

Once I turned off all the reboot (enabled) (watchdog, Bios etc) settings in the bios it is now at 34% and still going strong on the first RAID 1 array of 2 x 160gb disks (which shows up as 148gb under the array controller)

Definiatly something wrong in that bios and OS watchdog enabled settings somewhere.

Cheers

Steve

[chongkan]

Thanks a lot for this feedback Steve!!

Anyone else has tried it?

Regards to everyone!

[Chris Mcgookin]

I have the same issue, it does seem related to the watchdog setting.
I've not timed precisely but does seem to be around 10 mins.
It doesn't just happen during RAID build, machine also rebooted during linux install process.
I have 3 new ML150 G3 delivered yesterday to go to customer next week... a customer I advised to use HP rather than Dell SC440 :(

I also cannot confirm RHEL4.4 support for the RAID controller...or even any driver disk which takes account of the fact that these machines have no FDD!!!

I also believe Smartstart is not supported :(

1) Urgent fix required for apparent BIOS issues- no floppy based ROMpaq pls
2) adpahci driver CD for RHEL4.4?

Losing a lot of time on this...

[Andy Ratcliffe]

I'm getting the same thing on a brand new ML150 G3. I have found that if I go back into the Raid config, and then rebuild the array, it seems to carry on from where it left off.

I don't know what implications this will have at this stage - has anyone else tried this?

[Gilles R.]

We have the same problem with 4 HP Proliant ML150 G3 when we want to use RAID 1.

We have use the last bios : 2006.10.02 A - 17 Oct 06

The system hang when the build of the RAID 1 arrive near 30%

When we disable all watchdog options in Bios, the system don't hang and the RAID 1 is build entirely.

But after when we want to install Windows 2003 Server R2 (we also try with non R2, the problem is the same), we use the driver "HP Embedded SATA RAID Controller Driver for Windows 2000/Windows Server 2003 - version 1.2.5567.0 (19 Nov 06)". After the first reboot the system hang.
The error message is (in French) :
Windows n'a pas pu demarrer en raison d'un probleme de configuration materielle d'un disque de l'ordinateur.
Impossible de lire a partir du disque de demarrage selectionne.


Anybody has a solution ?

Thanks.

[J. Muurling]

Please report all problems to HP you can also reference to my support request.
My request is under investigation in USA but slow speed.
All the official solutions (bios, etc) did not work.
I made a workaround which is an official HP workaround now.
Try to install the OS without mirroring. Install the HP Raid software and build the mirror using this software. It helped for me, please try it and let me (and HP) know the results.

I think it is also an idea to make a list of all disks which are used.

[Gilles R.]

But in this case, it's not a hardware RAID, just a software RAID ?

[Andy Ratcliffe]

I just changed the watchdog timeout to 100 (I think the default is 10), and it all went through fine for me

[Gilles R.]

Andy Ratcliffe Dec 1, 2006 11:36:22 GMT Unassigned

--------------------------------------------------------------------------------
I just changed the watchdog timeout to 100 (I think the default is 10), and it all went through fine for me


+++++++++++++++++

I try it, it doesn't work for me.

[Gilles R.]

My HP ticket number is 1213676897

[Gilles R.]

We have open 3 other tickets (1 by server) :
1213682628
1213682579
1213682771

[Gilles R.]

That's work for us now :)

At the begining we use a usb key for the drivers for the SATA RAID when we install Windows 2003 R2 (with F6 option at the begining of the install).
When we replace the usb key by a usb floppy disk connected at the internal USB port (near SATA connectors) all work perfectly.


For resumed

Server : HP Proliant ML150 G3

Bios version : "Systems ROMPaq Firmware Upgrade Diskette for HP ProLiant ML150 G3 Servers" - version 2006.10.02 A (17 Oct 06)

Bios version for the SATA controler : "Firmware and BIOS for HP 8 Internal Port SAS HBA with RAID" - version 06.08.07.00 (8 Nov 06)

SATA Drivers : "HP Embedded SATA RAID Controller Driver for Windows 2000/Windows Server 2003 - version 1.2.5567.0 (19 Nov 06)

On the Bios, we have disable 2 Watchdog options :
Advanced - IPMI - BIOS POST Watchdog
Advanced - IPMI - OS Boot Watchdog
Without this modifications, SATA RAID building failed near 30%

We use a RAID 1 with 2 disks connected on the 2 first SATA connectors (SATA1 & SATA2)

All bios and drivers can be found here : http://h18023.www1.hp.com/support/files/server/us/locate/69_6265.html

[Jens Breiland]

FWIW, I have setup several ML150's and after experiencing some problems prior to this with Intel Server Motherboards embedded SATA RAID where the system just starts corrupting the partition, etc. I decided for future installations, to just use a separate adaptec 2410sa SATA raid card to avoid issues. After reading some of the problems others are experiencing, I realize that was the right thing to do. Perhaps on-motherboard/embedded SATA RAID technology is not mature enough to be counted on reliably? I am currently working on a random restarting issue with a proliant ML-350 that seems to be related with the built-in hot-swappable SATA RAID system. The server just restarts under heavy disk usage.

In retrospect, I should have probably just done an internal Adaptec raid config as my other ML-110 servers. I'm interested in any opinions or experiences other people in this group have had.

[Sameera Lakmalltd]

Try changing bios settings Watchdog timers t o disable state . steps

F10 --> AMPI or something like that

from it there are watchdog timers disable that
timers. it will work

bye

[Iwan van Steinvoorn]

We have had the same problem with our four ML150 G3 servers.
With the folowing BIOS version and BIOS settings we solved the problem:

Bios ProLiant BIOS O07
Build Date 06/23/2006

F10 -> PhoenixBios Setup -> Advanced -> IPMI ->:

BIOS POST Watchdog: Disabled
OS boot Watchdog: Disabled

Timer for loading OS (min) 100

Have a nice day!

[Jon Ward]

Refer to customer advisory c00842293 at http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c00842293&jumpid=reg_R1002_USEN for a specific reboot issue that HP is currently working on.

To proactively be notified when the firmware becomes available, consider registering for driver alerts, available from hp.com's Support & Troubleshooting page.

[Michael Diendorf]

hi
i had the same problem building 2 raid1 arrays on the ML150. in ctrl bios the system reset after some minutes during build ..

so i just ignored the problem and started to install my ms sbs2003 r2 and the installation run perfect. after windows was running
properly, i installed the hp storage manager software what came on the ML150 cd .. and there i saw my 2 raid1 .. still verifying !!
it took about 20h for both raid1 mirrors to complete (all i all 2x 2x250gb sata wd hds )

and now its working fine for more thanb a week... no problems with raid 1 arrays ..


besides acronis trueimage server edition works perfect in windows, i can image/clone any partion of this raid arrays to the other array. i always see 2 drives (my arrays)

but when i have to drop to dos for restoring this "system" image .. acronis keeps finding 4 single sata drives .. where drive 2 looks exactly like 1 and 4 looks like 3 ...
if i restore the image to drive one .. the restore skips after 30% and the boot partiton renders unreadable .. if i restore the image to drive 2 .. i can start the server with that image perfectly

just in case anyone ever tries aconis and runs into the same trouble

[Alexander Mayer]

hi, i accidently found this topic while searching for a solution on a reboot issue @ sbs 2003.


i had to set up raid 1 on 2 new ml150 G3 and experienced the same problems like u people.

i discovered, that although the servers keep restarting, since you dont miss the "Press F8 for RAID Setup" Step, you can continue the build. if you fail to hit f8 once, the array has to build completely new from 0% (if i remember correctly).

so if it restarts at e.g. 12% build and you hit f8 straight after the reboot, it continues to build at about 10-12%. its a pain in the neck, but it works. took me about 1,5-2 hours to complete the build.

dunno if there came a solution with a bios upgrade yet, but if not, this is the way it worked for me (didnt try the watchdog thing though).

greetings, alex