<?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: Server won't boot .... HELP!!! in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/server-won-t-boot-help/m-p/2739024#M1760</link>
    <description>Hello,&lt;BR /&gt;&lt;BR /&gt;Normally, server appliances cannot be fixed/repaired by the customer itself. You should use your maintenance contract or your warranty to have it repaired by HP.&lt;BR /&gt;&lt;BR /&gt;The password that the system asks at LILO prompt seems to be a security feature of LILO, aka "restricted". With this option in /etc/lilo.conf, in conjunction with a password, one must supply a LILO password to be able to change the LILO boot options.&lt;BR /&gt;&lt;BR /&gt;If you have a boot device other than the main hard disk, try to boot on a rescue floppy or install cdrom of any Linux distribution, then do the fsck from that rescue floppy/cdrom.&lt;BR /&gt;&lt;BR /&gt;Otherwise, try to guess the LILO or maintenance password. Try hplinux, hponly, linuxhp, root, hp...&lt;BR /&gt;&lt;BR /&gt;But if I were you, I would first contact my HP support line before trying any other option.&lt;BR /&gt;&lt;BR /&gt;Good luck.&lt;BR /&gt;&lt;BR /&gt;Kodjo&lt;BR /&gt;</description>
    <pubDate>Thu, 06 Jun 2002 17:51:26 GMT</pubDate>
    <dc:creator>Kodjo Agbenu</dc:creator>
    <dc:date>2002-06-06T17:51:26Z</dc:date>
    <item>
      <title>Server won't boot .... HELP!!!</title>
      <link>https://community.hpe.com/t5/operating-system-linux/server-won-t-boot-help/m-p/2739023#M1759</link>
      <description>I'm using a server appliance (sa1100) and after a power-loss the server won't boot.  Since this thing is WEB Based Admin, there's no root password set at install time.  &lt;BR /&gt;I've connected a PC to the serial port to view the boot process.  I see the messages "/dev/hda6 is inconsistent need to fsck manually without the -a or -p option". &lt;BR /&gt;I've tried to run "LINUX SINGLE" at the LILO boot prompt to change the root passwd via hyper-term but the system still request a root passwd.   What can I do to run the fsck???</description>
      <pubDate>Thu, 06 Jun 2002 11:03:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/server-won-t-boot-help/m-p/2739023#M1759</guid>
      <dc:creator>C Townsend</dc:creator>
      <dc:date>2002-06-06T11:03:53Z</dc:date>
    </item>
    <item>
      <title>Re: Server won't boot .... HELP!!!</title>
      <link>https://community.hpe.com/t5/operating-system-linux/server-won-t-boot-help/m-p/2739024#M1760</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;Normally, server appliances cannot be fixed/repaired by the customer itself. You should use your maintenance contract or your warranty to have it repaired by HP.&lt;BR /&gt;&lt;BR /&gt;The password that the system asks at LILO prompt seems to be a security feature of LILO, aka "restricted". With this option in /etc/lilo.conf, in conjunction with a password, one must supply a LILO password to be able to change the LILO boot options.&lt;BR /&gt;&lt;BR /&gt;If you have a boot device other than the main hard disk, try to boot on a rescue floppy or install cdrom of any Linux distribution, then do the fsck from that rescue floppy/cdrom.&lt;BR /&gt;&lt;BR /&gt;Otherwise, try to guess the LILO or maintenance password. Try hplinux, hponly, linuxhp, root, hp...&lt;BR /&gt;&lt;BR /&gt;But if I were you, I would first contact my HP support line before trying any other option.&lt;BR /&gt;&lt;BR /&gt;Good luck.&lt;BR /&gt;&lt;BR /&gt;Kodjo&lt;BR /&gt;</description>
      <pubDate>Thu, 06 Jun 2002 17:51:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/server-won-t-boot-help/m-p/2739024#M1760</guid>
      <dc:creator>Kodjo Agbenu</dc:creator>
      <dc:date>2002-06-06T17:51:26Z</dc:date>
    </item>
  </channel>
</rss>

