Hello-
I need to make a disk that I created by copying the / and /usr partitions
from a running system into a bootable disk. I tried doing this earlier today
and got the following when I booted the system up:
>>> b dkc300
CPU 0 booting
(boot dkc300.3.0.4.1 -flags s)
block 0 of dkc300.3.0.4.1 is a valid boot block
reading 13 blocks from dkc300.3.0.4.1
bootstrap code read in
Building FRU table
base = 200000, image_start = 0, image_bytes = 1a00
initializing HWRPB at 2000
initializing page table at 1f2000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
can't open osf_boot
halted CPU 0
I used the following to label the disk:
disklabel -wr -t advfs rz19 hsz50 /mdec/rzboot /mdec/bootrz
The disk is an advfs type disk, which I have mounted now, which does have
the file /osf_boot in the root directory. A diff on the osf_boot on the
operating disk and the new disk show no differences.
What am I missing to make this new disk bootable?
What magic does the CDROM installation perform that I can't seem to do from
the Unix command line?
Thank you in advance for any assistance with this issue.
Sue Hodges
attached mail follows:
Hello-
I need to make a disk that I created by copying the / and /usr partitions
from a running system into a bootable disk. I tried doing this earlier today
and got the following when I booted the system up:
>>> b dkc300
CPU 0 booting
(boot dkc300.3.0.4.1 -flags s)
block 0 of dkc300.3.0.4.1 is a valid boot block
reading 13 blocks from dkc300.3.0.4.1
bootstrap code read in
Building FRU table
base = 200000, image_start = 0, image_bytes = 1a00
initializing HWRPB at 2000
initializing page table at 1f2000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
can't open osf_boot
halted CPU 0
I used the following to label the disk:
disklabel -wr -t advfs rz19 hsz50 /mdec/rzboot /mdec/bootrz
The disk is an advfs type disk, which I have mounted now, which does have
the file /osf_boot in the root directory. A diff on the osf_boot on the
operating disk and the new disk show no differences.
What am I missing to make this new disk bootable?
What magic does the CDROM installation perform that I can't seem to do from
the Unix command line?
Thank you in advance for any assistance with this issue.
Sue
Received on Wed Sep 22 1999 - 20:00:09 NZST