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
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
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
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
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
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
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
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
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
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
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
LEARN ABOUT NETBSD
kloader
KLOADER(4) BSD Kernel Interfaces Manual KLOADER(4)
NAME
kloader -- in-kernel bootloader
SYNOPSIS
options KLOADER
options KLOADER_KERNEL_PATH=""/netbsd""
DESCRIPTION
The kloader is the in-kernel bootloader for platforms that do not have a proper firmware.
Some platforms supported by NetBSD do not have a firmware that can boot the NetBSD kernel. Examples are game consoles (dreamcast port), and
handhelds (hpcarm, hpcmips, and hpcsh ports). On such platforms the bootloader is usually a host program that runs under the native OS.
This means that rebooting NetBSD is a lengthy process of booting into the native OS first, launching the bootloader program, and finally
booting NetBSD again. This problem is addressed by kloader, which allows the currently running kernel to serve as a bootloader for the ker-
nel being booted, thus avoiding the burden of booting into the native OS first.
When kloader is configured into the kernel, a call to reboot(2) causes the kloader to load the new kernel into memory, and arrange for con-
trol to be passed to the new kernel -- just like a standalone bootloader does. The new kernel then boots in the ordinary manner.
SEE ALSO
reboot(2), boot(8), reboot(8)
HISTORY
kloader first appeared in NetBSD 1.6.
BUGS
kloader ignores howto and bootstr arguments passed to the reboot(2) system call, and reboots the system with the previous boot settings.
kloader doesn't support booting compressed kernels.
The hpcarm port doesn't support kloader yet.
BSD
April 3, 2004 BSD