Ok I got some more information from VmWare - it seems that the VmWare is having trouble reading the /boot information from /dev/md0
What I really need to do is just mount /boot somewhere else
I have placed a new hard drive in the server and I intend to mount /boot on it instead of /dev/mo0
Check out Solution #2 on
http://www.waltercedric.co
Here is what I intend to do
1. Back up the /boot files to /tmp
2. unmount /boot,
3. Create a new volume (partition) on harddrive that I just added
4. Format it
5. Mount it as /boot
6. Copy all the /boot files over to there,
7. Make backups of /etc/fstab
8. Change fstab /boot file system - now on /dev/newhd instead of /dev/md0
I shouldn't need to edit /boot/grub/menu.lst or /etc/grub.conf right?
Also when I am backing up and restoring /boot - do I just do a regular cp? rsync? or do I need to do a dd?
Main Topics
Browse All Topics





by: cjl7Posted on 2009-08-04 at 08:21:08ID: 25014708
Hmm,
I think something like this would do the trick (make sure you have a backup!!!!!)
1. remove a disk from the raid
2. create two partitions on that disk (/boot = 100MB, and the rest for LVM)
3. use rsync to copy all data from your live (running) environment
4. modify /etc/grub.conf and try to reboot
You should keep a live-cd in handy if all else fails...
Did I mention that you need to make a backup before you start?! You have been warned...
But I would probably just install a box in vmware and then migrate or move the apps I needed (you could use rsync for that as well)
Good luck!