Open Manage Version 7.2.0 on T420 server raid 5
I got Alert msg
Status - non Critical - "Predictive Failure reported: Physical Disk 0:1:3 Controller 0, Connector 0 "
Do I need to be worry ?
Do I need replace SAS ?
Where Can I find instruction
Solved! Go to Solution.
I didn`t try to continue.and yes It`s Dell replacement certified drive.
Drive 0:1:3 - was Failed - (20 hours after the alert msg as you said -THEFLASH1932-)
I found another Dell sas 600, and push it to cell number 5.
The server start to rebuild 0:1:5 by himself.
The server finish - (4 hours) to build 0:1:5 , then the status change to "online".
Everything looks fine!
I tried to assaing 0:1:4 as a hot-spare again , and now it works ! .
It`s look like that it was too late to try assign disk as a hot-spare.... Impossible to assign disk as hot-spare when you got physical drive alert\error .
Thank You THEFLASH1932 I really appreciate that.
Because it is not actually failed yet. When it fails, it will say Critical.
If you have hot-swap drives, go into OMSA and use the Prepare to Remove, Replace, or Force Offline option, then pull the drive from the chassis, then insert the new one. After 1 minute, if a rebuild has not started automatically, then assign it as a hot-spare to start the rebuild. Do NOT shut down the server to replace if not-swappable.
the current status
4 Physical sas identical
3 sas - Raid 5
0.3 online - problem
When the server online
- make full backup
- pull out the 0.4 physical drive
- execut 0.3 - offline
- pull out the 0.3 physical drive
- insert the 0.4 drive into the problematic 0.3 place
This is the correct way to deal with that situation?
* this is my RAID 5
0:1:0 online - 600GB SAS
0:1:1 online - 600GB SAS
0:1:2 online - 600GB SAS
0:1:3 online - problem 600GB SAS
0:1:4 ready - 600GB SAS
When I tried to assign disk 4 as a hot-spare I got
" Physical Disk 0:1:4: This Physical disk is not suitable to protect all current or potential virtual disks on this controller. Possible reasons include: Insufficient physical disk space, unsupported mix of SAS and SATA type physical disks, unsupported mix of SSD and HDD type physical disks, and non-SED drive assigned as a GHS when encryption virtual disk is present.
Continue with assigning as a global hot spare?
It`s ok to Continue ?