<?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: Boot error during startup in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-error-during-startup/m-p/2455422#M12334</link>
    <description>Hi Martin,&lt;BR /&gt;&lt;BR /&gt;You have a hardware problem as explained by Alex.</description>
    <pubDate>Thu, 19 Oct 2000 09:31:25 GMT</pubDate>
    <dc:creator>CHRIS_ANORUO</dc:creator>
    <dc:date>2000-10-19T09:31:25Z</dc:date>
    <item>
      <title>Boot error during startup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-error-during-startup/m-p/2455420#M12332</link>
      <description>Our HP9000 has been powered off for some time. Now I have tried to boot the server again. I have tried it from the primary boot path and also from the CD_ROM.&lt;BR /&gt;Always the following messages appear.&lt;BR /&gt;&lt;BR /&gt;Cannot find ENTRY_TEST&lt;BR /&gt;Failed I/O operation with ENTRY_10&lt;BR /&gt;STATUS -4&lt;BR /&gt;&lt;BR /&gt;Error Reading IPL&lt;BR /&gt;&lt;BR /&gt;Do I have a hardware problem or what ?&lt;BR /&gt;</description>
      <pubDate>Thu, 19 Oct 2000 09:12:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-error-during-startup/m-p/2455420#M12332</guid>
      <dc:creator>martin van den brink</dc:creator>
      <dc:date>2000-10-19T09:12:55Z</dc:date>
    </item>
    <item>
      <title>Re: Boot error during startup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-error-during-startup/m-p/2455421#M12333</link>
      <description>The majority of ENTRY_INIT errors encountered are: Status = -4 and&lt;BR /&gt;Status = -7.&lt;BR /&gt;&lt;BR /&gt;ENTRY_INIT -4 Causes:&lt;BR /&gt;- the disk is experiencing hardware faults and needs replacing.&lt;BR /&gt;- the path to the disk is experiencing problems. e.g.. Termination,&lt;BR /&gt;  cabling, SCSI adapter, SCSI adapter seating.&lt;BR /&gt;ENTRY_INIT -7 Causes:&lt;BR /&gt;- Booting from the wrong path or non-existent device.&lt;BR /&gt;- Trying to boot from a device that is not responding.&lt;BR /&gt; &lt;BR /&gt;Troubleshooting Steps:&lt;BR /&gt;. Power off the server, then power off the disks - leave all powered&lt;BR /&gt;  off for at least 30 seconds. Power on disks, then server.&lt;BR /&gt;&lt;BR /&gt;. When server is booting, check access LED's on boot disk, is it being&lt;BR /&gt;  accessed? Yes - possible bad disk. No - possible bad path to&lt;BR /&gt;  disk, e.g.. Cabling/termination/adapter. Time to log hardware call.&lt;BR /&gt;&lt;BR /&gt;. If boot disk is in an external disk enclosure, check the cabling is&lt;BR /&gt;  secure, and access/status lights are normal.&lt;BR /&gt;&lt;BR /&gt;. Attempt to boot from an alternate boot path if you have one,&lt;BR /&gt;  e.g.. Mirror boot disk, alternate boot disk.&lt;BR /&gt;&lt;BR /&gt;. Double check you have the correct boot path.&lt;BR /&gt;&lt;BR /&gt;. Use the SEArch option at the Boot Menu, does the primary boot path&lt;BR /&gt;  appear? If not, we cannot see the disk and time to log a hardware call.&lt;BR /&gt;  If we can see the boot disk, but still get ENTRY_INIT error when booting&lt;BR /&gt;  we need to log a hardware call.&lt;BR /&gt;&lt;BR /&gt;. We can boot to Recovery Shell and use the chroot option to fsck the&lt;BR /&gt;  boot disk, but this will always fail if we cannot get to the ISL&lt;BR /&gt;  prompt of a disk; in most occurrences of this error using the Recovery&lt;BR /&gt;  Shell (Support Media) is not helpful.&lt;BR /&gt;&lt;BR /&gt;. Perform preliminary steps to reinstall the system; As in most cases this&lt;BR /&gt;  error means the boot disk is bad and will need to be replaced. If the&lt;BR /&gt;  system is not mirrored then the recommended recovery method is to&lt;BR /&gt;  reinstall the system. Is the backup offsite? Do you know what sizes&lt;BR /&gt;  the vg00 logical volumes are?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Errors Returned by IODC ENTRY_INIT &lt;BR /&gt;Overview of ENTRY_INIT: To initialize and test a boot device so that ENTRY_I/O can transfer data to/from the boot device. ENTRY_INIT is also used to establish module or device communication.  &lt;BR /&gt;Status Description &lt;BR /&gt;2 Recoverable Error.&lt;BR /&gt;The call completed normally and the returned results are valid &lt;BR /&gt;0 OK.&lt;BR /&gt;The call completed normally without error &lt;BR /&gt;-2 Nonexistent option.&lt;BR /&gt;The call did not correspond to implemented options in entry_init  &lt;BR /&gt;-3 Can not complete call without error.&lt;BR /&gt;An error of unknown type prevented the call from completing correctly  &lt;BR /&gt;-4 Unrecoverable Hardware Error.&lt;BR /&gt;An unrecoverable hardware error has occurred between the processor PDC and IODC on the target controller or device  &lt;BR /&gt;-5 Unrecoverable data error.&lt;BR /&gt;ENTRY_INIT encountered an error while transferring data to/from the target controller or device  &lt;BR /&gt;-6 Illegal device address.&lt;BR /&gt;The device address supplied to ENTRY_INIT is invalid  &lt;BR /&gt;-7 Nonexistent device.&lt;BR /&gt;The device address supplied to ENTRY_INIT is valid, but, the target controller or device is not installed or is not responding  &lt;BR /&gt;-8 Module/device not ready.&lt;BR /&gt;The module or device is not ready to be initialized. The target is not ready because it has not completed its power on reset/selftest  &lt;BR /&gt;-9 Cannot locate a console or boot device.&lt;BR /&gt;ENTRY_INIT could not locate a console or boot device  &lt;BR /&gt;-10 Invalid argument.&lt;BR /&gt;ENTRY_INIT was passed an invalid command  &lt;BR /&gt;-11 Data buffer too small &lt;BR /&gt;-12 Unsupported record size &lt;BR /&gt;-13 Protocol Error.&lt;BR /&gt;A protocol error was encountered on bus during data transfer to/from the target controller or device (which also means 3rd part hardware or a boot disk) &lt;BR /&gt;</description>
      <pubDate>Thu, 19 Oct 2000 09:17:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-error-during-startup/m-p/2455421#M12333</guid>
      <dc:creator>Alex Glennie</dc:creator>
      <dc:date>2000-10-19T09:17:12Z</dc:date>
    </item>
    <item>
      <title>Re: Boot error during startup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-error-during-startup/m-p/2455422#M12334</link>
      <description>Hi Martin,&lt;BR /&gt;&lt;BR /&gt;You have a hardware problem as explained by Alex.</description>
      <pubDate>Thu, 19 Oct 2000 09:31:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-error-during-startup/m-p/2455422#M12334</guid>
      <dc:creator>CHRIS_ANORUO</dc:creator>
      <dc:date>2000-10-19T09:31:25Z</dc:date>
    </item>
    <item>
      <title>Re: Boot error during startup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/boot-error-during-startup/m-p/2455423#M12335</link>
      <description>Hi Martin&lt;BR /&gt;Before you get to deep into this problem check the obvious (As the server has been powered down for some time.)&lt;BR /&gt;&lt;BR /&gt;Connections on cables and boards without power oxidise and oxidants tend not to let electrickery run through them.&lt;BR /&gt;&lt;BR /&gt;So power down - unplug and refit all data cables - and recheck.&lt;BR /&gt;If this fails then I would get the system boards removed and refitted.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 20 Oct 2000 07:42:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/boot-error-during-startup/m-p/2455423#M12335</guid>
      <dc:creator>Paula J Frazer-Campbell</dc:creator>
      <dc:date>2000-10-20T07:42:12Z</dc:date>
    </item>
  </channel>
</rss>

