My guess would be that the initrd file doesn't contain the proper
modules for the disk controller in the new hardware. I've experienced
similar issues before. I would boot the system with a recovery CD.
Once the system is up, assemble the raid devices (md or lvm) and mount
the file systems to a location like /mnt/disk. Then chroot to /mnt/disk
and make sure important file systems like /boot, /proc, /sys etc are
there. If not run a mount -a. This should mount up the important
partitions from the /etc/fstab of the chrooted system.
Now you should be able to run mkinitrd which will build a new initrd for
the kernels in /boot based on the running module list from the rescue
kernel. I might take a backup of the /boot directory before just in case
(tar -czvf /usr/boot_backup.tgz /boot). If you're lucky the mkinitrd
will install the proper modules in your initrd, you should be able to
exit and reboot into your new system.
Martin Glazer wrote:
Hi,
I'm trying to move 2 drives, setup in a mdraid 1 mirror, from one
machine to another. The hardware is similar but not exactly the same.
I am getting a kernel panic on boot in that it cannot find the ext
partition.
Any suggestions on how to get this operational again (on the new
machine, I don't have access to the old any longer)? Do I have to
recreate the raid array? How?
Thanks
Martin
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
