13 DMS Troubleshooting

This chapter contains information to assist you in troubleshooting problems with your DMS server and lists the server files and processes to check if a client is having trouble booting.

13.1 Server Areas to Check for Client Booting Problems

If a DMS client has trouble booting, you can check several aspects of server operation to ensure that the server's end of the network connection is functioning properly:

The server may not be a Network File System (NFS) server. To check whether or not a server is an NFS server, enter the following command on the server:
```
# rcmgr get NFSSERVING
```
If the response is a 1, the system is an NFS server. If the response is a 0, the system is not an NFS server. Run nfssetup to configure the server to be an NFS server.

The network daemons may not be running on the server. This condition is reported by the client with a message like the following:
```
panic: vfs_mountroot: cannot mount root
```
If this message appears on the client, check to make sure that the following daemons are running on the server:
- portmap
- mountd
- nfsd
- nfsiod
Enter the following command on the server to see if the daemons are running:
```
# ps ax | grep -E "portmap|mountd|nfsd|nfsiod"
```
Process status will appear for any of those daemons that are running. (A line will also appear showing your egrep command.) If the daemons are not all running, you must start the inoperative ones.

The client's directories may be exported improperly. Determine if this is the case by examining entries in the server's /etc/exports file:
- If the client boots to single-user mode but will not boot to multiuser mode, make sure that the appropriate /usr file system and dmsN root area have entries in /etc/exports. Proper /etc/exports entries should look similar to the entry shown below. In this example, the client name is client1.
```
/clients/client1 -r=0 client1
/var/adm/dms/dms0.alpha/root/usr -r=0 -ro
```
  The contents of these entries are described in the exports(5) reference page.

If you are installing a hardware update release and you configure the DMS environment before you add the operating system hardware update, you must connect to the root directory in the DMS environment and issue the following two commands to undo the configuration:
```
# rm -rf usr/sys/conf/DATALESS
# rm -rf usr/sys/DATALESS
```

If you cannot execute commands on the client and the server and client are on different versions of the software, check to see if you copied the dmu version on the client on to the server. Refer to Section 11.1 for more information.

If you encounter the following warning when booting a DMS client, there is a problem with the disk or disk partition designated as the swap device when the dataless client was registered.
```
WARNING: /dev/rz6c swap partition has unused fstype, failed to add swap.
       : Swap is being set to lazy (over commitment) mode. The system will
       : come up to single-user mode. Set fstype for swap partition to
       : "swap" using "disklabel -s  swap" command and reboot.
```
Follow this procedure on the client system to correct this problem.
1. As superuser, change directory to /dev.
```
# cd /dev
```
2. Execute the MAKEDEV utility on the disk or disk partition designated as the swap device.
```
# ./MAKEDEV swapdev
```
3. Set the file system type for swapdev by executing the disklabel utility. Remember to specify swapdev as a raw device.
```
# disklabel -sF /dev/rswapdev swap
```
4. Reboot the client system.