Fresh LVM partitions don't work from kickstart
Carlos Villegas
villegas at math.gatech.edu
Fri Mar 19 21:38:21 UTC 2004
I kickstarted a FC2 test1 system with some lvm partitions
specified in the ks.cfg file, however upon the first boot the
system goes into single user mode, because it is unable to
recognize the LVM partitions. The problem is that fsck fails
(No such file or directory while trying to open
/dev/largespace/tmp) and so on for every other LVM partition.
Note that the partitions are NOT from a previous install, I have
seen some reports on that, but not on a freshly created LVM
partitioning. The relevant portions of the ks.cfg file are:
clearpart --all --initlabel
part pv.01 --fstype ext3 --size 10241 --grow
volgroup largespace pv.01
logvol /tmp --vgname largespace --size 2048 --name tmp
# some more logvol entries omitted.
I haven't filed a bug report, since I'm not sure which package is
the one holding the bug (I'm inclined to think is kernel, but
it could be elsewhere, like dev, initscripts or even anaconda).
The partitions are created properly, but the kernel doesn't seem
to be able to deal with them:
# lvm pvscan
PV /dev/hda3 VG largespace lvm2 [99.40 GB / 89.39 GB free]
Total: 1 [89.39 GB] / in use: 1 [89.39 GB] / in no VG: 0 [0 ]
# lvm vgscan
Reading all physical volumes. This may take a while...
Found volume group "largespace" using metadata type lvm2
# lvm lvscan
/dev/mapper/control: open failed: No such file or directory
Is device-mapper driver missing from kernel?
inactive '/dev/largespace/tmp' [2.00 GB] next free
(default)
# lvm pvdisplay
--- Physical volume ---
PV Name /dev/hda3
VG Name largespace
PV Size 99.40 GB / not usable 0
Allocatable yes
PE Size (KByte) 4096
Total PE 25446
Free PE 22885
Allocated PE 2561
PV UUID kIHuk7-ZCY0-VAho-iOpl-Qa1o-gpBx-YwVztb
# lvm lvdisplay
/dev/mapper/control: open failed: No such file or directory
Is device-mapper driver missing from kernel?
--- Logical volume ---
LV Name /dev/largespace/tmp
VG Name largespace
LV UUID ah222x-4yNI-AOMh-clbx-hRM7-xVjo-eLETZy
LV Write Access read/write
LV Status NOT available
LV Size 2.00 GB
Current LE 512
Segments 1
Allocation next free (default)
Read ahead sectors 0
# lvm vgck largespace
# echo $?
0
# uname -a
Linux localhost.localdomain 2.6.1-1.65smp #1 SMP Fri Jan 30
17:50:02 EST 2004 i686 athlon i386 GNU/Linux
I excluded some more lvm partitions from the output above. The
corresponding fstab entry for that partition is:
/dev/largespace/tmp /tmp ext3 defaults
1 2
Carlos
More information about the fedora-test-list
mailing list