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

      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
                          1337 @Dashrender
                          last edited by 1337

                          @Dashrender said in RHEL 4 not seeing ext3 label:

                          @JaredBusch said in RHEL 4 not seeing ext3 label:

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

                          You could potentially try to install centos4, or rhel4 is even better, so you get to a bootable system.
                          Then just copy the files from the backup over your installation.

                          It is an option I have thought about. I'll be on site this morning, and I will be shutting down the host and booting to a Fedora Live to run dd in an effort to get a solid disk image.

                          I tried their built in process on Tuesday and it failed with sector/block read errors. A little digging through the files on the recovery ISO showed that all they were doing was using dd, so I am hoping to use dd with more intelligent options to continue on and such.

                          What's repair solution for bad blocks in a setup like this? If dd can't read because of bad blocks, I'm hoping 'nix has some tool to fix/recover/replace these bad blocks, assuming the data's recoverable on the hardware, otherwise it's a restore time, right?

                          ddrescue is the best tool to use to copy from a drive that has errors. It's actually made for data recovery and is much smarter than dd. It will probe the drive and the data that is missing in different ways and several times so it can usually retrieve more data.

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

                            @JaredBusch said in RHEL 4 not seeing ext3 label:

                            @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.

                            Yeah, it's great!

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

                              Booted straight to the CentOS 4 ISO, went into linux rescue, updated the initrd img and bam. working system from the current (as of 4 days ago) manual disk images I made.
                              88b47d5c-c3dc-4635-ab9c-1ec25e69ab95-image.png

                              Next project to re-learn how they restore data files. Have not done that in almost 10 years. Having no virtual infrastructure to play with, prior to this, made that harder.

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