<?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 Cause of and action upon SCSI bus disconnects in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cause-of-and-action-upon-scsi-bus-disconnects/m-p/3441920#M207447</link>
    <description>Hello,&lt;BR /&gt;  &lt;BR /&gt;we have this&lt;BR /&gt; &lt;BR /&gt;# model;uname -srv&lt;BR /&gt;9000/804/K450&lt;BR /&gt;HP-UX B.11.11 U&lt;BR /&gt; &lt;BR /&gt;which is exhibiting quite a lot of SCSI bus disconnects&lt;BR /&gt; &lt;BR /&gt;# grep vmunix /var/adm/syslog/syslog.log|tail&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571835, dev: cb00e002, io_id: d1&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571836, dev: cb00e002, io_id: d1&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571833, dev: cb00e002, io_id: d1&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571837, dev: cb00e002, io_id: d1&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571838, dev: cb00f002, io_id: d2&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571839, dev: cb00f002, io_id: d2&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571840, dev: cb00f002, io_id: d2&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571841, dev: cb00f002, io_id: d2&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571838, dev: cb00f002, io_id: d2&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571842, dev: cb00f002, io_id: d2&lt;BR /&gt; &lt;BR /&gt;# grep -c 'SCSI: Unexpected Disconnect' /var/adm/syslog/syslog.log|tail&lt;BR /&gt;2485&lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt;To me this looks like a termination problem, or similar.&lt;BR /&gt; &lt;BR /&gt;The volumes however are all in sync&lt;BR /&gt; &lt;BR /&gt;# lvdisplay -v $(vgdisplay -v|awk '/LV Name/{print$NF}')|grep -ic stale&lt;BR /&gt;0&lt;BR /&gt;  &lt;BR /&gt; &lt;BR /&gt;And a look at the disks with OnlineDiag showed no errors.&lt;BR /&gt; &lt;BR /&gt;On the other hand this box'es patch level is a bit obsolete.&lt;BR /&gt;For instance I'm sure there will be a more recent SCSI patch (which may have fixed some hoax SCSI bus errors, who knows?)&lt;BR /&gt; &lt;BR /&gt;# swlist -l fileset -a create_date -a install_date -a title PHKL_25896|sed -n 5,\$p&lt;BR /&gt;#&lt;BR /&gt; &lt;BR /&gt;# PHKL_25896                            Fri Dec 27 13:46:12 MET 2002 200212270852.50 SCSI IO Cumulati&lt;BR /&gt;ve Patch &lt;BR /&gt;  PHKL_25896.C-INC                      Fri Dec 27 13:46:12 MET 2002 200212270852.50 ProgSupport.C-IN&lt;BR /&gt;C &lt;BR /&gt;  PHKL_25896.CORE2-KRN                  Fri Dec 27 13:46:12 MET 2002 200212270852.50 OS-Core.CORE2-KR&lt;BR /&gt;N &lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt;First, how do I translate the device hex identifier from syslog entries to single out the affected devices?&lt;BR /&gt; &lt;BR /&gt;Then what would you recommend?&lt;BR /&gt;Though the syslog SCSI errors have disappeared since Dec 10th, which also happened the date of last reboot&lt;BR /&gt; &lt;BR /&gt;# who -b&lt;BR /&gt;   .       system boot  Dec 10 13:33&lt;BR /&gt;  &lt;BR /&gt;I think this requires further investigation.&lt;BR /&gt; &lt;BR /&gt;Regards&lt;BR /&gt;Ralph&lt;BR /&gt;</description>
    <pubDate>Mon, 13 Dec 2004 04:06:02 GMT</pubDate>
    <dc:creator>Ralph Grothe</dc:creator>
    <dc:date>2004-12-13T04:06:02Z</dc:date>
    <item>
      <title>Cause of and action upon SCSI bus disconnects</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cause-of-and-action-upon-scsi-bus-disconnects/m-p/3441920#M207447</link>
      <description>Hello,&lt;BR /&gt;  &lt;BR /&gt;we have this&lt;BR /&gt; &lt;BR /&gt;# model;uname -srv&lt;BR /&gt;9000/804/K450&lt;BR /&gt;HP-UX B.11.11 U&lt;BR /&gt; &lt;BR /&gt;which is exhibiting quite a lot of SCSI bus disconnects&lt;BR /&gt; &lt;BR /&gt;# grep vmunix /var/adm/syslog/syslog.log|tail&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571835, dev: cb00e002, io_id: d1&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571836, dev: cb00e002, io_id: d1&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571833, dev: cb00e002, io_id: d1&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571837, dev: cb00e002, io_id: d1&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571838, dev: cb00f002, io_id: d2&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571839, dev: cb00f002, io_id: d2&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571840, dev: cb00f002, io_id: d2&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571841, dev: cb00f002, io_id: d2&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571838, dev: cb00f002, io_id: d2&lt;BR /&gt;Dec 10 15:06:19 tiber vmunix: SCSI: Unexpected Disconnect -- lbolt: 571842, dev: cb00f002, io_id: d2&lt;BR /&gt; &lt;BR /&gt;# grep -c 'SCSI: Unexpected Disconnect' /var/adm/syslog/syslog.log|tail&lt;BR /&gt;2485&lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt;To me this looks like a termination problem, or similar.&lt;BR /&gt; &lt;BR /&gt;The volumes however are all in sync&lt;BR /&gt; &lt;BR /&gt;# lvdisplay -v $(vgdisplay -v|awk '/LV Name/{print$NF}')|grep -ic stale&lt;BR /&gt;0&lt;BR /&gt;  &lt;BR /&gt; &lt;BR /&gt;And a look at the disks with OnlineDiag showed no errors.&lt;BR /&gt; &lt;BR /&gt;On the other hand this box'es patch level is a bit obsolete.&lt;BR /&gt;For instance I'm sure there will be a more recent SCSI patch (which may have fixed some hoax SCSI bus errors, who knows?)&lt;BR /&gt; &lt;BR /&gt;# swlist -l fileset -a create_date -a install_date -a title PHKL_25896|sed -n 5,\$p&lt;BR /&gt;#&lt;BR /&gt; &lt;BR /&gt;# PHKL_25896                            Fri Dec 27 13:46:12 MET 2002 200212270852.50 SCSI IO Cumulati&lt;BR /&gt;ve Patch &lt;BR /&gt;  PHKL_25896.C-INC                      Fri Dec 27 13:46:12 MET 2002 200212270852.50 ProgSupport.C-IN&lt;BR /&gt;C &lt;BR /&gt;  PHKL_25896.CORE2-KRN                  Fri Dec 27 13:46:12 MET 2002 200212270852.50 OS-Core.CORE2-KR&lt;BR /&gt;N &lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt;First, how do I translate the device hex identifier from syslog entries to single out the affected devices?&lt;BR /&gt; &lt;BR /&gt;Then what would you recommend?&lt;BR /&gt;Though the syslog SCSI errors have disappeared since Dec 10th, which also happened the date of last reboot&lt;BR /&gt; &lt;BR /&gt;# who -b&lt;BR /&gt;   .       system boot  Dec 10 13:33&lt;BR /&gt;  &lt;BR /&gt;I think this requires further investigation.&lt;BR /&gt; &lt;BR /&gt;Regards&lt;BR /&gt;Ralph&lt;BR /&gt;</description>
      <pubDate>Mon, 13 Dec 2004 04:06:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cause-of-and-action-upon-scsi-bus-disconnects/m-p/3441920#M207447</guid>
      <dc:creator>Ralph Grothe</dc:creator>
      <dc:date>2004-12-13T04:06:02Z</dc:date>
    </item>
    <item>
      <title>Re: Cause of and action upon SCSI bus disconnects</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cause-of-and-action-upon-scsi-bus-disconnects/m-p/3441921#M207448</link>
      <description>Hi Ralf,&lt;BR /&gt;It reminds me a failure I had few years ago, a root mirrored disk failure...&lt;BR /&gt;With the bad side of it the disk was disrupting time to time but did never crash or break definitely. In had unexplained crashes but coulnd diagnose because after the reboot all was fine till the next time (few days-few weeks) th crash was due to sharing on the same scsi controller a HDS 5750 subsystem with internal root disks and at each time it was going bezerk, it sent a reset that the HDS acknowledged. it was looking at the HDS logs I found out: thousands of reset were done. I called HDS saying this can happen when a disk fails but not completely, switching istelf on/off the crashes wer due to swap I had on the HDS...&lt;BR /&gt;&lt;BR /&gt;The difficulty was to decide which internal mirrored disk was causing all the trouble since after every reboot EMS found nothing...&lt;BR /&gt;One support Enginner asked me a type a now forgotten command which did return as error blaming the other disk, I was asked which disk was faulty and we changed the OTHER one, Ive been told experience shows that devices can often lie and blame the alter ego...&lt;BR /&gt;And the problem was solved...&lt;BR /&gt;&lt;BR /&gt;So I would keep an eye on this system to se if you have more occurences...&lt;BR /&gt;&lt;BR /&gt;cb would be 203:&lt;BR /&gt; # pwd&lt;BR /&gt;/dev/dsk&lt;BR /&gt; # ll|more&lt;BR /&gt;total 0&lt;BR /&gt;brw-r-----   1 bin        sys         31 0x003000 Feb 26  2002 c0t3d0&lt;BR /&gt;brw-r-----   1 bin        sys         31 0x012000 Feb  5  2002 c1t2d0&lt;BR /&gt;cr--------   1 root       root       203 0x012000 Feb 26  2002 c1t2d0.pt&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;these are the vg00 disks and one time I did have vxvm...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Good luck&lt;BR /&gt;&lt;BR /&gt;All the best&lt;BR /&gt;Victor&lt;BR /&gt;</description>
      <pubDate>Mon, 13 Dec 2004 05:14:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cause-of-and-action-upon-scsi-bus-disconnects/m-p/3441921#M207448</guid>
      <dc:creator>Victor BERRIDGE</dc:creator>
      <dc:date>2004-12-13T05:14:18Z</dc:date>
    </item>
  </channel>
</rss>

