<?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: runlevel script, runs in wrong order in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/runlevel-script-runs-in-wrong-order/m-p/4379221#M35595</link>
    <description>Hi smatador , thanks for the response/reply&lt;BR /&gt;&lt;BR /&gt;&amp;gt; What about chkconfig --list open-iscsi ?&lt;BR /&gt;# chkconfig --list open-iscsi&lt;BR /&gt;open-iscsi 0:off 1:off 2:off 3:on 4:off 5:on 6:off&lt;BR /&gt;&lt;BR /&gt;open-iscsi(iSCSI initiator Service) is running in runlevel 3 and 5, thats why I can see the iSCSI LUN&lt;BR /&gt;&lt;BR /&gt;# lsscsi&lt;BR /&gt;[0:0:0:0] disk IET VIRTUAL-DISK 0 /dev/sda&lt;BR /&gt;&lt;BR /&gt;# fdisk -l /dev/sda&lt;BR /&gt;&lt;BR /&gt;Disk /dev/sda: 5379 MB, 5379268608 bytes&lt;BR /&gt;166 heads, 62 sectors/track, 1020 cylinders&lt;BR /&gt;Units = cylinders of 10292 * 512 = 5269504 bytes&lt;BR /&gt;&lt;BR /&gt;Device Boot Start End Blocks Id System&lt;BR /&gt;/dev/sda1 1 1020 5248889 83 Linux&lt;BR /&gt;&lt;BR /&gt;&amp;gt; On the script of mountfs&lt;BR /&gt;Required-Start: $network $remote_fs $iscsi $netdaemons&lt;BR /&gt;&lt;BR /&gt;I did as you told, but still the script(mountfs) runs before the iSCSI initiator Service&lt;BR /&gt;&lt;BR /&gt;any how I got another good(dirty) solution/workaround, but I am still testing it. I will let the forum know about the solution/workaround very soon&lt;BR /&gt;&lt;BR /&gt;Regards</description>
    <pubDate>Mon, 16 Mar 2009 07:16:17 GMT</pubDate>
    <dc:creator>Maaz</dc:creator>
    <dc:date>2009-03-16T07:16:17Z</dc:date>
    <item>
      <title>runlevel script, runs in wrong order</title>
      <link>https://community.hpe.com/t5/operating-system-linux/runlevel-script-runs-in-wrong-order/m-p/4379219#M35593</link>
      <description>iSCSI-initiator(client) OS: SLES 10 SP2 x864&lt;BR /&gt;&lt;BR /&gt;on iSCSI-initiator, when system boots/starts, /dev/sda(iSCSI LUN) is visible/accessible/available&lt;BR /&gt;# lsscsi&lt;BR /&gt;[0:0:0:0]    disk    IET      VIRTUAL-DISK     0     /dev/sda&lt;BR /&gt;&lt;BR /&gt;# fdisk -l /dev/sda&lt;BR /&gt;&lt;BR /&gt;Disk /dev/sda: 5379 MB, 5379268608 bytes&lt;BR /&gt;166 heads, 62 sectors/track, 1020 cylinders&lt;BR /&gt;Units = cylinders of 10292 * 512 = 5269504 bytes&lt;BR /&gt;&lt;BR /&gt;   Device Boot      Start         End      Blocks   Id  System&lt;BR /&gt;/dev/sda1               1        1020     5248889   83  Linux&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;on iSCSI-initiator /etc/init.d/mountfs(attached) is a script, that mounts /dev/sda1(iSCSI LUN) on /data&lt;BR /&gt;&lt;BR /&gt;# chkconfig mountfs on&lt;BR /&gt;# chkconfig --list mountfs&lt;BR /&gt;# chkconfig --list mountfs&lt;BR /&gt;mountfs                   0:off  1:off  2:off  3:on   4:off  5:on   6:off&lt;BR /&gt;&lt;BR /&gt;# ls -l /etc/init.d/rc3.d/S05network&lt;BR /&gt;lrwxrwxrwx 1 root root 10 Mar 12 01:19 /etc/init.d/rc3.d/S05network -&amp;gt; ../network&lt;BR /&gt;&lt;BR /&gt;# ls -l /etc/init.d/rc3.d/S06open-iscsi&lt;BR /&gt;lrwxrwxrwx 1 root root 13 Mar 13  2009 /etc/init.d/rc3.d/S06open-iscsi -&amp;gt; ../open-iscsi&lt;BR /&gt;&lt;BR /&gt;# ls -l /etc/init.d/rc3.d/S11mountfs&lt;BR /&gt;lrwxrwxrwx 1 root root 10 Mar 14  2009 /etc/init.d/rc3.d/S11mountfs -&amp;gt; ../mountfs&lt;BR /&gt;&lt;BR /&gt;when I manually run "/etc/init.d/mountfs start", the script mounts /dev/sda1 on /data&lt;BR /&gt;when I manually run "/etc/init.d/mountfs stop", the script unmounts /dev/sda1&lt;BR /&gt;&lt;BR /&gt;Problem&lt;BR /&gt;--------&lt;BR /&gt;on system startup/boot "/etc/init.d/mountfs" fails to run automatically with the following message on console&lt;BR /&gt;&lt;BR /&gt;mounting LUN(SAN disk): mount: special device /dev/sda1 does not exist&lt;BR /&gt;                                                                                         failed&lt;BR /&gt;&lt;BR /&gt;Reason&lt;BR /&gt;------&lt;BR /&gt;on system startup/boot, OS(SUSE) runs the script(/etc/init.d/mountfs) before starting/running the iSCSI initiator service, thats why(I think) "/etc/init.d/mountfs" doesnt able access/mount /dev/sda1&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Please help, where I am doing wrong ? or is it a  bug ?&lt;BR /&gt;&lt;BR /&gt;attached is the script, and console messages(that shows the startup order of scripts)</description>
      <pubDate>Sat, 14 Mar 2009 07:27:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/runlevel-script-runs-in-wrong-order/m-p/4379219#M35593</guid>
      <dc:creator>Maaz</dc:creator>
      <dc:date>2009-03-14T07:27:21Z</dc:date>
    </item>
    <item>
      <title>Re: runlevel script, runs in wrong order</title>
      <link>https://community.hpe.com/t5/operating-system-linux/runlevel-script-runs-in-wrong-order/m-p/4379220#M35594</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;What about chkconfig --list open-iscsi ?&lt;BR /&gt;In the console message the mountfs appear first, it should be after the open-iscsi.&lt;BR /&gt;Put the open-isci first and the mountfs at the end.&lt;BR /&gt;On the script of mountfs&lt;BR /&gt;Required-Start:    $network $remote_fs $iscsi $netdaemons &lt;BR /&gt;</description>
      <pubDate>Sat, 14 Mar 2009 11:03:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/runlevel-script-runs-in-wrong-order/m-p/4379220#M35594</guid>
      <dc:creator>smatador</dc:creator>
      <dc:date>2009-03-14T11:03:30Z</dc:date>
    </item>
    <item>
      <title>Re: runlevel script, runs in wrong order</title>
      <link>https://community.hpe.com/t5/operating-system-linux/runlevel-script-runs-in-wrong-order/m-p/4379221#M35595</link>
      <description>Hi smatador , thanks for the response/reply&lt;BR /&gt;&lt;BR /&gt;&amp;gt; What about chkconfig --list open-iscsi ?&lt;BR /&gt;# chkconfig --list open-iscsi&lt;BR /&gt;open-iscsi 0:off 1:off 2:off 3:on 4:off 5:on 6:off&lt;BR /&gt;&lt;BR /&gt;open-iscsi(iSCSI initiator Service) is running in runlevel 3 and 5, thats why I can see the iSCSI LUN&lt;BR /&gt;&lt;BR /&gt;# lsscsi&lt;BR /&gt;[0:0:0:0] disk IET VIRTUAL-DISK 0 /dev/sda&lt;BR /&gt;&lt;BR /&gt;# fdisk -l /dev/sda&lt;BR /&gt;&lt;BR /&gt;Disk /dev/sda: 5379 MB, 5379268608 bytes&lt;BR /&gt;166 heads, 62 sectors/track, 1020 cylinders&lt;BR /&gt;Units = cylinders of 10292 * 512 = 5269504 bytes&lt;BR /&gt;&lt;BR /&gt;Device Boot Start End Blocks Id System&lt;BR /&gt;/dev/sda1 1 1020 5248889 83 Linux&lt;BR /&gt;&lt;BR /&gt;&amp;gt; On the script of mountfs&lt;BR /&gt;Required-Start: $network $remote_fs $iscsi $netdaemons&lt;BR /&gt;&lt;BR /&gt;I did as you told, but still the script(mountfs) runs before the iSCSI initiator Service&lt;BR /&gt;&lt;BR /&gt;any how I got another good(dirty) solution/workaround, but I am still testing it. I will let the forum know about the solution/workaround very soon&lt;BR /&gt;&lt;BR /&gt;Regards</description>
      <pubDate>Mon, 16 Mar 2009 07:16:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/runlevel-script-runs-in-wrong-order/m-p/4379221#M35595</guid>
      <dc:creator>Maaz</dc:creator>
      <dc:date>2009-03-16T07:16:17Z</dc:date>
    </item>
  </channel>
</rss>

