Port-vax archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Stopped at ifnal stages of netbooting MicroVax II with NetBSD



Well, the saga continues.

One kind person on here looked up the source generating the panic dump:

[   2.4600070] nfs_boot: trying DHCP/BOOTP                                                        
[   5.7000070] nfs_boot: DHCP next-server: 192.168.2.25                                           
[   5.7100070] nfs_boot: my_domain=ve3id.ddns.net                                                 
[   5.7300070] nfs_boot: my_addr=192.168.2.30                                                     
[   5.7500070] nfs_boot: my_mask=255.255.255.0                                                    
[   5.7600070] nfs_boot: gateway=192.168.2.1                                                      
[  12.1900070] root on 192.168.2.25:/export/vax/root                                              
[  12.2300070] panic: nfs_mountroot: getattr for root                                             
[  12.2600070] cpu0: Begin traceback...                                                           
[  12.2700070] panic: nfs_mountroot: getattr for root                                             
[  12.2900070] Stack traceback :                                                                  
[  12.3100070]   Process is executing in user space.                                              
[  12.3400070] cpu0: End traceback...                                                             
Stopped in pid 0.1 (system) at  netbsd:vpanic+0x171:    pushl   $0                                
db>

and found that it is failing whilst trying to do a getaddr on the server to get CTIME.

I looked at wireshark and saw the last output from the server was a 'confirm mount' request, but it looked like it was using V3 of the protocol.

So I tried to manually mount from another computer using:

mount -tnfs -_onfsvers_=2 192.168.2.25:/export/vax/root /mnt/test

And it worked successfully, so I think it is not the mounting action that is failing.

I can't find any way of manually executing that getaddr function from a working computer, nothing in any manual that I have seen.

Does anybody have any ideas how to do that so I can test without having to reboot the vax every time?

cheers,

Nigel




Nigel Johnson, MSc., MIEEE, MCSE VE3ID/G4AJQ/VA3MCU
Amateur Radio, the origin of the open-source concept!
Skype:  TILBURY2591 nw.johnson%ieee.org@localhost



On 2020-12-29 10:13 a.m., Johnny Billquist wrote:
By the way, you can verify that things are exported somewhat as expected by checking with showmount -e
Also, rpcinfo -p is good, to check that both mountd and nfs is actually registered and running.

If you change /etc/exports, you need to kick mountd (send it a HUP) for it to actually read in the new exports file.

  Johnny

On 2020-12-29 16:09, Johnny Billquist wrote:
Ok. So the lines before last night essentially gave root no permissions at all. So that could be a reason for the fail.
Now root and swap are accessible by root as root. usr and home are not really accessible by root still, but I guess that is fine.

And I assume bonzo is trying to mount /export/client/root as /

So, does it work any better now?

   Johnny

On 2020-12-29 16:04, Nigel Johnson wrote:
The commente-out lines were what wa sin there last night before I added
the four new lines.  bonzo i sthe name of the client.

#/export/vax/root       *(rw)
#/export/vax/usr        *(rw)
#/export/vax/home       *(rw)
/export/client/root -maproot=root:wheel    bonzo
/export/client/swap -maproot=root:wheel    bonzo
/export/client/usr  -maproot=nobody:nobody bonzo
/export/client/home -maproot=nobody:nobody bonzo


Nigel Johnson, MSc., MIEEE, MCSE VE3ID/G4AJQ/VA3MCU
Amateur Radio, the origin of the open-source concept!
Skype:  TILBURY2591 nw.johnson%ieee.org@localhost



On 2020-12-28 9:46 p.m., Johnny Billquist wrote:
What does /etc/exports on the exporting host look like?

I hope you are aware that by default, the remote root user gets mapped
to uid -2 on the host...

   Johnny

On 2020-12-28 19:58, Nigel Johnson wrote:
Happy New Year to all,

With lots of help from mind people on this list (remember my struggles
getting mopd to work under linux?), I am now well into netboot.

However, I get to this point and a kernel panic:

.......

[  1.1400070] ra0 at mscpbus0 drive 1:
RA81
[   1.2000070] rx0 at mscpbus1 drive 1:
RX33
[   2.1700070] ra0: size 650965
sectors
[   2.6200070] boot device:
qe0
[   2.6600070] root on
qe0
[   2.6900070] nfs_boot: trying
DHCP/BOOTP
[   5.9300070] nfs_boot: DHCP next-server:
192.168.2.25
[   5.9500070] nfs_boot:
my_domain=ve3id.ddns.net
[   5.9800070] nfs_boot:
my_addr=192.168.2.30
[   6.0000070] nfs_boot:
my_mask=255.255.255.0
[   6.0100070] nfs_boot:
gateway=192.168.2.1
[  12.4200070] root on
192.168.2.25:/export/vax/root
[  12.4600070] panic: nfs_mountroot: getattr for
root
[  12.4900070] cpu0: Begin
traceback...
[  12.5000070] panic: nfs_mountroot: getattr for
root
[  12.5100070] Stack traceback
:
[  12.5300070]   Process is executing in user
space.
[  12.5600070] cpu0: End
traceback...
Stopped in pid 0.1 (system) at  netbsd:vpanic+0x171:    pushl
$0
db>

The last entry in /var/log/messages on the server is:

2020-12-28T13:51:07.796416-05:00 T540p rpc.mountd[11839]: authenticated
mount request from 192.168.2.30:1023 for /export/vax/root
(/export/vax/root)

So I am not sure what is going on - can anybody help?

All directories under /export are set RW for root.

cheers,

Nigel












Home | Main Index | Thread Index | Old Index