You should probably locate an experienced Linux person near
you, to give you a hand when you start repartitioning, since one
mistake *can* make your Linux unbootable.
However you can usually delete and add partitions your
hearts content without changing the boot record (/dev/sda)
if you use the Linux command 'fdisk' to do it.
Also you can boot linux even if the boot record does get damaged,
if you have made an emergency boot floppy first. The command is:
mkbootdisk 2.4.2-2smp
On Wed, Oct 24, 2001 at 10:50:26AM -0600, 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
>
> and a partition list from /proc/partitions:
>
> major minor #blocks name rio rmerge rsect ruse wio wmerge wsect
> wuse running use aveq
>
> 8 0 35566479 sda 26 0 64 30 0 0 0 0 0 30 30
> 8 1 3148708 sda1 6 0 12 0 0 0 0 0 0 0 0
> 8 2 24097 sda2 6 0 12 20 0 0 0 0 0 20 20
> 8 3 1 sda3 0 0 0 0 0 0 0 0 0 0 0
> 8 5 21189703 sda5 6 0 12 0 0 0 0 0 0 0 0
> 8 6 10667128 sda6 6 0 12 10 0 0 0 0 0 10 10
> 8 7 530113 sda7 2 0 16 0 0 0 0 0 0 0 0
> 8 16 35566479 sdb 13031 16814 235214 94060 3874 6279 81350
> 575250 0 64460 669310
> 8 17 5245191 sdb1 313 174 3830 1980 158 19 1416 5480 0 2600
> 7460
> 8 18 24097 sdb2 38 470 1016 550 5 5 22 40 0 430 590
> 8 19 1 sdb3 1 0 2 10 0 0 0 0 0 10 10
> 8 21 6289416 sdb5 9583 10350 159398 51790 1217 458 13488 328830
> 0 48960 380620
> 8 22 16779861 sdb6 67 62 600 380 742 5025 46136 166440 0 2080
> 166820
> 8 23 3148708 sdb7 1773 1700 27772 10890 388 274 5392 38950 0
> 11530 49840
> 8 24 2096451 sdb8 1252 4058 42576 28430 1364 498 14896 35510 0
> 12360 63940
> 8 25 1975963 sdb9 3 0 18 30 0 0 0 0 0 30 30
>
> 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
>
>
>
> _______________________________________________
> Seawolf-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/seawolf-list
--
Jan Carlson janc at kubwa dot com
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
