10 More Discussions You Might Find Interesting
1. Ubuntu
I cannot access or boot from my C drive. I'm running Zorin 9 and the drive is a Samsung SSD. The disk was encrypted on install, and that has not given me any problems before.
When I start the system it gets to the memory test page, and does not then load the password prompt, which it used to.... (1 Reply)
Discussion started by: David4321
1 Replies
2. Solaris
Hello Forum,
I'm really in a fix now,
I'm getting this error message now, seems like the boot block is damaged?
When I do probe-all the system freezes...
Can any one guide me as what to do next?
System is Solaris 8 running Open Boot PROM 4
System also does not have a cd/dvd rom drive...
... (17 Replies)
Discussion started by: br1an
17 Replies
3. Solaris
I installed a new hard drive completely blank.
sun blade 150
openboot 4.10.6
message:
Boot device: disk:a File and args:
Bad magic number in disk label
Can't open label package
Evaluating:
Can't open boot device (15 Replies)
Discussion started by: janiper
15 Replies
4. Solaris
Hello,
I am wondering which commend /file to check to find out what is the boot device?
regards
Ahmed
Egypt (1 Reply)
Discussion started by: ahmedamer12
1 Replies
5. Solaris
hi all:
I have a sun blade-1000 for labs only, with 73G hd loaded, which boot block installed on slice 0. I'm confused by setting "boot-device" value in obp, which my question as follow:
in ok mode, I got device alias like this:
disk0: /pci@8,600000/SUNW,qlc@4/fp@0,0/disk@2,0
as I know the... (4 Replies)
Discussion started by: netshu
4 Replies
6. Solaris
I have a real emergency. I have a Sun Fire V240 UltraSparc server and am connected via the Serial Mgmnt Port with a Laptop. I have been building an Oracle database on it for the past couple months, not getting very far along with it , when suddenly, the system had a fatal crash. I've lost the... (2 Replies)
Discussion started by: mayewil
2 Replies
7. Solaris
Hi i need help pls ...
Server type sun fire 3800 I need to install solaris 9 .
When i boot the system i recieve the following :
System Controller 'sunfire3800':
Type 0 for Platform Shell
Type 1 for domain A console
Type 2 for domain B console
Type 3 for... (5 Replies)
Discussion started by: tt155
5 Replies
8. 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
9. UNIX for Dummies Questions & Answers
I watched this done a long time ago, but cannot find it anywhere. I need to alias the boot device "disk" to /sbus@7,0/QLGC,isp@0,10000/sd@c,0
I think I need to set "use-nvramrc?" to true, and then create an alias within the nvramrc to point disk to the boot disk, but this is the step I cannot... (3 Replies)
Discussion started by: 98_1LE
3 Replies
10. UNIX for Dummies Questions & Answers
I need to change the boot slice on a Sun box, more specifically the alias of "disk". When I do a printenv from the ok prompt, it lists "boot-device disk net", but when it boots, it is looking at the wrong slice on "disk" (3 Replies)
Discussion started by: 98_1LE
3 Replies
BOOTHOWTO(9) BSD Kernel Developer's Manual BOOTHOWTO(9)
NAME
boothowto, BOOT_FLAG -- flags passed to kernel during boot or shutdown
SYNOPSIS
#include <sys/reboot.h>
#include <sys/systm.h>
extern int boothowto;
#include <sys/boot_flag.h>
#define BOOT_FLAG(arg, retval) ...
DESCRIPTION
The boothowto variable contains flags passed to the kernel by the boot loader (see boot(8)), or the reboot(2) system call. The value is
interpreted as a bit mask, with bits defined by the ``RB_*'' and ``AB_*'' symbols in <sys/reboot.h>. The value is made available via the
sysctl(7) variable kern.boothowto.
The BOOT_FLAG macro defined in <sys/boot_flag.h> is used by many boot loaders to convert command line options into boothowto flags. Note
that not all boot loaders use this macro, and some boot loaders may have incompatible options.
Where possible, flags set by the reboot(2) system call will be passed to the new kernel after a reboot; the extent to which this is possible
is machine dependent.
In the following tables, each flag is listed with its symbolic name, the corresponding numeric value defined in <sys/reboot.h>, and the
option letter (if any) understood by the BOOT_FLAG macro.
Flags that affect booting or shutting down
The following flags affect actions taken during system boot or shutdown.
RB_AUTOBOOT 0 The default if no other flags are set. Causes the system to boot in the normal way.
RB_ASKNAME 0x00000001 -a This flag causes various parts of the system to prompt:
o The boot loader may prompt for the name or location of the kernel to be booted.
o The kernel will prompt for the root file system device.
o The kernel will prompt for the root file system type.
o The kernel will prompt for the location of the dump device.
o The kernel will prompt for the path to the init(8) program.
Some subsystems set this flag when they are unable to automatically make a decision.
RB_SINGLE 0x00000002 -s Boot in single-user mode. If this flag is set, the kernel passes the -s option to init(8).
RB_NOSYNC 0x00000004 If this flag is set, then some parts of the shutdown process will be less graceful than usual:
o Disks will not be synced (see sync(2) and cpu_reboot(9)).
o Devices will not be detached (see autoconf(9)).
o File systems will not be unmounted (see cpu_reboot(9), and vfs_shutdown(9)).
o The time of day clock will not be set (see resettodr(9)).
RB_HALT 0x00000008 -b If this flag is set, then reboot(2) will cause the system to halt instead of rebooting. This flag may be
set at boot time, and cannot be cleared by reboot(2).
RB_INITNAME 0x00000010 This flag is obsolete. It was previously used to cause the kernel to prompt for the name of the init(8)
program, but that function is now controlled by the RB_ASKNAME flag.
RB_KDB 0x00000040 -d Gives control to a kernel debugger early in the boot sequence. See ddb(4), ``options KGDB'' in
options(4), and ipkdb(9).
RB_RDONLY 0x00000080 This flag is deprecated. It previously caused the kernel to mount the root file system in read-only
mode, but now that is the default, and this flag has no effect.
RB_DUMP 0x00000100 Causes the kernel to dump memory to the dump device during shutdown. See savecore(8), cpu_reboot(9), and
dumpsys(9).
RB_MINIROOT 0x00000200 -m This flag informs the kernel that a mini-root file system is present in memory. See md(4), and
mdsetimage(8).
RB_STRING 0x00000400 This flag indicates that a boot string is present. The string may be provided by reboot(2) and will be
passed to the boot loader if possible.
RB_POWERDOWN (RB_HALT|0x800) This flag is used in conjunction with RB_HALT. If this flag is set, then then system will be powered
down if possible. If powerdown is not supported, then the system will halt.
RB_USERCONF 0x00001000 -c This flag causes the kernel to invoke the userconf(4) device configuration manager early in the boot
sequence.
Flags that affect verbosity
The following flags affect the verbosity of messages printed by the kernel. These flags are used by several functions described in
kprintf(9) to control whether output is sent to the console, the system log, both, or neither. The use of flags that increase verbosity
simultaneously with the use of flags that decrease verbosity, is not well defined.
AB_NORMAL 0 The default, if none of the other AB_* flags is set, is that ordinary kernel messages are sent both to
the console and to the system log.
AB_QUIET 0x00010000 -q Boot quietly. Ordinary kernel messages are sent to the system log, but not to the console. Messages
printed with aprint_naive(9) are sent to the console, but not to the system log.
AB_VERBOSE 0x00020000 -v Boot verbosely. Some messages will be printed that would otherwise not be printed. Both ordinary kernel
messages, and messages printed with aprint_verbose(9), will be sent both to the console and to the system
log. If this flag is not set, then messages printed with aprint_verbose(9) will be sent only to the sys-
tem log.
AB_SILENT 0x00040000 -z Boot silently. Most kernel messages will be sent only to the system log, not to the console. The
aprint_*() functions display a spinning symbol on the console.
AB_DEBUG 0x00080000 -x Boot with debug messages.
Machine-dependent flags
The following flags have machine-dependent meanings.
RB_MD1 0x10000000 -1 Some ports use this flag to disable multiprocessor mode, making them use only a single CPU. The zaurus
port uses this flag to enable the serial console.
RB_MD2 0x20000000 -2 The i386 and amd64 ports use this flag to disable acpi(4).
RB_MD3 0x40000000 -3 This flag is currently not used by any ports.
RB_MD4 0x80000000 -4 This flag is currently not used by any ports.
SEE ALSO
reboot(2), ddb(4), userconf(4), sysctl(7), boot(8), crash(8), init(8), reboot(8), savecore(8), sync(8), cpu_reboot(9), kprintf(9)
HISTORY
The boothowto variable appeared in 4.0BSD. The BOOT_FLAG macro appeared in NetBSD 1.6.
The RB_DFLTROOT option is now obsolete.
BSD
September 11, 2009 BSD
