From: Mike Broderick (broderic@MIT.EDU)
Date: Thu Aug 15 2002 - 13:03:33 EDT
Thanks to the any replies from Roberto Mackun, Andrew Macneil, Jim Belonis,
Gabor Zelenak, Oisin McGuinness, Matt Morris, alan@nabath.
osf_boot was not missing as some suggested. It was that I somehow didn't set
the file system type to advfs (to get an advfs boot block). These command
worked for me to re-write the label proerly w/o destrying data:
# disklabel -r rz8 >FILE
# disklabel -Rrt afvfs rz8 FILE RZxx
(Needed the 'RZxx' for 4.0g, but not in 5.1a)
Other suggested formats for the latter cmd were:
disklabel -R -r -t advfs /dev/rrz8a FILE /mdec/rzboot.advfs /mdec/bootrz.advfs
disklabel -t advfs -R rz18 FILE
The correct way to specify the file system type initially is
# disklabel -rw -t advfs rz8
_Mike
Mike Broderick wrote:
>
> I'm trying to do a late night urgent restore of a 4.0g system w/ hw/
> problems to new h/w. I restored the o/s file sets (all advfs) but
> cannot boot the disk...
>
> >>>boot -fl s dqb0
> pga0.0.0.15.0 - LINK_DOWN timeout
> inserting onto pollq.
> (boot dqb0.0.1.13.0 -flags s)
> block 0 of dqb0.0.1.13.0 is a valid boot block
> reading 13 blocks from dqb0.0.1.13.0
> bootstrap code read in
> base = 200000, image_start = 0, image_bytes = 1a00
> initializing HWRPB at 2000
> initializing page table at 1ff40000
> initializing machine state
> setting affinity to the primary CPU
> jumping to bootstrap code
> Removing from poll queue.
> can't open osf_boot
>
> halted CPU 0
>
> halt code = 5
> HALT instruction executed
> PC = 20000030
>
>
> I think I've seen this before and the problem is the disklabel type is
> not set to advfs. I had this problem on 5.1a and rewrote the label with...
>
> # disklabel -r dsk0 >dsk0label
> # disklabel -Rrt advfs dsk0 rz0label
>
> This does not work on 4.0g...
>
> # disklabel -r rz8 >/tmp/rz8label
> # disklabel -Rrt afvfs rz8 /tmp/rz8label
> Usage:
> Read ...
> ...
> #
>
> Anyone know how to do this?
>
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:49 EDT