Sponsored Content
Operating Systems Solaris T2000 Sparc server fails boot Post 302930512 by achenle on Monday 5th of January 2015 07:29:36 AM
Old 01-05-2015
Boot verbose - both CD and normal. What's different?
 

10 More Discussions You Might Find Interesting

1. Solaris

Sun Sparc T2000 + StorageTek 2540 - Help, I'm lost

I have a Sun Sparc T2000 (Solaris 10 05-08) and have installed a PCI-X 4GB Single Port HBA card in it. I have one StorageTek 2540 array that I would like to connect to the T2000. For the moment it would be a single path connection, but I've ordered a 2nd HBA, so eventually it would be... (4 Replies)
Discussion started by: soliberus
4 Replies

2. Solaris

Error while trying to boot from cdrom on Sun Fire T2000

Hi Guyz, I recently downloaded sol-10-u6-ga1-sparc-dvd.iso from Sun. I burned the disk as cd .iso. When trying to boot at the ok> boot cdrom i get the following error: ----------------------------------------------------------------------- Boot device:... (2 Replies)
Discussion started by: Mwamba
2 Replies

3. Solaris

Sun Server T2000 occasionally reboot

Hi, i am really 'fresh' to Solaris or any UNIX OS. My role as web developer but i need slightly involve to Solaris support. It is harder for me to understand it and i recently encounter a problems. /var file system (/dev/md/rdsk/d425) is being checked. run fsck -F ufs /dev/md/rdsk/d425 ... (8 Replies)
Discussion started by: webster5u
8 Replies

4. Solaris

Accessing a StorageTek 2530 Disk array from SUN, SPARC Enterprise T2000

Hello, Wondering if anyone can help me with mounting a file share from my Sun T2000 server running Solaris 10 to my connected 2530 disk array? I believe I've connected the disk array correctly and I have created a volume on the array using the filesystem (Sun_SAM-FS, RAID-5). The T2000... (15 Replies)
Discussion started by: DundeeDancer
15 Replies

5. Solaris

Solaris 10 install fails on sparc

I'm trying to do an upgrade/install from Solaris 8 to Solaris 10 on a SUN Sparc system. I halt the system, as documented, but when I attempt to boot off the distribution DVD; i.e. halt : : OK> boot cdrom The system indicates that the device is 'unrecognizable' These are SUN... (5 Replies)
Discussion started by: imagtek
5 Replies

6. Solaris

Auto boot problem on Sun T2000

Hi All I have a problem on T2000 server. bash-3.00# uname -a SunOS 5.10 aaa Generic_120011-14 sun4v sparc SUNW,Netra-T2000After the initial solaris installation server failed to boot: Rebooting with command: boot Boot device: disk:b File and args: The file just loaded does not appear... (1 Reply)
Discussion started by: ouzist
1 Replies

7. Solaris

T2000 Server cannot power on

Hi All, I recently had issues with my new T2000 server. I purchased a new mainboard and swapped the CPU and DIMMs to the new board. Now when i power on the server im unable to do so. I get the following error: ‘SC Alert: Host system poweron failed due to fault at MB/FF_POK.' When i do... (2 Replies)
Discussion started by: Caully
2 Replies

8. Hardware

Hardware RAID on Sun T2000 Server

Hi All I have a Sun T2000 server. Couple of years ago I had configured and mirrored the boot drive with an other drive using hardware RAID 1 using raidctl command. Following is the hardware RAID output. root@oracledatabaseserver / $ raidctl RAID Volume RAID RAID Disk... (0 Replies)
Discussion started by: Tirmazi
0 Replies

9. Shell Programming and Scripting

Grep command Fails on SunOS Sparc

Hi, This command works ggrep -v -F -x -f app1.txt app2.txt But, I don't have ggrep on SunOS Sparc so I tried using grep instead but it errors out grep: illegal option -- F bash-2.03$ uname -a SunOS mymac 5.8 Generic_Virtual sun4v sparc sun4v Can you help me with a grep command that... (6 Replies)
Discussion started by: mohtashims
6 Replies

10. Solaris

M5000 fails to boot

I have an m5000 that Is down. I have access to XSCF> and was able to get to the ok prompt. However, on >ok boot it failed to boot. erred with : svc.startd: svc:/system/device/fc-fabric:default: Method "/lib/svc/method/fc-fabric" failed due to signal KILL. Nov 29... (3 Replies)
Discussion started by: goya
3 Replies
BOOT.CFG(5)						      BSD File Formats Manual						       BOOT.CFG(5)

