https://bugzilla.novell.com/show_bug.cgi?id=379745 User werner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=379745#c16 --- Comment #16 from Dr. Werner Fink <werner@novell.com> 2008-07-30 07:29:50 MDT --- I'm now using in /etc/init.d/boot.halt HAS_MDRAID=no [...] mddev="" [...] # # Sometimes it is wanted to stop also the disks, but # do not do this for software raids. # while read line ; do case "$line" in md*:*active*) HAS_MDRAID=yes; break esac done < /proc/mdstat unset line # # If found a software raids, check out the devices # if test "$HAS_MDRAID" = "yes" ; then if test -e /etc/mdadm.conf ; then while read type dev rest; do case "$dev" in /dev/md*) mddev="${mddev:+$mddev }$dev" esac done < /etc/mdadm.conf unset type dev rest fi else opts="${opts:+$opts }-h" fi [...] # on umsdos fs this would lead to an error message, so direct errors to # /dev/null mount -no remount,ro / 2> /dev/null sync # for an software raid stop inactive devices and wait if test "$HAS_MDRAID" = "yes" ; then if test -n "$mddev" ; then mdadm --quiet --stop $mddev mdadm --quiet --wait $mddev else mdadm --quiet --stop --scan mdadm --quiet --wait /dev/md[0-9] /dev/md[0-9][0-9] fi fi which should be OK now. Btw. within boot.md the usage of $mdadm_BIN and mdadm is mixed. -- 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.