Advertisements

Dell Equallogic Hard Drive Firmware Upgrades – XQH6 and XRH7 >> ERHB

Like this Guy –> http://integritycomm.blogspot.com/2010/11/dell-equallogic-hard-drive-firmware.html

We received a letter advising us to update the firmware on the drives inside our EqualLogic. After upgrading the arrays to their latest firmware I then proceeded to update the drives.

Unfortunately, I am not patient. I thought the telnet session had stalled, so I hit carriage return a couple of times. With my luck at the end of the script it says

Do you want to proceed (y/n) [n]:

The default is n (which is good)

So by hitting carriage return I sent the N, but that is where it seemed to pause again. I tried the trusty CNTRL+X and CNTRL+C but nothing happened so then I just X’ed out of the telnet session.

Well, when I went to rerun the script it told me the script was already running…. grrr.

After some emails back and forth with support they had my restart the array (basically a fail over to the secondary controller) and then I was able to run the script.

So the lesson is be patient. Here is some sample output from after the script runs, it’s some very interesting data.

**********************

Analysis of drive 0:
Approved drive by, legacy .
The drive has had 1448178298 IOs issued to it and 12 errors. Access based on percent region of the drive below: 0 – 25  : 71.3(1032255010) percent(Count) / 41.7(5) Error percent(Count). 25 – 50  : 28.4(411454199) percent(Count) / 58.3(7) Error percent(Count). 50 – 75  : 0.2(2391519) percent(Count) / 0.0(0) Error percent(Count). 75 – 100 : 0.1(2077570) percent(Count) / 0.0(0) Error percent(Count).
Current Preemptive removal status is: Drive is being monitored.
No errors in past 360 seconds, so short term preemption is not active.
No errors in past 60 days, so LONG term preemptive not active.
Detailed error history(upto the last 10 errors): 12 total errors have been logged for this drive.
At local time of Tue Dec  7 18:39:46 2010 A Write at LBA 392362880 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 1 seconds.
At local time of Tue Apr  6 11:55:05 2010 A Write at LBA 382757760 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 1 seconds.
At local time of Thu Jun 10 03:26:43 2010 A Write at LBA 279021440 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 1 seconds.
At local time of Sat Jun 19 05:18:07 2010 A Write at LBA 376467840 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 29 seconds.    Special actions taken during error recovery: The drive required a power cycle. A drive reset failed in error recovery.
At local time of Sun Jun 27 04:57:27 2010 A Write at LBA 330719104 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 1 seconds.
At local time of Tue Jun 29 03:13:49 2010 A Write at LBA 386509184 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 1 seconds.
At local time of Thu Aug  5 10:08:58 2010 A Write at LBA 181311360 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 1 seconds.
At local time of Wed Aug 11 20:18:46 2010 A Write at LBA 167442048 for 512 blocks,  with a IO Error(0x5) error with a sub error of Drive fault(0x3)  (ASC/ASCQ(0x80/0x87) = (null))  and a recovery time of 1 seconds.
At local time of Mon Oct 11 03:12:48 2010 A Read at LBA 258519932 for 4 blocks,  with a IO Error(0x5) error with a sub error of Drive fault(0x3)  (ASC/ASCQ(0x29/0xcd) = (null))  and a recovery time of 32 seconds.    Special actions taken during error recovery: The drive required a power cycle. A drive reset failed in error recovery.
At local time of Sat Dec  4 02:31:05 2010 A Write at LBA 93825920 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 46 seconds.    Special actions taken during error recovery: The drive required a power cycle. A drive reset failed in error recovery.

Analysis of drive 1:
Approved drive by, legacy .
The drive has had 1448680394 IOs issued to it and 0 errors. Access based on percent region of the drive below: 0 – 25  : 71.4(1034481632) percent(Count) / No Errors. 25 – 50  : 28.3(409729673) percent(Count) / No Errors. 50 – 75  : 0.2(2391519) percent(Count) / No Errors. 75 – 100 : 0.1(2077570) percent(Count) / No Errors.
Current Preemptive removal status is: Drive is being monitored.
No errors in past 360 seconds, so short term preemption is not active.
No errors in past 60 days, so LONG term preemptive not active.
Detailed error history(upto the last 10 errors): None present.

Analysis of drive 2:
Approved drive by, legacy .
The drive has had 1438761266 IOs issued to it and 0 errors. Access based on percent region of the drive below: 0 – 25  : 71.2(1025055042) percent(Count) / No Errors. 25 – 50  : 28.4(409237135) percent(Count) / No Errors. 50 – 75  : 0.2(2391519) percent(Count) / No Errors. 75 – 100 : 0.1(2077570) percent(Count) / No Errors.
Current Preemptive removal status is: Drive is being monitored.
No errors in past 360 seconds, so short term preemption is not active.
No errors in past 60 days, so LONG term preemptive not active.
Detailed error history(upto the last 10 errors): None present.

