Sponsored Content
Operating Systems Solaris How to eject boot cdrom after booting from it? Post 302528692 by idlechatter on Tuesday 7th of June 2011 05:36:50 PM
Old 06-07-2011
How to eject boot cdrom after booting from it?

Hey everyone, I currently have a sparcstation 5, and am trying to run some scripts on it without booting off the hard drive.

Currently I am using a Solaris 8 install cd to boot into single user mode. However, the scripts I have are on a different CD.

What I would like to do is to use the Solaris 8 install CD to get to single user mode, eject it, and then mount the script CD and run the scripts off that.

I remember being able to eject the CD about a week ago using some command...but now I cannot for the life of me remember what I did.

I have tried:
Code:
umount /cdrom -> says cdrom is busy (I was in the root dir at the time) 
eject -> no default device 
umount /dev/dsk/c0t6d0s2 -> not in mnttab and no such file or directory 
iostat -En -> Segmentation fault - core dumped 
pressing the button the cdrom drive -> nothing happens 
eject cdrom -> no such file or directory 
mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /mnt -> no such device, cannot mount /dev/dsk/c0td0s2

and a bunch of other commands.

Would anyone happen to know how to eject the disc?

I've spent hours googling how to do this, but none of the sites seemed to help. I'm pretty new at solaris, so I may be missing something obvious.
 

10 More Discussions You Might Find Interesting

1. Solaris

cdrom will not eject

Hi I have placed a CD into the rom and now I can not eject it. when i type in eject cdrom i get the follwing error root@ssdb0009 # eject cdrom /vol/dev/rdsk/c0t6d0/dp_a0500_solaris_7_and_8_cd: Device busy Therefore i try and eject it with the -f option (eject -f cdrom) I still get the... (4 Replies)
Discussion started by: dennisca
4 Replies

2. Solaris

cannot find boot device and won't boot off cdrom

I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies

3. Solaris

Disksuite Raid 0 Concatenated Volume - booting from cdrom

Hello, If I boot up from install media in single user mode (Solaris 9 - if it matters), will I be able to mount a concatenated volume? I have combined several disks into one non-os filesystem and I want to be able to mount it while booted in single user mode from cdrom. i.e., mount... (0 Replies)
Discussion started by: calmgreen
0 Replies

4. AIX

Eject CDROM?

Now i have a prolem! I double click on my zip file from cdrom. System can not read my zip file and i can not eject my cdrom. How can i manage process and can i end a process or how can i eject my cdrom? please have me! thanks (4 Replies)
Discussion started by: leenguyen0101
4 Replies

5. Solaris

SF V210 CDROM drive auto eject!

Hi, When I insert a cd to CDROM drive in SF V210 Solaris 10 it took seconds then eject it auto! How can I solve this issue? Thanks Regards :) (8 Replies)
Discussion started by: HishamN
8 Replies

6. Solaris

not able to boot from cdrom

Hi all am trying to boot the system from cdrom in single user mode , however when i am giving command boot cdrom -s i am getting below error Boot Device: /pci@1f,0/pci@1,1/ide@3/cdrom@2,0: f file and args: Can't read disk label Can't open disk label package can,t open boot device ... (17 Replies)
Discussion started by: kumarmani
17 Replies

7. Solaris

can't boot cdrom

iam traying to install o/s in spark machine it showing error ok >boot cdrom is showing error short disk read failed to read superblock the file just loaded does not appear to excutable how to solve this can u help me (6 Replies)
Discussion started by: tirupathi
6 Replies

8. Solaris

CDROM will not eject - says device busy

Hi, I've seen similar posts on this board about ejecting CDROMs but I've tried the solutions people suggested but still cannot eject the CD. It's stuck in a production box so I can't reboot it... bash-3.00# eject -f cdrom /vol/dev/dsk/c0t0d0/sol_10_106_sparc/s0: Device busy bash-3.00#... (14 Replies)
Discussion started by: jimmy54321
14 Replies

9. Solaris

Trying to eject cdrom

The green cdrom light is blinking on our Sun Solaris server. I tried the eject command to eject cdrom: eject cdrom cdrom: No such file or directory bash-2.05# eject No default media available bash-2.05# eject cdrom0 cdrom0: No such file or directory The message log file shows: Oct 19... (6 Replies)
Discussion started by: agarcia19
6 Replies

10. UNIX for Beginners Questions & Answers

Cannot boot cdrom -s

