<?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: changing boot disk in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/changing-boot-disk/m-p/3718844#M67583</link>
    <description>LABELs are used instead of device names because device names can change with the time and the modification of the disk structure. Basically, every partition has a label, and instead of using /dev/sda1 you use LABEL=/boot1 for example. You can check the label for a partition with e2label. As described above, you can replace the LABEL= with /dev/sdbX.&lt;BR /&gt;&lt;BR /&gt;I want to know what is your strategy? Booting for that disk could not be as easy as you think, the boot loader also has information about the partitions that should use to boot. You should modify your boot loader first. Also, the boot loader may not be installed on your RAID 0 disk.&lt;BR /&gt;&lt;BR /&gt;How will you keep these filesystems sync?</description>
    <pubDate>Mon, 30 Jan 2006 07:11:42 GMT</pubDate>
    <dc:creator>Ivan Ferreira</dc:creator>
    <dc:date>2006-01-30T07:11:42Z</dc:date>
    <item>
      <title>changing boot disk</title>
      <link>https://community.hpe.com/t5/operating-system-linux/changing-boot-disk/m-p/3718842#M67581</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;We are running RedHat Linux 4 Enterprise Server. 3 disks are inside of the PC.&lt;BR /&gt;We are running a hardware RAID 1 (mirrored disks) on two disks and a simple RAID&lt;BR /&gt;0 on the third disk. So, we're not using the software RAID of RedHat Linux.&lt;BR /&gt;&lt;BR /&gt;For security reasons we copied the complete content of the RAID 1 disks&lt;BR /&gt;(/dev/sda) to the RAID 0 (/dev/sdb) disk, so we've the similar filesystem layout&lt;BR /&gt;on both disks. And we're able to boot from the RAID 0 disk.&lt;BR /&gt;&lt;BR /&gt;The problem:&lt;BR /&gt;&lt;BR /&gt;After rebooting, the original device file /dev/sda are used for mounting the&lt;BR /&gt;filesystems, although we booted from the RAID 0 disk. But we need the filesystem&lt;BR /&gt;mounted via /dev/sdb. We wanted to change the device file entries in /etc/fstab,&lt;BR /&gt;but the content of fstab is:&lt;BR /&gt;&lt;BR /&gt;# This file is edited by fstab-sync - see 'man fstab-sync' for details&lt;BR /&gt;LABEL=/1                /                       ext3    defaults        1 1&lt;BR /&gt;LABEL=/boot1            /boot                   ext3    defaults        1 2&lt;BR /&gt;none                    /dev/pts                devpts  gid=5,mode=620  0 0&lt;BR /&gt;none                    /dev/shm                tmpfs   defaults        0 0&lt;BR /&gt;none                    /proc                   proc    defaults        0 0&lt;BR /&gt;none                    /sys                    sysfs   defaults        0 0&lt;BR /&gt;LABEL=/tmp              /tmp                    ext3    defaults        1 2&lt;BR /&gt;LABEL=/usr              /usr                    ext3    defaults        1 2&lt;BR /&gt;LABEL=/var              /var                    ext3    defaults        1 2&lt;BR /&gt;LABEL=SWAP-sda6         swap                    swap    defaults        0 0&lt;BR /&gt;/dev/hdb                /media/cdrom            auto    pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0&lt;BR /&gt;/dev/hda                /media/floppy           auto    pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The device /dev/sda ist not listed here. So, how do we manage to get the&lt;BR /&gt;filesystem mounted via /dev/sdb after booting from the RAID 0 disk?&lt;BR /&gt;&lt;BR /&gt;Greetings&lt;BR /&gt;Thomas&lt;BR /&gt;</description>
      <pubDate>Fri, 27 Jan 2006 06:06:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/changing-boot-disk/m-p/3718842#M67581</guid>
      <dc:creator>Thomas Schler_1</dc:creator>
      <dc:date>2006-01-27T06:06:33Z</dc:date>
    </item>
    <item>
      <title>Re: changing boot disk</title>
      <link>https://community.hpe.com/t5/operating-system-linux/changing-boot-disk/m-p/3718843#M67582</link>
      <description>Thomas,&lt;BR /&gt;&lt;BR /&gt;You have two ways to fix this problem:&lt;BR /&gt;&lt;BR /&gt;1) to change filesystems labels on /dev/sdaX to something else, for example&lt;BR /&gt;&lt;BR /&gt;e2label  /dev/sda1 newlabel&lt;BR /&gt;&lt;BR /&gt;2) change to fstab:&lt;BR /&gt;instead of &lt;BR /&gt;&amp;gt;LABEL=/usr /usr ext3 defaults 1 2&lt;BR /&gt;you should put&lt;BR /&gt;/dev/sdb2 /usr ext3 defaults 1 2&lt;BR /&gt;&lt;BR /&gt;Note! - in order to understand which partition labeled as "/usr", you should use &lt;BR /&gt;e2label /dev/sda1 [2,3,4,5,6,...] commands.&lt;BR /&gt;&lt;BR /&gt;(In general, filesystem labels is effort to build the new abstract layer above disk partitions. In means, we work with filesystem labeled as "/usr" instead of using partition from /dev/sdd7. Sometimes it confusing...)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 29 Jan 2006 06:05:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/changing-boot-disk/m-p/3718843#M67582</guid>
      <dc:creator>Vitaly Karasik_1</dc:creator>
      <dc:date>2006-01-29T06:05:24Z</dc:date>
    </item>
    <item>
      <title>Re: changing boot disk</title>
      <link>https://community.hpe.com/t5/operating-system-linux/changing-boot-disk/m-p/3718844#M67583</link>
      <description>LABELs are used instead of device names because device names can change with the time and the modification of the disk structure. Basically, every partition has a label, and instead of using /dev/sda1 you use LABEL=/boot1 for example. You can check the label for a partition with e2label. As described above, you can replace the LABEL= with /dev/sdbX.&lt;BR /&gt;&lt;BR /&gt;I want to know what is your strategy? Booting for that disk could not be as easy as you think, the boot loader also has information about the partitions that should use to boot. You should modify your boot loader first. Also, the boot loader may not be installed on your RAID 0 disk.&lt;BR /&gt;&lt;BR /&gt;How will you keep these filesystems sync?</description>
      <pubDate>Mon, 30 Jan 2006 07:11:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/changing-boot-disk/m-p/3718844#M67583</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2006-01-30T07:11:42Z</dc:date>
    </item>
  </channel>
</rss>

