[Bug 853944] New: spurious (?) "Started Activate md array even though degraded" msg on boot; checked arrays are not degraded
https://bugzilla.novell.com/show_bug.cgi?id=853944 https://bugzilla.novell.com/show_bug.cgi?id=853944#c0 Summary: spurious (?) "Started Activate md array even though degraded" msg on boot; checked arrays are not degraded Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ar16@imapmail.org QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 i've a 13.1 server. /boot & / are on RAID. specifically /boot <-- RAID-1 / <-- LVM on RAID-10 on system boot, i see in serial console output ... [ OK ] Started Activate md array even though degraded. Starting Activate md array even though degraded... [ OK ] Started Activate md array even though degraded. ... the boot continue & completes. checking, there's no trace of the 'degraded' array dmesg | egrep -i "degraded|md.:|activate|array" [ 28.199267] md/raid10:md2: active with 4 out of 4 devices [ 28.268913] md2: bitmap initialized from disk: read 30 pages, set 0 of 953867 bits [ 28.324245] md2: detected capacity change from 0 to 2000404086784 [ 28.358596] md2: unknown partition table [ 28.860292] md/raid1:md0: active with 2 out of 2 mirrors [ 29.071396] md0: bitmap initialized from disk: read 2 pages, set 0 of 50176 bits [ 29.126892] md0: detected capacity change from 0 to 205520896 [ 29.185709] md0: unknown partition table journalctl -xb | egrep -i "degraded|md.:|activate|array|raid" (empty) cat /proc/mdstat Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [linear] md0 : active raid1 sda1[0] sdb1[1] 200704 blocks [2/2] [UU] bitmap: 0/25 pages [0KB], 4KB chunk md2 : active raid10 sdc1[0] sde1[4] sdd1[1] sdf1[3] 1953519616 blocks super 1.2 512K chunks 2 far-copies [4/4] [UUUU] bitmap: 0/466 pages [0KB], 2048KB chunk md125 : active raid1 sdb2[2] sda2[0] 243987048 blocks super 1.0 [2/2] [UU] unused devices: <none> mdadm --detail /dev/md0 /dev/md2 /dev/md125 | grep "State :" State : active State : active State : clean Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=853944 https://bugzilla.novell.com/show_bug.cgi?id=853944#c A R <ar16@imapmail.org> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |nfbrown@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=853944 https://bugzilla.novell.com/show_bug.cgi?id=853944#c1 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #1 from Neil Brown <nfbrown@suse.com> 2013-12-11 04:40:41 UTC --- I guess that message should be "Check if we need to start a degraded array" or something like that. I didn't realise the description of each systemd service would be printed as it runs, but I guess it makes sense. Or maybe I need to find a way for the systemd service to check if it is still needed after the timeout. You can safely ignore the message for now. I may be a while before I "fix" this. Thanks for the report. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=853944 https://bugzilla.novell.com/show_bug.cgi?id=853944#c2 --- Comment #2 from Neil Brown <nfbrown@suse.com> 2013-12-12 02:19:03 UTC --- You can get rid of the messages by adding the line Conflicts=sys-devices-virtual-block-%i.device near the top of /usr/lib/systemd/system/mdadm-last-resort@.timer It'll get this into an update at some stage, but it won't be for a while. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=853944 https://bugzilla.novell.com/show_bug.cgi?id=853944#c3 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #3 from Neil Brown <nfbrown@suse.com> 2014-02-18 01:52:42 UTC --- This is fixed in 'Factory' and in my home:neilbrown:branches:openSUSE:13.1:Update/mdadm package. As it is not cirtical I won't submit a 13.1 update just yet but it will certainly be fixed in the next update or upgrade. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=853944 https://bugzilla.novell.com/show_bug.cgi?id=853944#c4 --- Comment #4 from Swamp Workflow Management <swamp@suse.de> 2014-03-21 10:04:25 UTC --- openSUSE-RU-2014:0415-1: An update that has one recommended fix can now be installed. Category: recommended (low) Bug References: 853944 CVE References: Sources used: openSUSE 13.1 (src): pam-1.1.8-6.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=853944 http://bugzilla.novell.com/show_bug.cgi?id=853944#c5 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |9b3e05a5@opayq.com, | |neilb@suse.com Resolution|FIXED |--- Flags| |needinfo?(neilb@suse.com) OS|openSUSE 13.1 |openSUSE 42.1 --- Comment #5 from boo35 boo35 <9b3e05a5@opayq.com> --- noticing these messages in Opensuse Leap 42.1 boot-logs ... [ OK ] Created slice system-mdadm\x2dlast\x2dresort.slice. Starting Activate md array even though degraded... Starting Activate md array even though degraded... Starting Activate md array even though degraded... [ OK ] Started Activate md array even though degraded. [ OK ] Started Activate md array even though degraded. [ OK ] Started Activate md array even though degraded. ...
You can get rid of the messages by adding the line Conflicts=sys-devices-virtual-block-%i.device near the top of /usr/lib/systemd/system/mdadm-last-resort@.timer It'll get this into an update at some stage, but it won't be for a while.
checking, still not addressed cat /usr/lib/systemd/system/mdadm-last-resort@.timer [Unit] Description=Timer to wait for more drives before activating degraded array. DefaultDependencies=no Conflicts=sys-devices-virtual-block-%i.device [Timer] OnActiveSec=30 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=853944 http://bugzilla.novell.com/show_bug.cgi?id=853944#c6 Neil Brown <neilb@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |883f6ce9@opayq.com Flags| |needinfo?(883f6ce9@opayq.co | |m) --- Comment #6 from Neil Brown <neilb@suse.com> --- Hmmm.. that is strange. It seems that it order to stop the timer, we need to put that "Conficts" line in the ".service" file. Can you please move the Conflicts= line from mdadm-last-resort@.timer to mdadm-last-resort@.service can confirm that this fixes the issues? Thanks -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=853944 http://bugzilla.novell.com/show_bug.cgi?id=853944#c7 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(883f6ce9@opayq.co | |m) | --- Comment #7 from boo35 boo35 <9b3e05a5@opayq.com> --- (In reply to Neil Brown from comment #6)
Can you please move the Conflicts= line from mdadm-last-resort@.timer to mdadm-last-resort@.service can confirm that this fixes the issues?
Doesn't look like it. boot dmesg | grep -i activ | grep -i degraded [ 88.912859] systemd[1]: Starting Timer to wait for more drives before activating degraded array.. [ 88.912894] systemd[1]: Started Timer to wait for more drives before activating degraded array.. [ 88.912931] systemd[1]: Starting Timer to wait for more drives before activating degraded array.. [ 88.912963] systemd[1]: Started Timer to wait for more drives before activating degraded array.. [ 88.912984] systemd[1]: Starting Timer to wait for more drives before activating degraded array.. [ 88.913001] systemd[1]: Started Timer to wait for more drives before activating degraded array.. [ 119.419984] systemd[1]: Starting Activate md array even though degraded... [ 119.426709] systemd[1]: Starting Activate md array even though degraded... [ 119.435537] systemd[1]: Starting Activate md array even though degraded... [ 119.463533] systemd[1]: Started Activate md array even though degraded. [ 119.474120] systemd[1]: Started Activate md array even though degraded. [ 119.482104] systemd[1]: Started Activate md array even though degraded. cat /proc/mdstat | grep ^md | sort md0 : active raid1 sdf3[1] sde3[0] md1 : active raid1 sde4[0] sdf4[1] md2 : active raid10 sda1[1] sdc1[3] sdd1[2] sdb1[0] md3 : active raid10 sdm1[3] sdl1[0] sdn1[2] sdk1[1] md4 : active raid10 sdg1[0] sdh1[1] sdi1[2] sdj1[3] EDIT cat /usr/lib/systemd/system/mdadm-last-resort@.service [Unit] Description=Activate md array even though degraded DefaultDependencies=no + Conflicts=sys-devices-virtual-block-%i.device [Service] Type=oneshot ExecStart=/sbin/mdadm --run /dev/%i cat /usr/lib/systemd/system/mdadm-last-resort@.timer [Unit] Description=Timer to wait for more drives before activating degraded array. DefaultDependencies=no - Conflicts=sys-devices-virtual-block-%i.device [Timer] OnActiveSec=30 reboot dmesg | grep -i activ | grep -i degraded [ 88.693704] systemd[1]: Starting Timer to wait for more drives before activating degraded array.. [ 88.693721] systemd[1]: Started Timer to wait for more drives before activating degraded array.. [ 88.693729] systemd[1]: Starting Timer to wait for more drives before activating degraded array.. [ 88.693742] systemd[1]: Started Timer to wait for more drives before activating degraded array.. [ 88.693748] systemd[1]: Starting Timer to wait for more drives before activating degraded array.. [ 88.693761] systemd[1]: Started Timer to wait for more drives before activating degraded array.. [ 118.779355] systemd[1]: Starting Activate md array even though degraded... [ 118.790671] systemd[1]: Starting Activate md array even though degraded... [ 118.801642] systemd[1]: Starting Activate md array even though degraded... [ 118.850604] systemd[1]: Started Activate md array even though degraded. [ 118.856927] systemd[1]: Started Activate md array even though degraded. [ 118.864238] systemd[1]: Started Activate md array even though degraded. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=853944 http://bugzilla.novell.com/show_bug.cgi?id=853944#c8 Neil Brown <neilb@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(neilb@suse.com) |needinfo?(883f6ce9@opayq.co | |m) --- Comment #8 from Neil Brown <neilb@suse.com> --- That's odd .... it worked for me. Maybe try putting the 'Conflicts' line in both files. I have a hunch there is an ordering dependence. If the device appears before the timer is started the Conflicts has to be in one file, if the device appears after the timer is activated it needs to be in the other. So: try both please. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=853944 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |ibs:running:1739:moderate | |ibs:running:1500:moderate -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=853944 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:1739:moderate |ibs:running:1739:moderate |ibs:running:1500:moderate |ibs:running:1500:moderate | |obs:running:5266:moderate -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=853944 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:1739:moderate |obs:running:5266:moderate |ibs:running:1500:moderate | |obs:running:5266:moderate | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=853944 http://bugzilla.novell.com/show_bug.cgi?id=853944#c11 --- Comment #11 from Swamp Workflow Management <swamp@suse.de> --- SUSE-RU-2016:1648-1: An update that has 9 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 853944,939124,953595,954769,956236,957886,958597,966773,974154 CVE References: Sources used: SUSE Linux Enterprise Server 12-SP1 (src): mdadm-3.3.1-25.1 SUSE Linux Enterprise Desktop 12-SP1 (src): mdadm-3.3.1-25.1 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=853944 http://bugzilla.novell.com/show_bug.cgi?id=853944#c12 --- Comment #12 from Swamp Workflow Management <swamp@suse.de> --- SUSE-RU-2016:1649-1: An update that has 10 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 853944,930417,939124,952644,953380,953595,956236,958597,966773,974154 CVE References: Sources used: SUSE Linux Enterprise Server 12 (src): mdadm-3.3.1-6.15.1 SUSE Linux Enterprise Desktop 12 (src): mdadm-3.3.1-6.15.1 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=853944 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:5266:moderate | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=853944 http://bugzilla.novell.com/show_bug.cgi?id=853944#c13 --- Comment #13 from Swamp Workflow Management <swamp@suse.de> --- openSUSE-RU-2016:1712-1: An update that has 9 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 853944,939124,953595,954769,956236,957886,958597,966773,974154 CVE References: Sources used: openSUSE Leap 42.1 (src): mdadm-3.3.1-13.1 -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com