Jump to content

Recommended Posts

Posted (edited)

Hi

I have several ML350 Gen6 servers which have been hugely reliable over the years. They are all up to date on BIOS, firmware, drive firmware, controller firmware and all drivers.

Typically if a HDD experiences a failure, it will just failed, indicate red LED and I swap the drive, rebuilds and all ok.

 

However, within the last few months i've had 2 drive failures on these gen servers and its taken down the server completely - even inaccessible by iLO remotely to determine why its offline.

 

I go to the physical server and see the red health LED flashing on the front.

 

I have to remove all power, re-connect and boot the server, and then see the failed Hard drive RED, which i Pull out, replace, then the array builds no issues.

 

Not sure why this has has started happening when drives fail.

 

However, Note that the drives which have failed are not the windows RAID drives, it's been data array drive.

Edited by ITGURU
Posted
These servers where released over 10 years ago. I wouldn't be majorly surprised if drives are failing. They are moving parts and do have a shelf life.
Posted
These servers where released over 10 years ago. I wouldn't be majorly surprised if drives are failing. They are moving parts and do have a shelf life.

 

the drives failing is not the issue. i have replace several drives over the years and never been an issue i just hot swap them. it just seems to be with the more recent failures that the drives tske the whole server down.

 

these server's are built to last

Posted

I had this issue before upgrading our servers, upon looking into it a bit more I found that it was because there were multiple drives about to fail hence the inability to just hot swap the one although one of them didn't not show any issues. I replaced a couple of drives (as the others had previously been replaced) and restored from a backup. Before taking them offline I had a further two failures which I was able to hot swap. I never came across the issue again, so may have been pot luck, but definitely something to consider.

 

Thanks,

Posted
I had this issue before upgrading our servers, upon looking into it a bit more I found that it was because there were multiple drives about to fail hence the inability to just hot swap the one although one of them didn't not show any issues. I replaced a couple of drives (as the others had previously been replaced) and restored from a backup. Before taking them offline I had a further two failures which I was able to hot swap. I never came across the issue again, so may have been pot luck, but definitely something to consider.

 

Thanks,

 

Thanks for this, however after i've swapped the single drive and it's rebuilt 100% without any issues i've not had another drive failure as yet.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...