** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a
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
Hi Dimitri,
> On Feb 22, 2018, at 8:32 AM, Dimitri John Ledkov
> wrote:
>
> john-center - I believe mdadm is used by default, instead of dmraid.
> However, I'm not sure if we do correctly activate Intel Raids with
> mdadm. I have not done an install with either 16.04 or 18.04. Or I guess
> at l
john-center - I believe mdadm is used by default, instead of dmraid.
However, I'm not sure if we do correctly activate Intel Raids with
mdadm. I have not done an install with either 16.04 or 18.04. Or I guess
at least start the install up to the partitioning screen. My expectation
is, if one has ra
I followed the steps from #27 and everything works fine now on 16.04.3
with a SuperMicro Board X11SSH-F with Intel C236 Chipsets RST and two
sata disks as Raid 1.
I can also confirm #28, the first reboot still needed a hard reset and a
rebuild of the Raid 1, but after this, every (>10) shutdown an
I added a comment about this new fix on
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1608495. One thing
I wanted to add here, for the first time shutdown completed
successfully. In fact, I was a little startled when it happened. :-)
It powered off at the end of shutdown, instead of hangi
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
Hello,
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
Oh … this is _another_ bug. We are dealing here with the situation that
mdmon controlling rootfs on RAID is not handled at all with Ubuntu
initrd, while this new CentOS issue is a bug in said handling in the
CentOS initrd …
The reference is valuable nevertheless … not least because I have
systems
I would just like to inform you that this bug appear since last CentOS 7.4
update, 7.3 was ok.
https://bugs.centos.org/view.php?id=13916
Maybe it should be reported to Systemd Issues ?
** Bug watch added: bugs.centos.org/ #13916
https://bugs.centos.org/view.php?id=13916
--
You received this
Can we get any reaction from Ubuntu on this? Is the needed reworking of
the initrd about to happen for the LTS or is this a WONTFIX and root-on-
Intel-Matrix-RAID is simply not supported? It is clear what has to
happen to make things work again with systemd and mdadm/mdmon. Will it
happen?
--
You
as I don't want to rebuild now again, did anyone try
eg.
chmod +x ~/myshutdown.sh
sudo ~/myshutdown.sh
# with
echo r > /proc/sysrq-trigger
echo e > /proc/sysrq-trigger
echo s > /proc/sysrq-trigger
echo i > /proc/sysrq-trigger
echo u > /proc/sysrq-trigger
a BIOS reconfig. from "RAID" to "AHCI" did not change anything.
m.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587142
Title:
Shutdown hangs in md kworker after "Reached target Shutdown."
To mana
Shutting down with a "R E S U I O" Workaround
was ok. The Raid was not rebuilt.
m.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587142
Title:
Shutdown hangs in md kworker after "Reached target Shu
Is anyone working on this? I see that the bug is assigned, but apart
from that only messages from affected users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587142
Title:
Shutdown hangs in md kw
Well, of course effects are a pain. The sync is only 256G SSDs im my
case.
Main point is that the fix is known since many years and should
hopefully be quickly adaptible to Ubuntu. Or not … if it is really
necessary to switch to a return to the initrd like Fedora.
I wonder if 17.04 has this fixed
... interesting, but the pain is the new resync ... (writing 4(8) TB on each
"hanging" reboot, ehm ...)
I used SysReq to sync before power-off
echo 1 > /proc/sys/kernel/sysrq
ALT + "DRUCK" ( or "Print Screen") + R E I S U O
as a workaround. as I have to wait for the sync, I can't report now.
o
So I got a simple fix for being able to reboot again:
```
udpate-rc.d mdadm disable
```
With that, the mdmon instance from the initrd persists (with @sbin/mdmon
as argv[0]) and is not killed by systemd. So systemd-reboot does not
hang. But: Since mdmon is not killed at all now, the array always g
This very much looks like this ancient issue in RedHat:
https://bugzilla.redhat.com/show_bug.cgi?id=752593
It got fixed at some point in 2012 …
https://bugzilla.redhat.com/show_bug.cgi?id=785739
Is Ubuntu still running mdmon from inside the root fs and killing it
before r/o remount?
I am now p
** Attachment added: "screenshot"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142/+attachment/4945763/+files/reached_target.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587142
confirmed on
HP ProLiant ML10 Gen9, Xeon E3-1225 v5
Intel Raid Bios set to RAID1 (4 drives, 2xraid1)
Shutdowen/reboot hangs (kworkers) and Raid is rebuilt on every "reset"
Linux w11 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:51 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
Description:Ubu
Confirm on HPE ML10 gen9.
Ubuntu 16.04.2 LTS
Intel SATA RAID - RAID 1. Intel SSD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587142
Title:
Shutdown hangs in md kworker after "Reached target Shut
Confirm this on:
Supermicro X10DAi board and ASUS ESC4000 G3 server
Ubuntu 16.04.2 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587142
Title:
Shutdown hangs in md kworker after "Reached target
Confirm on this bug with hardware:
HP Z230, Intel Raid bios, Ubuntu 16.04.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587142
Title:
Shutdown hangs in md kworker after "Reached target Shutdown
Same problem with a SuperMicro Board X11SSH-F with Intel C236 Chipset
and two sata disks.
Installing the server with bios sata mode "RAID" and a RAID1 configured
in the Intel Raid bios (Ctrl+I), on a fresh Ubuntu install and also on
updated Ubuntu 16.04.2 the server doesn't restart or shutdown, it
** Changed in: systemd (Ubuntu)
Importance: High => Critical
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Confirming this same issue for me on a clean install of Ubuntu 16.04.2
X64 server on a HP 8300 Elite SFF pc. Anything I can collect to
troubleshoot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15871
I have a similar problem with a super micro X10DRH system board. If I have the
intel sata controller set to ACHI and install a fresh instance of 16.04 the
server works without issue. If I have the intel sata controller in RSTe RAID
mode with a 2 drive RAID1 configuration the server will hang o
With upstart-sysv, I have now observed a spurious RAID1 verify following
a reboot after an unrelated apt upgrade (libc stuff). It's the only
spurious RAID1 verify that I have observed so far with upstart-sysv. So
upstart-sysv is not perfect, but still better than systemd-sysv
regarding these issues
I still get the same issues with a fully updated Ubuntu Server 16.04.1
LTS (Linux 4.4.0-45-generic).
The patch from
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1320402/comments/13
does not seem to have any effect on these issues.
I have also tried the latest mainline kernel build from
h
Possibly also related to 1320402 (as the unnecessary resync probably
follows the incorrect stopping of the array).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587142
Title:
Shutdown hangs in md k
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587142
Title:
Shutdown hangs in md kworker after "Reached target Shutdown."
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (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/1587142
Title:
Sh
33 matches
Mail list logo