NAME
boot.cfg -- configuration file for /boot DESCRIPTION
The file /boot.cfg is used to alter the behaviour of the standard boot loader described in boot(8). Configuration changes include setting the timeout, choosing a console device, altering the banner text and displaying a menu allowing boot commands to be easily chosen. If a boot.cfg file is not present, the system will boot as normal. FILE FORMAT The format of the file is a series of lines containing keyword/value pairs separated by an equals sign ('='). There should be no whitespace surrounding the equals sign. Lines beginning with a hash ('#') are comments and will be ignored. Some keywords can be present multiple times in the file to define additional items. Such keywords are noted below. banner (may be present multiple times) The text from banner lines is displayed instead of the standard welcome text by the boot loader. Up to 10 lines can be defined. No special character sequences are recognised, so to specify a blank line, a banner line with no value should be given. clear If nonzero, clear the screen before printing the banner. If zero, do not clear the screen (the default). consdev Changes the console device to that specified in the value. Valid values are any of those that could be specified at the normal boot prompt with the consdev command. default Used to specify the default menu item which will be chosen in the case of Return being pressed or the timeout timer reaching zero. The value is the number of the menu item as displayed. As described above, the menu items are counted from 1 in the order listed in boot.cfg. If not specified, the default value will be option 1, i.e. the first item. format Changes how the menu options are displayed. Should be set to one of 'a' for automatic, 'l' for letters and 'n' for numbers. If set to automatic (the default), menu options will be displayed numerically unless there are more than 9 options and the timeout is greater than zero. If there are more than 9 options with a timeout greater than zero and the format is set to number, only the first 9 options will be available. load Used to load kernel modules, which will be passed on to the kernel for initialization during early boot. The argument is either the complete path and file name of the module to be loaded, or a symbolic module name. When the argument is not an absolute path, the boot loader will first attempt to load /stand/<machine>/<kernel_version>/modules/<name>/<name>.kmod. If that file does not exist, it will then attempt to load /<name>. May be used as many times as needed. menu (may be present multiple times) Used to define a menu item to be displayed to the end-user at boot time which allows a series of boot commands to be run without further typing. The value consists of the required menu text, followed by a colon (':') and then the desired command(s). Multiple commands can be specified separated by a semi-colon. If the specified menu text is empty (the colon appears immediately after the equals sign), then the displayed menu text is the same as the command. For example: menu=Boot normally:boot menu=Boot single-user:boot -s menu=Boot with module foo:load /foo.kmod;boot menu=Boot with serial console:consdev com0;boot menu=:boot hd1a:netbsd -as Each menu item will be prefixed by an ascending number when displayed, i.e. the order in the boot.cfg file is important. Each command is executed just as though the user had typed it in and so can be any valid command that would be accepted at the nor- mal boot prompt. In addition, ``prompt'' can be used to drop to the normal boot prompt. timeout If the value is greater than zero, this specifies the time in seconds that the boot loader will wait for the end-user to choose a menu item. During the countdown period, they may press Return to choose the default option or press a number key corresponding to a menu option. If any other key is pressed, the countdown will stop and the user will be prompted to choose a menu option with no further time limit. If the timeout value is set to zero, the default option will be booted immediately. If the timeout value is negative or is not a number, there will be no time limit for the user to choose an option. userconf Passes a userconf(4) command to the kernel at boot time . rndseed Takes the path to a random-seed file as written by the -S flag to rndctl(8) as an argument. This file is used to seed the kernel entropy pool rnd(9) very early in kernel startup, so that high quality randomness is available to all kernel modules. This argument should be supplied before any ``load'' commands that may load executable modules. EXAMPLES
Here is an example boot.cfg file: banner=Welcome to NetBSD banner================== banner= banner=Please choose an option from the following menu: menu=Boot normally:boot menu=Boot single-user:boot -s menu=Boot from second disk:boot hd1a: menu=Boot with module foo:load /foo.kmod;boot menu=Boot with modules foo and bar:load /foo.kmod;load /bar.kmod;boot menu=Boot Xen with 256MB for dom0:load /netbsd-XEN3_DOM0 console=pc;multiboot /usr/pkg/xen3-kernel/xen.gz dom0_mem=256M menu=Boot Xen with 256MB for dom0 (serial):load /netbsd-XEN3_DOM0 console=com0;multiboot /usr/pkg/xen3-kernel/xen.gz dom0_mem=256M console=com1 com1=115200,8n1 menu=Boot Xen with dom0 in single-user mode:load /netbsd-XEN3_DOM0 -s;multiboot /usr/pkg/xen3-kernel/xen.gz dom0_mem=256M menu=Go to command line (advanced users only):prompt clear=1 timeout=-1 default=1 userconf disable ehci* # Always load ramdisk module load=/miniroot.kmod N.B. Xen counts serial ports from com1 upwards, but NetBSD counts from com0, so the appropriate device name must be used. Please see the Xen with serial console example above. This will clear the screen and display: Welcome to NetBSD ================= Please choose an option from the following menu: 1. Boot normally 2. Boot single-user 3. Boot from second disk 4. Boot with module foo 5. Boot with modules foo and bar 6. Boot Xen with 256 MB for dom0 7. Boot Xen with 256 MB for dom0 (serial) 8. Boot Xen with dom0 in single-user mode 9. Go to command line (advanced users only) Option [1]: It will then wait for the user to type 1, 2, 3, 4, 5, 6, 7, 8 or 9 followed by Return. Pressing Return by itself will run option 1. There will be no timeout. SEE ALSO
boot(8), boothowto(9) HISTORY
The boot.cfg file appeared in NetBSD 5.0. AUTHORS
The boot.cfg extensions to boot(8) were written by Stephen Borrill <sborrill@NetBSD.org>. BUGS
Support for boot.cfg is currently for NetBSD/i386 and NetBSD/amd64 only. It is hoped that its use will be extended to other appropriate ports that use the boot(8) interface. BSD
November 28, 2011 BSD
All times are GMT -4. The time now is 12:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy