Sponsored Content
Operating Systems Solaris dvd/cdrom missing after solaris 10 jumpstart Post 302598445 by stockhes on Tuesday 14th of February 2012 12:52:24 PM
Old 02-14-2012
Quote:
Originally Posted by fpmurphy
Is this a replacement DVD drive or is it the original?
The original dvd drive which was just used to do the install - so HW is ok

I can boot from dvd drive as well

I think that the files in devices directory points to that a cdrom is detected

Code:
 
bash-3.00# ls -la /dev/dsk/c1t4d0p0
lrwxrwxrwx   1 root     root          51 Jan 11 03:07 /dev/dsk/c1t4d0p0 -> ../../devices/pci@0,0/pci108e,4849@1f,2/cdrom@4,0:q
bash-3.00# ls -la /dev/dsk/c1t4d0s0
lrwxrwxrwx   1 root     root          51 Jan 11 03:07 /dev/dsk/c1t4d0s0 -> ../../devices/pci@0,0/pci108e,4849@1f,2/cdrom@4,0:a
bash-3.00#

bios also indicates a sata device in the 4'th port

Last edited by stockhes; 02-14-2012 at 01:55 PM.. Reason: better emphasizing of the 4's
 

9 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. Solaris

jumpstart Solaris 10 on Solaris 9 server

I just built a jumpstart server on a Solaris 9 sun box and have had no problems jumpstarting other sol9 boxes using the custom rules. I've also copied a Solaris 10 image onto that same solaris 9 server and have had problems loading Solaris 10. These boxes will go directly to the manual OS install... (5 Replies)
Discussion started by: salty
5 Replies

3. Solaris

Jumpstart solaris

Hi all , I am trying to jumpstart ( webstart) solaris 9 on E2900 ( client) using the DVD of a V440 server ( jumstart server). I did the setup for the V440 as follows : cleaning up preexisting install client "XXXXXXX" removing XXXXXXXfrom bootparams removing /etc/bootparams, since it is... (14 Replies)
Discussion started by: ppass
14 Replies

4. Solaris

Jumpstart Solaris 10

Hello everyone, I tried to install solaris 10 using the command # boot net - install. I take the image correctly but when you start installing the Operating system installation takes a long (4 hours I have left and not advancing but not send me any errors), it can be seen from the following: ... (7 Replies)
Discussion started by: yflores
7 Replies

5. 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

6. Solaris

Solaris 10 missing /cdrom/cdrom0/

Good day everyone, I am trying to install some new senmail patch on my Solaris 10 system. I know the cdrom for my CP3260 blade servers in my rack worked for the last patches installed. However, when I went to copy from the .tar file from the cdrom to the /tmp. I received an error cannot... (2 Replies)
Discussion started by: cookiecrumbs
2 Replies

7. Solaris

Jumpstart Solaris 10

I have a laptop and need to build an Oracle Linux kickstart server and a Solaris Jumpstart server that can build sparc and x86 systems. Is the best way to create a dual boot from grub for Oracle Linux and Solaris x86? Can the Oracle Kickstart be used as a Jumpstart to build both Solaris 10... (2 Replies)
Discussion started by: Gian
2 Replies

8. HP-UX

Cdrom device possibly missing?

Hello, I am following the HPUX 11.31 install/update guide and I am trying to install "Update-UX" from the installation media. I put the CD into the drive, and I am trying to mount the device. The instructions state:Find the DVD-ROM device file name: ioscan -C disk -f -n -k | more A typical... (5 Replies)
Discussion started by: bstring
5 Replies

9. Solaris

Jumpstart from DVD

I want to have a bootable DVD that will perform a jumpstart install of Solaris 10 x86 I've mainly used JumpStart DVD (with Solaris flash archive) for x86 platform as a reference, and I used the sysidcfg, profile, rules, etc. from a working jumpstart server. For the life of me, though, I cannot... (1 Reply)
Discussion started by: jnojr
1 Replies
vold.conf(4)							   File Formats 						      vold.conf(4)

