Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
everything was working so well i dumped hda2, then tried to test it using restore.
the dump command used was: dump -0f /path/to/hda2.dump /dev/hda2 .
then, after doing: mkfs -t ext3 /dev/hda2,
the restore command used was: restore -rf /path/to/hda2.dump
upon boot, it complains as follows:
Creating root device
mkrootdev: label / not found
Mounting root filesystem
mount: error 2 mounting ext3
pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
umount /initrd/proc failed: 2
Freeing unused kernel memory: 128k freed
Kernel panic: No init found. Try passing init= option to kernel.
the grub.conf section i typically boot to is:
title Red Hat Linux (2.4.22-openmosix-2)
kernel /vmlinuz-2.4.22-openmosix-2 ro root=LABEL=/
but grub.conf sits on hda1, which was not modified recently.
fdisk -l looks good for hd1 and hda2: both id 83. fsck says hda2 is clean.
cd'ing around hda2 looks good, i don't notice anything different with the filesystem.
anybody know what i'm missing? a clean setup is hiding in hda2 somewhere...
agreed, i used e2label for partition labelling. including the labelling step, dump appears to be superior to dd for partition moving and system backup since partitions do not need to be held at constant size or require resizing after restoration to dissimilar partition sizes.