<?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: command exeution prob. at /root in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/command-exeution-prob-at-root/m-p/4866267#M397570</link>
    <description>Dear All,&lt;BR /&gt;&lt;BR /&gt;Thanks for the response. The problem is resolved.&lt;BR /&gt;I had to restart the Array and the server.&lt;BR /&gt;So its got connected to that Controller, may be some link failure was there.&lt;BR /&gt;&lt;BR /&gt;Rgds&lt;BR /&gt;Jack</description>
    <pubDate>Wed, 20 Oct 2004 08:26:52 GMT</pubDate>
    <dc:creator>Jack_126</dc:creator>
    <dc:date>2004-10-20T08:26:52Z</dc:date>
    <item>
      <title>command exeution prob. at /root</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/command-exeution-prob-at-root/m-p/4866261#M397564</link>
      <description>Dear All,&lt;BR /&gt;I am not able the run the ls or bdf at the root. Whereas if I go to some directory, I cal run ls command. The error in syslog I am attaching , so far server is running and oracle users are working.Why this happend and how to come out without shutting down the server.&lt;BR /&gt;&lt;BR /&gt;Oct 20 08:46:26 ERP3 vmunix: LVM: Path (device 0x1f040200) to PV 1 in VG 3 Faile&lt;BR /&gt;d!&lt;BR /&gt;Oct 20 08:46:26 ERP3 vmunix: LVM: Path (device 0x1f040300) to PV 2 in VG 3 Faile&lt;BR /&gt;d!&lt;BR /&gt;Oct 20 08:46:26 ERP3 vmunix: LVM: vg[3]: pvnum=0 (dev_t=0x1f040100) is POWERFAIL&lt;BR /&gt;ED&lt;BR /&gt;Oct 20 08:46:26 ERP3 vmunix: LVM: vg[3]: pvnum=1 (dev_t=0x1f040200) is POWERFAIL&lt;BR /&gt;ED&lt;BR /&gt;Oct 20 08:46:26 ERP3 vmunix: LVM: vg[3]: pvnum=2 (dev_t=0x1f040300) is POWERFAIL</description>
      <pubDate>Wed, 20 Oct 2004 04:23:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/command-exeution-prob-at-root/m-p/4866261#M397564</guid>
      <dc:creator>Jack_126</dc:creator>
      <dc:date>2004-10-20T04:23:01Z</dc:date>
    </item>
    <item>
      <title>Re: command exeution prob. at /root</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/command-exeution-prob-at-root/m-p/4866262#M397565</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Looks like HW problem coming up . &lt;BR /&gt;&lt;BR /&gt;Look at ls -1 /root&lt;BR /&gt;&lt;BR /&gt;If that works you have corruption or a file name with a space or something in it in the root directory&lt;BR /&gt;&lt;BR /&gt;try&lt;BR /&gt;&lt;BR /&gt;cd /root&lt;BR /&gt;ls -1|while read line&lt;BR /&gt;do&lt;BR /&gt;echo $line&lt;BR /&gt;ll -d $line&lt;BR /&gt;done&lt;BR /&gt;&lt;BR /&gt;If it hangs the last line printed is the problem.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;                    Steve Steel</description>
      <pubDate>Wed, 20 Oct 2004 04:34:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/command-exeution-prob-at-root/m-p/4866262#M397565</guid>
      <dc:creator>Steve Steel</dc:creator>
      <dc:date>2004-10-20T04:34:53Z</dc:date>
    </item>
    <item>
      <title>Re: command exeution prob. at /root</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/command-exeution-prob-at-root/m-p/4866263#M397566</link>
      <description>An HArdware failure can be any of the disks in VG3 or the SCSI channel which consists VG3 is going to fail.What is look in #ioscan -fnC disk&lt;BR /&gt;&lt;BR /&gt;do u have any EMS configured,check if available&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;SK&lt;BR /&gt;</description>
      <pubDate>Wed, 20 Oct 2004 05:49:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/command-exeution-prob-at-root/m-p/4866263#M397566</guid>
      <dc:creator>Sยภเl Kย๓คг</dc:creator>
      <dc:date>2004-10-20T05:49:20Z</dc:date>
    </item>
    <item>
      <title>Re: command exeution prob. at /root</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/command-exeution-prob-at-root/m-p/4866264#M397567</link>
      <description>An NFS (remotely mounted) filesystem can cause ls and bdf to hang.  Check for a networking problem here.&lt;BR /&gt;&lt;BR /&gt;The syslog messages indicate a problem with the 3 disks in volume group 3: &lt;BR /&gt;device 0x1f040200&lt;BR /&gt;device 0x1f040300&lt;BR /&gt;dev_t=0x1f040100&lt;BR /&gt;&lt;BR /&gt;To determine the devices:&lt;BR /&gt;# ll /dev/dsk |grep 040?00&lt;BR /&gt;&lt;BR /&gt;If these disks are in a cabinet, check cabling and power.  It might be as simple as that.&lt;BR /&gt;&lt;BR /&gt;# ioscan -fnC disk&lt;BR /&gt;Look for NO_HW or completely missing disks.  (This is a hardware problem.)&lt;BR /&gt;# diskinfo -v /dev/rdsk/cXtXdX&lt;BR /&gt;Look for problems.  (This is a hardware problem.)&lt;BR /&gt;&lt;BR /&gt;If there are no SCSI lbolt messages, this is probably not a hardware fault, but you may only need to increase the timeout.&lt;BR /&gt;&lt;BR /&gt;Check the timeout with pvdisplay.  If it says default, increase it with:&lt;BR /&gt;# pvchange -t 180 /dev/dsk/cXtXdX&lt;BR /&gt;&lt;BR /&gt;Watch for further errors.  If they continue or if there are other SCSI errors, then contact Hardware Support.&lt;BR /&gt;</description>
      <pubDate>Wed, 20 Oct 2004 06:07:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/command-exeution-prob-at-root/m-p/4866264#M397567</guid>
      <dc:creator>Cheryl Griffin</dc:creator>
      <dc:date>2004-10-20T06:07:07Z</dc:date>
    </item>
    <item>
      <title>Re: command exeution prob. at /root</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/command-exeution-prob-at-root/m-p/4866265#M397568</link>
      <description>Dear All,&lt;BR /&gt;The following error found. Its VA7110 having two controllers. itseems one controller is not working/faulty. But as its configured as RAID 0+1. I should be able to work with the volumes created on it. Here I ma not able to connect to the volumes. So far I have not restarted my server. The HDD in array showing all green lights which means there should not be any prob. with the HDDs.The o/p of ioscan is this...&lt;BR /&gt;disk      3  0/3/1/0/4/0.1.0.0.0.0.0  sdisk    NO_HW       DEVICE       HP      A6189B&lt;BR /&gt;                           /dev/dsk/c4t0d0   /dev/rdsk/c4t0d0&lt;BR /&gt;disk     11  0/3/1/0/4/0.1.0.0.0.0.1  sdisk    NO_HW       DEVICE       HP      A6189B&lt;BR /&gt;                           /dev/dsk/c4t0d1   /dev/rdsk/c4t0d1&lt;BR /&gt;disk     16  0/3/1/0/4/0.1.0.0.0.0.2  sdisk    NO_HW       DEVICE       HP      A6189B&lt;BR /&gt;                           /dev/dsk/c4t0d2   /dev/rdsk/c4t0d2&lt;BR /&gt;disk     19  0/3/1/0/4/0.1.0.0.0.0.3  sdisk    NO_HW       DEVICE       HP      A6189B&lt;BR /&gt;                           /dev/dsk/c4t0d3   /dev/rdsk/c4t0d3&lt;BR /&gt;disk      4  0/3/1/0/4/0.1.1.0.0.0.0  sdisk    NO_HW       DEVICE       HP      A6189B&lt;BR /&gt;                           /dev/dsk/c6t0d0   /dev/rdsk/c6t0d0&lt;BR /&gt;disk      8  0/3/1/0/4/0.1.1.0.0.0.1  sdisk    NO_HW       DEVICE       HP      A6189B&lt;BR /&gt;                           /dev/dsk/c6t0d1   /dev/rdsk/c6t0d1&lt;BR /&gt;disk     12  0/3/1/0/4/0.1.1.0.0.0.2  sdisk    NO_HW       DEVICE       HP      A6189B&lt;BR /&gt;                           /dev/dsk/c6t0d2   /dev/rdsk/c6t0d2&lt;BR /&gt;disk     15  0/3/1/0/4/0.1.1.0.0.0.3  sdisk    NO_HW       DEVICE       HP      A6189B&lt;BR /&gt;                           /dev/dsk/c6t0d3   /dev/rdsk/c6t0d3&lt;BR /&gt;disk      5  0/4/1/0/4/0.1.0.0.0.0.0  sdisk    CLAIMED     DEVICE       HP      A6189B&lt;BR /&gt;                           /dev/dsk/c8t0d0   /dev/rdsk/c8t0d0&lt;BR /&gt;disk     10  0/4/1/0/4/0.1.0.0.0.0.1  sdisk    CLAIMED     DEVICE       HP      A6189B&lt;BR /&gt;                           /dev/dsk/c8t0d1   /dev/rdsk/c8t0d1&lt;BR /&gt;disk     14  0/4/1/0/4/0.1.0.0.0.0.2  sdisk    CLAIMED     DEVICE       HP      A6189B&lt;BR /&gt;                           /dev/dsk/c8t0d2   /dev/rdsk/c8t0d2&lt;BR /&gt;disk     18  0/4/1/0/4/0.1.0.0.0.0.3  sdisk    CLAIMED     DEVICE       HP      A6189B&lt;BR /&gt;                           /dev/dsk/c8t0d3   /dev/rdsk/c8t0d3&lt;BR /&gt;disk      6  0/4/1/0/4/0.1.1.0.0.0.0  sdisk    CLAIMED     DEVICE       HP      A6189B&lt;BR /&gt;                           /dev/dsk/c10t0d0   /dev/rdsk/c10t0d0&lt;BR /&gt;disk      9  0/4/1/0/4/0.1.1.0.0.0.1  sdisk    CLAIMED     DEVICE       HP      A6189B&lt;BR /&gt;                           /dev/dsk/c10t0d1   /dev/rdsk/c10t0d1&lt;BR /&gt;disk     13  0/4/1/0/4/0.1.1.0.0.0.2  sdisk    CLAIMED     DEVICE       HP      A6189B&lt;BR /&gt;                           /dev/dsk/c10t0d2   /dev/rdsk/c10t0d2&lt;BR /&gt;disk     17  0/4/1/0/4/0.1.1.0.0.0.3  sdisk    CLAIMED     DEVICE       HP      A6189B&lt;BR /&gt;                           /dev/dsk/c10t0d3   /dev/rdsk/c10t0d3&lt;BR /&gt;&lt;BR /&gt;any way to make it work without restarting the server. &lt;BR /&gt;</description>
      <pubDate>Wed, 20 Oct 2004 06:41:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/command-exeution-prob-at-root/m-p/4866265#M397568</guid>
      <dc:creator>Jack_126</dc:creator>
      <dc:date>2004-10-20T06:41:00Z</dc:date>
    </item>
    <item>
      <title>Re: command exeution prob. at /root</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/command-exeution-prob-at-root/m-p/4866266#M397569</link>
      <description>You can try:&lt;BR /&gt;&lt;BR /&gt;ioscan -fuC disk&lt;BR /&gt;insf -C disk&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Wed, 20 Oct 2004 08:05:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/command-exeution-prob-at-root/m-p/4866266#M397569</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2004-10-20T08:05:31Z</dc:date>
    </item>
    <item>
      <title>Re: command exeution prob. at /root</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/command-exeution-prob-at-root/m-p/4866267#M397570</link>
      <description>Dear All,&lt;BR /&gt;&lt;BR /&gt;Thanks for the response. The problem is resolved.&lt;BR /&gt;I had to restart the Array and the server.&lt;BR /&gt;So its got connected to that Controller, may be some link failure was there.&lt;BR /&gt;&lt;BR /&gt;Rgds&lt;BR /&gt;Jack</description>
      <pubDate>Wed, 20 Oct 2004 08:26:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/command-exeution-prob-at-root/m-p/4866267#M397570</guid>
      <dc:creator>Jack_126</dc:creator>
      <dc:date>2004-10-20T08:26:52Z</dc:date>
    </item>
  </channel>
</rss>

