<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: root is on a multipathed device multipathd can not be stopped in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/root-is-on-a-multipathed-device-multipathd-can-not-be-stopped/m-p/6022271#M54198</link>
    <description>&lt;P&gt;Not critical at all. The message is produced by a check in the /etc/init.d/multipathd script, which prevents stopping multipathd with e.g. "service multipathd stop" when the root filesystem is on a multipathed device.&lt;/P&gt;&lt;P&gt;While multipathd can safely be restarted while multipathed devices are in use, leaving it stopped for an extended period of time is not a good idea.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The writer of the /etc/init.d/multipathd script apparently has not included a special check to silence the message when the system is halting or rebooting.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When the root filesystem is on a multipathed device, having the multipathd running as far in to the halt/reboot procedure as possible (ideally all the way to the point where the kernel halts/reboots the system) is actually a good thing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; the other thing is if I update the system with yum update it wont boot with the new kernel.. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;gt; I think I should rebuild the kernel image with mkinitrd.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The installation procedure for the new kernel package already includes a mkinitrd step, so doing it manually won't do anything unless you fix the root cause first.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;You say "it won't boot". What exactly happens? Where does the boot process stop? Does it hang? Does it fall to single-user mode? Has it successfully mounted the root filesystem at that point? Has the kernel detected the multipathed SAS storage? If you needed a special driver RPM to make the multipathed SAS storage accessible with the old kernel, you might need to update that RPM too. If the updated RPM does not contain a pre-built driver for the new errata kernel, you might have to rebuild the module before rebuilding the initrd for the new kernel and booting with it. This can be a bit tricky: check the installation instructions of the driver RPM.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Before rebuilding the initrd, you should make sure the /etc/modprobe.conf includes the appropriate SAS adapter driver module:&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;The first scsi_hostadapter alias should be simply "alias scsi_hostadapter &amp;lt;module name&amp;gt;" and the &amp;lt;module name&amp;gt; should be the name of the driver module needed to access your root filesystem.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;The subsequent scsi_hostadapter aliases (if required) should be of the form "alias scsi_hostadapter&amp;lt;N&amp;gt; &amp;lt;module name&amp;gt;" where &amp;lt;N&amp;gt; is a number (starting with 1), and &amp;lt;module name&amp;gt; is the name of the required storage adapter driver module.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;If the above tips won't help you, please identify the exact server model &lt;STRONG&gt;and&lt;/STRONG&gt; the model of any multipathed add-on SAS controller card(s) used on your system.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&amp;gt; If I run the command multipath -v0 or 1 2 it doesnt show anything..&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;If "multipath -v2" does not display anything, it simply means the command thinks there is nothing for it to do: either there are no multipathed devices detected (= perhaps missing a SAS driver update?) or udev has already run it automatically. Run "multipath -ll" to see the current state of the multipath subsystem.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 06 Apr 2013 17:23:26 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2013-04-06T17:23:26Z</dc:date>
    <item>
      <title>root is on a multipathed device multipathd can not be stopped</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-is-on-a-multipathed-device-multipathd-can-not-be-stopped/m-p/6019793#M54195</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi guys.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am installing RH 5.8 booting from a HP SAS storage with multipath.. the server is a HP proliant..&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;there is a / partition, swap and /var all in the storage..&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;the issue is when I restart the server while the system stop all service one says ERROR... and the error is this:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;root is on a multipathed device multipathd can not be stopped&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I can restart the server and it will boot.. but I am not sure if this is a critical issue that could affect me in the future.. the server will be in production and the only reason for restart or shutdown will be a for a very critical failure...&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am trying to find information about this but I allways end in any page showing the script which stop this service.. not sure if it is a bug or should I replace the original script with the one I found..&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;the other thing is if I update the system with yum update it wont boot with the new kernel.. I think I should rebuild the kernel image with mkinitrd.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If I run the command multipath -v0 or 1 2 it doesnt show anything..&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;any idea?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;thanks in advance&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Apr 2013 02:54:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-is-on-a-multipathed-device-multipathd-can-not-be-stopped/m-p/6019793#M54195</guid>
      <dc:creator>techux</dc:creator>
      <dc:date>2013-04-04T02:54:14Z</dc:date>
    </item>
    <item>
      <title>Re: root is on a multipathed device multipathd can not be stopped</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-is-on-a-multipathed-device-multipathd-can-not-be-stopped/m-p/6022271#M54198</link>
      <description>&lt;P&gt;Not critical at all. The message is produced by a check in the /etc/init.d/multipathd script, which prevents stopping multipathd with e.g. "service multipathd stop" when the root filesystem is on a multipathed device.&lt;/P&gt;&lt;P&gt;While multipathd can safely be restarted while multipathed devices are in use, leaving it stopped for an extended period of time is not a good idea.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The writer of the /etc/init.d/multipathd script apparently has not included a special check to silence the message when the system is halting or rebooting.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When the root filesystem is on a multipathed device, having the multipathd running as far in to the halt/reboot procedure as possible (ideally all the way to the point where the kernel halts/reboots the system) is actually a good thing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; the other thing is if I update the system with yum update it wont boot with the new kernel.. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;gt; I think I should rebuild the kernel image with mkinitrd.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The installation procedure for the new kernel package already includes a mkinitrd step, so doing it manually won't do anything unless you fix the root cause first.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;You say "it won't boot". What exactly happens? Where does the boot process stop? Does it hang? Does it fall to single-user mode? Has it successfully mounted the root filesystem at that point? Has the kernel detected the multipathed SAS storage? If you needed a special driver RPM to make the multipathed SAS storage accessible with the old kernel, you might need to update that RPM too. If the updated RPM does not contain a pre-built driver for the new errata kernel, you might have to rebuild the module before rebuilding the initrd for the new kernel and booting with it. This can be a bit tricky: check the installation instructions of the driver RPM.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Before rebuilding the initrd, you should make sure the /etc/modprobe.conf includes the appropriate SAS adapter driver module:&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;The first scsi_hostadapter alias should be simply "alias scsi_hostadapter &amp;lt;module name&amp;gt;" and the &amp;lt;module name&amp;gt; should be the name of the driver module needed to access your root filesystem.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;The subsequent scsi_hostadapter aliases (if required) should be of the form "alias scsi_hostadapter&amp;lt;N&amp;gt; &amp;lt;module name&amp;gt;" where &amp;lt;N&amp;gt; is a number (starting with 1), and &amp;lt;module name&amp;gt; is the name of the required storage adapter driver module.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;If the above tips won't help you, please identify the exact server model &lt;STRONG&gt;and&lt;/STRONG&gt; the model of any multipathed add-on SAS controller card(s) used on your system.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&amp;gt; If I run the command multipath -v0 or 1 2 it doesnt show anything..&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;If "multipath -v2" does not display anything, it simply means the command thinks there is nothing for it to do: either there are no multipathed devices detected (= perhaps missing a SAS driver update?) or udev has already run it automatically. Run "multipath -ll" to see the current state of the multipath subsystem.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 06 Apr 2013 17:23:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-is-on-a-multipathed-device-multipathd-can-not-be-stopped/m-p/6022271#M54198</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2013-04-06T17:23:26Z</dc:date>
    </item>
  </channel>
</rss>

