Sponsored Content
Full Discussion: mounting cdrom on Solaris 9
Operating Systems Solaris mounting cdrom on Solaris 9 Post 47466 by RTM on Wednesday 11th of February 2004 08:42:07 AM
Old 02-11-2004
Try Pressy's suggestion first - volume manager and automount should find it.

Also, normally the cdrom is target 6 so you should be looking for c0t6, c1t6, ... check what the target number is by looking at what is set on the cdrom (if appropriate)

If this is not X86 Solaris, then check that the system actually sees the cdrom from the ok prompt with probe-scsi-all.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

still cant get the solaris cdrom!!

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

burn cdrom with solaris

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

stop cdrom from auto-mounting

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

mounting cdrom

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

Mounting cdrom on DG/UX

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

cdrom mounting

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

SOLARIS 8 cdrom not being read

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

Solaris 10 on CDROM?

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

I/O error when mounting cdrom in Solaris 10

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

udev rules for mounting CDROM

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
scdpm(1M)						  System Administration Commands						 scdpm(1M)

NAME
scdpm - manage disk path monitoring daemon SYNOPSIS
scdpm [-a] {node | all} scdpm -f filename scdpm -m {[node | all][:/dev/did/rdsk/]dN | [:/dev/rdsk/]cNtXdY | all} scdpm -n {node | all} scdpm -p [-F] {[node | all][:/dev/did/rdsk/]dN | [/dev/rdsk/]cNtXdY | all} scdpm -u {[node | all][:/dev/did/rdsk/]dN | [/dev/rdsk/]cNtXdY | all} DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. The scdpm command manages the disk path monitoring daemon in a cluster. You use this command to monitor and unmonitor disk paths. You can also use this command to display the status of disk paths or nodes. All of the accessible disk paths in the cluster or on a specific node are printed on the standard output. You must run this command on a cluster node that is online and in cluster mode. You can specify either a global disk name or a UNIX path name when you monitor a new disk path. Additionally, you can force the daemon to reread the entire disk configuration. You can use this command only in the global zone. OPTIONS
The following options are supported: -a Enables the automatic rebooting of a node when all monitored disk paths fail, provided that the following conditions are met: o All monitored disk paths on the node fail. o At least one of the disks is accessible from a different node in the cluster. You can use this option only in the global zone. Rebooting the node restarts all resource and device groups that are mastered on that node on another node. If all monitored disk paths on a node remain inaccessible after the node automatically reboots, the node does not automatically reboot again. However, if any monitored disk paths become available after the node reboots but then all monitored disk paths again fail, the node automatically reboots again. You need solaris.cluster.device.admin role-based access control (RBAC) authorization to use this option. See rbac(5). -F If you specify the -F option with the -p option, scdpm also prints the faulty disk paths in the cluster. The -p option prints the cur- rent status of a node or a specified disk path from all the nodes that are attached to the storage. -f filename Reads a list of disk paths to monitor or unmonitor in filename. You can use this option only in the global zone. The following example shows the contents of filename. u schost-1:/dev/did/rdsk/d5 m schost-2:all Each line in the file must specify whether to monitor or unmonitor the disk path, the node name, and the disk path name. You specify the m option for monitor and the u option for unmonitor. You must insert a space between the command and the node name. You must also insert a colon (:) between the node name and the disk path name. You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5). -m Monitors the new disk path that is specified by node:diskpath. You can use this option only in the global zone. You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5). -n Disables the automatic rebooting of a node when all monitored disk paths fail. You can use this option only in the global zone. If all monitored disk paths on the node fail, the node is not rebooted. You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5). -p Prints the current status of a node or a specified disk path from all the nodes that are attached to the storage. You can use this option only in the global zone. If you also specify the -F option, scdpm prints the faulty disk paths in the cluster. Valid status values for a disk path are Ok, Fail, Unmonitored, or Unknown. The valid status value for a node is Reboot_on_disk_failure. See the description of the -a and the -n options for more information about the Reboot_on_disk_failure status. You need solaris.cluster.device.read RBAC authorization to use this option. See rbac(5). -u Unmonitors a disk path. The daemon on each node stops monitoring the specified path. You can use this option only in the global zone. You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5). EXAMPLES
Example 1 Monitoring All Disk Paths in the Cluster Infrastructure The following command forces the daemon to monitor all disk paths in the cluster infrastructure. # scdpm -m all Example 2 Monitoring a New Disk Path The following command monitors a new disk path.All nodes monitor /dev/did/dsk/d3 where this path is valid. # scdpm -m /dev/did/dsk/d3 Example 3 Monitoring New Disk Paths on a Single Node The following command monitors new paths on a single node. The daemon on the schost-2 node monitors paths to the /dev/did/dsk/d4 and /dev/did/dsk/d5 disks. # scdpm -m schost-2:d4 -m schost-2:d5 Example 4 Printing All Disk Paths and Their Status The following command prints all disk paths in the cluster and their status. # scdpm -p schost-1:reboot_on_disk_failure enabled schost-2:reboot_on_disk_failure disabled schost-1:/dev/did/dsk/d4 Ok schost-1:/dev/did/dsk/d3 Ok schost-2:/dev/did/dsk/d4 Fail schost-2:/dev/did/dsk/d3 Ok schost-2:/dev/did/dsk/d5 Unmonitored schost-2:/dev/did/dsk/d6 Ok Example 5 Printing All Failed Disk Paths The following command prints all of the failed disk paths on the schost-2 node. # scdpm -p -F all schost-2:/dev/did/dsk/d4 Fail Example 6 Printing the Status of All Disk Paths From a Single Node The following command prints the disk path and the status of all disks that are monitored on the schost-2 node. # scdpm -p schost-2:all schost-2:reboot_on_disk_failure disabled schost-2:/dev/did/dsk/d4 Fail schost-2:/dev/did/dsk/d3 Ok EXIT STATUS
The following exit values are returned: 0 The command completed successfully. 1 The command failed completely. 2 The command failed partially. Note - The disk path is represented by a node name and a disk name. The node name must be the host name or all. The disk name must be the global disk name, a UNIX path name, or all. The disk name can be either the full global path name or the disk name: /dev/did/dsk/d3 or d3. The disk name can also be the full UNIX path name: /dev/rdsk/c0t0d0s0. Disk path status changes are logged with the syslogd LOG_INFO facility level. All failures are logged with the LOG_ERR facility level. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), cldevice(1CL), clnode(1CL), attributes(5) Sun Cluster System Administration Guide for Solaris OS Sun Cluster 3.2 22 Jun 2006 scdpm(1M)
All times are GMT -4. The time now is 06:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy