how to get rid of bad blocks in a file on PERC 5/I?

Bond Masuda bond.masuda at jlbond.com
Mon May 3 14:04:46 CDT 2010


Thanks Patrick for your reply.

I know my original message was long, so perhaps it was missed, but I did run
a consistency check, at least twice. However, after each CC run, we tested a
dd_rescue attempt on the file in question and still had unreadable blocks. I
was expecting one of two things: 1) the consistency check reporting back all
sorts of problems, or 2) the unreadable blocks would go away. Neither was
the case and hence I decided to reach out.

I had forgotten about the "action=exportlog", thanks for reminding me about
that. This is what i found:

04/29/10 14:45:10: EVT#17279-04/29/10 14:45:10:  97=Puncturing bad block on
PD 03(e0/s3) at 33334430
04/29/10 14:45:10: EVT#17280-04/29/10 14:45:10:  97=Puncturing bad block on
PD 06(e0/s6) at 33334430
04/29/10 14:45:11: EVT#17282-04/29/10 14:45:11:  97=Puncturing bad block on
PD 04(e0/s4) at 33334430
04/29/10 14:45:11: EVT#17283-04/29/10 14:45:11:  97=Puncturing bad block on
PD 06(e0/s6) at 33334430
04/29/10 14:45:11: EVT#17284-04/29/10 14:45:11:  97=Puncturing bad block on
PD 03(e0/s3) at 33334430

-Bond

> -----Original Message-----
> From: linux-poweredge-bounces at dell.com [mailto:linux-poweredge-
> bounces at dell.com] On Behalf Of Patrick_Fischer at dell.com
> Sent: Monday, May 03, 2010 2:46 AM
> To: tim at seoss.co.uk; adam.nielsen at uq.edu.au
> Cc: linux-poweredge at lists.us.dell.com
> Subject: RE: how to get rid of bad blocks in a file on PERC 5/I?
> 
> Consistency Check:
> Check consistency. A check consistency determines the integrity of a
> virtual disk's redundant data. When necessary, this feature rebuilds
> the redundant information.
> Source:
> http://support.dell.com/support/edocs/software/svradmin/6.2/en/OMSS/cnt
> rls.htm#wp681476
> 
> the remapping of bad sectors should be run automatically if the sector
> can't be written and the controller try to write or read from it.
> 
> Please check all times the controller log if you got filesystem erros
> like you described.
> Check the log for Bad LBA's on the disk like searching the log file
> with "bad"
> Check the Count of the LBA's and check if it occurs on multiple disks
> like a punctured stripe....
> 
> The log you can get per megacli or open manage:
> 
> Server Administrator cli:
> omconfig storage controller action=exportlog controller=0
> where controller 0 = id of the involved controller



More information about the Linux-PowerEdge mailing list