<?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: Problems booting in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939271#M4054</link>
    <description>Or if you can't remove it, at least change it. man e2label or man tune2fs.&lt;BR /&gt;&lt;BR /&gt;G.</description>
    <pubDate>Mon, 31 Mar 2003 13:48:40 GMT</pubDate>
    <dc:creator>Goran Koruga</dc:creator>
    <dc:date>2003-03-31T13:48:40Z</dc:date>
    <item>
      <title>Problems booting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939265#M4048</link>
      <description>Greetings all,&lt;BR /&gt;&lt;BR /&gt;I have stumbled into a wired problem and I'm hoping someone here will be able to help me with it.&lt;BR /&gt;&lt;BR /&gt;I have a system with Redhat 7 installed on a 20 gig hdd. It uses the Lilo boot loader and the hdd is the /dev/hda device.&lt;BR /&gt;&lt;BR /&gt;I removed this hdd and stuck a new 20 gig and installed redhat v8 on it. The new hdd is dev/hda. &lt;BR /&gt;&lt;BR /&gt;Everything seemed to run fine. So I decided to connect the old hdd to the new redhat 8 system in order to transfer files to the new system.&lt;BR /&gt;&lt;BR /&gt;While the redhat 8 system which uses Grub as a bootloader, started to boot, i saw a message which indicated the kernel detected the 2nd hdd as /dev/hdc but then all these errors started poping up regarding some directories could not be found, and eventually the kernel would panic and halt there!&lt;BR /&gt;&lt;BR /&gt;It seems like there is some confusion happening when the older drive that has redhat 7 installed on it, is connected to the system... I'm guessing this has got to do something about automounting which takes place and then creates all these problems.&lt;BR /&gt;&lt;BR /&gt;Anyone that can help ?&lt;BR /&gt;&lt;BR /&gt;Both hdd's have active partitions and a working Linux installation on them, so If i was to connect them independantly to system, they would each boot without a problem.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.&lt;BR /&gt;&lt;BR /&gt;Chris P.</description>
      <pubDate>Mon, 31 Mar 2003 12:27:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939265#M4048</guid>
      <dc:creator>Admin32</dc:creator>
      <dc:date>2003-03-31T12:27:41Z</dc:date>
    </item>
    <item>
      <title>Re: Problems booting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939266#M4049</link>
      <description>Boot from a floppy and manually mount the file systems for the drive you want to keep.&lt;BR /&gt;Create a mount point for the old drive, manually mount it and copy over your files.&lt;BR /&gt;Then unmount and fdisk (or whatever) the old drive.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Paul</description>
      <pubDate>Mon, 31 Mar 2003 13:00:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939266#M4049</guid>
      <dc:creator>Paul R. Dittrich</dc:creator>
      <dc:date>2003-03-31T13:00:59Z</dc:date>
    </item>
    <item>
      <title>Re: Problems booting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939267#M4050</link>
      <description>There must be a way I can mount the whole drive into a directory without it affecting anything else; &lt;BR /&gt;&lt;BR /&gt;1) I havent got a boot disk&lt;BR /&gt;2) Your suggestion will not work as a long term solution as I need the old hdd available all the time on the new system.&lt;BR /&gt;</description>
      <pubDate>Mon, 31 Mar 2003 13:11:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939267#M4050</guid>
      <dc:creator>Admin32</dc:creator>
      <dc:date>2003-03-31T13:11:20Z</dc:date>
    </item>
    <item>
      <title>Re: Problems booting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939268#M4051</link>
      <description>Hi.&lt;BR /&gt;&lt;BR /&gt;Does it still work if you unplug the old disk ?&lt;BR /&gt;&lt;BR /&gt;G.</description>
      <pubDate>Mon, 31 Mar 2003 13:14:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939268#M4051</guid>
      <dc:creator>Goran Koruga</dc:creator>
      <dc:date>2003-03-31T13:14:45Z</dc:date>
    </item>
    <item>
      <title>Re: Problems booting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939269#M4052</link>
      <description>Goran,&lt;BR /&gt;&lt;BR /&gt;As I have explained in the original question, yes.&lt;BR /&gt;&lt;BR /&gt;If you take either hdd and connect them to the system by them selves, they will boot.&lt;BR /&gt;&lt;BR /&gt;All I'm trying to do it attach the older hdd to the new system and access its partitions ... I cant see why the new system (actually new hdd with redhat 8) would not boot and cause the kernel to panic.  Again, I'm guessing this has got something to do with automounting the drive once its detected...</description>
      <pubDate>Mon, 31 Mar 2003 13:28:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939269#M4052</guid>
      <dc:creator>Admin32</dc:creator>
      <dc:date>2003-03-31T13:28:55Z</dc:date>
    </item>
    <item>
      <title>Re: Problems booting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939270#M4053</link>
      <description>OK,&lt;BR /&gt;&lt;BR /&gt;this is just a guess, but try removing the label it uses for mounting / from the old disk (assuming you have the same for old and new disk).&lt;BR /&gt;&lt;BR /&gt;It might also help if you were a bit more specific about the errors.&lt;BR /&gt;&lt;BR /&gt;Goran</description>
      <pubDate>Mon, 31 Mar 2003 13:33:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939270#M4053</guid>
      <dc:creator>Goran Koruga</dc:creator>
      <dc:date>2003-03-31T13:33:17Z</dc:date>
    </item>
    <item>
      <title>Re: Problems booting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939271#M4054</link>
      <description>Or if you can't remove it, at least change it. man e2label or man tune2fs.&lt;BR /&gt;&lt;BR /&gt;G.</description>
      <pubDate>Mon, 31 Mar 2003 13:48:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939271#M4054</guid>
      <dc:creator>Goran Koruga</dc:creator>
      <dc:date>2003-03-31T13:48:40Z</dc:date>
    </item>
    <item>
      <title>Re: Problems booting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939272#M4055</link>
      <description>Hi Criss,&lt;BR /&gt;&lt;BR /&gt;In your situation, I would start from a floppy drive (which I could make started with one disk). &lt;BR /&gt;Then I would copy the conent of the scond disk to the big disk.&lt;BR /&gt;At last I would use fdisk and format / diskdruid / .... to make the disk available as a data disk in the current system.&lt;BR /&gt;&lt;BR /&gt;Hope this helps&lt;BR /&gt;Donald</description>
      <pubDate>Mon, 31 Mar 2003 15:45:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939272#M4055</guid>
      <dc:creator>Donald Kok</dc:creator>
      <dc:date>2003-03-31T15:45:18Z</dc:date>
    </item>
    <item>
      <title>Re: Problems booting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939273#M4056</link>
      <description>Hi,&lt;BR /&gt;Offlate, RedHat uses labels(/, /usr, etc) to identify the hard disks partitions rather than the device(/dev/hdc1, /dev/hdc2) nos. &lt;BR /&gt;&lt;BR /&gt;You have two options.&lt;BR /&gt;&lt;BR /&gt;1. Edit the /etc/fstab on both the disks after booting from a floppy and change them to use the device names for the partitions instead of Labels.&lt;BR /&gt;&lt;BR /&gt;2. Use e2label to change the lables on the second disk (/dev/hdc) to something other than the labels mentioned in /etc/fstab.&lt;BR /&gt;&lt;BR /&gt;I would prefer sol.1 coz, u can boot from both the disks individually. else, u might be stuck where in when u boot from the second disk with the labels changed, all ur partions wont get mounted.&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;-balaji</description>
      <pubDate>Tue, 01 Apr 2003 04:23:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939273#M4056</guid>
      <dc:creator>Balaji N</dc:creator>
      <dc:date>2003-04-01T04:23:56Z</dc:date>
    </item>
    <item>
      <title>Re: Problems booting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939274#M4057</link>
      <description>Okay, that makes some sence.... Does anyone know how to create a boot disk in Linux Redhat ?&lt;BR /&gt;&lt;BR /&gt;I didn't choose to make one at the time of installation :)&lt;BR /&gt;</description>
      <pubDate>Tue, 01 Apr 2003 08:22:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939274#M4057</guid>
      <dc:creator>Admin32</dc:creator>
      <dc:date>2003-04-01T08:22:47Z</dc:date>
    </item>
    <item>
      <title>Re: Problems booting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939275#M4058</link>
      <description>It's okay .. I've figured it out and created the boot disk.&lt;BR /&gt;&lt;BR /&gt;I'll need though some guidence as to what changes I should make to the old hdd's fstab.&lt;BR /&gt;&lt;BR /&gt;Here is what the old hdd's fstab currently contains:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;LABEL=/                 /                       ext2    defaults        1 1&lt;BR /&gt;LABEL=/boot             /boot                   ext2    defaults        1 2&lt;BR /&gt;LABEL=/home             /home                   ext2    defaults        1 2&lt;BR /&gt;/dev/cdrom              /mnt/cdrom              iso9660 noauto,owner,ro 0 0&lt;BR /&gt;/dev/scd0               /mnt/cdrw               iso9660 noauto,user,ro  0 0&lt;BR /&gt;/dev/fd0                /mnt/floppy             auto    noauto,owner    0 0&lt;BR /&gt;/dev/hda1               /win                    auto    noauto,owner    0 0&lt;BR /&gt;none                    /proc                   proc    defaults        0 0&lt;BR /&gt;none                    /dev/pts                devpts  gid=5,mode=620  0 0&lt;BR /&gt;/dev/hda6               swap                    swap    defaults        0 0&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 01 Apr 2003 08:47:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939275#M4058</guid>
      <dc:creator>Admin32</dc:creator>
      <dc:date>2003-04-01T08:47:07Z</dc:date>
    </item>
    <item>
      <title>Re: Problems booting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939276#M4059</link>
      <description>you have two ways of doing this.&lt;BR /&gt;&lt;BR /&gt;1. do a df -h and see the mounted partitions, it will show the partition name and mount point. edit the fstab, remove the LABEL=/ and replace it as /dev/hda1 and similar for all such partitions. &lt;BR /&gt;&lt;BR /&gt;2. or run a fdisk -l. this will list all the partitions. run e2label partition name and note down the lables. and them modify the fstab accordingly.&lt;BR /&gt;&lt;BR /&gt;you need to mount the other hard disk and do that as well.&lt;BR /&gt;&lt;BR /&gt;hth.&lt;BR /&gt;-balaji</description>
      <pubDate>Tue, 01 Apr 2003 09:06:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/problems-booting/m-p/2939276#M4059</guid>
      <dc:creator>Balaji N</dc:creator>
      <dc:date>2003-04-01T09:06:06Z</dc:date>
    </item>
  </channel>
</rss>

