02-11-2004
mounting cdrom on Solaris 9
Here's some cmd output:
bash-2.05# ls /dev/dsk/*
/dev/dsk/c0t0d0s0 /dev/dsk/c0t0d0s4 /dev/dsk/c0t1d0s0 /dev/dsk/c0t1d0s4
/dev/dsk/c0t0d0s1 /dev/dsk/c0t0d0s5 /dev/dsk/c0t1d0s1 /dev/dsk/c0t1d0s5
/dev/dsk/c0t0d0s2 /dev/dsk/c0t0d0s6 /dev/dsk/c0t1d0s2 /dev/dsk/c0t1d0s6
/dev/dsk/c0t0d0s3 /dev/dsk/c0t0d0s7 /dev/dsk/c0t1d0s3 /dev/dsk/c0t1d0s7
bash-2.05# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 20165785 4433381 15530747 23% /
/dev/dsk/c0t0d0s6 5041230 3708031 1282787 75% /usr
/proc 0 0 0 0% /proc
mnttab 0 0 0 0% /etc/mnttab
fd 0 0 0 0% /dev/fd
/dev/dsk/c0t0d0s1 962367 135017 769608 15% /var
swap 539600 40 539560 1% /var/run
swap 540184 624 539560 1% /tmp
bash-2.05# mount -oro /dev/dsk/c0t1d0s6 /cdrom
mount: I/O error
mount: cannot mount /dev/dsk/c0t1d0s6
bash-2.05# mount -oro /dev/dsk/c0t1d0s3 /cdrom
mount: I/O error
mount: cannot mount /dev/dsk/c0t1d0s3
bash-2.05# mount -oro /dev/dsk/c0t0d0s6 /cdrom
mount: /dev/dsk/c0t0d0s6 is already mounted, /cdrom is busy,
or the allowable number of mount points has been exceeded
As you can see from my output, I can't mount anywhere. If I try to mount using any of the partitions on d0 then I get the /cdrom is busy or the allowable number of mount points has been exceeded. If I try to mount on t1 then I just get I/0 error. I'm just trying to load a trial of StarOffice. What's going on here and why is this so difficult? Any advice would be great.--thanks--AJ
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
ok here is what i do and get:
# mount /dev/sd6a /cdrom
mount /dev/sd6a write-protected
ok so what do i do its a external cdrom and its on scsi number 6. its a SparcSTATION 2. we're trying to put red hat sparc 6.2 on it but it wont boot. i am about to take the hard drives out and install it a... (8 Replies)
Discussion started by: wixifer
8 Replies
2. UNIX for Dummies Questions & Answers
Hallo,
who can help me to configure a scsi cd writer to my sun server enterprice 1000.
1. Hardware configuration
2. Burn program
etc..
Please send me links or dokuments were i can get more infos about this theme.
regards joerg (1 Reply)
Discussion started by: joerg
1 Replies
3. UNIX for Dummies Questions & Answers
Somebody loaded RH 7.3 for me on my PC & now I'm running through & configuring all my settings.
Question: Every time I insert a CD into the cdrom, it automatically mounts the cdrom if there's anything on the CD. How do I disable this? I don't want it to automount.
Thanks in advance!! (2 Replies)
Discussion started by: jalburger
2 Replies
4. UNIX for Dummies Questions & Answers
Hey everyone,
Quick question...I am trying to get packages off a cdrom for NETBSD. I tried mounting using this command mount /dev/rccd0a /etc/home/cdrom. But I just get an error.
I did a dmesg |grep ^cd and it said that my cdrom was at cd0.?
Am I doing something wrong.? Any help would... (2 Replies)
Discussion started by: vaff4k
2 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I'm looking to mount a cd on an old AViiON system we have. No one here really has any expertise with this platform so any help will be appreciated. I * think* the device is sd(apsc(pci(1),B,0,7),5,0), however I'm not sure at all.
Thanks! (0 Replies)
Discussion started by: madesjardins
0 Replies
6. Solaris
Hi,
I want to know HOw can I know on which slice cdrom is mounted?by default on which slice generally it is mounting? (1 Reply)
Discussion started by: manoj.solaris
1 Replies
7. Solaris
Hello,
I'm a new SA fairly familar with Solaris. I'm using the COEInstaller tool and am unable to read a cd. The cd is fine.
The machine continues to see the last cdrom I've used which was an image. I've tried restarted the server, restarted COEInstaller but the machine still see's the last... (3 Replies)
Discussion started by: computerguy_2
3 Replies
8. Solaris
Hello,
First i'm Dutch, and my English is not very well. Sorry. :D
I have got a Sun Microsystems Ultra 3D (with SPARC processor). The file must be burned to a DVD. And my computer can onley read a cd.
How to get Solaris 10 on a few cds?
Please help me.
Thanks a lot..
Greets. (21 Replies)
Discussion started by: TomW
21 Replies
9. Solaris
hi unix friends,
has anyone faced this problem before ? i inserted my cd into my X1450 machine, it says I/O error.
mount -F hsfs -o ro /dev/dsk/clt0d0s0 /cdrom
mount: I/O error
mount: cannot mount /dev/dsk/c1t0d0s0
what should i do ? (4 Replies)
Discussion started by: Exposure
4 Replies
10. Shell Programming and Scripting
Hi All,
I need a simple udev rules in my server Centos 5.4. This rules needs to get trigger my script whenever the cdrom is attached to the server.
Could you please provide your suggestion on it.
Thanks,
Kalai (0 Replies)
Discussion started by: kalpeer
0 Replies
LEARN ABOUT HPUX
cmdisklock
cmdisklock(1m) cmdisklock(1m)
NAME
cmdisklock - manage Serviceguard cluster lock devices.
SYNOPSIS
cmdisklock check path
cmdisklock [-f] reset path
DESCRIPTION
cmdisklock is a tool to check the current state of a Serviceguard cluster lock device. It can also be used to reset the state of the clus-
ter lock device. The need to reset the cluster lock device state could arise if the cluster lock device is replaced or becomes corrupt.
A cluster lock device can be either an HP-UX LVM cluster lock or a cluster lock LUN device. HP-UX LVM cluster locks exist only on a disk
in an LVM volume group. Cluster lock LUNs exist only on disks dedicated to cluster lock. cmdisklock is useful for checking either type of
cluster lock and for re-initializing cluster lock LUN devices after a failure or corruption.
NOTE
To restore an HP-UX LVM cluster lock, use vgcfgrestore. cmdisklock will fail until vgcfgrestore is run, and cmdisklock is unnecessary as
long as vgcfgbackup was done after the cluster lock was initialized. See the Managing Serviceguard manual for details.
The syntax of the path option depends on the type of lock. For HP-UX LVM cluster lock disks, the syntax is VG:PV (for example:
/dev/vglock:/dev/dsk/c0t0d2). For cluster lock LUN disks, the path is the disk device path. For example, /dev/sdd1 (on Linux) or
/dev/dsk/c0t1d2 (on HP-UX).
Options
cmdisklock supports the following options:
check Check the current state of the cluster lock device and report the results.
reset Reset (initialize) the state of the cluster lock device. This operation should only be performed on a cluster lock
LUN device. For HP-UX LVM cluster lock, use vgcfgrestore as documented in the Managing Serviceguard manual. After
performing a reset, a check can be used to verify that the lock is cleared.
EXAMPLES
If the cluster lock LUN device becomes corrupted and the cluster is up, messages like the following will appear in syslog.
Mar 15 12:20:41 usb cmdisklockd[17599]: WARNING: Cluster lock LUN /dev/dsk/c0t1d2 is corrupt: bad label. Until this situation is cor-
rected, a single failure could cause all nodes in the cluster to crash.
Mar 15 12:20:41 usb cmdisklockd[17599]: After ensuring that all active nodes in the cluster have logged this message, run 'cmdisklock reset
/dev/dsk/c0t1d2' to repair
Mar 15 12:20:41 usb cmdisklockd[17599]: Cluster lock disk /dev/dsk/c0t1d2 is inaccessible
Once the above messages appear in syslog on all running nodes, the following command will re-initialize the cluster lock LUN:
ucd:/> cmdisklock reset /dev/dsk/c0t1d2
WARNING: Cluster lock LUN /dev/dsk/c0t1d2 is corrupt: bad label. Until this situation is corrected, a single failure could cause all nodes
in the cluster to crash.
After ensuring that all active nodes in the cluster have logged this message, run 'cmdisklock reset /dev/dsk/c0t1d2' to repair
/dev/dsk/c0t1d2 is inaccessible
Resetting cluster lock device /dev/dsk/c0t1d2
Cluster lock reset completed
/dev/dsk/c0t1d2 is accessible
cleared
After the lock is restored, a message like the following appears in syslog:
Mar 15 12:23:11 usb cmdisklockd[17599]: Cluster lock disk /dev/dsk/c0t1d2 is accessible
WARNINGS
CAUTION
For cluster lock LUN, reset is a potentially destructive operation. While cmdisklock checks for known volume manager and file system use
(overridden by -f), it does not validate that the device to be reset is actually used by any cluster. If -f is used on the wrong device
file, loss of data may result.
CAUTION
Care should be taken when doing a reset when the cluster is active as there is a remote possibility that the cluster will partition right
when this command is run and both nodes could end up thinking they have successfully acquired the lock. To avoid this situation, make sure
cmcld has logged a message in syslog on all running nodes saying the device is inaccessble, before performing a reset. Note that it is
safe to run cmdisklock when the cluster is down.
RETURN VALUE
cmdisklock returns the following values:
0 Successful completion.
1 The disk is inaccessible or is not recognized as a cluster lock.
AUTHOR
cmdisklock was developed by HP.
SEE ALSO
cmapplyconf(1m), cmviewcl(1m), vgcfgbackup(1m), vgcfgrestore(1m)
Requires Optional Serviceguard Software cmdisklock(1m)