1 2 Previous Next 15 Replies Latest reply: Feb 7, 2011 12:16 AM by user1435412 RSS

    Boot from san system update 2.6.18-194.el5 to 2.6.32-100.0.19.el5 fails

    618017
      I installed a Boot from San System on a FC SAN system using device-mapper / mpath.
      My boot disk was #boot=/dev/mapper/mpath0.
      I updated my kernel from 2.6.18-194.el5 to 2.6.32-100.0.19.el5 .
      I rebooted my server after the update.

      The 2.6.32-100.0.19.el5 fails to boot up giving the following error.

      When I use the option linux mpath at the beginning of the install it goes through the install and then when it is doing its first reboot
      it comes up with

      Checking File systems
      fsck.ext3: No such file or Directory while trying to open /dev/mapper/mpath0p1.

      Then drops me into a maintenance shell.


      Is there any work around I can use to ensure that the
      "/dev/mapper/mpath0p1" gets created ?

      Edited by: user615014 on Nov 4, 2010 12:16 AM
        • 1. Re: Boot from san system update 2.6.18-194.el5 to 2.6.32-100.0.19.el5 fails
          Catch-22
          Can you post the output of:

          # modprobe dm-multipath
          # /etc/init.d/multipathd start
          # chkconfig multipathd on

          # multipath -v2
          # multipath -v3
          # multipath -ll
          • 2. Re: Boot from san system update 2.6.18-194.el5 to 2.6.32-100.0.19.el5 fails
            Sergio-Oracle
            How did you install the kernel? Did you also install the device-mapper-multipath that goes with it?

            Sergio
            • 3. Re: Boot from san system update 2.6.18-194.el5 to 2.6.32-100.0.19.el5 fails
              Catch-22
              Perhaps some relevant info can also be found here:

              unbrekable enterprise kernel installation issue

              Can you try the following and report if this works:

              # modprobe dm-multipath

              # kver=`uname -r`
              # mkinitrd --with=dm-multipath* -v -f /boot/initrd-$kver.img $kver
              ...
              Adding module dm-multipath

              # reboot

              Edited by: Joe Shmoe on Nov 5, 2010 5:20 AM
              • 4. Re: Boot from san system update 2.6.18-194.el5 to 2.6.32-100.0.19.el5 fails
                618017
                Here are some clarifications :

                I installed OEL 5.5 with RHCK kernel which is the 2.6.18.194.el5 on a Device-mapper device by using
                "boot mpath".
                The dilemma I have is the system now has a read-only files system on the 2.6.32.100 kernel.

                I can still boot on the device-mapper device on the 2.6.18.194 kernel.
                I plan to do a mkinitrd by booting on the 2.6.18.194 kernel and build a new 2.6.32.100 kernel .
                Let me know if this approach would work .


                Thanks for all your responses , Highly Appreciated.
                • 5. Re: Boot from san system update 2.6.18-194.el5 to 2.6.32-100.0.19.el5 fails
                  Catch-22
                  You can verify the initrd image name:

                  cat /boot/grub/grub.conf

                  then build the initrd using:
                  # mkinitrd --with=dm-multipath -v -f /boot/initrd-2.6.32-100.0.19.el5.img 2.6.32-100.0.19.el5
                  Similar problem:

                  unbrekable enterprise kernel installation issue
                  • 6. Re: Boot from san system update 2.6.18-194.el5 to 2.6.32-100.0.19.el5 fails
                    618017
                    I tried out the

                    mkinitrd --with=dm-multipath -v -f /boot/initrd-2.6.32-100.0.19.el5.img 2.6.32-100.0.19.el5


                    and it still has the same problem as prior to this.

                    Checking File systems
                    fsck.ext3: No such file or Directory while trying to open /dev/mapper/mpath0p1.

                    Then drops me into a maintenance shell.



                    The device-mapper loads but I saw following errors during the mkinitrd :

                    /root
                    [root~]# mkinitrd --with=dm-multipath -v -f /boot/initrd-2.6.32-100.0.19.el5.img 2.6.32-100.0.19.el5
                    Creating initramfs
                    Looking for deps of module ehci-hcd
                    Looking for deps of module ohci-hcd
                    Looking for deps of module uhci-hcd
                    Looking for deps of module ext3
                    Looking for driver for device mapper/mpath0p2
                    Found DM device mapper/mpath0p2
                    Looking for deps of module pci:v00001077d00002432sv00001077sd00000138bc0Csc04i00: scsi_tgt scsi_transport_fc qla2xxx
                    Looking for deps of module scsi_tgt
                    Looking for deps of module scsi_transport_fc: scsi_tgt
                    Looking for deps of module qla2xxx: scsi_tgt scsi_transport_fc
                    Looking for deps of module pci:v000010DEd00000376sv00000000sd00000000bc06sc04i00: shpchp
                    Looking for deps of module shpchp
                    Looking for deps of module pci:v00001077d00002432sv00001077sd00000138bc0Csc04i00: scsi_tgt scsi_transport_fc qla2xxx
                    Looking for deps of module pci:v000010DEd00000376sv00000000sd00000000bc06sc04i00: shpchp
                    Looking for deps of module pci:v00001077d00002432sv00001077sd00000138bc0Csc04i00: scsi_tgt scsi_transport_fc qla2xxx
                    Looking for deps of module pci:v000010DEd00000376sv00000000sd00000000bc06sc04i00: shpchp
                    Looking for deps of module pci:v00001077d00002432sv00001077sd00000138bc0Csc04i00: scsi_tgt scsi_transport_fc qla2xxx
                    Looking for deps of module pci:v000010DEd00000376sv00000000sd00000000bc06sc04i00: shpchp
                    Looking for deps of module mptbase
                    Looking for deps of module mptsas: scsi_transport_sas mptbase mptscsih
                    Looking for deps of module scsi_transport_sas
                    Looking for deps of module mptscsih: mptbase
                    Looking for deps of module sata_nv
                    Looking for deps of module lpfc: scsi_tgt scsi_transport_fc
                    Looking for deps of module ide-disk
                    Looking for deps of module dm-mod
                    Looking for deps of module dm-mirror
                    Looking for deps of module dm-zero
                    Looking for deps of module dm-snapshot
                    Looking for deps of module dm-multipath
                    Looking for deps of module dm-round-robin: dm-multipath
                    Looking for deps of module dm-mem-cache
                    Looking for deps of module dm-region_hash
                    Looking for deps of module dm-message
                    Looking for deps of module dm-raid45
                    Using modules: /lib/modules/2.6.32-100.0.19.el5/kernel/drivers/usb/host/ehci-hcd.ko /lib/modules/2.6.32-100.0.19.el5/kernel/drivers/usb/host/ohci-hcd.ko /lib/modules/2.6.32-100.0.19.el5/kernel/drivers/usb/host/uhci-hcd.ko /lib/modules/2.6.32-100.0.19.el5/kernel/drivers/scsi/scsi_tgt.ko /lib/modules/2.6.32-100.0.19.el5/kernel/drivers/scsi/scsi_transport_fc.ko /lib/modules/2.6.32-100.0.19.el5/kernel/drivers/scsi/qla2xxx/qla2xxx.ko /lib/modules/2.6.32-100.0.19.el5/kernel/drivers/pci/hotplug/shpchp.ko /lib/modules/2.6.32-100.0.19.el5/kernel/drivers/message/fusion/mptbase.ko /lib/modules/2.6.32-100.0.19.el5/kernel/drivers/scsi/scsi_transport_sas.ko /lib/modules/2.6.32-100.0.19.el5/kernel/drivers/message/fusion/mptscsih.ko /lib/modules/2.6.32-100.0.19.el5/kernel/drivers/message/fusion/mptsas.ko /lib/modules/2.6.32-100.0.19.el5/kernel/drivers/ata/sata_nv.ko /lib/modules/2.6.32-100.0.19.el5/kernel/drivers/scsi/lpfc/lpfc.ko /lib/modules/2.6.32-100.0.19.el5/kernel/drivers/md/dm-multipath.ko /lib/modules/2.6.32-100.0.19.el5/kernel/drivers/md/dm-round-robin.ko
                    /sbin/nash -> /tmp/initrd.OY5337/bin/nash
                    /sbin/insmod.static -> /tmp/initrd.OY5337/bin/insmod
                    /etc/udev/rules.d/05-udev-early.rules -> /tmp/initrd.OY5337/etc/udev/rules.d/05-udev-early.rules
                    /sbin/firmware_helper.static -> /tmp/initrd.OY5337/sbin/firmware_helper
                    /sbin/udevd.static -> /tmp/initrd.OY5337/sbin/udevd
                    copy from `/lib/modules/2.6.32-100.0.19.el5/kernel/drivers/usb/host/ehci-hcd.ko' [elf64-x86-64] to `/tmp/initrd.OY5337/lib/ehci-hcd.ko' [elf64-x86-64]
                    copy from `/lib/modules/2.6.32-100.0.19.el5/kernel/drivers/usb/host/ohci-hcd.ko' [elf64-x86-64] to `/tmp/initrd.OY5337/lib/ohci-hcd.ko' [elf64-x86-64]
                    copy from `/lib/modules/2.6.32-100.0.19.el5/kernel/drivers/usb/host/uhci-hcd.ko' [elf64-x86-64] to `/tmp/initrd.OY5337/lib/uhci-hcd.ko' [elf64-x86-64]
                    copy from `/lib/modules/2.6.32-100.0.19.el5/kernel/drivers/scsi/scsi_tgt.ko' [elf64-x86-64] to `/tmp/initrd.OY5337/lib/scsi_tgt.ko' [elf64-x86-64]
                    copy from `/lib/modules/2.6.32-100.0.19.el5/kernel/drivers/scsi/scsi_transport_fc.ko' [elf64-x86-64] to `/tmp/initrd.OY5337/lib/scsi_transport_fc.ko' [elf64-x86-64]
                    copy from `/lib/modules/2.6.32-100.0.19.el5/kernel/drivers/scsi/qla2xxx/qla2xxx.ko' [elf64-x86-64] to `/tmp/initrd.OY5337/lib/qla2xxx.ko' [elf64-x86-64]
                    `/lib/firmware/ql2500_fw.bin' -> `/tmp/initrd.OY5337/lib/firmware/ql2500_fw.bin'
                    `/lib/firmware/ql2400_fw.bin' -> `/tmp/initrd.OY5337/lib/firmware/ql2400_fw.bin'
                    `/lib/firmware/ql2322_fw.bin' -> `/tmp/initrd.OY5337/lib/firmware/ql2322_fw.bin'
                    `/lib/firmware/ql2300_fw.bin' -> `/tmp/initrd.OY5337/lib/firmware/ql2300_fw.bin'
                    `/lib/firmware/ql2200_fw.bin' -> `/tmp/initrd.OY5337/lib/firmware/ql2200_fw.bin'
                    `/lib/firmware/ql2100_fw.bin' -> `/tmp/initrd.OY5337/lib/firmware/ql2100_fw.bin'
                    copy from `/lib/modules/2.6.32-100.0.19.el5/kernel/drivers/pci/hotplug/shpchp.ko' [elf64-x86-64] to `/tmp/initrd.OY5337/lib/shpchp.ko' [elf64-x86-64]
                    copy from `/lib/modules/2.6.32-100.0.19.el5/kernel/drivers/message/fusion/mptbase.ko' [elf64-x86-64] to `/tmp/initrd.OY5337/lib/mptbase.ko' [elf64-x86-64]
                    copy from `/lib/modules/2.6.32-100.0.19.el5/kernel/drivers/scsi/scsi_transport_sas.ko' [elf64-x86-64] to `/tmp/initrd.OY5337/lib/scsi_transport_sas.ko' [elf64-x86-64]
                    copy from `/lib/modules/2.6.32-100.0.19.el5/kernel/drivers/message/fusion/mptscsih.ko' [elf64-x86-64] to `/tmp/initrd.OY5337/lib/mptscsih.ko' [elf64-x86-64]
                    copy from `/lib/modules/2.6.32-100.0.19.el5/kernel/drivers/message/fusion/mptsas.ko' [elf64-x86-64] to `/tmp/initrd.OY5337/lib/mptsas.ko' [elf64-x86-64]
                    copy from `/lib/modules/2.6.32-100.0.19.el5/kernel/drivers/ata/sata_nv.ko' [elf64-x86-64] to `/tmp/initrd.OY5337/lib/sata_nv.ko' [elf64-x86-64]
                    copy from `/lib/modules/2.6.32-100.0.19.el5/kernel/drivers/scsi/lpfc/lpfc.ko' [elf64-x86-64] to `/tmp/initrd.OY5337/lib/lpfc.ko' [elf64-x86-64]
                    copy from `/lib/modules/2.6.32-100.0.19.el5/kernel/drivers/md/dm-multipath.ko' [elf64-x86-64] to `/tmp/initrd.OY5337/lib/dm-multipath.ko' [elf64-x86-64]
                    copy from `/lib/modules/2.6.32-100.0.19.el5/kernel/drivers/md/dm-round-robin.ko' [elf64-x86-64] to `/tmp/initrd.OY5337/lib/dm-round-robin.ko' [elf64-x86-64]
                    /sbin/lvm.static -> /tmp/initrd.OY5337/bin/lvm
                    /sbin/multipath.static -> /tmp/initrd.OY5337/bin/multipath
                    cp: cannot stat `/sbin/multipath.static': No such file or directory
                    /var/lib/multipath/bindings -> /tmp/initrd.OY5337//var/lib/multipath/bindings
                    /sbin/scsi_id -> /tmp/initrd.OY5337/bin/scsi_id
                    /etc/scsi_id.config -> /tmp/initrd.OY5337/etc/scsi_id.config
                    /sbin/mpath_prio_*.static -> /tmp/initrd.OY5337//sbin/mpath_prio_*
                    cp: cannot stat `/sbin/mpath_prio_*.static': No such file or directory
                    /sbin/dmsetup.static -> /tmp/initrd.OY5337/bin/dmsetup
                    /sbin/kpartx.static -> /tmp/initrd.OY5337/bin/kpartx
                    /sbin/dmraid.static -> /tmp/initrd.OY5337/bin/dmraid
                    /sbin/kpartx.static -> /tmp/initrd.OY5337/bin/kpartx
                    Adding module ehci-hcd
                    Adding module ohci-hcd
                    Adding module uhci-hcd
                    Adding module scsi_tgt
                    Adding module scsi_transport_fc
                    Adding module qla2xxx
                    Adding module shpchp
                    Adding module mptbase
                    Adding module scsi_transport_sas
                    Adding module mptscsih
                    Adding module mptsas
                    Adding module sata_nv
                    Adding module lpfc
                    Adding module dm-multipath
                    Adding module dm-round-robin
                    [root ~]#

                    Should I try with a different version of "device-mapper-multipath" say the redhat 55 version as the Oracle linux version does not have static binaries.

                    Any thougts!

                    Edited by: user615014 on Nov 9, 2010 11:54 AM
                    • 7. Re: Boot from san system update 2.6.18-194.el5 to 2.6.32-100.0.19.el5 fails
                      Catch-22
                      I'm using OL 5.5 with Oracle Unbreakable Enterprise Kerne, but I do not get this error.

                      Do you have the components from Oracle 5.5 UEK installed, setup public yum?

                      http://public-yum.oracle.com/repo/OracleLinux/OL5/5/base/x86_64/

                      # yum install device-mapper-multipath*
                      # yum install mkinitrd*
                      # yum install kernel-firmware*
                      • 8. Re: Boot from san system update 2.6.18-194.el5 to 2.6.32-100.0.19.el5 fails
                        user10480875
                        Did you manage to solve this ... I am experiencing the same problem when trying to use a 'multipath' device as a boot device after the 2.6.32 kernel upgrade.
                        Regards,
                        Dennis
                        • 9. Re: Boot from san system update 2.6.18-194.el5 to 2.6.32-100.0.19.el5 fails
                          Herbert van den Bergh-Oracle
                          There are some issues with booting from SAN with the UEK at the moment. I suggest you continue to use the 2.6.18 kernel until this is resolved.
                          • 10. Re: Boot from san system update 2.6.18-194.el5 to 2.6.32-100.0.19.el5 fails
                            user1435412
                            Same problem here: Installed OEL 5.5 with multipathing (FC SAN), "multipath -ll" shows no problems, rebooted without problems. Updated to UEK with "yum install oracle-linux" (that updated my kernel from 2.6.18-194.el5 to 2.6.32-100.0.19.el5) without problems.

                            After first reboot with new kernel i see the maintenance shell and this error

                            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

                            Are there any news to this problem? I'd really like to use the new "Unbreakable Enterprise Kernel" instead of the "old" Kernel from 5.5. How can I do this?
                            • 11. Re: Boot from san system update 2.6.18-194.el5 to 2.6.32-100.0.19.el5 fails
                              Herbert van den Bergh-Oracle
                              We hope to release a fix for this problem with OL5 update 6.
                              • 12. Re: Boot from san system update 2.6.18-194.el5 to 2.6.32-100.0.19.el5 fails
                                user1435412
                                Thank you for the fast response! Can you give us a release date for OL 5.6?

                                And: Can i update from OL 5.6 to UEK too?
                                • 13. Re: Boot from san system update 2.6.18-194.el5 to 2.6.32-100.0.19.el5 fails
                                  Sergio-Oracle
                                  And: Can i update from OL 5.6 to UEK too?
                                  5.6 includes Unbreakabel Enterprise Kernel

                                  Sergio
                                  • 14. Re: Boot from san system update 2.6.18-194.el5 to 2.6.32-100.0.19.el5 fails
                                    Herbert van den Bergh-Oracle
                                    It turns out that the fix for booting UEK from san didn't make it into update 6. Stay tuned for a fix in a later UEK patch.
                                    1 2 Previous Next