I think I've lost more and more sanity looking through all the posts about my issue on various mailing lists and what, and I'm still at odds why I'm having this issue with lvm. I'm using a Debian proper kernel with automagicly generated initrd. /boot is the only thing not on lvm. I'm close to a concession with starting over with everything on / and just call it done. But, I want some input before I run that direction. A few days ago this machine died, so I decided to move it to a vmware-server system I have until I decide to isolate what hardware issue is causing the no post :)... I have fresh backups in dump format on an nfs server. To start, I used the sarge r5 netinst to setup my partition layout, with everything but /boot on lvm (swap on lvm to). After I got the partitions laid out and disks formatted, I shut down and rebooted to a debian live cd (nothing was installed). While on the debian-live cd, I installed lvm2, and activated the "m" volume group (I hate typing long paths, m it just a haphazard choice). I then mounted the root on /mnt, and all decending partitions where they belong. I restored the dumps from backup, fixed fstab to match the new layout, and chrooted into the restored system. I then purged all the old kernels and grub, installed lvm2, and reinstalled grub, grub-install '(hd0)', installed the kernel, and said yes to creating the menu.lst. It all seems to boot well, until just before it has to pull the root filesystem into action. Just prior to the kernel panic, it says" Unable to find volume group "m". I've attached a screen shot. What should I attempt now? Thanks in advance! Scott.
Attachment:
new vmware setup-005.png
Description: PNG image
