We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
My Fiesty-Gutsy Upgrade wouldn't let me back in after the screensaver
kicked in. I had to hard shutdown my machine. Here's an email I just
sent to some of my friends (the irony that I've all typed up for you
already. LOL)
1. I booted with the Xubuntu 7.10 alternate CD started rescue mode. No
I was also hit by this bug. Together with a non-working EVMS (see bug
#124641), it really gave me a hard time after upgrading my server...
For me, the workaround was to uninstall the EVMS package and manually
put in a startup script to detect the VGs, as panos lined out in the
comment above.
--
The _new_ way of mounting is through evms?? IIRC EVMS has been an
improvement on LVM1, but has been superseded by LVM2 since then. I dont
even think EVMS is currently still under development anymore..
--
after upgrading from feisty to gutsy, /dev/mapper no longer contains my LVM
volume group
I ran into exact the same problem when I tried to set up a ext3 partition for
LVM. I have no idea what evms is, but the workaround is found in the lvm HOWTO,
section 7.2 (http://tldp.org/HOWTO/LVM-HOWTO/initscriptdebian.html).
Installing the init script solved the problem for me. However, I am
The new way of mounting volume groups is through evms.
However, evms does not run nice with the 2.6.22 kernel if you do not manage
*all* partitions (including root) through evms.
So your options:
* install evms and run an older kernel (very annoying if you have nvidia
graphics)
* install evms
Downloaded Gutsy Tribe 5 - Server Edition CD, installed from fresh,
adding the LVM drives during hte manual partitioning step. Everything
worked fine until I rebooted at end of installation, to be met with the
same issue, got dropped into a maintenance shell.
I figured this was weird, as I could
Indeed, the automatically mounting of the volume groups have been
disabled in Gutsy so it seems. Which is HIGHLY annoying. Any reason why?
Any other methods that got introduced that we don't know about?
Thanks!
--
after upgrading from feisty to gutsy, /dev/mapper no longer contains my LVM
** Changed in: lvm2 (Ubuntu)
Sourcepackagename: None = lvm2
--
after upgrading from feisty to gutsy, /dev/mapper no longer contains my LVM
volume group
https://bugs.launchpad.net/bugs/139337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
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
--
after upgrading from feisty to gutsy, /dev/mapper no longer contains my LVM
volume group
https://bugs.launchpad.net/bugs/139337
You
10 matches
Mail list logo
