"Mikkel L. Ellertson" wrote:

> On Wed, 24 Oct 2001, Donald Brandon wrote:
>
> > Hey listers:
> >
> > I need some help  (even if it is a point to the right list, in which
> > case I am sorry to bother).  Recently, we purchased a new system that is
> > going to become our team's server.  One of my colleagues was tasked with
> > getting it set up to do everything we needed out of it.  This colleague
> > has since left, leaving me to do clean up.  Here is what I have.  The
> > system is a redhat (seawolf) distribution with dual hard drives.  The
> > last thing I need to do is to repartition the second hard drive into two
> > large partitions for data storage.  This is where the problem (at least
> > for me) comes in.
> >
> > The sytem requires both hard drives to boot.  If you unplug one hard
> > drive, it won't boot.   If you plug that back in and unplug the other,
> > it won't boot.  This could cause problems when I go to repartition the
> > other drive.  I am not by any means an expert when it comes to Linux
> > (but I feel I am improving ) ;-)
> >
> > Here is my lilo.conf:
> >
> > boot=/dev/sda
> > map=/boot/map
> > install=/boot/boot.b
> > prompt
> > timeout=50
> > message=/boot/message
> > linear
> > default=linux
> >
> > image=/boot/vmlinuz-2.4.2-2smp
> >         label=linux
> >         initrd=/boot/initrd-2.4.2-2smp.img
> >         read-only
> >         root=/dev/sdb7
> >
> > image=/boot/vmlinuz-2.4.2-2
> >         label=linux-up
> >         initrd=/boot/initrd-2.4.2-2.img
> >         read-only
> >         root=/dev/sdb7
> >
> [snip]
> >
> > I see what is happening.  My colleague left the first drive alone which
> > contained the boot record and original partitions and partioned the
> > second drive to our needs.  But now the boot record remains on the drive
> > to be used for storage.  Is there a way for me to leave the boot record
> > on the first drive or should it be moved to the second?  Any insight???
> >
> > Thanks in advance..
> > DB
> >
> >
> The output of /etc/fstab, or the mount command, and the output of "df
> -h" would be helpfull here.  Also the output of fdisk -l.  Untill we
> know what is mounted where, it is hard to say what is needed.

You are right.  A couple of good outputs.  Unfortunately, df shows that only
the second hard drive is mounted :

Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb7             3.0G   98M  2.7G   4% /
/dev/sdb2              23M  7.8M   13M  36% /boot
/dev/sdb1             4.9G  346M  4.3G   8% /home
/dev/sdb5             5.9G  1.1G  4.5G  20% /usr
/dev/sdb6              16G   23M   14G   1% /usr/local
/dev/sdb8             2.0G   21M  1.8G   2% /var

and here is fstab :

LABEL=/1                /                       ext2    defaults        1 1
LABEL=/boot1            /boot                   ext2    defaults        1 2
LABEL=/home             /home                   ext2    defaults        1 2
/dev/fd0                /mnt/floppy             auto    noauto,owner    0 0
LABEL=/usr1             /usr                    ext2    defaults        1 2
LABEL=/usr/local        /usr/local              ext2    defaults        1 2
LABEL=/var              /var                    ext2    defaults        1 2
none                    /proc                   proc    defaults        0 0
none                    /dev/pts                devpts  gid=5,mode=620  0 0
/dev/sda7               swap                    swap    defaults        0 0
/dev/sdb9               swap                    swap    defaults        0 0
/dev/cdrom              /mnt/cdrom              iso9660 noauto,owner,kudzu,ro
0
0
/dev/hdd4               /mnt/zip250.0           auto    noauto,owner,kudzu 0
0
fstab (END)

>
>
> The way the system is set up, you will not be able to remove one drive
> without editing /etc/fstab.  If the system can be set to boot with just
> the information on the second drive, you will probably find it simpler
> to boot from a floppy, and then edit /etc/lilo.conf, and install lilo to
> the MBR of the second drive.  If you try and install lilo to the second
> drive with both drives installed, it will not work because lilo will
> have the wrong BIOS number for the drive after you remove the first
> drive.

Question:  If we determine what partition of sda is being used to boot,
could we leave that partition as is and use disk druid to edit the remaining
or is this bad????

>
>
> Now, as far as repartitioning the drives, you can do that wihtout
> removing a drive.  Exactly what you will have to do depends on how the
> drives are partitioned now.  You may have a small /boot partition on
> /dev/sda2, it is hard to tell.  Once we know what is mounted where, and
> how full each partition is, there are a lot of options.
>
> Mikkel
> --
>
>     Do not meddle in the affairs of dragons,
>  for you are crunchy and taste good with ketchup.
>
> _______________________________________________
> Seawolf-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/seawolf-list
begin:vcard 
n:Brandon;Donald
tel;pager:(228) 870-5610
tel;fax:(228) 688-4853
tel;work:(228) 688-5245
x-mozilla-html:FALSE
org:Naval Research Laboratory;Mapping, Charting, and Geodesy
adr:;;											;;;;
version:2.1
email;internet:[EMAIL PROTECTED]
x-mozilla-cpt:;0
fn:Donald Brandon
end:vcard

Reply via email to