03-01-2010
system went down due to possible cpu/memory error (AFAR/AFSR). As autoboot had been set to true, we found it contsnantly trying to boot from rootdisk (and failing).
i'm 100% positive that boot into single user didnt succeed. I do know that I accepted all defaults when doing the 'boot -a' so maybe it wa something there that allowed me to boot without VX control.
We have a number of machines that are mirrored using vxvm (inherited systems - not my choice!) so it would be good to get to the bottom of this if anyone can shed some light.
we're running solaris 9 & vxvm version 3.5
10 More Discussions You Might Find Interesting
1. SCO
Hi,
I have an openserver 5.0.0 machine in the office. The sysad of that machine left years ago without leaving the password to anyone.
I was wondering if someone has a copy of the boot / root diskettes (rescue) for this version? Or perhaps if anyone knows a download link / location in the... (0 Replies)
Discussion started by: marcpascual
0 Replies
2. Solaris
Hi, Im getting a downtime of 4 hrs to do porting of bootdisks.
Currently, the system is running on Sf4800. 2 internal disk 36G connected to a SE3510 storage.
We're getting 72G disks and we want to restore the OS from the current 36G to the 72G disk. System is under veritas volume manager ctrl.... (4 Replies)
Discussion started by: incredible
4 Replies
3. Solaris
Previously , i remove the disk by
#vxdg -g testdg -k rmdisk testdg02
But i got error when i -k adddisk
bash-2.03# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none - - online invalid
c0t1d0s2 auto:none ... (1 Reply)
Discussion started by: waibabe
1 Replies
4. Solaris
Hello guys!
I use the Solaris 10 x86 machine.
I need to clone the boot disk.
Why, when I copy slice 1 - there is a following:
# ufsdump 0f - /dev/rdsk/c0d0s1 | (cd /mnt && ufsrestore rf - )
DUMP: Warning - super-block on device `/dev/rdsk/c0d01` is corrupt - run fsck
Dump: The Entire... (6 Replies)
Discussion started by: wolfgang
6 Replies
5. Solaris
Hi All
Hope it's okay to post on this sub-forum, couldn't find a better place
I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies
6. Solaris
Hi,
Can you help me on booting x86 server configured under VxVM. Server boots fine normally from both the disks but if I try to boot server from mirror disk without starting veritas, then it does not boot.
vxplex -g rootdg dis var-02
vxplex -g rootdg dis swapvol-02
vxplex -g rootdg dis... (2 Replies)
Discussion started by: milindphanse604
2 Replies
7. Solaris
Update:
The / file system (/dev/rdsk/c1t0d0s0) is being checked
fsck unable to stat
WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0).
Root password for system maintenance (control-d to bypass):
I am unable to hit control-d to by pass.
I... (50 Replies)
Discussion started by: br1an
50 Replies
8. Red Hat
Hi guys,
thanks for helping out.
If you have two boot disk mirrored and your primary boot disk fails, how will you boot the system from the second disk?
Thank you very much for your assistance on this matter.
Arrey (5 Replies)
Discussion started by: cjashu
5 Replies
9. UNIX for Dummies Questions & Answers
Came home the other day to a Napp-it Gui that would not load.
Login would appear but when i attempted I would get the following
Set default permissions and reading disk and pool parameter, please wait..
in case of problems, try a reboot after Power-Off or check disk and pool status at CLI.... (1 Reply)
Discussion started by: fastedd27
1 Replies
10. HP-UX
Hello all,
So I made a rookie mistake today. I forgot to remove my disk from my disk group, before running the following command:for i in `ioscan -fnN | awk /NO/'{print $3}'`
do
rmsf -H $i
done
I am trying to run the following command, but not having any luck obviously:vxdg -g dgvol1 rmdisk... (0 Replies)
Discussion started by: mrkejames2
0 Replies
LEARN ABOUT FREEBSD
loader.4th
LOADER.4TH(8) BSD System Manager's Manual LOADER.4TH(8)
NAME
loader.4th -- loader.conf processing tools
DESCRIPTION
The file that goes by the name of loader.4th is a set of commands designed to manipulate loader.conf(5) files. The default /boot/loader.rc
includes loader.4th and uses one of its commands to automatically read and process the standard loader.conf(5) files. Other commands exists
to help the user specify alternate configurations.
The commands of loader.4th by themselves are not enough for most uses. Please refer to the examples below for the most common situations,
and to loader(8) for additional commands.
Before using any of the commands provided in loader.4th, it must be included through the command:
include loader.4th
This line is present in the default /boot/loader.rc file, so it is not needed (and should not be re-issued) in a normal setup.
The commands provided by it are:
boot
boot kernelname [...]
boot directory [...]
boot -flag ... Boot as specified by the loader.conf(5) files read.
Depending on the arguments passed, it can override boot flags and either the kernel name or the search path for
kernel and modules.
boot-conf
boot-conf kernelname [...]
boot-conf directory [...]
boot-conf -flag ... Works like boot described above, but instead of booting immediately, uses autoboot, so it can be stopped.
start Reads /boot/defaults/loader.conf, all other loader.conf(5) files specified in it, then loads the desired kernel
and modules (if not already loaded). After which you can use the boot or autoboot commmands or simply exit
(provided autoboot_delay is not set to NO) to boot the system. start is the command used in the default
/boot/loader.rc file (see loader(8)).
initialize Initialize the support library so commands can be used without executing start first. Like start, it reads
/boot/defaults/loader.conf and all other loader.conf(5) files specified in it (but does not load kernel or
modules). Returns a flag on the stack to indicate if any configuration files were successfully loaded.
read-conf filename Reads and processes a loader.conf(5) file. Does not proceed to boot.
enable-module module Enables the loading of module.
disable-module module Disables the loading of module.
toggle-module module Toggles the loading of module on and off.
show-module module Shows the information gathered in the loader.conf(5) files about the module module.
retry Used inside loader.conf(5) files to specify the action after a module loading fails.
ignore Used inside loader.conf(5) files to specify the action after a module loading fails.
try-include file [file ...]
Process script files if they exist. Each file, in turn, is completely read into memory, and then each of its
lines is passed to the command line interpreter. If any error is returned by the interpreter, the try-include
command aborts immediately, without reading any other files, and silently returns without error.
FILES
/boot/loader The loader(8).
/boot/loader.4th loader.4th itself.
/boot/loader.rc loader(8) bootstrapping script.
/boot/defaults/loader.conf
File loaded by the start command.
EXAMPLES
Standard /boot/loader.rc:
include /boot/loader.4th
start
Load a different kernel with the standard configuration:
set kernel="kernel.old"
unload
boot-conf
Read an additional configuration file and then proceed to boot:
unload
read-conf /boot/special.conf
boot-conf
Disable the loading of the splash screen module and bitmap and then proceed to boot:
unload
disable-module splash_bmp
disable-module bitmap
boot-conf
SEE ALSO
loader.conf(5), loader(8)
HISTORY
The loader.4th set of commands first appeared in FreeBSD 3.2.
AUTHORS
The loader.4th set of commands was written by Daniel C. Sobral <dcs@FreeBSD.org>.
BUGS
A British espionage series.
BSD
November 13, 2013 BSD