Sponsored Content
Full Discussion: T5220
Operating Systems Solaris T5220 Post 302526344 by tonijel on Tuesday 31st of May 2011 09:11:46 AM
Old 05-31-2011
Thanks DukeNuke, i think i tryied already with the eject button , but drive
didn't eject, i'll try again, but just for the info, is there some command in the ok
promt for ejecting the drive ?
 

10 More Discussions You Might Find Interesting

1. Solaris

kstat on T5220

We used kstat on netra240/440 to check if the link is full duplex. So we do something like: bash-3.00# kstat -pc net bge:1::/'link_duplex'/ | cut -f2 2 The output 2 indicates the link is full duplex. This kind of check worked all right for Netra 240/440 systems. However, the nxge... (2 Replies)
Discussion started by: illcar
2 Replies

2. Solaris

ILOM and sc on T5220

I 've 2 different T5220 and both are showing different prompts when i ssh to the console. 1. Shows sc> ALOM 2. Shows -> ILOM as far as i know the T5220 comes with ILOM , so why i 'm seeing 2 different type of console for same tyep of hardware ? and i found that we... (6 Replies)
Discussion started by: fugitive
6 Replies

3. Solaris

SC on T5220 not responding

Hi, SC on one of my T5220 is not responding .. it does not show not let me type anything .. what could be the reason for it ? though when i powercycle the box from sc it shows me the system coming up but after that does not let me login thru sc sc> console -f Enter #. to return to ALOM. (2 Replies)
Discussion started by: fugitive
2 Replies

4. Solaris

LDOMs on T5220

We're just about to migrate a large application from an Enterprise 6900 to a pair of T5220s utilising LDOMs. Does anyone have any experience of LDOMs on this kit and can provide any recommendations or pitfalls to avoid? I've heard that use of LDOMs can have an impact on I/O speeds as it's all... (9 Replies)
Discussion started by: JerryHone
9 Replies

5. Solaris

T5220 server

Hi, We have two T5220 servers in our datacentre one server is showing 64 processors online and another showing 32 processors online two are newly purchased, there is no hardware faults in this server one server has 64gb memory and it shows 64 processors, and other having 32gb memory and it... (5 Replies)
Discussion started by: rajasekg
5 Replies

6. Solaris

Set up new T5220 remotely

I have a new T5220 racked at our remote office and the guys who racked it does not know how to configure the SP on the system .. is there any way i can do it remotely ? (1 Reply)
Discussion started by: fugitive
1 Replies

7. Solaris

ILOM problem on T5220

I have setup my T5220 ILOM .. and its working fine. But if my network connection is broken to the ILOM i 'm unable to login to the ILOM for few hrs .. it gives me either wrong user/passwd error and after few hrs the same user/passwd works .. what could be the reason for this and how can i resove... (3 Replies)
Discussion started by: fugitive
3 Replies

8. Solaris

Jumpstart Issues With T5220

I'm trying to use a V210 (sun4u) configured as a jumpstart server to flash install a number of T5220's (sunv4). The Facts: V210 - Solaris 10 (September 2010 Release / not patched) T5220's - Archive's created using prior (unknown) version of solaris 10. Flar -i <archive name> shows the... (6 Replies)
Discussion started by: Celtic_Monkey
6 Replies

9. Solaris

T5220

Hi Guys and Gals, Wondering if anyone could help me, tricky one this. Got a T5220 with a graphics card. When you power it on, it outputs its output to the screen and you can type commands with the keyboard etc. But no matter what version of Solaris 10 you use, when you do a boot cdrom... (1 Reply)
Discussion started by: callmebob
1 Replies

10. Solaris

Where are my other disks on T5220 ?

Hi, I got a (used) server to install Solaris 11 and wipe out every information on existing disks. There are 6 disks of 300GB and two disks of 146GB. I am not able to figure out, how to find out RAID (if there is any) and break it. Can anybody help me with that ? Below is configuration. I have... (18 Replies)
Discussion started by: solaris_1977
18 Replies
eject(1)							   User Commands							  eject(1)

