<?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: system panic ,anyone can help? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/system-panic-anyone-can-help/m-p/3693560#M247657</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;One of the reasons of such system panic buring bootup is unable to mount "root" filesystem.&lt;BR /&gt;&lt;BR /&gt;You can try to boot using old kernel &lt;BR /&gt;ISL &amp;gt; hpux -lm /stand/vmunix.prev&lt;BR /&gt;Don't use (;0) while booting.&lt;BR /&gt;&lt;BR /&gt;Another probable cause could be bad super block of the root file system. In this case you need to boot with core OS media and  run fsck -b &lt;ALT-BLOCK number=""&gt; &lt;ROOT-PARTITION&gt;&lt;BR /&gt;&lt;BR /&gt;If you have mirrored disk , try above with that disk.&lt;BR /&gt;&lt;BR /&gt;If you have changed anything like generating new kernel or SCSI card changed etc. revert it back.&lt;BR /&gt;&lt;BR /&gt;&lt;/ROOT-PARTITION&gt;&lt;/ALT-BLOCK&gt;</description>
    <pubDate>Sat, 17 Dec 2005 20:48:33 GMT</pubDate>
    <dc:creator>Sameer_Nirmal</dc:creator>
    <dc:date>2005-12-17T20:48:33Z</dc:date>
    <item>
      <title>system panic ,anyone can help?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-panic-anyone-can-help/m-p/3693557#M247654</link>
      <description>HP L2000 &lt;BR /&gt;&lt;BR /&gt;gsp chasis log&lt;BR /&gt;&lt;BR /&gt;Log Entry #   1 :&lt;BR /&gt;SYSTEM NAME: uninitialized&lt;BR /&gt;DATE: 01/01/1970 TIME: 00:02:12&lt;BR /&gt;ALERT LEVEL: 3 = System blocked waiting for operator input&lt;BR /&gt;&lt;BR /&gt;SOURCE: 1 = processor&lt;BR /&gt;SOURCE DETAIL: 1 = processor general   SOURCE ID: 0&lt;BR /&gt;PROBLEM DETAIL: 0 = no problem detail&lt;BR /&gt;&lt;BR /&gt;CALLER ACTIVITY: E = system warning   STATUS: 0&lt;BR /&gt;CALLER SUBACTIVITY: 00 = implementation dependent&lt;BR /&gt;REPORTING ENTITY TYPE: E = HP-UX   REPORTING ENTITY ID: 00&lt;BR /&gt;&lt;BR /&gt;0xF8E000301100E000 00000000 0000E000 type 31 = legacy PA HEX chassis-code&lt;BR /&gt;0x58E008301100E000 00004600 0100020C type 11 = Timestamp 01/01/1970 00:02:12&lt;BR /&gt;Type CR for next entry, - CR for previous entry, Q CR to quit.&lt;BR /&gt;&lt;BR /&gt;when booted the system ,it paused at following messages&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Main Menu: Enter command or menu &amp;gt; bo p1&lt;BR /&gt;Interact with IPL (Y, N, or Cancel)?&amp;gt; y&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Press Q/q to quit, Enter to continue: &lt;BR /&gt;&lt;BR /&gt;Booting... &lt;BR /&gt;Boot IO Dependent Code (IODC) revision 1&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;HARD Booted.&lt;BR /&gt;&lt;BR /&gt;ISL Revision A.00.38  OCT 26, 1994 &lt;BR /&gt;&lt;BR /&gt;ISL&amp;gt; hpux -lm (;0)/stand/vmunix&lt;BR /&gt;&lt;BR /&gt;Boot&lt;BR /&gt;: disk(0/0/1/1.0.0.0.0.0.0;0)/stand/vmunix&lt;BR /&gt;6692864 + 866040 + 1709296 start 0x212be8&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;alloc_pdc_pages: Relocating PDC from 0xf0f0000000 to 0x7f9ab000.&lt;BR /&gt;gate64: sysvec_vaddr = 0xc0002000 for 1 pages&lt;BR /&gt;&lt;BR /&gt;Press Q/q to quit, Enter to continue: &lt;BR /&gt;&lt;BR /&gt;NOTICE: autofs_link(): File system was registered at index 3.&lt;BR /&gt;NOTICE: nfs3_link(): File system was registered at index 5.&lt;BR /&gt;&lt;BR /&gt;    System Console is on the Built-In Serial Interface&lt;BR /&gt;Logical volume 64, 0x3 configured as ROOT&lt;BR /&gt;Logical volume 64, 0x2 configured as SWAP&lt;BR /&gt;Logical volume 64, 0x2 configured as DUMP&lt;BR /&gt;    Swap device table:  (start &amp;amp; size given in 512-byte blocks)&lt;BR /&gt;        entry 0 - major is 31, minor is 0x10003; start = 0, size = 2097152&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Press Q/q to quit, Enter to continue: &lt;BR /&gt;&lt;BR /&gt;linkstamp:          Sun Dec 11 16:14:05 EAT 2005&lt;BR /&gt;_release_version:   @(#)B2352B/9245XB HP-UX (B.11.00) #1: Wed Nov  5 22:38:19 PST 1997&lt;BR /&gt;__kern_ci_revision: $Header: kern_sequence.c,v 1.6.106.512 97/11/05 18:01:46 msosa Exp $&lt;BR /&gt;&lt;BR /&gt;panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ????? &lt;BR /&gt;&lt;BR /&gt;PC-Offset Stack Trace (read across, top of stack is 1st):&lt;BR /&gt;  0x002db93c  0x003549dc  0x0026c748&lt;BR /&gt;  0x0010651c  0x0021314c&lt;BR /&gt;End Of Stack&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Press Q/q to quit, Enter to continue: q&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;some other messages below&lt;BR /&gt;&lt;BR /&gt;gate64: sysvec_vaddr = 0xc0002000 for 1 pages&lt;BR /&gt;NOTICE: autofs_link(): File system was registered at index 3.&lt;BR /&gt;NOTICE: nfs3_link(): File system was registered at index 5.&lt;BR /&gt;&lt;BR /&gt;    System Console is on the Built-In Serial Interface&lt;BR /&gt;Logical volume 64, 0x3 configured as ROOT&lt;BR /&gt;Logical volume 64, 0x2 configured as SWAP&lt;BR /&gt;Logical volume 64, 0x2 configured as DUMP&lt;BR /&gt;    Swap device table:  (start &amp;amp; size given in 512-byte blocks)&lt;BR /&gt;        entry 0 - major is 31, minor is 0x10003; &lt;BR /&gt;&lt;BR /&gt;start = 0, size = 2097152&lt;BR /&gt;&lt;BR /&gt;************* SYSTEM ALERT **************&lt;BR /&gt;SYSTEM NAME: uninitialized&lt;BR /&gt;DATE: 01/01/1970 TIME: 00:02:05&lt;BR /&gt;ALERT LEVEL: 12 = Software failure&lt;BR /&gt;&lt;BR /&gt;REASON FOR ALERT&lt;BR /&gt;SOURCE: 1 = processor&lt;BR /&gt;SOURCE DETAIL: 1 = processor general   SOURCE ID: 0&lt;BR /&gt;PROBLEM DETAIL: 0 = no problem detail&lt;BR /&gt;&lt;BR /&gt;LEDs:  RUN      ATTENTION     FAULT     REMOTE     POWER&lt;BR /&gt;       FLASH    OFF           OFF       ON         ON&lt;BR /&gt;&lt;BR /&gt;0xF8E000C01100B800 00000000 0000B800 - type 31 = legacy PA HEX chassis-code&lt;BR /&gt;0x58E008C01100B800 00004600 01000205 - type 11 = Timestamp 01/01/1970 00:02:05&lt;BR /&gt;A: ack read of this entry - X: Disable all future alert messages&lt;BR /&gt;Anything else skip redisplay the log entry&lt;BR /&gt;-&amp;gt;Choice:Timeout!&lt;BR /&gt;*****************************************&lt;BR /&gt;&lt;BR /&gt;************* SYSTEM ALERT **************&lt;BR /&gt;SYSTEM NAME: uninitialized&lt;BR /&gt;DATE: 01/01/1970 TIME: 00:02:05&lt;BR /&gt;ALERT LEVEL: 12 = Software failure&lt;BR /&gt;&lt;BR /&gt;REASON FOR ALERT&lt;BR /&gt;SOURCE: 1 = processor&lt;BR /&gt;SOURCE DETAIL: 1 = processor general   SOURCE ID: 0&lt;BR /&gt;PROBLEM DETAIL: 0 = no problem detail&lt;BR /&gt;&lt;BR /&gt;LEDs:  RUN      ATTENTION     FAULT     REMOTE     POWER&lt;BR /&gt;       ON       FLASH         FLASH     ON         ON&lt;BR /&gt;&lt;BR /&gt;0xA0E000C01100B000 00000000 000005E9 - type 20 = major change in system state&lt;BR /&gt;0x58E008C01100B000 00004600 01000205 - type 11 = Timestamp 01/01/1970 00:02:05&lt;BR /&gt;A: ack read of this entry - X: Disable all future alert messages&lt;BR /&gt;Anything else skip redisplay the log entry&lt;BR /&gt;-&amp;gt;Choice:x&lt;BR /&gt;*****************************************&lt;BR /&gt;&lt;BR /&gt;CAUTION: System Alerts have been disabled. This will re-enable with &lt;BR /&gt;a re-boot or power-on of the system. To re-enable system alerts now, you&lt;BR /&gt;may use the AC (Alert Display Configuration) command.&lt;BR /&gt;&lt;BR /&gt;************* SYSTEM ALERT **************&lt;BR /&gt;Alert messages are now disabled. Enter Commands Interface AC command to enable them again&lt;BR /&gt;*****************************************&lt;BR /&gt;&lt;BR /&gt;********** VIRTUAL FRONT PANEL **********&lt;BR /&gt;System Boot detected&lt;BR /&gt;*****************************************&lt;BR /&gt;LEDs:  RUN      ATTENTION     FAULT     REMOTE     POWER&lt;BR /&gt;       FLASH    FLASH         FLASH     ON         ON&lt;BR /&gt;&lt;BR /&gt;platform                  config                    626F&lt;BR /&gt;processor                 slave rendezvous          1C17&lt;BR /&gt;processor                 test                      1142&lt;BR /&gt;PDH                       INIT                      3722&lt;BR /&gt;processor                 test                      1100&lt;BR /&gt;processor                 test                      1100&lt;BR /&gt;processor                 test                      1100&lt;BR /&gt;processor                 test                      1100&lt;BR /&gt;processor                 test                      1100&lt;BR /&gt;processor                 test                      1100</description>
      <pubDate>Sat, 17 Dec 2005 12:29:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-panic-anyone-can-help/m-p/3693557#M247654</guid>
      <dc:creator>yuchengliu_1</dc:creator>
      <dc:date>2005-12-17T12:29:31Z</dc:date>
    </item>
    <item>
      <title>Re: system panic ,anyone can help?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-panic-anyone-can-help/m-p/3693558#M247655</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Try booting the system in a Sible User mode.&lt;BR /&gt;&lt;BR /&gt;Stop the boot process when it prompts and try your luck.&lt;BR /&gt;&lt;BR /&gt;Even it works better log a call with HP.&lt;BR /&gt;Cheers 007...&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 17 Dec 2005 15:07:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-panic-anyone-can-help/m-p/3693558#M247655</guid>
      <dc:creator>Chan 007</dc:creator>
      <dc:date>2005-12-17T15:07:49Z</dc:date>
    </item>
    <item>
      <title>Re: system panic ,anyone can help?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-panic-anyone-can-help/m-p/3693559#M247656</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Your system may have had a SCSI disk go bad. It could also be just a loose cable or something like that.&lt;BR /&gt;&lt;BR /&gt;I had a D320 do this to be continuously twice, once when I connected a scsi card with the same scsi id as the scsi card at the other end of a jbod and once when a disk failed in a HP-6000 disk array.&lt;BR /&gt;&lt;BR /&gt;In both cases solving the scsi problem made the problem go away.&lt;BR /&gt;&lt;BR /&gt;It could however be almost any kind of hardware issue. If you've done anything to the system recently consider backing that change out.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Sat, 17 Dec 2005 17:27:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-panic-anyone-can-help/m-p/3693559#M247656</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2005-12-17T17:27:28Z</dc:date>
    </item>
    <item>
      <title>Re: system panic ,anyone can help?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-panic-anyone-can-help/m-p/3693560#M247657</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;One of the reasons of such system panic buring bootup is unable to mount "root" filesystem.&lt;BR /&gt;&lt;BR /&gt;You can try to boot using old kernel &lt;BR /&gt;ISL &amp;gt; hpux -lm /stand/vmunix.prev&lt;BR /&gt;Don't use (;0) while booting.&lt;BR /&gt;&lt;BR /&gt;Another probable cause could be bad super block of the root file system. In this case you need to boot with core OS media and  run fsck -b &lt;ALT-BLOCK number=""&gt; &lt;ROOT-PARTITION&gt;&lt;BR /&gt;&lt;BR /&gt;If you have mirrored disk , try above with that disk.&lt;BR /&gt;&lt;BR /&gt;If you have changed anything like generating new kernel or SCSI card changed etc. revert it back.&lt;BR /&gt;&lt;BR /&gt;&lt;/ROOT-PARTITION&gt;&lt;/ALT-BLOCK&gt;</description>
      <pubDate>Sat, 17 Dec 2005 20:48:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-panic-anyone-can-help/m-p/3693560#M247657</guid>
      <dc:creator>Sameer_Nirmal</dc:creator>
      <dc:date>2005-12-17T20:48:33Z</dc:date>
    </item>
  </channel>
</rss>

