10-05-2009
thx dude..
i hav find a soln for it..
soln:-
syntax:
boot: defbootstr ahslink=mdac Sdsk=mdac(0,0,0,1) disable=[scsi chip driver name]
example:
boot: defbootstr ahslink=mdac Sdsk=mdac(0,0,0,1) disable=DAC960
---------- Post updated at 04:54 PM ---------- Previous update was at 04:25 PM ----------
i hav a same problem in another acer altos machine
error:
NOTICE: k_trap - Unexpected NMI in system mode!
boot: defbootstr link=mdac
boot: defbootstr link=alad
boot: ahslink
boot: defbootstr ahslink=mdac Sdsk=mdac(0,0,0,1)
boot: defbootstr ahslink=mdac Sdsk=mdac(0,0,1)
boot: defbootstr ahslink=mdac Sdsk=mdac(0,0,0,1) disable=DAC960
boot: defbootstr ahslink=alad Sdsk=alad(0,0,0,1) disable=DAC960
boot: defbootstr ahslink=alad Sdsk=alad(0,0,0,1)
but these command are not working.....
plz help me..
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I am a newbie to Solaris. I want to know how to find out the controller target and disk number on a SunFire V890 box that has 6X72GB disks. The probe-scsi output is as shown below:
/pci@8,600000/SUNW,qlc@2
LiD HA LUN --- Port WWN --- ----- Disk description -----
0 0 0 ... (1 Reply)
Discussion started by: sudhir_shet
1 Replies
2. SCO
hi all
i use sco open server reliseas 5 on my system i get an image from system hard disk to another hard disk with acronis software and start system with new(backup)hard disk, but during the boot process some errors generate as follow
warning:hd:noroot disk controler was found
hd:a boot-time... (2 Replies)
Discussion started by: mehran_malek
2 Replies
3. HP-UX
Replace an unknown status controller on HP FC60 disk array
Author:JoyOnline JoyChangLu@gmail.com
Trouble description:
The users detected that the status of controller at A is unknown.
Analysis and diagnostic:
Physical observed all leds on enclosure of disk array is normal.
The... (4 Replies)
Discussion started by: JoyOnLine
4 Replies
4. SCO
I'm "attempting" to install SCO 5.0.7 on an HP ML370 G4 server and am ready to bash the keyboard with head now. I keep getting the error message "WARNING hd: no root disk controller found" when running the bootable install cd.
I have a raid 5 array with an online spare created using 4 36.3 GB... (2 Replies)
Discussion started by: FrictionBurn
2 Replies
5. Solaris
hi all
i am using vxvm 5.1 on my sun blade 150 which is running with solaris 5.10. When i give the command "vxdisk list" it gives the following output
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none - - online... (2 Replies)
Discussion started by: kingston
2 Replies
6. SCO
So today I tried to upgrade a customer from a Proliant with an HPSAS controller to an Intel server with a MEGASAS controller.
First, I downloaded the megasas driver from SCO and installed it on the old system.
Then I created a new Microlite Edge emergency boot cd with the new driver on it.
I... (2 Replies)
Discussion started by: jgt
2 Replies
7. Solaris
I changed disk controller. Unplugged every disk, inserted another controller card, an IBM M1015. The disks are recognized in BIOS, and the controller card's BIOS shows up. But after that, I drop into GRUB and a prompt. That is all.
How shall I solve this problem? I am thinking of booting from... (2 Replies)
Discussion started by: kebabbert
2 Replies
8. 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
9. Solaris
Hi
The scenario in the oracle t4-1 hardware with solaris 10 is as follows:
1. The initial install on the server was performed with an incorrect disk layout.
2. New disks were ordered and slot into the server.
3. The disks are allocated a controller and a disk number based on the disk or... (13 Replies)
Discussion started by: kerrygold
13 Replies
10. Solaris
Hi,
I have a Sun Fire V440 server that fails to boot up correctly. A lot of services are not started and the sytems acts really slow to commands. During boot I can see the following Error:
WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1):
SCSI transport failed: reason 'reset': retrying... (15 Replies)
Discussion started by: oliwei
15 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