boot incomplete. Due to /usr on lvm2?
Hi.
I'd be very grateful of some help here. Done lots of googling etc...
My old HD is failing (IBM "DeathStar") so I've bought a new one. It's SATA.
I wanted to use lvm2 to make resizing easier. I read about it, and found
that having / on lvm2 made it harder to get it to boot. I found this post on
this list:
http://lists.debian.org/debian-user/2005/04/msg00245.html
which recommended using lvm2 for only /usr /tmp /home /opt /var. I thought
that's be great-they're the ones that vary in size, and it'll boot. However
it won't-it doesn't launch X, but does give a text log-in. I suspect it's
because /usr is on lvm and not available as the machine boots. So, do I need
to use the lvm-mkinitrd script I wanted to avoid?-Even though / itself isn't
on lvm. What possible pitfalls would there be with that? Would you recommend
not having /usr on lvm? If so, I may abandon lvm altogether, getting fed-up
with it. I don't think the problem is with the drive being SATA, the PC gets
to the console booting from it. I'm using testing, 2.6.11-1-k7 kernel and
wanted to try out xfs, although I found some posts about file-system
corruption with it and 2.6 series kernels, so may revert to ext3. I have
/boot on a seperate partition. /etc/fstab has entries for the lvm lv's. I'm
not sure how to get more boot diagnostics for this problem, I'm using RIP
bootable recovery CD to work on the lvm partitions, and knoppix to send
this...
I'll post more info if you need it.
Arthur.
Reply to: