Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mdadm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780196
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lvm2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780196
Title:
@xnox
sudo apt install dracut-core did not work for me.
In my case:
raid md1 was unmounted but raid md0 was not.
raid md0 was mounted to /
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780196
finalrd accepted from NEW queue. unassigning self.
** Changed in: mdadm (Ubuntu)
Assignee: Steve Langasek (vorlon) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780196
Title:
$ sudo apt install dracut-core
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780196
Title:
Timed out Availability of block devices service
To manage notifications about this bug go to:
mdadm package ships mdadm-shutdown.service which should aid with
unmounting raid arrays on shutdown.
However, for it to work it requires an installation of package dracut-
core
Could you please try
$ apt install dracut-core
and let me know if that resolves long shut down times for you?
In the
I also ran into this problem with Ubuntu Server 18.04 and a RAID 1 array
(shutdown would wait 1:30 for the array to be unmounted). Manually
unmounting the array before shutdown removed the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Also affects: mdadm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780196
Title:
Timed out Availability of block devices service
To manage
I think it can be fixed in 2 ways:
* blkdeactivate handles properly the syncing software-raid arrays
* re-order this service, to be after the "standard" software-raid deinit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FYI: This problem can happen when the md0 device still synchronizing.
Now, when the md0 is in sync, the service stopped as well:
# journalctl -b -1 -u blk-availability.service
systemd[1]: Starting Availability of block devices...
systemd[1]: Started Availability of block devices.
systemd[1]:
I found the commit where introduced this blkdeactivate:
https://sourceware.org/git/?p=lvm2.git;a=commit;h=c698ee14bbb1310cf2383c8977d14a8e29139f8c
> Traverses the tree of block devices and tries to deactivate them.
> Currently, it supports device-mapper-based devices together with LVM.
> See
11 matches
Mail list logo
