Scott Robertson wrote:
You might have trouble booting the new server because the multipath uuid
seems to get placed in the init script in the initrd. Since the multipath
uuid will likely be different on the new server than it was on the old, you
may have to unpack your initrd, edit the init script (I would just have it
run multipath with no uuid arguments), and package it back up. You might
want to delete the /var/lib/multipath/bindings file in both the initrd and
in the real var filesystem as well.
If you install to boot from SAN with multipath, by default anaconda
will create a multipath.conf which blacklists all and then explicitly
creates mpath devices for any discovered WWN/LUNs during install.
Make sure your /etc/multipath.conf will create multipath devices for
any WWN/LUN.
Then follow this kbase:
How can I boot a server from a replicated SAN LUN using
device-mapper-multipath in Red Hat Enterprise Linux 5?
http://kbase.redhat.com/faq/docs/DOC-17660
You can modify the initrd manually, but remaking the initrd in the new
environment is more likely to work (less chance for mistake).
It sounds like you worked through some previous issues of getting boot
from SAN to work, but for your reference you may find this kbase useful:
How do I install Red Hat Enterprise Linux 5 to boot from SAN using
device-mapper-multipath?
http://kbase.redhat.com/faq/docs/DOC-17644
John Brier
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
