1 Dec
2013
1 Dec
'13
9:01 p.m.
All,
I've been wrestling to get BSD 4.3 Quasijarus installed on my uVAX2. This
is what I'm doing...
1) Booting over the network to NetSBD over NetRoot
2) Used NetBSD to partition and format the disks
3) Used the 'restore' command to extract the 'dump''d root
4) Used tar to extract the proper usr (and other) directories
5) Edited the local disk's fstab
... where I'm getting hung up is bootblocks. What boot blocks do I write to
my drive and how?
I have an Emulex controller (MSCP emulator) with a SCSI disk attached. The
disk shows up as SCSI ID 1, and dua1 from the prom. It shows up as /dev/ra0
in NetBSD. I can mount/unmount the drive, etc.
I tried the NetBSD 'installboot' with 'raboot' as the bootblock and it
doesn't work with the output below...
>> b dua1
2..1..0..
?06 HLT INST
PC = 00100529
Not sure what's going on. Any ideas?
--
-Jon
Jonathan Katz, Indianapolis, IN.
1 Dec
1 Dec
9:09 p.m.
On Mon, 2 Dec 2013, Jonathan Katz wrote:
I tried the NetBSD 'installboot' with
'raboot' as the bootblock and it
doesn't work with the output below...
Try to manually dd the bootblock to the beginning of the disk...try
kraboot, bootkra, or similar.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
>> b dua1
2..1..0..
?06 HLT INST
PC = 00100529
Not sure what's going on. Any ideas?
9:24 p.m.
On Mon, Dec 2, 2013 at 12:09 AM, Cory Smelosky <b4 at gewt.net> wrote:
Try to manually dd the bootblock to the beginning of
the disk...try
kraboot, bootkra, or similar.
I did "cat rdboot bootrd > myboot; dd if=myboot of=/dev/ra0a" ... and
rdboot/bootrd were the boot blocks from Quasijarus. Same error. Maybe I
need to do it to /dev/rra0c or something, but I'm afraid that would fubar
the disk label on the local disks.
9:31 p.m.
On Mon, 2 Dec 2013, Jonathan Katz wrote:
On Mon, Dec 2, 2013 at 12:09 AM, Cory Smelosky <b4
at gewt.net> wrote:
not specified, the default names are of the form
basenameboot for the primary (block 0) bootstrap, and boot-
basename for the secondary (block 1-15) bootstrap; for exam-
ple, /usr/mdec/hpboot and /usr/mdec/boothp if the disk dev-
ice is hp0.
(from the `disklabel` man page).
You'll need both boot blocks. put raboot in block 1, and bootra with an
offset of 1 block from start of disk.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Try to manually dd the bootblock to the beginning
of the disk...try
kraboot, bootkra, or similar.
I did "cat rdboot bootrd > myboot; dd if=myboot of=/dev/ra0a" ...
and
rdboot/bootrd were the boot blocks from Quasijarus. Same error. Maybe I
need to do it to /dev/rra0c or something, but I'm afraid that would fubar
the disk label on the local disks.
9:34 p.m.
On Mon, 2 Dec 2013, Jonathan Katz wrote:
On Mon, Dec 2, 2013 at 12:09 AM, Cory Smelosky <b4
at gewt.net> wrote:
Also: c is "whole disk" on vax so I think you'll want /dev/ra0c. (It's
such a small binary I wouldn't expect it to do much damage.
#define LABELOFFSET 64 /* offset of label in sector */
( from `man 5 disklabel`. Convert that to blocks and you'll know what not
to overwrite. ;) )
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Try to manually dd the bootblock to the beginning
of the disk...try
kraboot, bootkra, or similar.
I did "cat rdboot bootrd > myboot; dd if=myboot of=/dev/ra0a" ...
and
rdboot/bootrd were the boot blocks from Quasijarus. Same error. Maybe I
need to do it to /dev/rra0c or something, but I'm afraid that would fubar
the disk label on the local disks.
2 Dec
2 Dec
5:52 a.m.
I figured it out. Somewhat.
installboot and 'dd' were being truncated after 1.5k of writing to disk. I
don't know why, but I think it was something NetBSD was doing.
Using the disklabel command I got further. I saved the existing label to
disklabel.ra0 and then re-labelled the disk with the "myboot" boot block,
which concatenated the 512-byte (1 sector) 'raboot' file with the ~6k
'bootra' file. This easily fits in the 64*512 bytes reserved for the
bootblocks.
kremvax# disklabel -R -B -b /mdec/myboot ra0 ./disklabel.ra0
That got me to
>> b dua1
2..1..0..
loading boot
and it just hung :(
Reading through documentation old and new, we're supposed to use 'rdboot'
instead of 'raboot' But I'm still lost in looking for a full solution.
3806
days inactive
3806
days old
5 comments
2 participants
participants (2)
-
b4＠gewt.net -
jon＠jonworld.com