2009년 02월 21일
SAN Boot Using Multipath RHEL5.1 or RHEL5.2
Release Found: Red Hat Enterprise Linux 5
To resolve this issue, Grub must be reinstalled. To reinstall Grub on the multipath device perform the following procedure.
Note: This method has been validated on Red Hat Enterprise Linux 5.1 and 5.2.
leave only the mpath0 lun masked. Remove the other luns. This is very important, as writing to the other luns must be avoided.
Boot the system in rescue mode.
When rescue mode starts, do not search for any partitions, click on 'skip'
When the shell is spawned do the following:
# mkdir /mnt/sysimage
# mkdir /mnt/sysimage/boot
# multipath -F
# multipath -v0
# multipath -lCheck to see if the mpath0 device is now there, then continue:
# kpartx -a /dev/mapper/mpath0
# lvm vgscan --config 'devices{ filter = [ "a/mapper/", "r/.*/" ] }'
# lvm vgchange -ay --config 'devices{ filter = [ "a/mapper/", "r/.*/" ] }'
# mount -t ext3 /dev/mapper/VolGroup00-LogVol00 /mnt/sysimage/
# mount -t ext3 /dev/mapper/mpath0p1 /mnt/sysimage/boot/
# mount -t proc none /mnt/sysimage/proc
# chroot /mnt/sysimage
# dmsetup mknodes mpath0
# dmsetup mknodes mpath0p1
# dmsetup mknodes mpath0p2In the chrooted environment, verify if /boot/grub/grub.conf is present and corresponds to the correct grub configuration. Also, verify if /boot/grub/devices.map contains the line:
(hd0) /dev/mapper/mpath0If this is the case, run:
# grub-install /dev/mapper/mpath0Reboot the system and verify if it reboots properly.
# by | 2009/02/21 13:38 | 하쿠마의삽질신공 | 트랙백 | 덧글(0)





☞ 내 이글루에 이 글과 관련된 글 쓰기 (트랙백 보내기) [도움말]