Sol 10 11/04 issue on sun w1100z

Apparently I'm the only one with this problem. But I've reinstalled 8 times and it is the same every time. Not sure what I'm doing wrong.

Basically after installing Solaris I can no longer mount anything. This is solaris 10 SX latest version downloaded. It boots up fine and mounts the local filesystems for swap and / but if I put a CD in the drive (any drive, any CD) it just spits it back out when it tries to read it.

Also my USB devices no longer mount.

I haven't seen any errors in my logs or dmesg that would point to it. But I honestly am not sure what to look for.

I don't know if this has anything to do with it but I want to inform you anyway. My system is on a lan with a netgear wifi router. It's got a built-in DHCP server which assigns IP address only, no hostname / domain names. When going through the install I select Networked system, DHCP, no ipv6, and yes to DNS. I give it the domain name, and nameserver IP and it complains about not being able to resolve it's own domain name (I think that was the error). Asks if I want to accept or change config, I just accept.

After rebooting the system name is "Unknown". Should this matter?

Also it asks for NFS v4 if I want to use the system derived domain name or supply my own. I've tried both options with no different results.

Any ideas what i can do to get this working? I'm guessing it's an automount problem someway tied to NFS. But like I said I'm not sure.

Nick

[1509 byte] By [nes@students.uwf.edu] at [2007-11-26 0:42:59]
# 1

Concerning the ejecting CD, and perhaps the USB issue...

The good news is that you aren't going crazy, it is a known

bug with a workaround. By default, the removable media

service is not starting because it is disabled during the

installation. Hopefully the fix will be integrated soon.

Meanwhile the workaround is to enable the service.

First, check the status:

# svcs -l svc:/network/rpc/smserver:default

if it is disabled, then you should enable it:

# svcadm enable svc:/network/rpc/smserver:default

then recheck the status and see if it is enabled.

Concerning the DHCP stuff, you will be unhappy if you let

the nodename be set by DHCP. There are several ways

to work around this, but basically you want the /etc/nodename

file to contain a name which is also aliased to localhost in the

/etc/inet/hosts

file. Meanwhile, there should be a file

/etc/hostname.?

which should contain "dhcp".

With this sort of configuration, any process which assumes that

the nodename is the same a hostname for the host will work

(eg. X).

Concerning the NFSv4 question, you can blissfully ignore this

until such time as your servers are running NFSv4. This is a

new feature provided by NFSv4 which will be the client default

NFS version, hence the question is asked, but it won't be

meaningful until you servers are running NFSv4 at which time

you should be able to get the answer from your sys admin.

-- richard

relling1 at 2007-7-5 19:38:47 > top of Java-index,Solaris Operating System,Solaris 10 Features...