On Mon, Jun 03, 2019 at 04:19:13PM +0300, Belous Victor wrote:
> Thanks, Claudio Jeker
>
> 03.06.2019 15:39, Claudio Jeker пишет:
> > On Mon, Jun 03, 2019 at 03:15:07PM +0300, Belous Victor wrote:
> > > Hi!
> > >
> > > I can't boot the sparc t1000 server.
> > >
> > > I have openbsd installed on virtualbox, the config openbsd server it is
> > >
> > >
> > > openbsd# uname -a
> > > OpenBSD openbsd.centerinform. 6.5 GENERIC#3 amd64
> > >
> > > openbsd# cat /etc/ethers
> > > 00:14:4f:c4:7d:d6 sparc
> > >
> > > openbsd# cat /etc/hosts
> > > 127.0.0.1 localhost
> > > ::1 localhost
> > > 192.168.215.130 sparc
> > > 192.168.215.131 openbsd
> > >
> > > openbsd# cat /etc/rc.conf.local
> > > bootparamd_flags=
> > > mountd_flags=
> > > nfsd_flags=
> > > ntpd_flags-"NO"
> > > pf=NO
> > > portmap_flags=
> > > rarpd_flags="-al"
> > > tftpd_flags="/tftpboot"
> > >
> > > openbsd# cat /etc/bootparams
> > > sparc root=192.168.215.231:/bsd.rd
> > >
> > This is not correct. bootparams points to a directory that acts as the
> > root directory on the sparc system.
> > You can set it to /home/bvictor/install/sparc64 or some other place where
> > bsd.rd is located.
>
> Now
>
> openbsd# cat /etc/bootparams
> sparc root=192.168.215.231:/home/bvictor/install/sparc64
> openbsd#
>
>
>
> >
> > > {0} ok boot net
> > You may want to use boot net bsd.rd (so that the bsd.rd kernel is loaded).
>
> {0} ok boot net bsd.rd
>
> SC Alert: Host System has Reset
> ChassisSerialNumber NNL0812010
>
>
>
> Atlas, Shpalernaya, 28 Sun T1000
>
>
>
>
> Boot device: /pci@7c0/pci@0/network@4 File and args: bsd.rd
> 1000 Mbps full duplex Link up
> >> OpenBSD BOOT 1.12
> 1000 Mbps full duplex Link up
> No response for RARP request
> open /pci@7c0/pci@0/network@4/etc/random.seed: No such file or directory
> 1000 Mbps full duplex Link up
> No response for RARP request
> open /pci@7c0/pci@0/network@4/bsd.rd: No such file or directory
>
> Boot:
>
>
> > > SC Alert: Host System has Reset
> > > ChassisSerialNumber NNL0812010
> > >
> > >
> > >
> > > Atlas, Shpalernaya, 28 Sun T1000
> > >
> > >
> > >
> > >
> > > Boot device: /pci@7c0/pci@0/network@4 File and args:
> > > 1000 Mbps full duplex Link up
> > > > > OpenBSD BOOT 1.12
> > > Trying bsd...
> > > 1000 Mbps full duplex Link up
> > > No response for RARP request
> > > open /pci@7c0/pci@0/network@4/etc/random.seed: No such file or directory
> > > 1000 Mbps full duplex Link up
> > > No response for RARP request
> > > open /pci@7c0/pci@0/network@4/bsd: No such file or directory
> > >
> > Not sure what is up with 'No response for RARP request'. In the end you
> > already got ofwboot.net loaded via tftp. It is possile that the T1000 is
> > using dhcp for this and so the RARP is not fully working (at least the
> > tcpdump output had no RARP packets in it).
>
> I thinks, OpenBSD BOOT uses RARP, but with errors. Tcpdump show, it don't
> sent ARP request correct
>
> 16:13:20.544694 0.0.0.0.bootpc > 255.255.255.255.bootps: secs:2 [|bootp]
> 0000: 4500 0148 0000 0000 0411 b5a6 0000 0000 E..H............
> 0010: ffff ffff 0044 0043 0134 7168 0101 0600 .....D.C.4qh....
> 0020: 0000 0000 0002 0000 0000 0000 0000 0000 ................
> 0030: 0000 0000 0000 0000 0014 4fc4 7dd6 0000 ..........O.}...
> 0040: 0000 0000 0000 0000 0000 0000 0000 0000 ................
> 0050: 0000 0000 0000 0000 0000 0000 0000 0000 ................
> 0060: 0000 0000 0000 ......
>
This is not a RARP packet. So it seems your system is not receiving the
RARP packets sent by ofwboot.net on the T1000. Since you mentioned that
this is a virtual system it could be that the host is filtering the
requests out. The bootloader will fall back to bootp if rarpd/bootparams
fails.
You may be able to setup dhcpd to load the kernel by setting a host entry
for the sparc system with the full path to your NFS reachable bsd.rd as
bootfile.
--
:wq Claudio