NAME
eject - eject media such as CD-ROM and floppy from drive SYNOPSIS
eject [-dfnpq] [device | nickname] DESCRIPTION
The eject utility is used for those removable media devices that do not have a manual eject button, or for those that do, but are managed by Volume Management (see vold(1M)). The device may be specified by its name or by a nickname; if Volume Management is running and no device is specified, the default device is used. Only devices that support eject under program control respond to this command. eject responds differently, depending on whether or not Vol- ume Management is running. With Volume Management When eject is used on media that can only be ejected manually, it will do everything except remove the media, including unmounting the file system if it is mounted. In this case, eject displays a message that the media can now be manually ejected. If a window system is running, the message is displayed as a pop-up window, unless the -p option is supplied. If no window system is running or the -p option is supplied, a message is displayed both to stderr and to the system console that the media can now be physically removed. Volume Management has the concept of a default device, which eject uses if no pathname or nickname is specified. Use the -d option to check what default device will be used. Without Volume Management When Volume Management is not running and a pathname is specified, eject sends the eject command to that pathname. If a nickname is sup- plied instead of a pathname, eject will recognize the following list: +-----------------------------+-----------------------------+ | Nickname | Path | |fd |/dev/rdiskette | |fd0 |/dev/rdiskette | |fd1 |/dev/rdiskette1 | |diskette |/dev/rdiskette | |diskette0 |/dev/rdiskette0 | |diskette1 |/dev/rdiskette1 | |rdiskette |/dev/rdiskette | |rdiskette0 |/dev/rdiskette0 | |rdiskette1 |/dev/rdiskette1 | |floppy |/dev/rdiskette | |floppy0 |/dev/rdiskette0 | |floppy1 |/dev/rdiskette1 | +-----------------------------+-----------------------------+ The list above can be reproduced with the -n option. Do not physically eject media from a device which contains mounted file systems. eject automatically searches for any mounted file systems which reside on the device and attempts to umount them prior to ejecting the media (see mount(1M)). If the unmount operation fails, eject prints a warning message and exits. The -f option may be used to specify an eject even if the device contains mounted partitions; this option works only if Volume Management is not running. eject can also display its default device and a list of nicknames. If you have inserted a floppy diskette, you must use volcheck(1) before ejecting the media to inform Volume Management of the floppy's presence. OPTIONS
The following options are supported: -d Displays the name of the default device to be ejected. -f Forces the device to eject even if it is busy, if Volume Management is not running. -n Displays the nickname to device name translation table. -p Does not try to call the eject_popup program. -q Queries to see if the media is present. OPERANDS
The following operands are supported: device Specifies which device to eject, by the name it appears in the directory /dev. nickname Specifies which device to eject, by its nickname as known to this command. EXAMPLES
Example 1: Ejecting a CD while Volume Management is running To eject a CD from its drive, while Volume Management is running (assuming only one CD-ROM drive): example> eject cdrom0 Example 2: Ejecting a CD-ROM without running Volume Management To eject a CD-ROM drive with pathname /dev/dsk/c0t3d0s2, without Volume Management running: example> eject /dev/dsk/c0t3d0s2 Example 3: Ejecting a floppy disk To eject a floppy disk (whether or not Volume Management is running): example> eject floppy0 EXIT STATUS
The following exit codes are returned: 0 The operation was successful or, with the -q option, the media is in the drive. 1 The operation was unsuccessful or, with the -q option, the media is not in the drive. 2 Invalid options were specified. 3 An ioctl() request failed. 4 Manually ejectable media is now okay to remove. FILES
/dev/diskette0 default diskette file /dev/sr0 default CD-ROM file (deprecated) /dev/dsk/c0t6d0s2 default CD-ROM file /usr/lib/vold/eject_popup popup used for manually ejected media ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
volcancel(1), volcheck(1), volmissing(1), mount(1M), rmmount(1M), vold(1M), ioctl(2), rmmount.conf(4), vold.conf(4), attributes(5), volfs(7FS) DIAGNOSTICS
A short help message is printed if an unknown option is specified. A diagnostic is printed if the device name cannot be opened or does not support eject. Device Busy An attempt was made to eject a device that has a mounted file system. A warning message is printed when doing a forced eject of a mounted device. BUGS
There should be a way to change the default on a per-user basis. If Volume Management is not running, it is possible to eject a volume that is currently mounted (see mount(1M)). For example, if you have a CD-ROM drive at /dev/dsk/c0t3d0s2 mounted on /mnt, the following command (without Volume Management running) will work: example> eject /dev/dsk/c0t3d0s0 since both slices s0 and s2 reference the whole CD-ROM drive. SunOS 5.10 20 Sep 1996 eject(1)
All times are GMT -4. The time now is 07:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy