HP DL380 Drive Array Failure - All drives lost RAID info
Hi
We have a set HP servers running simple File server duties. Last night during backup the Veritas 10 engine tried backing up a file on server 04 and failed backup as 'file is corrupt'. This was the last entry of this server in the log.
When we looked at the server this am the drives all flashed red and the RAID card does not recognise the array but only single drives. Another array on that server on the same controller which contained the system disk is recognised as array but no file system is found.
Swapping the disks to an identical server returns same problem, so the issue is with the drives not the hardware around it.
It appears that all drives lost the RAID Info stored on the drives itself.
Configuration:
ML380 G4
HP 6402 RAID Array controller 4x 146.8Gb RAID5 and 2x36.4Gb RAID1+0
2 questions:
Has anyone seen a failure with these results?
Any klnown procedure of restoring disk side RAID config?
Help is appreciated
Thanks
We have a set HP servers running simple File server duties. Last night during backup the Veritas 10 engine tried backing up a file on server 04 and failed backup as 'file is corrupt'. This was the last entry of this server in the log.
When we looked at the server this am the drives all flashed red and the RAID card does not recognise the array but only single drives. Another array on that server on the same controller which contained the system disk is recognised as array but no file system is found.
Swapping the disks to an identical server returns same problem, so the issue is with the drives not the hardware around it.
It appears that all drives lost the RAID Info stored on the drives itself.
Configuration:
ML380 G4
HP 6402 RAID Array controller 4x 146.8Gb RAID5 and 2x36.4Gb RAID1+0
2 questions:
Has anyone seen a failure with these results?
Any klnown procedure of restoring disk side RAID config?
Help is appreciated
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Many thanks for all your help, unfortunately we had to rebuild from backup, after we assessed that another day downtime is worse than the lost data. Taught me to have spare drives, mmh the constraints of a nSME.
Thanks again.
Thanks again.
ASKER
We had 4 hours response from HP with a new controller so we thought fine. But the new controller would mark the drives as detailed in the question, SmartStart 7.10 confirmed the info from the ROM.
Hence we moved the drives to another server to isolate the problem from the affected server.
Idea was that if the drives spin up OK and array is found, given that we replaced the controller than the error must be withe the server (MB/backplane)
The other server we tested the drives on had the same confid (DL380) but a 642 controller instead and was running a live server... We removed the drives and placed the 04 server drives and we had the same result so the problem moved.
Ergo we concluded if the drives do not show the arrays on the other controller than the info on the drives about the config must have gotten corrupted.
When we placed the original drives back in the test server these started up OK.
We then put the damaged drives back into the 04 server but swapped channels on the controller only to get the same result.
All this points to the drives.
Ideas?