1 2 Previous Next 15 Replies Latest reply on Apr 7, 2009 12:43 PM by wgkorb-JavaNet Go to original post
      • 15. Re: T3 RAID problem
        wgkorb-JavaNet
        My upgrade to S10 is a ways off yet, and as such, I am a little concerned that I'm going to have an issue with this filesystem. Specifically, the problem that existed before the T3B controller upgrade is now reflected multiple times per day every day when the disk scrubber process runs:
        Apr 07 08:29:38 t3 ALTD[1]: N: Vol verify started for volume (Raid set) v0
        Apr 07 08:39:47 t3 ISR1[2]: W: u1d03 SCSI error occurred: Medium Error (sense key = 0x3). Unrecovered Read Error.
        Apr 07 08:39:47 t3 ISR1[2]: W: u1d07 SCSI error occurred: Medium Error (sense key = 0x3). Unrecovered Read Error.
        Apr 07 08:39:47 t3 SX11[2]: N: u2ctr Vol verify found multiple read-disk errors on stripe 58729 of volume (Raid set) v0. Skipping stripe.
        Apr 07 08:39:50 t3 ISR1[2]: W: u1d08 SCSI error occurred: Medium Error (sense key = 0x3). Unrecovered Read Error.
        Apr 07 08:39:51 t3 ISR1[2]: W: u1d03 SCSI error occurred: Medium Error (sense key = 0x3). Unrecovered Read Error.
        Apr 07 08:39:51 t3 SX11[2]: N: u2ctr Vol verify found multiple read-disk errors on stripe 58821 of volume (Raid set) v0. Skipping stripe.
        Is there a way I can force these stripes to be rewritten short of a dump/restore?

        Also, I noticed that either a vol verify or a disk verify of my hot spare happens constantly. Is that by design? Is there any way for me to adjust that schedule to be a bit less frequent (e.g., once per day)? I only ask because I'm concerned that all of this activity will accelerate the inevitable demise of these disks since they are getting fairly old.

        Thanks,
        Bill
        1 2 Previous Next