<?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: disk belly up? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-belly-up/m-p/2834766#M89842</link>
    <description>I'll be bringing it down tomorrow AM. Thanks for the input. Points assigned.&lt;BR /&gt;&lt;BR /&gt;Randy</description>
    <pubDate>Mon, 28 Oct 2002 23:33:27 GMT</pubDate>
    <dc:creator>Randy_9</dc:creator>
    <dc:date>2002-10-28T23:33:27Z</dc:date>
    <item>
      <title>disk belly up?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-belly-up/m-p/2834763#M89839</link>
      <description>I believe I am seeing the demise of one of my disks.&lt;BR /&gt;&lt;BR /&gt;From /var/adm/syslog/syslog.log&lt;BR /&gt;&lt;BR /&gt;Oct 28 13:10:10 isis vmunix: &lt;BR /&gt;Oct 28 13:14:28 isis  above message repeats 3 times&lt;BR /&gt;Oct 28 13:14:55 isis vmunix: I/O hardware probe timed out&lt;BR /&gt;Oct 28 13:14:55 isis vmunix: Last successful probe at path 8/16/5.2&lt;BR /&gt;Oct 28 13:15:14 isis vmunix: &lt;BR /&gt;Oct 28 13:15:14 isis vmunix: SCSI: Request Timeout; Abort -- lbolt: 61100873, dev: bc013000, io_id: 10774a5&lt;BR /&gt;Oct 28 13:20:18 isis vmunix: SCSI: Request Timeout; Abort -- lbolt: 61131273, dev: bc013000, io_id: 10774a5&lt;BR /&gt;Oct 28 13:25:22 isis vmunix: SCSI: Request Timeout; Abort -- lbolt: 61161673, dev: bc013000, io_id: 10774a5&lt;BR /&gt;&lt;BR /&gt;/dev/dsk: (One of 5 disks)&lt;BR /&gt;brw-r-----   1 bin        sys         31 0x013000 Aug 16  2001 c1t3d0&lt;BR /&gt;&lt;BR /&gt;From an old "diskinfo" query record:&lt;BR /&gt;disk      4  8/16/5.3.0  sdisk       NO_HW     DEVICE    SEAGATE ST32550W&lt;BR /&gt;                        /dev/dsk/c1t3d0   /dev/rdsk/c1t3d0&lt;BR /&gt;&lt;BR /&gt;The "ioscan" command hangs, and I have to terminate the window the end the process.&lt;BR /&gt;&lt;BR /&gt;I don't see this disk as being configured via "vgdisplay" for the VG's on this system.&lt;BR /&gt;&lt;BR /&gt;Thoughts....&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Randy</description>
      <pubDate>Mon, 28 Oct 2002 23:10:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-belly-up/m-p/2834763#M89839</guid>
      <dc:creator>Randy_9</dc:creator>
      <dc:date>2002-10-28T23:10:13Z</dc:date>
    </item>
    <item>
      <title>Re: disk belly up?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-belly-up/m-p/2834764#M89840</link>
      <description>Hi Randy,&lt;BR /&gt;&lt;BR /&gt;From what you have listed, i agree that the disk is giving issues. You may try rebooting the box in single user mode. &lt;BR /&gt;&lt;BR /&gt;If there is any issue with the driver configuration, the box will automatically reconfigure it. Else, get ready to call HP for replacement.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Anil</description>
      <pubDate>Mon, 28 Oct 2002 23:21:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-belly-up/m-p/2834764#M89840</guid>
      <dc:creator>Anil C. Sedha</dc:creator>
      <dc:date>2002-10-28T23:21:26Z</dc:date>
    </item>
    <item>
      <title>Re: disk belly up?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-belly-up/m-p/2834765#M89841</link>
      <description>Randy,&lt;BR /&gt;&lt;BR /&gt;I would agree that your disk is most likely in need of being replaced.  You could most likely run an ioscan command for anything but disks and get it to return without hanging.  Something like ioscan-fnC tape for instance.  You can do a strings /etc/lvmtab to see if this disk is part of a volume group.  Regardless, I'd open a call for hardware support if your disk is covered.&lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;Eric</description>
      <pubDate>Mon, 28 Oct 2002 23:24:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-belly-up/m-p/2834765#M89841</guid>
      <dc:creator>erics_1</dc:creator>
      <dc:date>2002-10-28T23:24:34Z</dc:date>
    </item>
    <item>
      <title>Re: disk belly up?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-belly-up/m-p/2834766#M89842</link>
      <description>I'll be bringing it down tomorrow AM. Thanks for the input. Points assigned.&lt;BR /&gt;&lt;BR /&gt;Randy</description>
      <pubDate>Mon, 28 Oct 2002 23:33:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-belly-up/m-p/2834766#M89842</guid>
      <dc:creator>Randy_9</dc:creator>
      <dc:date>2002-10-28T23:33:27Z</dc:date>
    </item>
    <item>
      <title>Re: disk belly up?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-belly-up/m-p/2834767#M89843</link>
      <description>As you are not seeing any disks it could be a controller/cable issue.  The addresses do not match; the error is at 8/16/5.2, but the disk you are talking about is 8/16/5.3&lt;BR /&gt;&lt;BR /&gt;Alan&lt;BR /&gt;</description>
      <pubDate>Wed, 30 Oct 2002 23:15:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-belly-up/m-p/2834767#M89843</guid>
      <dc:creator>Alan Edwards</dc:creator>
      <dc:date>2002-10-30T23:15:27Z</dc:date>
    </item>
  </channel>
</rss>

