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
The shutdown now also hangs during a resync. So it behaves
inconsistently. I update the subject and the description to reflect
this.
** Summary changed:
- Reboot hangs once RAID1 resynced
+ Shutdown hangs in md kworker after "Reached target Shutdown."
** Description changed:
I'm booting a ful
** Attachment added: "shutdown-log-part2.png"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142/+attachment/4673088/+files/shutdown-log-part2.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubun
Public bug reported:
I'm booting a fully patched 16.04 from an Intel Rapid Storage Technology
enterprise RAID1 volume (ThinkServer TS140 with two SATA
ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).
If the RAID volume is recovering or resyncing for whatever reason, then
`sudo sy
5 matches
Mail list logo
