I think this issue is occuring because I am running a bcache cache
device on a VROC IMSM 'fake raid' device. Once I followed Dimitri's
finalrd steps in post #14 (this is required), I also had to add the
following script '/lib/systemd/system-shutdown/bcache_stop'
Please make sure you run 'chmod +x
I find that the issue is resolved if I run "/usr/bin/finalrd" after I
boot so that the /run/initramfs directory is populated.
Do I need to run "/usr/bin/finalrd" on start (I see it runs on
shutdown)?
Do I need any "/etc/initramfs-tools" hooks or scripts?
--
You received this bug notification be
It seems like the fix stopped working - On every reboot now, the IMSM
VROC raid drive is being resynced
Is this related to a bug that produces this error? I see this a few
times right before reboot
systemd shutdown [1] Failed to wait for process : protocol error
--
You received this bug notific
First reboot: IMSM/VROC RAID1 resynced (as you stated)
I waited for the RAID volume to become clean and then rebooted.
Second reboot: Raid did not resync and bcache volume successfully mounted!
Third reboot: Raid did not resync and bcache volume successfully mounted!
Thank you so much, Dimitri!
On Fri, 7 Feb 2020, 17:25 Joshua Diamant, <1608...@bugs.launchpad.net>
wrote:
> Anything special needed for bcache for finalrd?
I don't know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608495
T
Anything special needed for bcache for finalrd?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608495
Title:
IMSM fakeraid handled by mdadm: unclean mounted volumes on
shutdown/reboot
To manage n
thank you so much, Dimitri. I will test and confirm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608495
Title:
IMSM fakeraid handled by mdadm: unclean mounted volumes on
shutdown/reboot
To mana
TO correctly shutdown IMSM/VROC intel matrix raid devices, I expect you
to need to install finalrd & add mdadm finalrd hook.
$ sudo apt install finalrd
Download the attached hook, place it into
/usr/share/finalrd/mdadm.finalrd, mark it executable (sudo chmod +x
/usr/share/finalrd/mdadm.finalrd)
I am having this issue using IMSM / VROC 6.2 on Ubuntu 18.04 LTS, Kernel
5.3.0-28, mdadm - v4.1-rc1 - 2018-03-22.
I am running a bcache cache device on one of the RAID 1 IMSM (VROC)
arrays. At the very minimum, every reboot the device needs to resync
(not shutting down clean).
What other informat
** Changed in: mdadm (Ubuntu Zesty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608495
Title:
IMSM fakeraid handled by mdadm: unclean mounted volumes on
I don't think it's used by default for IMSM raid installation. That's
why your devices were likely set up by dmraid first. When you mentioned
in a previous comment about installing dracut-core, this automatically
installs dmraid with kpartx. Mdadm never gets involved. When I've
manually install
@john-center
I believe mdadm is already used by default during installation. However,
when reinstalling my desktop it was not smooth at all. It seems like
underlying devices got probed / mounted by something before mdadm-udeb
was available in the d-i and thus i had to manualy unmount things and
as
I saw this fix & installed it before your update went out. I did it by
hand, so I didn't know about the dracut-core package or
enabling/starting the mdadm-shutdown.service. Even without dracut-core,
it worked for me.
I did make some changes to 64-md-raid-assembly.rules. I commented out
the ENV{
Followed the instructions from comment #7:
Base installation: Xenial/16.04
ii mdadm 3.4-4ubuntu0.1
ii dracut-core 044+3-3
Using IMSM based mdadm mounted on /home:
/dev/mapper/datavg01-home 197G 121G 67G 65% /home
PV VG Fmt Attr PSize PFree
/dev/md126p6 datavg
Just a quick clarification, first boot/shutdown will still not be clean,
but subsequent ones (those that are booted with the updated mdadm
package) should be clean.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
as part of https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1722491
there is currently mdadm update available from xenial-proposed and
zesty-proposed that might resolve this issue.
To test that solution please perform the following:
1) Install mdadm from xenial-proposed/zesty-proposed
- Se
I have a reproducer test case, and a partial fix for xenial I think.
I will start a bileto PPA with test packages for this issue.
** Also affects: mdadm (Ubuntu Zesty)
Importance: Critical
Assignee: Dimitri John Ledkov (xnox)
Status: Confirmed
** Also affects: mdadm (Ubuntu Xenial)
** Changed in: mdadm (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608495
Title:
IMSM fakeraid handled by mdadm: unclean mounted volumes on
shutdown/
See also 1320402 and 1587142
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608495
Title:
IMSM fakeraid handled by mdadm: unclean mounted volumes on
shutdown/reboot
To manage notifications about
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/1608495
Title:
IMSM
I did a quick test and created a mdadm.shutdown in /lib/systemd/system-
shutdown like the template in Yakkety (adapted path to binary and made
it executable). Unfortunately that did not help. However there might be
some step missing to activate it in systemd. I guess I need to make
output more verb
I can do some testing as well. Admittedly any unsuccessful run is a bit
of a pain as the re-sync takes 1-2hrs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608495
Title:
IMSM fakeraid handled by m
annoying.
/lib/systemd/system-shutdown/mdadm.shutdown should be syncing everything
up, but of course that's only in unstable / yakkety.
I have spare drives finally again, so I will setup ISMS on my xenial
desktop and play around with it. Hopefully package from yakkety is "good
enough" for SRU int
23 matches
Mail list logo
