Disk or CDROM problem? Post: 302399883

Sponsored Content

Operating Systems Solaris Disk or CDROM problem? Post 302399883 by incredible on Monday 1st of March 2010 11:26:39 PM

03-02-2010

Registered User

Hi
1) yes, you can see the errors even if the cdrom drive is not used at all
2) this is how the OS sees the devices, via controller numbers and target id etc.
you can check the device path from ok> prompt too , using devalias

3) yes, you may not wish to replace the drive and continue using the system
BUT, a caution!! if your system corrupts for any reason and if there's a need rise to use the drive to boot from cdrom, THEN YOU WILL have a problem..
SO suggest to just replace it.

incredible

View Public Profile for incredible

Find all posts by incredible

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Cdrom Problem!!!

Hi everybody: I have Solaris 8 installed on my little Enterprise 3500 and, for a cruel fate of the destiny, Im the admin.... Here is the problem: a week ago I took out a CD from the CDROM drive in an abnormal way. I inserted a clip in the little hole in the front of the drive because the button...

2. Solaris

Ultra 2 CDROM Problem

I have a Ultra 2 running solaris9, I'm trying to do a boot cdrom to install Solaris 10. During the boot, the system can't find the CDROM drive. It shows up during a probe-scsi-all. Also, when booted to Solaris 9 I place a CD in the drive it takes almost 10 minutes before the CD is readable on the...

3. AIX

problem on sharing cdrom drive in AIX with linux

HI i have setuped a nfs between a AIX system and a linux os ,keeping AIX as sever i need to share the CDrom in AIX server with the linux operating system. ie. linux os machine does't have a cdrom . will i be able be share ..i tried a lot but it gives a message which resembles NFS access...

LEARN ABOUT NETBSD

eject

EJECT(1)						    BSD General Commands Manual 						  EJECT(1)

NAME

     eject -- eject a floppy disk, cdrom or tape

SYNOPSIS

     eject [-fv] [-l | -L | -U] [-t device-type] [-d] device

     eject -n

DESCRIPTION

     The eject program ejects a medium from the specified device.  It can also load a cdrom in the drive if this operation is supported by the
     hardware.	The device argument specifies a device either by its full path name (identified by a /dev/ prefix), or by one of the built-in
     nicknames.  If the medium contains a file system that is currently mounted, eject will attempt to unmount the file system before ejecting.

     The following options are available:

     -d   Deprecated.

     -f   Force the eject operation without attempting to unmount any file systems first.

     -l   Load media in the drive (only supported for the cdrom device type).

     -L   Lock the media into the drive (but see BUGS below).

     -n   List the built-in nicknames on standard output.

     -t device-type
	  Specify the device type.  The argument must be one of diskette, floppy, cdrom, disk, or tape.  This option is necessary when ejecting a
	  device for which no built-in knowledge is available.

     -U   Unlock the media from the drive.

     -v   Display some of the actions taken on standard output.

BUGS

     Most disk drivers automatically lock the media on the first open and unlock it on the last close, making 'eject -L' almost useless, since
     when it closes the device, it gets unlocked again.

BSD
								  October 6, 2001							       BSD