Unsolved
This post is more than 5 years old
1 Message
0
3669
September 1st, 2018 10:00
Failed Drives In PS4000e
I had (2) 1 TB hard drives fail in in a PS4000e EgualLogic Array at the same time. Drive #4 and drive #8 failed in a RAID 50 set. I inserted a exact replacement drive in slot #4. I'm still waiting for a drive to arrive for slot #8. After 48 hrs I still see a 'initializing drive' message from a CLI prompt. Is there a chance I have lost all my data or will it take the replacement of the second drive in order for the array to come back online?
Thanks.
No Events found!
DELL-Sam L
Moderator
•
7.6K Posts
0
September 6th, 2018 07:00
Hello Pontiac87,
When you replaced the failed drive, was the Dell part# on the drive the same? There is a chance that your data could be lost but would need to look at the logs of your PS4000e to be sure. If your PS4000e still has a support contact then we can review the logs.
Please let us know if you have any other questions.
d1hawkins
1 Message
0
March 13th, 2019 06:00
Was this ever resolved? We're having a very similar problem and have the same configuration. ps4000 raid 50
We physically moved locations and now we are not able to access our ps4000 via ethernet. None of the 6 ethernet connection show any lights on. When we connect via the serial port, most commands give the message "storage array still initializing". If we run the command "ru raidtool", it indicates 1 drive is going bad (however the light on the drive is green). We also see the following message "Logger daemon is losing messages because offline disks are generating more events than the daemon can handle"
Should we have to replace the drive in order for this to work?
Anything else we should try or look at it?
dwilliam62
4 Operator
•
1.5K Posts
0
June 24th, 2019 14:00
Hello,
There is a specific Equallogic forum here in the Dell Community Forums.
NO, do not replace any drives.
That error messages suggest that you RAIDset has faulted and there is not disk space to store the event messages. So if fills a buffer and overflows, generating that error you see.
You need to be careful on what steps you take.
Did you get this resolved since posting here?
Regards,
Don