4.0.1 mount problems

Article View: comp.sys.sun

Article #11080

#11080

From: Lee Ward
Date: Wed, 22 Feb 1989 14:20

56 lines
2971 bytes

Any idea why a 3/60 client would panic trying to mount root from a 3/180
server?

It looks like the client responds with "bad port" with an ICMP error after
loading the kernel on the root mount request. The ethernet interface on
the 3/180 is configured:

ie0: flags=43<UP,BROADCAST,RUNNING>
        inet 129.24.12.130 netmask fffff800 broadcast 129.24.15.255

All the 60's do this under any network load. Below is the (edited to
relevant info) output of an etherfind. Oh yeah, eventually (hours later)
the boot succeeds. So much for the network IS the computer...

The end of tftp boot and initial mount to get the kernel:

UDP from 129.24.12.160.1344 to 129.24.12.130.1060  12 bytes
UDP from 129.24.12.160.1344 to 129.24.12.130.1060  12 bytes
UDP from 129.24.12.160.1344 to 129.24.12.130.1060  12 bytes
   60  arp   129.24.12.160   129.24.12.130
UDP from 129.24.12.160.1022 to 129.24.12.130.710  124 bytes
 RPC Call prog 100026 proc 2 V1
   60  arp   129.24.12.160   129.24.12.130
UDP from 129.24.12.160.1021 to 129.24.12.130.sunrpc  136 bytes
 RPC Call portmapper  PMAPPROC_GETPORT  V2
UDP from 129.24.12.160.1020 to 129.24.12.130.697  128 bytes
 RPC Call mountd  MNTPROC_MNT  V1
UDP from 129.24.12.160.1019 to 129.24.12.130.2049  124 bytes
 RPC Call nfs  RFS_GETATTR  V2

After the kernel is loaded...

UDP from 129.24.12.160.1019 to 129.24.12.130.2049  136 bytes
 RPC Call nfs  RFS_READ  V2
   60  arp   129.24.12.160   129.24.12.130
UDP from 129.24.12.160.1023 to 129.24.12.130.710  124 bytes
 RPC Call prog 100026 proc 2 V1
UDP from 129.24.12.160.1023 to 129.24.12.130.sunrpc  104 bytes
 RPC Call portmapper  PMAPPROC_GETPORT  V2
UDP from 129.24.12.160.1023 to 129.24.12.130.697  128 bytes
 RPC Call mountd  MNTPROC_MNT  V1
UDP from 129.24.12.160.1023 to 129.24.12.130.697  128 bytes
 RPC Call mountd  MNTPROC_MNT  V1
UDP from 129.24.12.160.1023 to 129.24.12.130.697  128 bytes
 RPC Call mountd  MNTPROC_MNT  V1
UDP from 129.24.12.160.1023 to 129.24.12.130.697  128 bytes
 RPC Call mountd  MNTPROC_MNT  V1
UDP from 129.24.12.160.1023 to 129.24.12.130.697  128 bytes
 RPC Call mountd  MNTPROC_MNT  V1
ICMP from 129.24.12.160 to 129.24.12.130 dst unreachable bad port
  bad packet was: UDP from 129.24.12.130.697 to 129.24.12.160.1023  68 bytes
 RPC Call prog 2 proc 10 V1129512960
ICMP from 129.24.12.160 to 129.24.12.130 dst unreachable bad port
  bad packet was: UDP from 129.24.12.130.697 to 129.24.12.160.1023  68 bytes

			--Lee (Ward)

Technical Details

Message-ID: <2276@unmvax.unm.edu>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!ames!husc6!rice!sun-spots-request

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!ames!husc6!rice!sun-spots-request
From: lee@doc.cs.unm.edu (Lee Ward)
Newsgroups: comp.sys.sun
Subject: 4.0.1 mount problems
Message-ID: <2276@unmvax.unm.edu>
Date: 22 Feb 89 14:20:02 GMT
Sender: usenet@rice.edu
Organization: University of New Mexico at Albuquerque
Lines: 56
Approved: Sun-Spots@rice.edu
Original-Date: 15 Feb 89 23:42:08 GMT
X-Sun-Spots-Digest: Volume 7, Issue 165, message 4 of 15