UNIX for Advanced & Expert Users

I have a problem mounting a particular CD on both my E220R servers, the same CD mounts on all my unlta10 servers.
I tried mounting with volmgt started and manually after stopping volmgt. but neither worked. These servers are able to mount every other Cd inserted in them.
The mount command line i used was;
mount -F hsfs -r -o ro /dev/dsk/c0t6d0s0 /cdrom
and it gave me this error message;
mount: /dev/dsk/c0t6d0s0 no such device
Meanwhile i tried manual mount of other Cds on the same machine with same command line and it worked, save that i had to start volmgt before i could eject them.


What could be the problem/

It seems like it's a problem with the content of the cd instead of something wrong with your command (although I don't know why you use -r (mount read-only) and -o ro (mount option read-only).

What is on the cd that you are trying to mount?

I thot i mentioned the fact that the CD i was trying to load was successfully loaded on my ultra 10 servers. Soo it cannot be a CD content problem.

I think the E220R is generally a shitty Sun hardware. The Ultra 10's are far more rugged.

So you did mention that. Sorry.

Are the U10s running the same version of Solaris? Same patch level?

Do you have to stop vold to manually mount those other CDs that work? Will vold not mount them?

What is the patch level of the 220R? What version of OS?

Also check that your 220R has the same known filesystems as the U10s (compare the /etc/fs directories)

Also, if you can, post what the cd is that will not mount. It still may have something to do with the OS, patch level, and type of cd. If I happen to have the same one, then I can load it on a 220R to see if there is a problem with mine that I can assist you further.

Did you manually mount the other CD's ??
The default is that vold will use the automounter to mount CD's in /cdrom/cdrom0 ...

What does vold output to /var/adm/messages when you put this CD in with it running?

the message
mount: /dev/dsk/c0t6d0s0 no such device

can be explained as: there is not a device file in the /dev/dsk directory.

so maybe theres no device file for a cdrrom at all OR you try to use a wrong device.

You can check the dmesg output for the correct device name,if found you can check the /dev/.. directory if this file exist.

if the device file does not exist, you need to reboot your system with the -r option to rebuild the device directories.

other option, the cd-device is out of order.

take care