My question was:
If I needed a separate utility (a la sun's installboot)
to make a bootable disk. (question in full at the end of
the email).
The answer is:
No separate installboot utility needed. 'disklabel'writes
boot blocks to the disk when run. There are options to
- make it not write boot bloxks
- make the bootblock Advfs (default is ufs).
Ref:
man disklabel
Thanks: for the very prompt resonses from the list members -
Peter Reynolds
Sunil Kurupath
Dr. Tom Blinn
David J. DeWolfe
Mike Iglesias
alan_at_nabeth.cxo.dec.com
Why SUMMARY was 'partial':
I followed the procedure described to prepare my
alternate boot-disk. But it still doesnt boot for some
reason.
Here is an exact description of what I am doing:
note:
>From SRM, the disks are DKA0, DKA1. (Actually, two separate volumes
coming from an external RAID).
During regular (and cdrom) boot, the disks are
rz0 and rzb0
>>>show dev
dka0.0.0.6.0 DKA0 IFT 3101 0111
dka1.0.0.6.0 DKA1 IFT 3101 0111
dka600.6.0.6.0 DKA600 RRD46 0557
dva0.0.0.0.0 DVA0
mka500.5.0.6.0 MKA500 SONY SDT-5000 3.30
ewa0.0.0.7.0 EWA0 00-00-F8-1F-6B-74
pka0.7.0.6.0 PKA0 SCSI Bus ID 7
>>> show
auto_action BOOT
boot_dev dka0.0.0.6.0
boot_file
boot_osflags A
boot_reset OFF
bootdef_dev dka0.0.0.6.0
booted_dev dka0.0.0.6.0
booted_file
booted_osflags i
char_set 0
console serial
>>> boot
(system boots from DKA0. I login from the console as root)
...
rz0 at scsi0 target 0 lun 0 (LID=0) (IFT 3101 0111) (Wide16)
rzb0 at scsi0 target 0 lun 1 (LID=1) (IFT 3101 0111) (Wide16)
tz5 at scsi0 target 5 lun 0 (LID=2) (SONY SDT-5000 3.30)
rz6 at scsi0 target 6 lun 0 (LID=3) (DEC RRD46 (C) DEC 0557)
...
# cd dev; ./MAKEDEV
# disklabel -r rzb0 > dl.b0
# disklabel -z rzb0
# vi dl.b0 (and modify it to reflect the file system partitioning on rz0)
# disklabel -R -r rzb0 dl.b0
(I use ufs, so should not need any other flags)
(replicate the data from rz0 --> rzb0)
# newfs /dev/rrzb0a
# mount /dev/rzb0a /mnt
# dump -0f - | (cd /mnt; restore -xf -)
# umount /mnt
(done with /, now do /usr)
# newfs /dev/rrzb0g
# mount /dev/rzb0g /mnt
# dump -0f - | (cd /mnt; restore -xf -)
# umount /mnt
(verified that the contents of rzb0{a,g} are okay)
(modify rzb0a:/etc/fstab to reflect the new device names)
# mount /dev/rzb0a /mnt
# vi /mnt/etc/fstab
(change /dev/rz0ba for /
/dev/rzb0b for swap -- not really needed but just wanted rzb0 to be standalone.
/dev/rzb0g for /usr)
# umount /mnt
(all done. reboot and test)
# shutdown -h now
>>> show dev
>>> boot DKA1
...
( It is able to read vmunix from rzb0 but cannot use rzb0a for
root partition. I made sure that the / and /usr partitions
on the new disk are equal or bigger than the older setup, so
I am not missing anything on the new disk. The swap is larger
as well. The original disk doesnt mount anything other than /
and /usr).
I am not sure what I am missing. Would appreciate any pointers.
Thanks!!
-vijay
ps:
My original question:
>>>
Greetings:
I'm replacing an aging root disk on one of our alpha servers
(164LX 4.0f). I made the partions and replicated the contents on the
new disk (and changed fstab file to reflect the the new disk device
names).
I'm planning to put the new disk in, change the boot device
to the new disk in SRM, and boot up. On sun systems that I'm familiar
with, you need to install a boot block on the disk to make it bootable.
I'm wondering if there is an equivalent utility on the digital unix
side.
<<<
Received on Mon Feb 28 2000 - 17:18:08 NZDT