kernel panic after restoring...please help

Help
dump_geek
2006-08-22
2013-05-20
  • dump_geek

    dump_geek - 2006-08-22

    Hello all,

    I have been working on unix & linux. There was no problem at all when i used vdump and restore in unix.

    Now with Linux redhat Ent 4.0 W.S version, it comes up with freaking errors....like KERNEL PANIC....

    The procedure I followed is
    dump version 0.4b3 hope this is the latest on i686 processor.

    dump procedure::-
    dump -0f /dev/nst0 /
    dump -0f /dev/nst0 /boot

    on two different tapes.
    checked the contents using  restore -i

    everything looked fine

    RESTORE PROCEDURE:-

    Booted from CD, and went through installation process until automatic partition and switched off the computer after formating.(i believe this process should work instead of going for the whole installation process)

    restarted with bootable CD in Linux rescue mode,
    mounted boot and root partitions /dev/sda1 and /dev/sda2 on /mnt/linux/boot and /mnt/linux/root Respectively as ext3.
    using command
    mount -t ext3 /dev/sda1 /mnt/linux/boot
    mount -t ext3 /dev/sda2 /mnt/linux/root

    and then restored using the command

    restore rf /dev/nst0 .

    All went fine so far

    then rebooted machine...
    machine boots until grub, and then starts loading all other hardware
    but suddenly comes up with errors like these....

    .............................................
    Reading all physical volumes ……

    Cdrom: open failed

    Couldn’t find device with uuid ‘gejMIV-Mvvi-Q1Wq-mZ27------……’

    Couldn’t find all physical columes for volume group VolGroup00

    Volume group “VolGroup00” not found

    ERROR: /bin/lvm exited abnormally!

    Creating root device
    Mounting root filesystem
    Mount: error 6 mounting ext3
    Mount: error 2 mounting none
    Switching to new root
    Switchroot: mount failed :22
    Umount /initrd/dev failed :2

    Kernel panic –not sysncing : Attempted to kill init

    .................................

    I can't understand what's the problem..UUID..?
    do i need to change uuid...or initrd file

    Please help me find the solution.

    Thanks
    awaiting reply...

    dump_geek

     
    • Stelian Pop

      Stelian Pop - 2006-08-23

      The problem is that you have recreated the LVM partitions, and the UUID of the new partitions doesn't correspond to the UUID contained in the restored files.

      Unfortunately you'll have to dig yourself for information, I'm not sure where exactly this information is stored. Probably in the initrd.

      Try booting in rescue mode, mount your root partition, chroot into it, then remove /boot/initrd-xxxxx, and recreate it using mkinird. Maybe this will be sufficient.

      You could also ask for help on some LVM forum/mailing list.

      Stelian.

       
    • dump_geek

      dump_geek - 2006-08-29

      Thankyou very much stelian, for your advice, i tried it but got struck in making a initrd file...
      anyway, can u please tell me  if the steps i have taken to restore a system are correct...

      I normally booted from CD and made automatic partitions and then formatted them to ext3 filesystems. stopped cd, and restarted in linux rescue mode.

      I wondered, why is it very simple in unix, where we just use vdump and restore ...and not in linux...
      i was able to use dump, but am not sure how to follow with restore in linux, if i wanted to do full system restore.

      I was looking for any live example, or any hints to follow for restore..

      thanks in advance,

       
      • Stelian Pop

        Stelian Pop - 2006-08-30

        Linux 'restore' is a straight forward port of the BSD restore utility, so I don't get what you mean by  "it very simple in unix, where we just use vdump and restore ...and not in linux..."

        If you want us to be able to help you, we need a bit more information than "got struck in making a initrd file.". Post full logs in order to show what goes wrong.

        I think you have restored all your system correctly, you only have to recreate some files on your restored system in order to take into account the change in partitionning.

        Post the contents of (the restored) /boot/grub/menu.lst and also /etc/fstab.

        Try this: boot in rescue mode on the CD, then:
            mkdir /tmp/root
            mount -t ext3 /dev/sda2 /tmp/root
            mount -t ext3 /dev/sda1 /tmp/root/boot
            chroot /tmp/root
            mkinitrd -f /boot/initrd-2.6.a-b.c.img 2.6.a-b.c
        (replace 2.6.a-b.c with the real version of your kernel, look into /boot to find it out)
            sync
            exit
            reboot

         
    • dump_geek

      dump_geek - 2006-09-13

      Hi,
      Sorry i was not around.

      thankyou for ur reply, as per your advice i did made an initrd file, everything seemed to work fine.
      when i rebooted, this time it came with same errors as i listed in my earlier post, but with a different uuid.
      I am thinking it's more concerned with lvm tools,like pvcreate and lvcreate stuff.
      i am looking at the lvm stuff, if it might help.

      so after restore the etc/fstab file looks like
      -----------------
      /dev/VolGroup00/LogVol00  /     ext3 defaults 1 1
      LABEL=/boot               /boot ext3 defaults 1 2
      none                     /dev/pts devpts   gid=5,mode=620 00
      none                     /dev/shm  tmpfs defaults 0 0
      none                     /proc  proc defaults 0 0
      none                    /sys   sysfs defaults 0 0
      /dev/VolGroup00/LogVol01 swap   swap defaults 0 0
      /dev/hda                /media/cdrom auto
      /dev/fd0                /media/floppy auto
      ----------------------------
      and the /boot/grub/menu.lst shows

      default=0
      timeout=5
      splashimage=(hd0,0)/grub/splash.xpm.gz
      hiddenmenu
      title Red HAt Enterprise Linux WS(2.6.9-22.ELsmp)
            root (hd0,0)
            kernel /vmlinuz-2.6.9-22.ELsmp ro root=/dev/VolGroup00/LogVol00 rhgb quiet
            initrd /initrd-2.6.9-22ELsmp.img
      title Red HAt Enterprise Linux WS(2.6.9-22.EL)
            root (hd0,0)
            kernel /vmlinuz-2.6.9-22.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet
            initrd /initrd-2.6.9-22EL.img

      --------------------

      on pvdisplay it's comming up with
      PV name unknown device
      VG name VolGroup01
      and
      PV name /dev/sdb1
      VG name VolGroup01

      i am anyway not using /dev/sdb1 at all.

      my boot partition /boot i restored on /dev/sda1
      and root partition is restored on /dev/sda2

      i think thers is a slight problem in volgroup01 in vg name and in comparision with grub.conf, or etc/fstab file

      i might have to play around with these lvm s

      please advice
      thankx in advance

       
    • Stelian Pop

      Stelian Pop - 2006-09-15

      Something is wrong with your LVM volumes. Try some variation of pvscan / vgscan, etc.

      This has really little to do with dump, I really think you should ask your questions directly to some LVM experts. For example, the mailing list at https://www.redhat.com/mailman/listinfo/linux-lvm is probably the best resource for that kind of problems.

      Stelian.

       

Log in to post a comment.