Good Afternoon, I'm trying to boot from cdrom so I: bash-2.05# init 0 {1} ok boot cdrom -s and I get: Rebooting with command: boot cdrom -s Boot Device: /pci@1e,600000/ide@d/cdrom@2,0:f File and args: -s Can't read disk label. Can't open disk label package Evaluating: Can't open boot... (13 Replies)
Discussion started by: Stellaman1977
13 Replies
BOOT0CFG(8)						    BSD System Manager's Manual 					       BOOT0CFG(8)

NAME
boot0cfg -- boot manager installation/configuration utility SYNOPSIS
boot0cfg [-Bv] [-b boot0] [-d drive] [-e bell character] [-f file] [-i volume-id] [-m mask] [-o options] [-s slice] [-t ticks] disk DESCRIPTION
The FreeBSD 'boot0' boot manager permits the operator to select from which disk and slice an i386 machine (PC) is booted. Note that what are referred to here as ``slices'' are typically called ``partitions'' in non-BSD documentation relating to the PC. Typi- cally, only non-removable disks are sliced. The boot0cfg utility optionally installs the 'boot0' boot manager on the specified disk; and allows various operational parameters to be con- figured. On PCs, a boot manager typically occupies sector 0 of a disk, which is known as the Master Boot Record (MBR). The MBR contains both code (to which control is passed by the PC BIOS) and data (an embedded table of defined slices). The options are: -B Install the 'boot0' boot manager. This option causes MBR code to be replaced, without affecting the embedded slice table. -b boot0 Specify which 'boot0' image to use. The default is /boot/boot0 which will use the video card as output, alternatively /boot/boot0sio can be used for output to the COM1 port. (Be aware that nothing will be output to the COM1 port unless the modem signals DSR and CTS are active.) -d drive Specify the drive number used by the PC BIOS in referencing the drive which contains the specified disk. Typically this will be 0x80 for the first hard drive, 0x81 for the second hard drive, and so on; however any integer between 0 and 0xff is acceptable here. -e bell character Set the character to be printed in case of input error. -f file Specify that a backup copy of the preexisting MBR should be written to file. This file is created if it does not exist, and replaced if it does. -i volume-id Specifies a volume-id (in the form XXXX-XXXX) to be saved at location 0x1b8 in the MBR. This information is sometimes used by NT, XP and Vista to identify the disk drive. The option is only compatible with version 2.00 of the 512-byte boot block. -m mask Specify slices to be enabled/disabled, where mask is an integer between 0 (no slices enabled) and 0xf (all four slices enabled). Each mask bit enables corresponding slice if set to 1. The least significant bit of the mask corresponds to slice 1, the most sig- nificant bit of the mask corresponds to slice 4. -o options A comma-separated string of any of the following options may be specified (with ``no'' prepended as necessary): packet Use the disk packet (BIOS INT 0x13 extensions) interface, as opposed to the legacy (CHS) interface, when doing disk I/O. This allows booting above cylinder 1023, but requires specific BIOS support. The default is 'packet'. setdrv Forces the drive containing the disk to be referenced using drive number definable by means of the -d option. The default is 'nosetdrv'. update Allow the MBR to be updated by the boot manager. (The MBR may be updated to flag slices as 'active', and to save slice selection information.) This is the default; a 'noupdate' option causes the MBR to be treated as read-only. -s slice Set the default boot selection to slice. Values between 1 and 4 refer to slices; a value of 5 refers to the option of booting from a second disk. The special string ``PXE'' or a value of 6 can be used to boot via PXE. -t ticks Set the timeout value to ticks. (There are approximately 18.2 ticks per second.) -v Verbose: display information about the slices defined, etc. FILES
/boot/boot0 The default 'boot0' image /boot/boot0sio Image for serial consoles (COM1,9600,8,N,1,MODEM) EXIT STATUS
The boot0cfg utility exits 0 on success, and >0 if an error occurs. EXAMPLES
To boot slice 2 on the next boot: boot0cfg -s 2 ada0 To enable just slices 1 and 3 in the menu: boot0cfg -m 0x5 ada0 To go back to non-interactive booting, use fdisk(8) to install the default MBR: fdisk -B ada0 SEE ALSO
geom(4), boot(8), fdisk(8), gpart(8) AUTHORS
Robert Nordier <rnordier@FreeBSD.org> BUGS
Use of the 'packet' option may cause 'boot0' to fail, depending on the nature of BIOS support. Use of the 'setdrv' option with an incorrect -d operand may cause the boot0 code to write the MBR to the wrong disk, thus trashing its previ- ous content. Be careful. BSD
October 1, 2013 BSD
All times are GMT -4. The time now is 03:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy