Solaris - Can't mount my cdrom

As root :

drvconfig

and try again.

The cdrom must on
and with cdrom medium

after try

eject -q  

try:

mount -F hsfs -o ro /dev/dsk/c0t1d0s2 /cdrom

if your 2nd hd is /dev/dsk/c0t1d0  then:

mount -F hsfs -o ro /dev/dsk/c0t2d0s2 /cdrom

or soemting like:
mount -F hsfs -o ro /dev/dsk/c0t1d0s0 /cdrom

Thanks for the help, but unfortunately, none of these suggestions worked.  Here is the output from some of them:

bash-2.03# drvconfig
bash-2.03# cd /cdrom
bash-2.03# ls
bash-2.03# cd /
bash-2.03# eject -q
No default media available
bash-2.03# mount -F hsfs -o ro /dev/dsk/c0t1d0s2 /cdrom
mount: /dev/dsk/c0t1d0s2 is already mounted, /cdrom is busy,
        or allowable number of mount points exceeded
bash-2.03# mount -F hsfs -o ro /dev/dsk/c0t2d0s2 /cdrom
hsfs mount: /dev/dsk/c0t2d0s2 is not an hsfs file system.
bash-2.03# mount -F hsfs -o ro /dev/dsk/c0t1d0s0 /cdrom
mount: /dev/dsk/c0t1d0s0 is already mounted, /cdrom is busy,
        or allowable number of mount points exceeded

Thanks for the help.  Here is a look at what is mounted:

bash-2.03# df -k
Filesystem            kbytes    used   avail capacity  Mounted on
/dev/dsk/c0t0d0s0    6191949 5263353  866677    86%    /
/proc                      0       0       0     0%    /proc
fd                         0       0       0     0%    /dev/fd
mnttab                     0       0       0     0%    /etc/mnttab
swap                  460552      16  460536     1%    /var/run
swap                  460896     360  460536     1%    /tmp
/dev/dsk/c0t0d0s3    7995933 7761914  154060    99%    /space
/dev/dsk/c0t2d0s6    39523340       9 39128098     1%    /oracle

Try this ( Solaris servers )
drvconfig
Insert the CDROM into the drive
then try to stop/start the following service
/etc/init.d/volmgt stop/start

ps -ef | grep vold  If vold process is running, stop and start the vold process

Stop the vold process by entering
kill -15 process_ID_number

Start the vold process by entering
/usr/sbin/vold &

Make sure vold process is running and /cdrom exists in root directory

Then execute the following command:
mount -F hsfs -o ro /dev/dsk/c0t0d0s2 /cdrom/cdrom0

The default device for the cdrom is /dev/dsk/c0t6d0s2

For barthalamu's system, the cdrom is
/dev/dsk/c0t0d0s2

I forgot to mention, if you need to mount the cdrom manualy, you need to STOP "vold" -volume manager, and make sure that the mount point is an empty dir

Try:

/etc/rc2.d/S92volmgt stop

mkdir /aa
mount -F hsfs -o ro /dev/dsk/c0t0d0s2

to make sure that a dir is not using by any process:

fuser -c -k /dir-name

Thanks pchandar and Tintin, but it did not work.  Here is the output.

ps -ef | grep vold
    root  1244  1237  5 18:47:36 pts/4    0:02 /usr/sbin/vold
    root  1247  1237  0 18:47:47 pts/4    0:00 grep vold

bash-2.03# mount -F hsfs -o ro /dev/dsk/c0t0d0s2 /cdrom/cdrom0
mount: mount-point /cdrom/cdrom0 does not exist.

bash-2.03# mount -F hsfs -o ro /dev/dsk/c0t0d0s2 /cdrom      
hsfs mount: /dev/dsk/c0t0d0s2 is not an hsfs file system.

bash-2.03# mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /cdrom
mount: No such device
mount: cannot mount /dev/dsk/c0t6d0s2

A typing error on my previous command, the device should be:

/dev/dsk/c0t1d0s2

So try:

/etc/rc2.d/S92volmgt stop
mkdir /aa
mount -F hsfs -o ro /dev/dsk/c0t1d0s2

to make sure that a dir is not using by any process:

fuser -c -k /dir-name

I STILL can't mount my cdrom.  Thanks for all the help from everyone though.  Could my cdrom have gone physically bad?  It seems fine.  I may try swapping it out for another.

Perhaps the cd is wrong.

Put a new cd example with
Solaris 8

Otetelisanu:

Good thought, but I have tried it with several real cds.

per the ls output of /dev/dsk and df -k, your cdrom appears to be on /dev/dsk/c0t1d0s2.  insert the cd into the drive and then su to root and run:  fstyp /dev/dsk/c0t1d0s2 - this will return the fstype of the cd.  With that information do:  mount -F <fstype> -o ro /dev/dsk/c0t1d0s2 /cdrom.  Replace <fstype> with the appropriate fstype.  You could also use /mnt instead of /cdrom.

Try the following.

1. start volume management
   /etc/init.d/volmgt start
2. mount your CD on to the CD Drive
3. run "volcheck" command
   # volcheck
4. df -k should show that CD as mounted.

Please post your results.

barthalamu,

From reading this thread, I'm not sure you know exactly what the device is for your CD-ROM. To get this, execute the following command:

# cfgadm -al | grep CD
c0::dsk/c0t1d0                 CD-ROM       connected

The data in column 1 is relative, so you must prefix it with /dev. For example, /dev/dsk/c0t1d0.  I don't know what type of system you have, so your results will probably be different.  Notice that we haven't specified a "slice" yet.

Once you have this device path, you need to try to mount slice 0 of the CD-ROM, not slice 2. If you try to mount slice 2, you get the "is not an hsfs file system" error.  Using the example above, just append "s0" to the device path. For example, /dev/dsk/c0t1d0s0.

"Yuzh" was correct that you need to make sure vold isn't running before you try this. Also, make sure you are not sitting in the /cdrom directory when you try to mount the CD-ROM.  Here are the steps.


Replace c#t#d#s0 with your correct device path:


# pkill vold
# cd /
# mount -F hsfs -o ro /dev/dsk/c#t#d#s0 /cdrom
# df -k


If this doesn't work, something else is very messed up. However, you can determine if your CD-ROM drive is still working by booting the system from the CD-ROM. For example, at the ok prompt:

ok boot cdrom

If the system boots from the CD-ROM, you kow the drive is still working properly.

I hope this helps.

With a cdrom you need to mount slice 2 as this represents the entire disk, otherwise, you will receive an error.  man vold for more information.

Bring your system down to the OK prompt then type
probe-scsi-all

If your disk is IDE then type
probe-ide-all

If your cdrom shows up with one of them then it may be good.

Find the target for the cdrom, insert a Solaris CD into it. You can then type "show-disks" to find the attached controllers for you system. Choose the one from your probe-ide or probe-scsi command. You then would type

boot ^y2,0:f -s

control y will insert the controller you want to boot off of. You then need to specify the target and slice to boot.

Here are two examples, one for scsi and one for ide.

boot /pci@1f,0/pci@1/scsi@3/disk@2,0:f -s

boot /pci@1f,0/pci@1,1/ide@3/disk@2,0:f -s

disk@2,0:f (2 is for the target, the 0 is for the LUN the :f tells it to boot the partition for an ultra. :d is for SPARC)

If your system boots after this then reply back to me. Otherwise replace your CDROM.


###NOTE###
The recommendation from barthalmu might work if you were trying to mount anything but a solaris cdrom.

S0 is HSFS
S1-S5 are all UFS. S2 is not the whole disk on a solaris cdrom.

mount -F hsfs -o ro /dev/dsk/c0t2d0s0 /cdrom

remember to turn off volmgt.

It is actually useless to mount slice 2 because it should only contain a link back to slice zero with the proper architecture identified (sun4m).

Thanks for the advise all...I don't have access to that machine for a few days.  I will try all the suggestions then.  Thanks.

Thanks for everyone who has tried to help me.  Here is the output from some suggestions:

cysurfer:

without vold running:
# fstyp /dev/dsk/c0t1d0s2
hsfs fstyp: cannot open </dev/dsk/c0t1d0s2>
/dev/dsk/c0t1d0s2: No such device or address
udfs fstyp: cannot open </dev/dsk/c0t1d0s2> errorno <6>
/dev/rdsk/c0t1d0s2: No such device or address
Unknown_fstyp (no matches)

with vold running:
# fstyp /dev/dsk/c0t1d0s2
hsfs fstyp: cannot open </dev/dsk/c0t1d0s2>
/dev/dsk/c0t1d0s2: Device busy
udfs fstyp: cannot open </dev/dsk/c0t1d0s2> errorno <16>
/dev/rdsk/c0t1d0s2: Device busy
Unknown_fstyp (no matches)


rearls1:

# cfgadm -al | grep CD
c0::dsk/c0t1d0                 CD-ROM       connected    configured   unknown

Without vold:
# ./volmgt stop
# ps -ef | grep vold
# mount -F hsfs -o ro /dev/dsk/c0t1d0s0 /cdrom_mount
mount: /dev/dsk/c0t1d0s0 no such device

With vold running:
# mount -F hsfs -o ro /dev/dsk/c0t1d0s0 /cdrom_mount
mount: /dev/dsk/c0t1d0s0 is already mounted, /cdrom_mount is busy, or allowable number of mount points exceeded

Also, I'm definately not in the /cdrom_mount directory.  I have not tried booting from the CDROM of this machine, as I don't have physical access to it for a little while.  I will try this though.

guerriero33t:

Thanks for the suggestion.  When I have physical access to the machine again, I will try this.


Again...thanks to all for the helpful advise.  I am still trying.

It has been a while, so I do not know if you are still trying to mount the cdrom.

I also installed JASS and had a similar issue.  Here is how I solved it:

Make sure you vold is shutdown:  ps -ef | grep vold

If in the future you mount cdrom and floppies to be automounted you need to enable the vold daemon.



Do the following to determine where your cd is located:

iostat -En

You will get a response similar to this:

c0t0d0          Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: SEAGATE  Product: ST318203LSUN18G  Revision: 034A Serial No: LRK8328900007111
Size: 18.11GB <18110967808 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c1t2d0          Soft Errors: 0 Hard Errors: 0 Transport Errors: 1
Vendor: TOSHIBA  Product: CD-ROM XM-7002Bc Revision: 1110 Serial No: 04/27/00
Size: 18446744073.71GB <-1 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0

In my case as you can see, the CDROM was located at c1t2d0. To that I added slice s0 to mount it:

mount -F hsfs -o ro /dev/dsk/c1t2d0s0 /mnt/cdrom

Be careful with your 1 (one) and l (L) and 0 (zero) and o (O)'s.

Good luck

Hi barthalamu!

I head your same problem on my ultra10 with solaris 9...

Maybe you made my same mistake: I have been commented the line

# smserverd to support removable media devices
100155/1   tli   rcp/ticotsord   wait   root   /usr/lib/smedia/rpc.smserverd rpc.smserverd

in my /etc/inetd.conf.


If you run

rmmount -D -c /etc/rmmount.conf -d /dev/dsk/your_cdrom

I suppose you got an error message like

rmmount(some_number) VOLUME_ACTION was null

This mean vold can't connect to smmserverd service.

I hope you can fix your trouble!
Good luck!
biggeorge

P.S. Sorry for my horrible english... :o)

No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is:

PAQ and refund

Please leave any comments here within the next four days.

PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!

liddler
EE Cleanup Volunteer