[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 562
  • Last Modified:

Proliant ML 330 reporting 1783 Disk Array controller failure after power outage

This 2-year old server with 2 hard drives (sorry don't know the size) and Raid 0 lost power and now reports "error in primary device 0 - Please replace it" then displays "1783 Disk Array  controller failure".  

Unfortunately, I'm not familiar with RAID specifics.  I believe that the hard drive has died and needs replaced (even though it reports a controller failure), but I'm not sure of the correct process for getting this machine back up and running.   Any advice would be greatly appreciated.

Thanks.
0
tlindlahr
Asked:
tlindlahr
1 Solution
 
rjwesleyCommented:
Based on HP support pages, I would say that you may be looking at replacing your controller card.

Are there any other errors during POST?

https://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=671538

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=678719

0
 
arthurjbCommented:
Are you able to read the disks on that controller?

If so, before you do anything else you need to backup the data on those drives.

If you cannot read the data from thoses drives then what I would do first, is completely power down the system, leave it off for a few minutes, the restart the system.

It is very likely that the power outage event did not shut down the device properly.

It is important that if you can backup the data that you do so, because if it is a failing controller, when you power down, it may not come back up.....
0
 
tlindlahrAuthor Commented:
Luckily, we have a backup already of the data, so I'm not concerned about that.  

This machine has been shut down and left off for more than 24 hours and still get the same error.

I disconnected the primary drive and connected the 2nd drive in its place and do NOT get the same controller error, but after entire boot process end up with "non-system disk" error.  This is why I believe its the drive not the controller.  There are no other errors on POST.
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 
arthurjbCommented:
You did prove that it is the drive.

You mentioned that the system was using RAID 0  that means that you had no data protection at all.  

RAID 1 would be a mirror, and RAID 5 would be a protected group of disks where any one of the disks could die but the data would still be protected.

Since you had no data protection, all you need to do now is get a replacement drive, reload the system, and reload the data.

I would suggest replacing both drives with double the size disks, and use RAID 1 so that next time this happens, you will only have to replace the drive, and not be stuck reloading the data.

Good Luck!
0
 
tlindlahrAuthor Commented:
So, if I did indeed have RAID1, (I think it was RAID0, but...) I would need to replace the drive, and what else?  

If in fact, I do replace both drives, am I correct in my assumption that I am back at ground zero, reload OS, etc and then reload all the data from my back up?

Thanks for your help
0
 
pgm554Commented:
If it was RAID 0 ,you're data is gone.
However,you stll might have an issue with restoring your data in that RAID 0 uses all the storage capacities of both drives combined.
RAID 0 >  2 X 36GB drives = 72 gb storage capacity.
RAID 1 >  2 X 36GB drives = 36 gb storage capicity.

So you would be forced to go RAID 0 again if you have more than the native capacity of you old drive.

And RAID 0 as you've found out ain't all that great.
0
 
arthurjbCommented:
pqm554's comment was why I mentioned that you need to use double size drives for replacement if you plan to go RAID 1.


If it actually was RAID 1 already, then you may have ruined your chance of recovery by moving the good drive to the other location, but I do not know the recovery process for that machine.

As things seem now, you will be at ground zero needing to reload everything.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now