Re: Making a new drive the Boot drive has failed to work
From: Mark Worsdall (freebsd_at_NoSpAmPlEaSe-wizdom.org.uk)
Date: 07/31/05
- Next message: Peter Köhlmann: "Re: Review of FreeBSD 5.4"
- Previous message: Mark Worsdall: "Re: mount point has gone, device is mounted, can't umount device"
- Next in thread: Rainer Goellner: "Re: Making a new drive the Boot drive has failed to work"
- Reply: Rainer Goellner: "Re: Making a new drive the Boot drive has failed to work"
- Maybe reply: Gunther Nikl: "Re: Making a new drive the Boot drive has failed to work"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 31 Jul 2005 20:04:02 +0100
[snip]
I decided to start all over.
The new Maxtor 73Gb drive is assigned SCSI ID8.
Here is the complete list of drives:
CONFIG A:
SCSI ID0 Hard Disk 0 IBM 9G da0
SCSI ID1 Hard Disk 1 FUJ 18G da1
SCSI ID4 Hard Disk 2 QUA 36G da2
SCSI ID6 Hard Disk 3 MAX 73Ga da3
SCSI ID8 Hard Disk 4 MAX 73Gb da4
When everything is completed we want to end up with:
CONFIG FINAL
SCSI ID0 Hard Disk 0 MAX 73Gb da0
SCSI ID4 Hard Disk 1 QUA 36G da1
SCSI ID6 Hard Disk 2 MAX 73Ga da2
This requires my assistant to remove the jumper from MAX73b to make it
SCSI ID0 and disconnect the SCSI cable from IBM & FUJ drives.
So while in CONFIG A I used the PC Style Disk slicer in
/stand/sysinstall. I told it to use the Entire Disc for FreeBSD and
pressed B to make it Bootable. Then pressed W and quit. So now I have a
complete FreeBSD (165) slice on da4.
Then I used the Disklabeler in /stand/sysinstall to Create partitions
(or slices) in the following way:
da4s1e /mnt/rt 200M
da4s1b SWAP 2G
da4s1f /mnt/usr 6G
da4s1g /mnt/var 1G
da4s1h /mnt/loc 12G
da4s1a /mnt/tmp 2G
da2s1d /mnt/www 1G
I was not happy with this since when I pressed Auto defaults it made
da4s1a be the / which is what da0s1a is currently. I tried again but it
would not let me make them how I wanted!!! At this point I hoped that at
a later stage I would be able to make it boot to da4s1e.
I then mounted the partitions/slices (so confused about which is what in
slices and partitions) from da4 and copied the old da0&1 stuff to /mnt/*
da4.
I then wanted to make sure that da4 had a mbr so I did:
fdisk -B -b /boot/mbr da4
su-2.04# fdisk -v da4
******* Working on device /dev/da4 *******
parameters extracted from in-core disklabel are:
cylinders=8942 heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=8942 heads=255 sectors/track=63 (16065 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165,(FreeBSD/NetBSD/386BSD)
start 63, size 143653167 (70143 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
I have already altered the fstab in /mnt/rt/etc/fstab to reflect CONFIG
FINAL. In that same folder is a copy of the original fstab.bak
I unmounted /mnt/rt
and did:
disklabel -B da4s1e
Then HALTED, SWITCHED OFF and removed 2 old SCSI drives and took jumper
off MAX73Gb making it go from SCSI ID 8 to 0
Switched On.
This time it sits there saying
>> FreeBSD/i386 BOOT
Default: 0:da(0,a)
No /boot/loader
>> FreeBSD/i386 BOOT
Default: 0:da(0,a)
No /kernel
I am guessing this is to do with it looking for slice 1a when it should
be looking for slice 1e.
Had no idea what to do now so we halted and rebooted in CONFIG A mode.
So for testing can we reboot remotely making da4s1e being the boot drive
so it ignores da0s1a? Remember fstab has been altered on this slice for
final configuration, so will be wrong. fstab.test is in /mnt/rt/etc on
da4 and that is correct.
Can't work out what I should have done.
-- Mark Worsdall https://www.paypal.com/refer/pal=LS79YHQ9VUGLJ
- Next message: Peter Köhlmann: "Re: Review of FreeBSD 5.4"
- Previous message: Mark Worsdall: "Re: mount point has gone, device is mounted, can't umount device"
- Next in thread: Rainer Goellner: "Re: Making a new drive the Boot drive has failed to work"
- Reply: Rainer Goellner: "Re: Making a new drive the Boot drive has failed to work"
- Maybe reply: Gunther Nikl: "Re: Making a new drive the Boot drive has failed to work"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
