So the disks became incorrectly labelled is that what you're saying? I though "mpath" isn't guaranteed to persist and that /dev/mappper paths should be used anyway? -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of madunix Sent: Saturday, 19 June 2010 6:32 a.m. To: General Red Hat Linux discussion list Subject: mpath I booted lately several RHEL5.1 Bladecenter servers with multipath, the multipath has been implemented typing mpath during the booting installation from CD. For our disaster recovery, we found that the linux rhel5 system wont boot up from replicated SAN LUN using device mapper multipath ... its reporting kernel panic and cant e2fsck files system to continue ctrl D and type root password ...etc in order to boot the system we remounted in read/write mode and edit /etc/fstab then removed the mpath dev from boot disk, the system was able to boot madunix -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list ========================================================== For more information on the Television New Zealand Group, visit us online at tvnz.co.nz ========================================================== CAUTION: This e-mail and any attachment(s) contain information that is intended to be read only by the named recipient(s). This information is not to be used or stored by any other person and/or organisation. -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
