after upgrading from feisty to gutsy, /dev/mapper no longer contains my LVM volume group
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lvm2 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I used update-manager to update from feisty to gutsy on my server, which has a number of drives mounted on an LVM volume group.
Under fiesty these drives appeared in /dev/mapper as /dev/mapper/
After running the full upgrade script and rebooting, the machine failed ot fully start because the /dev/mapper/data directory no longer exists (and /home is stored on there).
Running lvs, vgs or pvs correclty shows the logical volumes, physical volumes and volume groups -
root@mibsvr01:/# vgs
VG #PV #LV #SN Attr VSize VFree
data 9 5 0 wz--n- 145.39G 21.61G
root@mibsvr01:/# pvs
PV VG Fmt Attr PSize PFree
/dev/sdb1 data lvm1 a- 30.59G 1.61G
/dev/sdc1 data lvm1 a- 9.97G 0
/dev/sdc2 data lvm1 a- 9.97G 4.94G
/dev/sdc3 data lvm1 a- 9.97G 9.97G
/dev/sdc5 data lvm1 a- 9.97G 96.00M
/dev/sdc6 data lvm1 a- 9.97G 0
/dev/sdc7 data lvm1 a- 9.97G 0
/dev/sdc8 data lvm1 a- 34.97G 0
/dev/sdc9 data lvm1 a- 20.02G 5.00G
root@mibsvr01:/# lvs
LV VG Attr LSize Origin Snap% Move Log Copy%
apps data -wn--- 12.00G
data data -wn--- 4.00G
downloads data -wn--- 58.00G
mp3 data -wn--- 44.78G
root data -wn--- 5.00G
root@mibsvr01:/# ls /dev/mapper
control
Hope that helps
I tried booting from kernel 2.6.20-15 instead of the newer 2.6.22-11, but is hasn't made a differance, it still cant see the /dev/mapper/data directories