18.02.2014 Views

string

string

string

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

(Continuation)<br />

panic - boot: Could not mount filesystem.<br />

program terminated<br />

ok<br />

Normally this is a result of the bootparams not being able to get to the install<br />

image.<br />

The second problem is that other users have had the same error message, with the<br />

additional message:<br />

’Timeout waiting for ARP/RARP packet...’<br />

Action<br />

To solve the first problem:<br />

1. Check how the dfstab(4) (/etc/dfs/dfstab on the install image NFS server)<br />

looks:<br />

share -F nfs -o ro,anon=o /jumpstart-dir<br />

2. Run share(1M) command on the installed image NFS server, to make sure it is<br />

shared properly.<br />

3. Check /etc/bootparams file on the net install server. Look for entries with<br />

incorrect boot path.<br />

4. Make sure that /usr/sbin/rpc.bootparamd is running on the boot server. If<br />

necessary, kill and restart it.<br />

5. Check /etc/ethers on the boot server for duplicate or conflicting entries<br />

6. At OK prompt, run test net /test-net and/or watch net /watch-net to test the<br />

network connectivity<br />

A workaround for the second problem is to check the nsswitch.conf(4) file. If<br />

some of the entries point to NIS such as:<br />

rpc nis files<br />

hosts nis files<br />

ethers nis files<br />

bootparams files<br />

nis<br />

Alphabetical Message Listing 151

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!