NAME
vold.conf - volume management configuration file SYNOPSIS
/etc/vold.conf DESCRIPTION
The vold.conf file contains the removable media configuration information used by vold(1M). This information includes the database to use, labels that are supported, devices to use, actions to take when certain media events occur, and the list of file systems that are unsafe to eject without unmounting. Modify vold.conf to specify which program should be called when media events (actions) occur or when you need to add another device to your system. See EXAMPLES for more information on adding devices. If you modify vold.conf, you must tell vold to reread vold.conf by sending a HUP signal. Use the following command: # kill -HUP `pgrep vold` File Format The syntax for the vold.conf file is shown here. # Database to use db database # Labels supported label label_type shared_object device # Devices to use use device type special shared_object symname [ options ] # Actions insert regex [ options ] program program args eject regex [ options ] program program args notify regex [ options ] program program args # List of file system types unsafe to eject unsafe fs_type fs_type Of these syntax fields, you can safely modify Devices to use and Actions. Do not modify the db line. Devices to Use Field All use device statements must be grouped together by device type. (For example, all use cdrom statements must be grouped together and all use floppy statements must be grouped together.) The explanations of the syntax for the Devices to use field are as follows: device The type of removable media device to be used. Legal values are cdrom, floppy, pcmem and rmdisk. type The specific capabilities of the device. Legal value is drive. special This sh(1) expression specifies the device or devices to be used. Path usually begins with /dev. shared_object The name of the program that manages this device. vold(1M) expects to find this program in /usr/lib/vold. symname The symbolic name that refers to this device. The symname is placed in the device directory. options The user, group, and mode permissions for the media inserted (optional). The special and symname parameters are related. If special contains any shell wildcard characters (that is, has one or more asterisks or question marks in it), then the syname must end with"%d". In this case, the devices that are found to match the regular expression are sorted, then numbered. The first device will have a zero filled in for the "%d", the second device found will have a one, and so on. If the special specification does not have any shell wildcard characters then the symname parameter must explicitly specify a number at its end (see EXAMPLES below). Actions Field Here are the explanations of the syntax for the Actions field. insert|eject|notify The media event prompting the event. regex This sh(1) regular expression is matched against each entry in the /vol file system that is being affected by this event. options You can specify what user or group name that this event is to run as (optional). program The full path name of an executable program to be run when regex is matched. program args Arguments to the program. Default Values The default vold.conf file is shown here. # Volume Daemon Configuration file # # Database to use (must be first) db db_mem.so # Labels supported label cdrom label_cdrom.so cdrom label dos label_dos.so floppy rmdisk pcmem label sun label_sun.so floppy rmdisk pcmem # Devices to use use cdrom drive /dev/rdsk/c*s2 dev_cdrom.so cdrom%d use floppy drive /dev/rdiskette[0-9] dev_floppy.so floppy%d use pcmem drive /dev/rdsk/c*s2 dev_pcmem.so pcmem%d forceload=true use rmdisk drive /dev/rdsk/c*s2 dev_rmdisk.so rmdisk%d # Actions eject dev/diskette[0-9]/* user=root /usr/sbin/rmmount eject dev/dsk/* user=root /usr/sbin/rmmount insert dev/diskette[0-9]/* user=root /usr/sbin/rmmount insert dev/dsk/* user=root /usr/sbin/rmmount notify rdsk/* group=tty user=root /usr/lib/vold/volmissing -p remount dev/diskette[0-9]/* user=root /usr/sbin/rmmount remount dev/dsk/* user=root /usr/sbin/rmmount # List of file system types unsafe to eject unsafe ufs hsfs pcfs udfs EXAMPLES
Example 1: A sample vold.conf file. To add a CD-ROM drive to the vold.conf file that does not match the default regular expression (/dev/rdsk/c*s2), you must explicitly list its device path and what symbolic name (with %d) you want the device path to have. For example, to add a CD-ROM drive that has the path /dev/rdsk/my/cdroms? (where s? are the different slices), add the following line to vold.conf (all on one line): use cdrom drive /dev/rdsk/my/cdroms2 dev_cdrom.so cdrom%d Then, when media is inserted in this CD-ROM drive, vold assigns it the next symbolic name. For example, if two CD-ROMs match the default regular expression, they would be named cdrom0 and cdrom1. And, any that match the added regular expression would be named starting with cdrom2. For a diskette that does not match the vold.conf default regular expression (vol/dev/aliases/floppy[0-9]), a similar line would have to be added. For example, to add a diskette whose path was /dev/my/fd0, you would add the following to vold.conf: use floppy drive /dev/my/fd0 dev_floppy.so floppy%d SEE ALSO
sh(1), volcancel(1), volcheck(1), volmissing(1), rmmount(1M), rpc.smserverd(1M), vold(1M), rmmount.conf(4), volfs(7FS) NOTES
vold manages both the block and character device for removable media. However, to make the configuration file easier to set up and scan, only one of these devices needs to be specified. If you follow the conventions specified below, vold figures out both device names if only one of them is specified. For example, if you specify the block device, it figures out the pathname to the character device; if you specify the pathname to the character device, it figures out the block device. CD-ROM Naming Conventions The CD-ROM pathname must have a directory component of rdsk (for the character device) and dsk for the block device. For example, if you specify the character device using the line: use cdrom drive /dev/rdsk/my/cdroms2 dev_cdrom.so cdrom%d then it is assumed that the block device is at /dev/dsk/my/cdroms2 Diskette Naming Conventions For diskettes, vold requires that the device pathnames end in either rfd[0-9] or rdiskette[0-9] for the character device, and fd[0-9] or diskette[0-9] for the block device. As with the CD-ROM, it generates either the block name given the character name, or the character name given the block name. SunOS 5.10 21 Jun 2002 vold.conf(4)
All times are GMT -4. The time now is 09:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy