ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Possible failed hdd

Joshua Small_2
Valued Contributor

Possible failed hdd

Hey guys,

I have an ML110 with a Fastrack S150 SX4.

I'm seeing the following periodic logs:

04/05/06 21:03:16 Error Error Event Logged Controller #1 : Disk Maxtor 6Y080M0 (Ch. 2, Master) error at LBA 0x416eea starting from LBA 0x416e80. (Feature=0x0, Block count=0x80, Command=0x20, Status=0x51, Error=0x40.
04/05/06 21:03:15 Error Error Event Logged Controller #1 : Disk Maxtor 6Y080M0 (Ch. 2, Master) error at LBA 0x416eea starting from LBA 0x416e80. (Feature=0x0, Block count=0x80, Command=0x20, Status=0x51, Error=0x40.
04/05/06 08:01:50 Error Error Event Logged Controller #1 : Disk Maxtor 6Y080M0 (Ch. 2, Master) error at LBA 0x68398e starting from LBA 0x683987. (Feature=0x0, Block count=0x8, Command=0x20, Status=0x51, Error=0x40.
03/30/06 12:30:59 Information Disk Error Fixed Controller #1 : A disk error at LBA 0x1faae7 on Channel2 is fixed
03/30/06 12:30:59 Information Bad Sector Log Cleared Controller #1 : Bad sector log entry cleared: LBA 0x1faae7 on disk at channel2
03/30/06 12:30:59 Information Bad Sector Log Updated Controller #1 : Bad sector log updated: LBA 0x1faae7 on disk at channel2
03/30/06 12:30:59 Error Error Event Logged Controller #1 : Disk Maxtor 6Y080M0 (Ch. 2, Master) error at LBA 0x1faae7 starting from LBA 0x1faae5. (Feature=0x0, Block count=0x12, Command=0x20, Status=0x51, Error=0x40.
03/30/06 12:30:59 Error Error Event Logged Controller #1 : Disk Maxtor 6Y080M0 (Ch. 2, Master) error at LBA 0x1faae6 starting from LBA 0x1faae5. (Feature=0x0, Block count=0x12, Command=0x20, Status=0x51, Error=0x40.
03/30/06 12:30:59 Error Error Event Logged Controller #1 : Disk Maxtor 6Y080M0 (Ch. 2, Master) error at LBA 0x1faae6 starting from LBA 0x1faae5. (Feature=0x0, Block count=0x12, Command=0x20, Status=0x51, Error=0x40.
03/30/06 12:30:59 Information Disk Error Fixed Controller #1 : A disk error at LBA 0x1faae5 on Channel2 is fixed


This suggests to me a HDD failure. However, the disk array is only ever reported as "Functional", I never see a disk go offline.

What confuses me is that it says "bad sector log updated" but if I hit "view bad sector log" the file is empty.

Promise Array Management 4.0 reports the disk as being fine effectively. However I will receive a log once a week like the above.

How can I diagnose further?