ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Solved RHEL 4 not seeing ext3 label

    IT Discussion
    rhel 4 rhel grub kernel panic ext3 root label
    5
    33
    2.5k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • JaredBuschJ
      JaredBusch
      last edited by

      Process completed with no errors yesterday.

      293AE05D-628B-4F33-AC36-196325845B0E.jpeg

      Now to merge it all back together and try to restore it to a VM.

      DashrenderD 1 Reply Last reply Reply Quote 0
      • 1
        1337
        last edited by

        It feels like I'm watching reality TV.

        JaredBuschJ 1 Reply Last reply Reply Quote 0
        • DashrenderD
          Dashrender @JaredBusch
          last edited by

          @JaredBusch said in RHEL 4 not seeing ext3 label:

          Process completed with no errors yesterday.

          Now to merge it all back together and try to restore it to a VM.

          Do you need to merge it? just wondering?

          JaredBuschJ 1 Reply Last reply Reply Quote 0
          • JaredBuschJ
            JaredBusch @Dashrender
            last edited by

            @Dashrender said in RHEL 4 not seeing ext3 label:

            Do you need to merge it? just wondering?

            How else does it become a single disk image file to import into my hypervisor?

            1 Reply Last reply Reply Quote 0
            • JaredBuschJ
              JaredBusch
              last edited by

              So back home, and I have the files backed up in like 4 places.

              I recombined the .img files and then unzipped them.

              Getting ready to setup a new VM on Proxmox, but I poked around dmesg on the running system first.

              SCSI subsystem initialized
              Fusion MPT base driver 3.02.73rh
              Copyright (c) 1999-2006 LSI Logic Corporation
              Fusion MPT SPI Host driver 3.02.73rh
              ACPI: PCI Interrupt 0000:02:05.0[A] -> GSI 34 (level, low) -> IRQ 201
              mptbase: Initiating ioc0 bringup
              ioc0: 53C1030: Capabilities={Initiator,Target}
              scsi0 : ioc0: LSI53C1030, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=201
              ACPI: PCI Interrupt 0000:02:05.1[B] -> GSI 33 (level, low) -> IRQ 209
              mptbase: Initiating ioc1 bringup
              ioc1: 53C1030: Capabilities={Initiator,Target}
              scsi1 : ioc1: LSI53C1030, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=209
              Fusion MPT SAS Host driver 3.02.73rh
              megaraid cmm: 2.20.2.6rh (Release Date: Tue Jan 16 12:35:06 PST 2007)
              megaraid: 2.20.4.6-rh2 (Release Date: Wed Jun 28 12:27:22 EST 2006)
              megaraid: probe new device 0x1000:0x1960:0x1028:0x0518: bus 9:slot 4:func 0
              ACPI: PCI Interrupt 0000:09:04.0[A] -> GSI 106 (level, low) -> IRQ 233
              megaraid: fw version:[351S] bios version:[1.10]
              scsi2 : LSI Logic MegaRAID driver
              scsi[2]: scanning scsi channel 0 [Phy 0] for non-raid devices
                Vendor: PE/PV     Model: 1x6 SCSI BP       Rev: 1.0 
                Type:   Processor                          ANSI SCSI revision: 02
              scsi[2]: scanning scsi channel 1 [Phy 1] for non-raid devices
              scsi[2]: scanning scsi channel 2 [virtual] for logical drives
                Vendor: MegaRAID  Model: LD 0 RAID1   69G  Rev: 351S
                Type:   Direct-Access                      ANSI SCSI revision: 02
              SCSI device sda: 143114240 512-byte hdwr sectors (73274 MB)
              sda: asking for cache data failed
              sda: assuming drive cache: write through
              SCSI device sda: 143114240 512-byte hdwr sectors (73274 MB)
              sda: asking for cache data failed
              sda: assuming drive cache: write through
               sda: sda1 sda2 sda3
              Attached scsi disk sda at scsi2, channel 2, id 0, lun 0
                Vendor: MegaRAID  Model: LD 1 RAID5  139G  Rev: 351S
                Type:   Direct-Access                      ANSI SCSI revision: 02
              SCSI device sdb: 286228480 512-byte hdwr sectors (146549 MB)
              sdb: asking for cache data failed
              sdb: assuming drive cache: write through
              SCSI device sdb: 286228480 512-byte hdwr sectors (146549 MB)
              sdb: asking for cache data failed
              sdb: assuming drive cache: write through
               sdb: sdb1
              Attached scsi disk sdb at scsi2, channel 2, id 1, lun 0
              

              I think this tells me that I should try the megaRAID controller this time. I swaer I already tried. But I have slept since then. Tuesday and Wednesday were crazy stressed getting data..
              c4c6ce3d-8f9c-4ab3-80c3-6e2e76837feb-image.png

              1 Reply Last reply Reply Quote 0
              • JaredBuschJ
                JaredBusch
                last edited by JaredBusch

                Well damnit. It does not see the second disk..
                869f9c6c-d31d-4411-980d-10b8ebdfe3bf-image.png

                Looks like an error during boot

                8b5c082d-b43e-4cf9-92bd-ef3f42ffc7cb-image.png

                1 Reply Last reply Reply Quote 0
                • DashrenderD
                  Dashrender
                  last edited by

                  can you boot from a live image and see both disks?

                  I did a d2vm of a windows 2003 server and I had to run checkdisk like 10 times before it finally worked.. don't ask my why I tried it so many times... I think there is a thread around here somewhere about it.

                  JaredBuschJ 1 Reply Last reply Reply Quote 0
                  • JaredBuschJ
                    JaredBusch @Dashrender
                    last edited by JaredBusch

                    @Dashrender said in RHEL 4 not seeing ext3 label:

                    can you boot from a live image and see both disks?

                    I did a d2vm of a windows 2003 server and I had to run checkdisk like 10 times before it finally worked.. don't ask my why I tried it so many times... I think there is a thread around here somewhere about it.

                    The restored drives are fine. Can be mounted as previously noted and the label reports correctly.

                    The issue seems to be that the kernel, as built, is not loading the drives correctly. Potentially because the VM is using a SCSI driver method the old ass kernel does not understand.

                    1 Reply Last reply Reply Quote 0
                    • jt1001001J
                      jt1001001
                      last edited by

                      Didn't Dell "back in the day" use or require their own megaraid driver's on Linux?? Can't remember as its been ages since I delt with a 28XX series with a PERC raid card.

                      1 Reply Last reply Reply Quote 0
                      • JaredBuschJ
                        JaredBusch
                        last edited by

                        Using VirtIO SCSI (the default selection) the drives are not even seen by tthe recovery boot image. The onyl thing shown is the USB drive holding the data to restore.
                        e6665609-7ac4-4968-9f75-8f817a852a28-image.png

                        1 Reply Last reply Reply Quote 0
                        • JaredBuschJ
                          JaredBusch
                          last edited by

                          Using VMWare PVSCSI the system won't even boot.
                          e7671a64-0269-4984-ac2e-1847502f3d15-image.png

                          1 Reply Last reply Reply Quote 0
                          • JaredBuschJ
                            JaredBusch
                            last edited by

                            VirtIO SCSI Single is the same as VirtIO SCSI
                            27608918-ccaa-4455-b01d-819d57c3ea3e-image.png

                            1 Reply Last reply Reply Quote 0
                            • JaredBuschJ
                              JaredBusch
                              last edited by

                              The LSI 53C895A shows the drives, so attempting a restore..
                              Note: Even though it says "Default" this is not the default choice when you go through the wizard, VirtIO SCSI is the default selection.
                              8cfde816-02ae-444e-b4d4-a3dc8cd62f85-image.png

                              JaredBuschJ 1 Reply Last reply Reply Quote 0
                              • JaredBuschJ
                                JaredBusch
                                last edited by

                                Here is a video of the physical server booting. You can see the drives coming online at the 1:56 mark

                                Youtube Video

                                1 Reply Last reply Reply Quote 0
                                • JaredBuschJ
                                  JaredBusch @JaredBusch
                                  last edited by

                                  @JaredBusch said in RHEL 4 not seeing ext3 label:

                                  The LSI 53C895A shows the drives, so attempting a restore..
                                  Note: Even though it says "Default" this is not the default choice when you go through the wizard, VirtIO SCSI is the default selection.
                                  8cfde816-02ae-444e-b4d4-a3dc8cd62f85-image.png

                                  So the restore completed, but no boot drive detected I guess.
                                  ac6edfb9-b567-45aa-aab9-885606a5c793-image.png

                                  JaredBuschJ 1 Reply Last reply Reply Quote 0
                                  • JaredBuschJ
                                    JaredBusch @JaredBusch
                                    last edited by

                                    @JaredBusch or because I am getting cross eyed and did not notice that scsi0 was not selected in the boot order....
                                    b46ef043-f923-400f-ac7f-8e04f5e68e04-image.png

                                    Fixed that.. Label not found.
                                    cad1f9e7-017f-4836-8395-e32c6aa064ed-image.png

                                    1 Reply Last reply Reply Quote 0
                                    • JaredBuschJ
                                      JaredBusch
                                      last edited by

                                      CentOS 4.8 booting to rescue mode
                                      02a7dd4e-87f4-4b2d-97d7-6088e8ef8d00-image.png

                                      The labels show as being correct.
                                      4f822755-4fbd-45ae-a4b3-c9d82b97b110-image.png

                                      1 Reply Last reply Reply Quote 0
                                      • JaredBuschJ
                                        JaredBusch
                                        last edited by JaredBusch

                                        This guy had a similar issue. he was moving from VMWare (old) instead of Physical to KVM.
                                        https://serverfault.com/questions/1040265/cannot-migrate-ancient-vm

                                        But his non-answer does not help.

                                        Also, it appears my scsi_mod is loading first. so not the same issue he had.
                                        35bda802-21aa-4302-a3fc-8864822953d2-image.png

                                        1 Reply Last reply Reply Quote 0
                                        • JaredBuschJ
                                          JaredBusch
                                          last edited by JaredBusch

                                          and solved it. finally..

                                          one of the reboots into the CentOS 4 disc was slow or something and I caught it pop this screen (took me 6 reboots to get screenshot).
                                          This is the Kudzu hardware detection thing.
                                          d6f21140-d34b-4a8b-9936-516e8f93a01b-image.png

                                          The VM is setup using the LSI 53C895A SCSI Controller.
                                          Booted into rescue mode with the CentOS 4 CD.

                                          chroot /mnt/sysimage
                                          vi /etc/modprobe.conf
                                          # make this the only scsi_hostapadter
                                          alias scsi_hostadapter sym53c8xx
                                          # exit vi !!! omfg how!!!
                                          cd /boot
                                          mkinitrd -v -f initrd-2.6.9-55.EL.img 2.6.9-55.EL
                                          exit
                                          exit
                                          

                                          System automatically reboots to come out of rescue mode.
                                          Make sure you remove the ISO at this point.
                                          Then boom..
                                          0a0f66d6-4a95-43f3-bd9a-adcd8ef6514d-image.png

                                          a4fb8019-806b-4f51-8e2c-4ba0f195ed36-image.png

                                          1 Reply Last reply Reply Quote 1
                                          • JaredBuschJ
                                            JaredBusch @1337
                                            last edited by JaredBusch

                                            @Pete-S said in RHEL 4 not seeing ext3 label:

                                            It feels like I'm watching reality TV.

                                            Restoring the above dd created images now.
                                            2740401d-9c2b-401b-949e-6a812c381ef3-image.png

                                            I like to dump live as I work on weird things like this, because it will almost certainly help someone else at some point.

                                            1 1 Reply Last reply Reply Quote 2
                                            • 1
                                            • 2
                                            • 1 / 2
                                            • First post
                                              Last post