Sponsored Content
Operating Systems Solaris How to eject boot cdrom after booting from it? Post 302528706 by achenle on Tuesday 7th of June 2011 07:01:20 PM
Old 06-07-2011
After you boot off the CD to single-user mode, what does the "mount" command show?
 

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
SYSTEMD-FSTAB-GENERATOR(8)                                    systemd-fstab-generator                                   SYSTEMD-FSTAB-GENERATOR(8)

NAME
systemd-fstab-generator - Unit generator for /etc/fstab SYNOPSIS
/lib/systemd/system-generators/systemd-fstab-generator DESCRIPTION
systemd-fstab-generator is a generator that translates /etc/fstab (see fstab(5) for details) into native systemd units early at boot and when configuration of the system manager is reloaded. This will instantiate mount and swap units as necessary. The passno field is treated like a simple boolean, and the ordering information is discarded. However, if the root file system is checked, it is checked before all the other file systems. See systemd.mount(5) and systemd.swap(5) for more information about special /etc/fstab mount options this generator understands. One special topic is handling of symbolic links. Historical init implementations supported symlinks in /etc/fstab. Because mount units will refuse mounts where the target is a symbolic link, this generator will resolve any symlinks as far as possible when processing /etc/fstab in order to enhance backwards compatibility. If a symlink target does not exist at the time that this generator runs, it is assumed that the symlink target is the final target of the mount. systemd-fstab-generator implements systemd.generator(7). KERNEL COMMAND LINE
systemd-fstab-generator understands the following kernel command line parameters: fstab=, rd.fstab= Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any mounts or swap devices configured in /etc/fstab. rd.fstab= is honored only by the initial RAM disk (initrd) while fstab= is honored by both the main system and the initrd. root= Takes the root filesystem to mount in the initrd. root= is honored by the initrd. rootfstype= Takes the root filesystem type that will be passed to the mount command. rootfstype= is honored by the initrd. rootflags= Takes the root filesystem mount options to use. rootflags= is honored by the initrd. mount.usr= Takes the /usr filesystem to be mounted by the initrd. If mount.usrfstype= or mount.usrflags= is set, then mount.usr= will default to the value set in root=. Otherwise, this parameter defaults to the /usr entry found in /etc/fstab on the root filesystem. mount.usr= is honored by the initrd. mount.usrfstype= Takes the /usr filesystem type that will be passed to the mount command. If mount.usr= or mount.usrflags= is set, then mount.usrfstype= will default to the value set in rootfstype=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrfstype= is honored by the initrd. mount.usrflags= Takes the /usr filesystem mount options to use. If mount.usr= or mount.usrfstype= is set, then mount.usrflags= will default to the value set in rootflags=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrflags= is honored by the initrd. systemd.volatile= Controls whether the system shall boot up in volatile mode. Takes a boolean argument or the special value state. If false (the default), this generator makes no changes to the mount tree and the system is booted up in normal mode. If true the generator ensures systemd-volatile-root.service(8) is run as part of the initial RAM disk ("initrd"). This service changes the mount table before transitioning to the host system, so that a volatile memory file system ("tmpfs") is used as root directory, with only /usr mounted into it from the configured root file system, in read-only mode. This way the system operates in fully stateless mode, with all configuration and state reset at boot and lost at shutdown, as /etc and /var will be served from the (initially unpopulated) volatile memory file system. If set to state the generator will leave the root directory mount point unaltered, however will mount a "tmpfs" file system to /var. In this mode the normal system configuration (i.e. the contents of "/etc") is in effect (and may be modified during system runtime), however the system state (i.e. the contents of "/var") is reset at boot and lost at shutdown. Note that in none of these modes the root directory, /etc, /var or any other resources stored in the root file system are physically removed. It's thus safe to boot a system that is normally operated in non-volatile mode temporarily into volatile mode, without losing data. Note that enabling this setting will only work correctly on operating systems that can boot up with only /usr mounted, and are able to automatically populate /etc, and also /var in case of "systemd.volatile=yes". SEE ALSO
systemd(1), fstab(5), systemd.mount(5), systemd.swap(5), systemd-cryptsetup-generator(8), kernel-command-line(7) systemd 237 SYSTEMD-FSTAB-GENERATOR(8)
All times are GMT -4. The time now is 02:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy