Find the answer to your Linux question:
Results 1 to 4 of 4
Machines are similar hardware, moving from newer box (compA) to slightly older (compB). Both machines are single SATA drives. Pulled cover from compA, removed drive, replaced into compB. When booting ...
  1. #1
    Just Joined!
    Join Date
    Jun 2009
    Posts
    2

    Moving hard drive with RHEL 4 from one machine to another.

    Machines are similar hardware, moving from newer box (compA) to slightly older (compB). Both machines are single SATA drives. Pulled cover from compA, removed drive, replaced into compB.

    When booting I get this error:
    Booting 'Red Hat Enterprise Linux ES (2.6.9-67.ELsmp)'

    root(hd0,0)
    Filesystem type is ext2fs, partition type 0x83
    kernel /vmlinuz-2.6.9-67.ELsmp ro root=/dev/VolGroup00/LogVol00 rhgb quiet
    initrd /initrd-2.6.9-67.ELsmp.img

    Uncompressing Linux… Ok, booting the kernel.
    Red Hat nash version 4.2.1.13 starting
    Reading all physical volumes. This may take a while…
    No volume groups found
    Volume group “VolGroup00” not found
    ERROR: /bin/lvm exited abnormally! (pid 460)
    Mount: error 6 mounting ext3
    Mount: error 2 mounting none
    Switchroot: mount failed: 22
    Umount /initrd/dev failed: 2
    Kernel panic – not syncing: Attempted to kill init!

    -----end-----


    Boot to rescue with cd, mounts ok

    #fdisk -l

    Disk /dev/sda: 80.0 GB,

    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 13 104391 83 Linux
    /dev/sda2 14 9729 78043770 8e Linux LVM

    Any help would be appreciated.

  2. #2
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
    Posts
    8,974
    Make sure their bios settings are the same. Also, what other hardware differences are there, such as disc controller, amount of memory, CPU type, video controller? Anyway, the system is not finding the LVM volume group that should be on the 2nd partition (according to the partition table you posted). Either the controller is mapping the drive incorrectly, or something happened to it. That's why I mention the BIOS settings. If you have the sata -> ata translation turned on in one machine, but not the other, then the drive geometries are likely misinterpreted.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  3. #3
    Just Joined!
    Join Date
    Jun 2009
    Posts
    2
    Thanks for the tip.

    The hardware move was from a Dell Optiplex 755 to a Dell Optiplex 745, I would post the differences, but I don't think they are too significant and I didn't get that far.

    After you mentioned the BIOS settings I turned on Legacy support and it booted fine. Auto ran through Kudzu for new hardware and seems to be working fine now.

    Thanks again.

  4. #4
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
    Posts
    8,974
    Quote Originally Posted by thephilly View Post
    Thanks for the tip.

    The hardware move was from a Dell Optiplex 755 to a Dell Optiplex 745, I would post the differences, but I don't think they are too significant and I didn't get that far.

    After you mentioned the BIOS settings I turned on Legacy support and it booted fine. Auto ran through Kudzu for new hardware and seems to be working fine now.

    Thanks again.
    Glad that sorted it out. It's the silly little stuff like that which drive us nuts!
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
...