So this is the reason for mdadm being installed?
I kept wondering why I have to have a raid-manager when I don't have or
plan on having a raid in my system. :/
What is the reason for this dependency? Why does every user, with or
without raid-systems, get this? These
W: mdadm: /etc/mdadm/mdadm.co
Correct in an upload today, you're right that this dependency isn't
needed since it was only for an initramfs ordering issue which has long-
since been removed.
** Changed in: lvm-common (Ubuntu)
Status: In Progress => Fix Released
--
Bogus dependency on mdadm
https://bugs.launchpad.net/b
As since yesterday's update I cannot boot my system properly (seemed to be a
mdadm issue). I have removed mdadm package (I'm also using directly lvm on
non-md devices).
However, this seems to have wipeout my /boot! The grub directory is not there
anymore :-(
I'm trying to recover my system befor
I have to update my previous statement. My /boot was not wiped-out, it was not
mounted !?! That was explaining why it was empty.
However, I am not explaining myself why since yesterday updates in mdadm and
lvm-common, I have so many troubles to boot.
Just to make things clear: I have /boot (ext3)
** Changed in: lvm-common (Ubuntu)
Status: Unconfirmed => In Progress
--
Bogus dependency on mdadm
https://bugs.launchpad.net/bugs/98929
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
I saw an update of evms today. I have upgrade and reboot my computer to check
if it could solve the problem. It did solve it.
Now my system is working again.
--
Bogus dependency on mdadm
https://bugs.launchpad.net/bugs/98929
You received this bug notification because you are a member of Ubuntu
B
So this is the reason for mdadm being installed?
I kept wondering why I have to have a raid-manager when I don't have or
plan on having a raid in my system. :/
What is the reason for this dependency? Why does every user, with or
without raid-systems, get this? These
W: mdadm: /etc/mdadm/mdadm.co
Correct in an upload today, you're right that this dependency isn't
needed since it was only for an initramfs ordering issue which has long-
since been removed.
** Changed in: lvm-common (Ubuntu)
Status: In Progress => Fix Released
--
Bogus dependency on mdadm
https://bugs.launchpad.net/b
As since yesterday's update I cannot boot my system properly (seemed to be a
mdadm issue). I have removed mdadm package (I'm also using directly lvm on
non-md devices).
However, this seems to have wipeout my /boot! The grub directory is not there
anymore :-(
I'm trying to recover my system befor
I have to update my previous statement. My /boot was not wiped-out, it was not
mounted !?! That was explaining why it was empty.
However, I am not explaining myself why since yesterday updates in mdadm and
lvm-common, I have so many troubles to boot.
Just to make things clear: I have /boot (ext3)
** Changed in: lvm-common (Ubuntu)
Status: Unconfirmed => In Progress
--
Bogus dependency on mdadm
https://bugs.launchpad.net/bugs/98929
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
I saw an update of evms today. I have upgrade and reboot my computer to check
if it could solve the problem. It did solve it.
Now my system is working again.
--
Bogus dependency on mdadm
https://bugs.launchpad.net/bugs/98929
You received this bug notification because you are a member of Ubuntu
B
So this is the reason for mdadm being installed?
I kept wondering why I have to have a raid-manager when I don't have or
plan on having a raid in my system. :/
What is the reason for this dependency? Why does every user, with or
without raid-systems, get this? These
W: mdadm: /etc/mdadm/mdadm.co
Correct in an upload today, you're right that this dependency isn't
needed since it was only for an initramfs ordering issue which has long-
since been removed.
** Changed in: lvm-common (Ubuntu)
Status: In Progress => Fix Released
--
Bogus dependency on mdadm
https://bugs.launchpad.net/b
As since yesterday's update I cannot boot my system properly (seemed to be a
mdadm issue). I have removed mdadm package (I'm also using directly lvm on
non-md devices).
However, this seems to have wipeout my /boot! The grub directory is not there
anymore :-(
I'm trying to recover my system befor
I have to update my previous statement. My /boot was not wiped-out, it was not
mounted !?! That was explaining why it was empty.
However, I am not explaining myself why since yesterday updates in mdadm and
lvm-common, I have so many troubles to boot.
Just to make things clear: I have /boot (ext3)
** Changed in: lvm-common (Ubuntu)
Status: Unconfirmed => In Progress
--
Bogus dependency on mdadm
https://bugs.launchpad.net/bugs/98929
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
I saw an update of evms today. I have upgrade and reboot my computer to check
if it could solve the problem. It did solve it.
Now my system is working again.
--
Bogus dependency on mdadm
https://bugs.launchpad.net/bugs/98929
You received this bug notification because you are a member of Ubuntu
B
So this is the reason for mdadm being installed?
I kept wondering why I have to have a raid-manager when I don't have or
plan on having a raid in my system. :/
What is the reason for this dependency? Why does every user, with or
without raid-systems, get this? These
W: mdadm: /etc/mdadm/mdadm.co
Correct in an upload today, you're right that this dependency isn't
needed since it was only for an initramfs ordering issue which has long-
since been removed.
** Changed in: lvm-common (Ubuntu)
Status: In Progress => Fix Released
--
Bogus dependency on mdadm
https://bugs.launchpad.net/b
So this is the reason for mdadm being installed?
I kept wondering why I have to have a raid-manager when I don't have or
plan on having a raid in my system. :/
What is the reason for this dependency? Why does every user, with or
without raid-systems, get this? These
W: mdadm: /etc/mdadm/mdadm.co
Correct in an upload today, you're right that this dependency isn't
needed since it was only for an initramfs ordering issue which has long-
since been removed.
** Changed in: lvm-common (Ubuntu)
Status: In Progress => Fix Released
--
Bogus dependency on mdadm
https://bugs.launchpad.net/b
As since yesterday's update I cannot boot my system properly (seemed to be a
mdadm issue). I have removed mdadm package (I'm also using directly lvm on
non-md devices).
However, this seems to have wipeout my /boot! The grub directory is not there
anymore :-(
I'm trying to recover my system befor
I have to update my previous statement. My /boot was not wiped-out, it was not
mounted !?! That was explaining why it was empty.
However, I am not explaining myself why since yesterday updates in mdadm and
lvm-common, I have so many troubles to boot.
Just to make things clear: I have /boot (ext3)
** Changed in: lvm-common (Ubuntu)
Status: Unconfirmed => In Progress
--
Bogus dependency on mdadm
https://bugs.launchpad.net/bugs/98929
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
I saw an update of evms today. I have upgrade and reboot my computer to check
if it could solve the problem. It did solve it.
Now my system is working again.
--
Bogus dependency on mdadm
https://bugs.launchpad.net/bugs/98929
You received this bug notification because you are a member of Ubuntu
B
As since yesterday's update I cannot boot my system properly (seemed to be a
mdadm issue). I have removed mdadm package (I'm also using directly lvm on
non-md devices).
However, this seems to have wipeout my /boot! The grub directory is not there
anymore :-(
I'm trying to recover my system befor
I have to update my previous statement. My /boot was not wiped-out, it was not
mounted !?! That was explaining why it was empty.
However, I am not explaining myself why since yesterday updates in mdadm and
lvm-common, I have so many troubles to boot.
Just to make things clear: I have /boot (ext3)
** Changed in: lvm-common (Ubuntu)
Status: Unconfirmed => In Progress
--
Bogus dependency on mdadm
https://bugs.launchpad.net/bugs/98929
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
I saw an update of evms today. I have upgrade and reboot my computer to check
if it could solve the problem. It did solve it.
Now my system is working again.
--
Bogus dependency on mdadm
https://bugs.launchpad.net/bugs/98929
You received this bug notification because you are a member of Ubuntu
B
So this is the reason for mdadm being installed?
I kept wondering why I have to have a raid-manager when I don't have or
plan on having a raid in my system. :/
What is the reason for this dependency? Why does every user, with or
without raid-systems, get this? These
W: mdadm: /etc/mdadm/mdadm.co
Correct in an upload today, you're right that this dependency isn't
needed since it was only for an initramfs ordering issue which has long-
since been removed.
** Changed in: lvm-common (Ubuntu)
Status: In Progress => Fix Released
--
Bogus dependency on mdadm
https://bugs.launchpad.net/b
As since yesterday's update I cannot boot my system properly (seemed to be a
mdadm issue). I have removed mdadm package (I'm also using directly lvm on
non-md devices).
However, this seems to have wipeout my /boot! The grub directory is not there
anymore :-(
I'm trying to recover my system befor
I have to update my previous statement. My /boot was not wiped-out, it was not
mounted !?! That was explaining why it was empty.
However, I am not explaining myself why since yesterday updates in mdadm and
lvm-common, I have so many troubles to boot.
Just to make things clear: I have /boot (ext3)
** Changed in: lvm-common (Ubuntu)
Status: Unconfirmed => In Progress
--
Bogus dependency on mdadm
https://bugs.launchpad.net/bugs/98929
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
I saw an update of evms today. I have upgrade and reboot my computer to check
if it could solve the problem. It did solve it.
Now my system is working again.
--
Bogus dependency on mdadm
https://bugs.launchpad.net/bugs/98929
You received this bug notification because you are a member of Ubuntu
B
36 matches
Mail list logo
