I upgrade using YUM my CentOS 4 system the other night. I was noticing that X wasn't coming up because of a gdk_thread issue (actually, the window manager wasn't starting. I cold get X to start from the command line). Surprised that it took 587MB of downloads, since I was current as of September 29th. When rebooting, I was forced to the login prompt, because my LVM group with my home directory couldn't be mounted. I'm not very familiar with LVM, I had only used it to make one consolidated directory for my 100 and 160GB hard drives. Though lvmdisplay could show the volume group, fsck and mount didn't like it. Oh, and the upgrade didn't fix the thread problem. Anyone have an idea whether it was just me having the LVM problem? I'm currently reinstalling CentOS4 (pre update 1) from CD. At least when running diskdruid, I could mount the LVM group. So, after my install, assuming it is still visible when booting from hard drive, I'll backup those drives before running YUM again. I'f the window manager doesn't start up again, I'll reformat on my next install.
>>> sender: "Kevin Krieser" date: "Sun, Oct 16, 2005 at 02:51:20PM -0500" <<<EOQ > [..] > Anyone have an idea whether it was just me having the LVM problem?I just upgraded to 4.2 and everything looks fine. I have all my partitions on LVM, except for /boot: [root at dell ~]# cat /etc/redhat-release && mount -t ext3 CentOS release 4.2 (Final) /dev/mapper/storage-root on / type ext3 (rw) /dev/md0 on /boot type ext3 (rw) /dev/mapper/storage-home on /home type ext3 (rw) /dev/mapper/storage-usr on /usr type ext3 (rw) /dev/mapper/storage-var on /var type ext3 (rw,mand) /dev/mapper/storage-data on /var/data type ext3 (rw) I have LVM on top of RAID1, which is made of two Fujitsu SCSI disk of 18GB. Have a nice day all, Alex
> When rebooting, I was forced to the login prompt, because my LVM group > with my home directory couldn't be mounted. > > I'm not very familiar with LVM, I had only used it to make one > consolidated directory for my 100 and 160GB hard drives.I have the same issue. I've got a volume group spread across 2 disks and when I try to activate that volgroup I get the following: <snip> [root at hetfield mapper]# vgchange -ay VolGroup02 device-mapper ioctl cmd 9 failed: Invalid argument Couldn't load device 'VolGroup02-DVD'. 1 logical volume(s) in volume group "VolGroup02" now active <snip> and the relevant portion of the /var/log/messages has: <snip> Oct 17 08:45:07 hetfield kernel: device-mapper: dm-linear: Device lookup failed Oct 17 08:45:07 hetfield kernel: device-mapper: error adding target to table <snip> My other two volgroups are working fine. It's just this third one that has problems. I did quite a bit of googling yesterday, but I didn't come up with much although I have to confess that I know jack about the device mapper... Regards, Pat