<?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 Why boot record  broken after firmware upgrade? in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/why-boot-record-broken-after-firmware-upgrade/m-p/4466729#M37660</link>
    <description>I had weird problem after firmware upgrade on one of my servers (Tyan-based motherboard with SATA controller). &lt;BR /&gt;The problem that after I upgraded BIOS my Linux stopped boot. Only booting from rescue CD and reinstalling grub boot record fixed this problem. &lt;BR /&gt;I'm still curious why this happened... Any ideas?</description>
    <pubDate>Sun, 26 Jul 2009 08:14:15 GMT</pubDate>
    <dc:creator>Vitaly Karasik_1</dc:creator>
    <dc:date>2009-07-26T08:14:15Z</dc:date>
    <item>
      <title>Why boot record  broken after firmware upgrade?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/why-boot-record-broken-after-firmware-upgrade/m-p/4466729#M37660</link>
      <description>I had weird problem after firmware upgrade on one of my servers (Tyan-based motherboard with SATA controller). &lt;BR /&gt;The problem that after I upgraded BIOS my Linux stopped boot. Only booting from rescue CD and reinstalling grub boot record fixed this problem. &lt;BR /&gt;I'm still curious why this happened... Any ideas?</description>
      <pubDate>Sun, 26 Jul 2009 08:14:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/why-boot-record-broken-after-firmware-upgrade/m-p/4466729#M37660</guid>
      <dc:creator>Vitaly Karasik_1</dc:creator>
      <dc:date>2009-07-26T08:14:15Z</dc:date>
    </item>
    <item>
      <title>Re: Why boot record  broken after firmware upgrade?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/why-boot-record-broken-after-firmware-upgrade/m-p/4466730#M37661</link>
      <description>If the system was originally set to boot from a non-default disk, this setting may have been reset to default in the firmware upgrade.&lt;BR /&gt;&lt;BR /&gt;Reinstalling the boot record would then make the new disk bootable, probably by mapping back to the old boot disk.&lt;BR /&gt;&lt;BR /&gt;If you have an old backup copy of your GRUB configuration file and/or /boot/grub/device.map file, compare them to the current versions. Any differences might be enlightening.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Sun, 26 Jul 2009 08:51:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/why-boot-record-broken-after-firmware-upgrade/m-p/4466730#M37661</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2009-07-26T08:51:53Z</dc:date>
    </item>
    <item>
      <title>Re: Why boot record  broken after firmware upgrade?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/why-boot-record-broken-after-firmware-upgrade/m-p/4466731#M37662</link>
      <description>&amp;gt;If the system was originally set to boot &amp;gt;from a non-default disk, this setting may &amp;gt;have been reset to default in the firmware &amp;gt;upgrade.&lt;BR /&gt;It's not the case - I double-checked boot order - in all cases it was my 1st SATA disk.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;If you have an old backup copy of your GRUB &amp;gt;configuration file &amp;gt;and/or /boot/grub/device.map file, compare &amp;gt;them to the current versions. Any &amp;gt;differences might be enlightening. &lt;BR /&gt;Grub config was't changed. All what I did it's "grub&amp;gt;root (hd0,0)", "grub&amp;gt; setup (hd0)" - i.e., with the same device as it was into grub.conf.&lt;BR /&gt;</description>
      <pubDate>Sun, 26 Jul 2009 11:25:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/why-boot-record-broken-after-firmware-upgrade/m-p/4466731#M37662</guid>
      <dc:creator>Vitaly Karasik_1</dc:creator>
      <dc:date>2009-07-26T11:25:39Z</dc:date>
    </item>
    <item>
      <title>Re: Why boot record  broken after firmware upgrade?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/why-boot-record-broken-after-firmware-upgrade/m-p/4466732#M37663</link>
      <description>Shalam Vitaly,&lt;BR /&gt;&lt;BR /&gt;Vitaly, I've seen this happen once in a while. Happened after updating the firmware on an HP branded server to a system that was connected to a SAN. It tried after the upgrade to boot off the SAN until I reinstalled grub.&lt;BR /&gt;&lt;BR /&gt;The cause of this was determined to be a bug in the firmware release. I suspect this is the case with you as well.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Sun, 26 Jul 2009 12:28:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/why-boot-record-broken-after-firmware-upgrade/m-p/4466732#M37663</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2009-07-26T12:28:37Z</dc:date>
    </item>
    <item>
      <title>Re: Why boot record  broken after firmware upgrade?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/why-boot-record-broken-after-firmware-upgrade/m-p/4466733#M37664</link>
      <description>Shalom &amp;amp; thank you!&lt;BR /&gt;In you case it seems like BIOS upgrade changed storage devices order. In my case I have just 4 local disks and I tried to eject all of them except the first system drive - this didn't help. So I don't sure that your explanation is relevant for my server...</description>
      <pubDate>Sun, 26 Jul 2009 12:37:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/why-boot-record-broken-after-firmware-upgrade/m-p/4466733#M37664</guid>
      <dc:creator>Vitaly Karasik_1</dc:creator>
      <dc:date>2009-07-26T12:37:09Z</dc:date>
    </item>
    <item>
      <title>Re: Why boot record  broken after firmware upgrade?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/why-boot-record-broken-after-firmware-upgrade/m-p/4466734#M37665</link>
      <description>Bonjour ,&lt;BR /&gt;&lt;BR /&gt;Read the "grub info" specially the node device map 15.3 (15.3 The map between BIOS drives and OS devices), This I think explain it better then I could ... &lt;BR /&gt;&lt;BR /&gt;I think this is your problem if I understand this correctly.&lt;BR /&gt;&lt;BR /&gt;enjoy life &lt;BR /&gt;&lt;BR /&gt;Jean-Pierre Huc&lt;BR /&gt;</description>
      <pubDate>Mon, 27 Jul 2009 10:12:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/why-boot-record-broken-after-firmware-upgrade/m-p/4466734#M37665</guid>
      <dc:creator>Huc_1</dc:creator>
      <dc:date>2009-07-27T10:12:04Z</dc:date>
    </item>
    <item>
      <title>Re: Why boot record  broken after firmware upgrade?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/why-boot-record-broken-after-firmware-upgrade/m-p/4466735#M37666</link>
      <description>But in this case grub config should be modified, and this isn't my case.</description>
      <pubDate>Mon, 27 Jul 2009 10:18:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/why-boot-record-broken-after-firmware-upgrade/m-p/4466735#M37666</guid>
      <dc:creator>Vitaly Karasik_1</dc:creator>
      <dc:date>2009-07-27T10:18:02Z</dc:date>
    </item>
  </channel>
</rss>

