Mailinglist Archive: opensuse-bugs (5243 mails)

< Previous Next >
[Bug 793954] raid1 array sometimes started with one of two disks at boot (again)

https://bugzilla.novell.com/show_bug.cgi?id=793954

https://bugzilla.novell.com/show_bug.cgi?id=793954#c32


--- Comment #32 from Volker Kuhlmann <volker3204@xxxxxxxxxxxxxxx> 2013-03-14
23:17:20 NZDT ---
Re comment #30
Unfortunately adding udev-trigger to
# Should-Start: udev-trigger
DOES NOT fix the problem.

My older SATA/PATA system still has the line
ENV{ID_FS_TYPE}=="linux_raid_member", ACTION=="add", RUN+="/sbin/mdadm
--incremental $env{DEVNAME}"
in /lib/udev/rules.d/64-md-raid.rules commented out. Otherwise it's up to all
updates of 12.1, and it seems reliable.

My system with 2 SATA has all updates, no changes, and raid1 is @*^$ed (still
12.1 too).

My additional scripts may look excessive but have the deciding advantage that
they are guaranteed to work. Their warning features will also be necessary for
any future tests (I don't want to get screwed again).

Of about 8 reboots for testing today the problem showed in the first 3 and then
disappeared. I hate that. Is there anything that could adapt to a changed
system configuration (straws, grasp)?

Over the next few weeks I expect to upgrade to 12.3, until then I can test the
change

-ExecStart=/sbin/udevadm trigger --type=subsystems --action=add ; /sbin/udevadm
trigger --type=devices --action=add
+ExecStart=/sbin/udevadm trigger --type=subsystems --action=add
+ExecStart=/sbin/udevadm trigger --type=devices --action=add

in /lib/systemd/system/udev-trigger.service

--
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.

< Previous Next >