Analysis of drive 3:
Approved drive by, legacy .
The drive has had 1442597461 IOs issued to it and 17 errors. Access based on percent region of the drive below: 0 – 25  : 71.2(1027469491) percent(Count) / 58.8(10) Error percent(Count). 25 – 50  : 28.5(410658881) percent(Count) / 41.2(7) Error percent(Count). 50 – 75  : 0.2(2391519) percent(Count) / 0.0(0) Error percent(Count). 75 – 100 : 0.1(2077570) percent(Count) / 0.0(0) Error percent(Count).
Current Preemptive removal status is: Drive mirror has been requested.
No errors in past 360 seconds, so short term preemption is not active.
No errors in past 60 days, so LONG term preemptive not active.
Detailed error history(upto the last 10 errors): 17 total errors have been logged for this drive.
At local time of Mon Dec  6 20:02:11 2010 A Write at LBA 171795840 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 1 seconds.
At local time of Fri May 14 02:15:17 2010 A Write at LBA 98670592 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 1 seconds.
At local time of Fri May 21 22:03:50 2010 A Write at LBA 386509184 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 1 seconds.
At local time of Mon May 24 03:29:27 2010 A Write at LBA 341505920 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 1 seconds.
At local time of Sat Aug 28 03:29:23 2010 A Write at LBA 193960320 for 512 blocks,  with a IO Error(0x5) error with a sub error of Drive fault(0x3)  (ASC/ASCQ(0x80/0x87) = (null))  and a recovery time of 1 seconds.
At local time of Thu Sep  2 02:35:10 2010 A Write at LBA 47802240 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 34 seconds.    Special actions taken during error recovery: The drive required a power cycle. A drive reset failed in error recovery.
At local time of Fri Sep 10 16:56:11 2010 A Write at LBA 104849280 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 46 seconds.    Special actions taken during error recovery: The drive required a power cycle. A drive reset failed in error recovery.
At local time of Sun Oct 17 02:25:02 2010 A Write at LBA 93841280 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 46 seconds.    Special actions taken during error recovery: The drive required a power cycle. A drive reset failed in error recovery.
At local time of Sun Oct 17 12:39:11 2010 A Write at LBA 238471040 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 31 seconds.    Special actions taken during error recovery: The drive required a power cycle. A drive reset failed in error recovery.
At local time of Wed Dec  1 02:15:07 2010 A Write at LBA 90193280 for 512 blocks,  with a IO Error(0x5) error with a sub error of Drive fault(0x3)  (ASC/ASCQ(0x80/0x87) = (null))  and a recovery time of 1 seconds.

Analysis of drive 4:
Approved drive by, legacy .
The drive has had 1436628948 IOs issued to it and 14 errors. Access based on percent region of the drive below: 0 – 25  : 71.1(1020999326) percent(Count) / 57.1(8) Error percent(Count). 25 – 50  : 28.6(411160533) percent(Count) / 42.9(6) Error percent(Count). 50 – 75  : 0.2(2391519) percent(Count) / 0.0(0) Error percent(Count). 75 – 100 : 0.1(2077570) percent(Count) / 0.0(0) Error percent(Count).
Current Preemptive removal status is: Drive mirror has been requested.
No errors in past 360 seconds, so short term preemption is not active.
No errors in past 60 days, so LONG term preemptive not active.
Detailed error history(upto the last 10 errors): 14 total errors have been logged for this drive.
At local time of Mon Nov 29 02:32:15 2010 A Write at LBA 93436800 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 46 seconds.    Special actions taken during error recovery: The drive required a power cycle. A drive reset failed in error recovery.
At local time of Fri Apr 30 15:59:41 2010 A Write at LBA 125992448 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 28 seconds.    Special actions taken during error recovery: The drive required a power cycle. A drive reset failed in error recovery.
At local time of Sat Jun 19 09:11:26 2010 A Write at LBA 338531200 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 32 seconds.    Special actions taken during error recovery: The drive required a power cycle. A drive reset failed in error recovery.
At local time of Fri Jul 30 05:10:58 2010 A Write at LBA 231035648 for 512 blocks,  with a IO Error(0x5) error with a sub error of Drive fault(0x3)  (ASC/ASCQ(0x80/0x87) = (null))  and a recovery time of 1 seconds.
At local time of Wed Aug  4 02:14:27 2010 A Write at LBA 294855040 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 28 seconds.    Special actions taken during error recovery: The drive required a power cycle. A drive reset failed in error recovery.
At local time of Tue Aug 31 06:39:18 2010 A Write at LBA 89624960 for 384 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 1 seconds.
At local time of Thu Sep  2 07:43:17 2010 A Write at LBA 89566080 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 28 seconds.    Special actions taken during error recovery: The drive required a power cycle. A drive reset failed in error recovery.
At local time of Thu Sep  9 23:24:09 2010 A Write at LBA 20379520 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 1 seconds.
At local time of Sun Nov 14 01:48:44 2010 A Write at LBA 20617600 for 512 blocks, with a  IO Error(0x5) error with a sub error of (0x0)  and a recovery time of 1 seconds.
At local time of Mon Nov 22 11:58:18 2010 A Write at LBA 296603520 for 512 blocks, with a  IO timed out(0x3c) error with a sub error of (0x0)  and a recovery time of 31 seconds.    Special actions taken during error recovery: The drive required a power cycle. A drive reset failed in error recovery.

Analysis of drive 5:
Approved drive by, legacy .
The drive has had 1439688520 IOs issued to it and 9 errors. Access based on percent region of the drive below: 0 – 25  : 71.2(1025259012) percent(Count) / 55.6(5) Error percent(Count). 25 – 50  : 28.5(409960419) percent(Count) / 44.4(4) Error percent(Count). 50 – 75  : 0.2(2391519) percent(Count) / 0.0(0) Error percent(Count). 75 – 100 : 0.1(2077570) percent(Count) / 0.0(0) Error percent(Count).
Current Preemptive removal status is: Drive mirror has been requested.
No errors in past 360 seconds, so short term preemption is not active.
No errors in past 60 days, so LONG term preemptive not active.
Detailed error history(upto the last 10 errors): 9 total errors have been logged for this drive.

ETC….

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: