Fwd: Critical problem with an ES A16U G2430

m.roth at 5-cent.us m.roth at 5-cent.us
Wed Jan 22 20:32:04 UTC 2014


Doll, Margaret Ann wrote:
> We have an ES A16U G2430 from Infotrend Industres that was probably
> purchased in 2009 by William Fripp for the Geological Department at Brown
> University.

TMI, there.... <g>
>
> The system is in a critical state.    The system further states a critical
> problem in the LD/LV event.

I haven't done much with LVM in years - my manager doesn't care for it, we
use a fair bit of RAID, but...
>
> Is there something I can do to correct the problem without rebuilding the
> entire array?
>
>>From the message log where /dev/sdg1, /dev/sdb1,
> /dev/sdc1,  /dev/sde1,  and
> /dev/sdf1
>
>
> Jan 21 11:43:17 porter2 kernel: sd 2:0:0:5: Unhandled sense code
> Jan 21 11:43:17 porter2 kernel: sd 2:0:0:5: SCSI error: return code =
> 0x08100002
> Jan 21 11:43:17 porter2 kernel: Result: hostbyte=invalid
> driverbyte=DRIVER_SENSE,SUGGEST_OK
> Jan 21 11:43:17 porter2 kernel: sdg: Current: sense key: Medium Error
> Jan 21 11:43:17 porter2 kernel:     Add. Sense: Unrecovered read error
> Jan 21 11:43:17 porter2 kernel:
> Jan 21 11:43:17 porter2 kernel: Info fld=0x40000803

This looks like a clue to me - I wonder if sdg is failing, or has failed.
I don't understand the other SMART failures, since in what you've
included, there's no duplicate of the line below
> Jan 21 11:43:17 porter2 kernel: EXT3-fs error (device sdg1):

for the other drives.
<snip>
Do you have a current snapshot? I *think* you're going to have to quiesce
the LVM and swap that drive (MAKE SURE you've got the correct one - use
lshw or smartctl to find the s/n of each, before you pull the drive.

I did a quick google on replacing failed LVM drive, and found
<http://ds9a.nl/lvm-howto/HOWTO/cvs/lvm-howto/output/lvm-howto-6.html>

Hope that helps.

       mark




More information about the redhat-list mailing list