Unsolved
This post is more than 5 years old
3 Posts
0
577
January 14th, 2017 08:00
Failed HDD1 in poweredge t300 but cannot install OpenManage
I have inherited a poweredge t300 running SBS 2008 sp1 that is showing an E1810 fault on HDD1. The machine has PERC6/i which I understand means that the controller supports hot-swapping of drives. Unfortunately, the system does not have Dell OpenManage installed and my attempts to install the latest version are not working. I have downloaded the installer but when I double click to run it, nothing happens. I have not yet identified the type of drives in the system.
Is there an older version of OMSA that I could try?
Can I hot-swap the faulty drive some other way (using the OS)?
I understand it is not good practice to power down the server in order to remove and reinstall a new drive and that hot – swapping is the way to go.
Thanks for any suggestions
Daniel My
10 Elder
•
6.2K Posts
0
January 14th, 2017 09:00
Hello
This is the latest version of OMSA compatible with your server and operating system. The other versions section has older versions:
www.dell.com/support/home/Drivers/DriversDetails?driverId=N273Y
Hot-swapping a drive is not something you do from the OS or an application. Hot-swapping a drive is physically removing and replacing the drive. The PERC6 supports hot-swap, but you also need a backplane. Cabled drives are not hot-swappable.
If the drive is failed or offline then it doesn't matter. If you are replacing a drive that is online then you risk data loss if you replace it while the system is turned off. Modern controllers are designed to mitigate risk when best practices are not followed. The PERC6 should not have issues with improper drive replacement because it checks the metadata tags on each disk before bringing them online. This is mainly an issue with PERC4 and older controllers.
www.dell.com/support/home/product-support/product/poweredge-rc-6i/manuals
Thanks
szdoug
3 Posts
0
January 14th, 2017 13:00
Thanks Daniel for the speedy response.
I downloaded the version of OMSA that you suggested (it was the same as the one I had tried but I downloaded again in case it was corrupted). When I double-click on the file I see an hourglass for a fraction of a second and then nothing happens. I am guessing I am missing some other required feature/driver/update?
In the event that I cannot run OpenManage to take the faulty drive offline then it looks like I have no option but to power down to do the replacement. However, it was comforting to hear that PERC6 will check the disks before bringing the new one online.
I am going to have to powerdown just to identify the drives in the system so that I can order a correct replacement. Do you think there will be a problem doing this (ie. powering down, look at the drives, then power back up again with the faulty drive still in place)? The server is still functional at present although a bit slow. Is there a better option?
Thanks a bunch,
szdoug
3 Posts
0
January 14th, 2017 15:00
OK - some more information. I located the original Dell disk with OMSA on it. However, when I tried to install it indicated that my system has various issues that prevented install. So I think I going to forget using OMSA since from what you say I don't need it since the drive has failed (flashing amber light on the drive chassis).
Three of the 4 bays are occupied and the middle drive (HDD1) is flashing amber. Other two are solid green. The sticker on each bay indicates SATA 250 GB. Is this all I need to know to order a replacement drive? I couldn't see the make/model.
My plan is to:
1. Powerdown the system and remove the faulty drive to allow me to identify the make/model
2. Put the faulty drive back in the system.
3. Reboot
After obtaining a replacement drive I will:
1. Powerdown the system
2. Replace the faulty drive
3. Reboot and wait for rebuild.
Does this sound OK?
Thanks for your patience - this is my first time dealing with this kind of problem.
Gordon
Daniel My
10 Elder
•
6.2K Posts
0
January 14th, 2017 15:00
Don't put the failed drive back into the system. A drive failure does not mean the drive is bad. A drive is marked as failed by the controller for many reasons. If you reseat the drive then it may rebuild back into the array. If you have determined that the drive is failed then you don't want it rebuilding into the array.
A rebuild will not likely initiate on its own if a drive is replaced during a shutdown. You will likely have to set the new drive as a hot spare to get it to initiate a rebuild. The instructions for replacing a drive are in the PERC manual I linked in my initial response.
If you need further assistance with this issue then please contact fee-based support.
Thanks