Mounting an LVM volumn

[dreeser2-store at yahoo.com]

> 
> ... on a Compaq Presario V6017AU with AMD Turion64
> x2. Prior to
> installing 2.6.22.9-91, I have been using
> 2.6.22.7-85 for some time
> without any problems.
> 
> However, after installing 2.6.22.9-91, I could not
> even get to the
> stage of logging in via X windows. I always get a
> freeze / hang during
> startup ... but the freeze is not consistent, it is
> quite random.
> Sometimes, during USB initialisation, sometimes
> after, etc...
> 
> The only thing that I have tried to find out the
> difference is
> comparing the output in /var/log/messages between
> the 2 kernels. Some
> of the differences that i found was:
> 
> 1) The with .7-85 kernel, it was using a "Generic
> RTC driver" while
> with the .9-91, it was using "Real Time Clock Driver
> v1.12ac". ( Are
> they even different drivers or is it the same driver
> which changed
> name from one version to another ? )
> 
> 2) .7-85 kernel logged the message
> 
> kernel: drivers/rtc/hctosys.c: unable to open rtc
> device (rtc0)
> 
> ... while .9-91 did not log this message.
> 
> 3) .7-85 kernel logged the messages:
> 
> kernel: rtc_cmos 00:07: rtc core: registered
> rtc_cmos as rtc0
> kernel: rtc0: alarms up to one year, y3k
> 
> ... which .9-91 did not log.
> 
> Can anyone recommend another way of finding out why
> I would get a
> freeze during startup with .9-91 ?
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Sun, 7 Oct 2007 08:10:05 +0000 (UTC)
> From: Thufir <hawat.thufir at gmail.com>
> Subject: Mounting an LVM volume
> To: fedora-list at redhat.com
> Message-ID: <fea48s$118$1 at sea.gmane.org>
> Content-Type: text/plain; charset=UTF-8
> 
> I want to mount my fedora partition from another
> disc, here's what I have 
> so far:
> 
> 
> 
> 
> arrakis ~ #
> arrakis ~ # fdisk /dev/hda
> 
> The number of cylinders for this disk is set to
> 9729.
> There is nothing wrong with that, but this is larger
> than 1024,
> and could in certain setups cause problems with:
> 1) software that runs at boot time (e.g., old
> versions of LILO)
> 2) booting and partitioning software from other OSs
>   (e.g., DOS FDISK, OS/2 FDISK)
> 
> Command (m for help): p
> 
> Disk /dev/hda: 80.0 GB, 80026361856 bytes
> 255 heads, 63 sectors/track, 9729 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> 
>   Device Boot      Start        End      Blocks  Id 
> System
> /dev/hda1              1        1912    15358108+ 
> 83  Linux
> /dev/hda2            1913        1925      104422+ 
> 83  Linux
> /dev/hda3            1926        9729    62685630 
> 8e  Linux LVM
> 
> Command (m for help):
> Command (m for help): q
> 
> arrakis ~ #
> arrakis ~ #
> arrakis ~ # cat lvm.txt
> 
> #load device module
> modprobe dm-mod
> #change the volumes that exist to active
> vgchange -ay
> #mount the logical partition
> mkdir -p /mnt/VolGroup00/LogVol00
> mount /dev/hda3/VolGroup00/LogVol00
> /mnt/VolGroup00/LogVol00
> arrakis ~ #
> arrakis ~ # ./lvm.txt
> ./lvm.txt: line 5: vgchange: command not found
> mount: special device /dev/hda3/VolGroup00/LogVol00
> does not exist
>       (a path prefix is not a directory)
> 
> arrakis ~ #
> arrakis ~ # date
> Sun Oct  7 00:23:55 PDT 2007
> arrakis ~ #
> arrakis ~ #
> 
> 
> <http://nopaste.info/dc6c513ea0.html>
> 
> 
> 
> 
> I don't understand what's wrong with the mount
> command.  It's pretty much 
> a copy/paste from
> <http://www.fedoraforum.org/forum/archive/index.php/
> t-64964.html>
> 
> 
> 
> Thanks,
> 
> Thufir
> 
=== message truncated ===
 I think I pulled the trigger too soon in my previous
message. I should have asked what system you are
booting in when you want to mount the LVM volumns. On
my system I boot into fedora f7 from an sda 3
partition, or from the live CD. During the boot
something (I bekieve it is udev) sees the LVM
partitions and adds a /dev/VolGroup00 directory in
/dev with sub files of LogVol00 and LogVol001.
 I don't need to make them active, in fact to mount
them I suspect you don't want them active. Then the
mount command I sent before should work, after you
mkdir to mount on.