Problem
Both disks in the rootdg marked as failing. Could not mirror the rootvol to another internal disk due to bad blocks. The 'fsck' of the rootvol didn't work either.
Error
VxVM ERROR V-5-2-440 Unexpected error:
VxVM vxckdiskrm ERROR V-5-1-10127 disassociating disk-media rootdisk: Record is associated.
And later after removing failed disks, and after flasharchive to configure new devices - when attempted to encapsulate::
Enter disk name for c1t2d0 [ ,q,?] (default: rootdg01) rootdisk
A new disk group rootdg will be created and the disk device c1t2d0 will be encapsulated and added to the disk group with the disk name rootdisk.
Enter desired private region length [ ,q,?] (default: 2048)
VxVM ERROR V-5-2-338 The encapsulation operation failed with the following error:
VxVM vxencap ERROR V-5-2-213 It is not possible to encapsulate c1t3d0, for the following reason:
<VxVM vxslicer ERROR V-5-1-565 Disk contains overlapping partitions.>
VxVM vxckdiskrm ERROR V-5-1-10127 disassociating disk-media rootdisk: Record is associated.
And later after removing failed disks, and after flasharchive to configure new devices - when attempted to encapsulate::
Enter disk name for c1t2d0 [
A new disk group rootdg will be created and the disk device c1t2d0 will be encapsulated and added to the disk group with the disk name rootdisk.
Enter desired private region length [
VxVM ERROR V-5-2-338 The encapsulation operation failed with the following error:
VxVM vxencap ERROR V-5-2-213 It is not possible to encapsulate c1t3d0, for the following reason:
<VxVM vxslicer ERROR V-5-1-565 Disk contains overlapping partitions.>
Cause
Both the rootdisk and rootmirror failing and needed to be replaced.
Solution
After unencapsulating the rootdg, the customer booted up via cd, used flasharchive to configure the one of the unused internal disks.
Then he ran into issues with the encapsulation, where we found the need to clean the device tree: Had him run 'vxdisk -e list' command.. it shows that the native device names on the right - aren't matching up with what's on the left side! This confirmed the eed to do a device tree cleanup -- for some reason the reconfiguration reboot didn't clean this up..
---Did the device tree cleanup:
# mv /etc/vx/array.info /etc/vx/array.info.old
# mv /etc/vx/disk.info /etc/vx/disk.info.old
# rm /dev/vx/dmp/*
# rm /dev/vx/rdmp/*
# rm /dev/dsk/*
# rm /dev/rdsk/*
# devfsadm -Cv
# vxconfigd -k vxdctl enable
-The disk access names were matching the OS native names - checked with 'vxdisk -e list'
-Encapsulation was successful .
After this was done the mirroring of the rootdisk to the new rootmirror device was successful.
Then he ran into issues with the encapsulation, where we found the need to clean the device tree: Had him run 'vxdisk -e list' command.. it shows that the native device names on the right - aren't matching up with what's on the left side! This confirmed the eed to do a device tree cleanup -- for some reason the reconfiguration reboot didn't clean this up..
---Did the device tree cleanup:
# mv /etc/vx/array.info /etc/vx/array.info.old
# mv /etc/vx/disk.info /etc/vx/disk.info.old
# rm /dev/vx/dmp/*
# rm /dev/vx/rdmp/*
# rm /dev/dsk/*
# rm /dev/rdsk/*
# devfsadm -Cv
# vxconfigd -k vxdctl enable
-The disk access names were matching the OS native names - checked with 'vxdisk -e list'
-Encapsulation was successful .
After this was done the mirroring of the rootdisk to the new rootmirror device was successful.
No comments:
Post a Comment