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 t
Hello Jan and thank you for filing a bug report. Unfortunately this
issue has not seen attention in quite some time. Currently evms is only
available in Dapper and Hardy. If you're still experiencing this issue
please let us know however be aware evms has been dropped from Debian
and most likely
You are right about Ubuntu using the UUIDs to mount by default. What
happened in my case is that the drive was installed later (after Ubuntu
was already installed)... so i simply formatted it (ext3) and mounted it
myself, using the /dev/sdXn style partition reference.
i was thinking, if /etc/fstab
Thanks for this - I didn't know EVMS made them available elsewhere.
But Ubuntu seems to automatically use disk UUIDs rather than /dev/sdaX-style
partition references. And after upgrading to Gutsy, my UUIDs still point to the
old devices.
Shouldn't they be updated when the evms package is install
Found the problem: EVMS was moving, or acquiring the /dev/sdb1 device,
and creating another node under /dev/evms/sdb1.
I'm not sure if i had EVMS installed under Feisty, but either upgrading
it to Gusty or having it installed when upgrading to Gusty triggered the
problem.
Took me almost an hour (
** Attachment added: "Extract from /var/kern.log of the last time i tried to
boot from kernel 2.6.22-14"
http://launchpadlibrarian.net/10031391/kern.log
--
can't mount secondary sata drive
https://bugs.launchpad.net/bugs/153027
You received this bug notification because you are a member of U
