1825795 Members
2150 Online
109687 Solutions
New Discussion

Re: bad disk?

 
Paul Benvenuti
Occasional Advisor

bad disk?

Hello all,

I need help identifying a potential disk problem...

lvdisplay shows c2t6d0 all extents current, c2t5d0 shows some stale.

ioscan does not return errors.

dd shows read errors on c2t6d0.

I don't like that the stale extents are on t5, but i/o read errors are on t6.

What should I believe? (and what should I do?)

Many thanks,

Paul
3 REPLIES 3
Tim Nelson
Honored Contributor

Re: bad disk?

c2t6 is the bad disk.

if c2t5 shows as stale then you have some trouble. Basically when the writes occured to c2t6 ( probably the primary ) c2t5 could not sync and now both are toast.

I am not aware of any way to recover from this. Even if you try to extend in another disk for a three-way mirror that new disk will probably report stale as well.

I think the consencious will be "recovery" time.

Sandman!
Honored Contributor

Re: bad disk?

If this VG has mirrored lvols then do a vgsync and check the status of the stale extents again on each of the PVs. Did you do a dd readonly on c2t5d0?
Paul Benvenuti
Occasional Advisor

Re: bad disk?

Output of vgsync...

# vgsync /dev/vg00
Resynchronized logical volume "/dev/vg00/lvol1".
vgsync: Couldn't re-synchronize stale partitions of the logical volume:
Device offline/Powerfailed

vgsync: Couldn't resynchronize logical volume "/dev/vg00/lvol2".
vgsync: Couldn't resynchronize volume group "/dev/vg00".

The dd command I used is...

dd if=/dev/rdsk/c2t6d0 of=/dev/null bs=1024k