Bug 461760
| Summary: | Unable to boot after mpath installation | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Tryggvi Farestveit <tryggvi> |
| Component: | anaconda | Assignee: | Peter Jones <pjones> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.2 | CC: | ddumas, jyundt, kpaden1, orenhe, oren, tryggvi |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-07-01 21:25:05 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Moving to RHEL 5.5 so it doesn't get mistakenly closed by the bot Please retest with a more recent release of RHEL 5. If the problem is still occurring, feel free to reopen the bug. Development Management has reviewed and declined this request. You may appeal this decision by reopening this request. I am running RHEL 5.5. The multipath boot fails for me also. |
Description of problem: When installing RHEL 5.2 (and 5.1) x86-64 using mpath installation option (linux text mpath) and booting from san the node does not boot normally after install. I´ve tried this with both RHEL 5.1 and 5.2. While booting the following error occurs: Checking filesysetms /dev/VolGroup00/LogVol00: clean, 123426/7325696 files, 9917773/7323648 blocks fsck.ext3: no such file or directory while trying to open /dev/mapper/mpath0p1 /dev/mapper/mpath0p1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 fileystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck - b8193 How reproducible: I´ve tried this three times on the same node using 5.1 once and 5.2 twice. I have a IBM blade connected to HP EVA thru brocade switch and I am using qlogic "ISP2422-based". Steps to Reproduce: 1. During booting to the install enter "linux text mpath" 2. Following packages were installed according to anaconda-ks.cfg: @cluster-storage, @admin-tools, @editors, @development-tools, @gnome-software-development, @text-internet, @x-software-development @virtualization, @gnome-desktop, @dialup, @core, @base @java, @base-x, @development-libs, @graphical-internet emacs, imake, mesa-libGLU-devel, kexec-tools, bridge-utils device-mapper-multipath, xorg-x11-utils, xorg-x11-server-Xnest xorg-x11-server-Xvfb, perl-XML-SAX, perl-XML-NamespaceSupport -sysreport 3.Boot into the newly installed system I´ve changed to single path to the SAN disk Workaround: login remount: mount -o rw,remount /dev/root edit /etc/fstab replace: /dev/mapper/mpath0p1 /boot ext3 defaults 1 2 with: LABEL=/boot /boot ext3 defaults 1 2 sync reboot --- This is not clean enough workaround, but it seems that mpath is not loaded when booting so we are unable to talk to /dev/mapper/mpath*. The LVM finds it disks and are using /dev/sdX, by changeing to label the /dev/sdX is used.