RAID issue - please assist

Been said here multiple times but ill add...Dont do  anything before having complete backups!

I would not even touch those physical drives, leave them in place as they are...backup over the network or to external and then go from there...do this asap!

I have had controllers do very strange things when moving drives especially when things are old and faulty.
 
Yay old HP Microserver with it's hard(soft)ware RAID
First thing,make a copy of all the important files
Second load up something like macrium reflect and image the harddrive to an external disk
Next check the drives using a Bootable HDSentinel using a USB-bay/dock to prevent windows doing any fuzzies in another machine (I made a custom ISO image with Windows PE and HD Sentinel and uploaded you a copy to wetransfer as the bootable DOS one is toss)
 
@PaulB_ - have you had a chance to review the raid controller within the bios?

If not then you should be able to determine the raid controller from the device manager within Windows.

If the raid controller is an Intel raid controller then install Intel Rapid Storage Engine software and once installed you'll be able to review the status of the raid array, making changes to allow for rebuild upon installation of a new disk, and then removing the faulty drive with a new drive.
 
@PaulB_ - have you had a chance to review the raid controller within the bios?

If not then you should be able to determine the raid controller from the device manager within Windows.

If the raid controller is an Intel raid controller then install Intel Rapid Storage Engine software and once installed you'll be able to review the status of the raid array, making changes to allow for rebuild upon installation of a new disk, and then removing the faulty drive with a new drive.
It's a microserver N54L
1678864396995.png
 
1679386585772.jpeg


1679386615701.jpeg

1679386634235.jpeg
1679386672125.jpeg
1679386687605.jpeg
1679386708828.jpeg

1679386719337.jpeg

1679386767995.jpeg1679386779380.jpeg
My aplogies for only getting back to you all now.
The issue is still there, but have only recently gotten round to getting photos of the configuration.

I have removed reference to the name of the raid, as it identifies the organisation, and out of concern that the original IT company will come across these, and it's not my intention to put anybody in a bad light. As an IT Techncian who has made my fair share mistakes, I'd rather not point out others.
 
Right,it's a mirror and 1 member has failed
Not a disaster yet
First thing,make a copy of all the important files
Second load up something like macrium reflect and image the harddrive to an external disk
Next check the drives using a Bootable HDSentinel using a USB-bay/dock to prevent windows doing any fuzzies in another machine (I made a custom ISO image with Windows PE and HD Sentinel and uploaded you a copy to wetransfer as the bootable DOS one is toss)
 
Right,it's a mirror and 1 member has failed
Not a disaster yet
Thought as much..
What would the procedure be to replace the drive, and ensure the raid is mirrored to another drive?
Simply remove faulty drive, replace with another drive, and the new drive will automatically remirror, or is this wishful thinking?

and thanks for the HDSentinel image. Will do all that, when I'm next on site....
 
Thought as much..
What would the procedure be to replace the drive, and ensure the raid is mirrored to another drive?
Simply remove faulty drive, replace with another drive, and the new drive will automatically remirror, or is this wishful thinking?

and thanks for the HDSentinel image. Will do all that, when I'm next on site....
Add new disk,go into raid software and "adopt" the disk as a spare,it should rebuild then
You run a risk of a secondary failure though so have a backup of criticals handy first
 
Add new disk,go into raid software and "adopt" the disk as a spare,it should rebuild then
You run a risk of a secondary failure though so have a backup of criticals handy first
If I may suggest that you replace the failed drive, rebuild, and then replace the current healthy drive and don’t go with WD Red’s - they’re cheap and horrible.
 
Add new disk,go into raid software and "adopt" the disk as a spare,it should rebuild then
You run a risk of a secondary failure though so have a backup of criticals handy first
Pardon my ignorance, but is this raid software within Windows, or within the BIOS? (CTRL + F Menu) and must the spare be added while the other two are still connected?

If I may suggest that you replace the failed drive, rebuild, and then replace the current healthy drive and don’t go with WD Red’s - they’re cheap and horrible.
and thanks, going to recommend this the the chairperson of the organisation. If I remember correctly these ARE WD Reds.

Thanks once again for all the valuable feedback.
 
That’s hardware raid, but you’ll be able to download the raid management software from the vendors website if it isn’t already installed on the server.
 
Pardon my ignorance, but is this raid software within Windows, or within the BIOS? (CTRL + F Menu) and must the spare be added while the other two are still connected?


and thanks, going to recommend this the the chairperson of the organisation. If I remember correctly these ARE WD Reds.

Thanks once again for all the valuable feedback.

Since you have the spare slots it would be best to add the third drive and have it adopt and mirror and only then removing the faulty one.

But from everything I can see there it looks like the second drive isn’t even connected and that’s why it’s complaining. I only see one serial number listed and it claims to be healthy.

For all you know there’s simply a problem with the connection on power or SATA and the drive is actually fine.

Are you 100% sure there is actually a drive in both those caddies? I’d power down and pull them both out to confirm if you haven’t already. Wouldn’t be at all surprised if you find it completely empty.

And if they are both there try moving them all one slot up to confirm it’s not a problem with the ports.
 
Last edited:
You run a risk of a secondary failure though so have a backup of criticals handy first

This happens more often than not, practically the sole reason why raid 6 exists to replace raid 5. If Op can, should place at least 3 if not 4 disks into the server to mirror, disks are relatively inexpensive.
 
HD Sentiel does report the second HDD connected

1679920637319.png
Teamviewered into the server quickly, and as one can see just shows limited info.
With regards to RAID software, I had a look on the HP website, and there's very limited info with what one must use to adopt the additional HDDs.

I'll keep looking on the HP website, in case i'm missing something.
I spoke to the chairperson of the organisation, and passed on Jade's feedback about WD Reds being nasty drives, and they seem to be fine with replacing both the drives, just need to confirm how exactly.

By the sounds of things, I now have a way forward. Just need to find the appropriate RAID management software. HP's website is non existant.

SCSI\DiskAMD_____1X2_Mirror/RAID11.10 Here is the dev ID from Device manager.

The smaller 1TB Drive which shows up on HD Sentienel is used for backups.
Thanks so much for the advice so far, much appreciated.
 
75% on the primary disk isn't particularly healthy either,Disk2 also not reporting much so probably toasty
Backup and replace asap
 
Also need advice on the best brand/model of 2TB replacement drives to get. Something which combines affordability with reliability.
Unless someone knows of a good retailer, the replacement drives will be bought via Takealot.

This is a home for mentally challenged people, so their cashflow isn't the greatest.

Thanks
 
Top
Sign up to the MyBroadband newsletter
X