Sponsored Content
Full Discussion: Solaris (9) won't boot!
Operating Systems Solaris Solaris (9) won't boot! Post 40685 by finster on Sunday 21st of September 2003 10:41:16 AM
Old 09-21-2003
you could of hit stop - a upon boot to get to your ok prompt.


then as stated above use printenv to show settings.

Is the system in diagnostic mode?

check diag-switch? (it should respond with false...)

if not: setenv diag-switch? false

Your machine was trying to boot from the net and this is the default setting for diag-switch=true. By changing it to diag-switch=false, default would be the disk. (maybe not the correct disk e.g. (disk0, disk1, etc) then edit boot-device disk0 or whatever disk #.


e.g setenv boot-device disk? (where ? is a #, disk = disk0 = scsi id 3)

The following link (sun manuals for ultra 60) willl have most of your answers.

http://www.sun.com/products-n-soluti..._60/index.html

Hope this helps for future references....
 

10 More Discussions You Might Find Interesting

1. AIX

server won't boot

Hi all , i was trying to upgrade firmware on machine 7028-6E4 and it failed . Now machine does not boot anymore , i can not get SMC menu either ... What are my options ? Thanks, Rahim (1 Reply)
Discussion started by: rahim
1 Replies

2. Solaris

cannot find boot device and won't boot off cdrom

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

Ultra 60 won't boot

I just was given an Ultra 60 that I'm trying to get started so that I can re-load the system with Solaris 10. I can't seem to get the system to boot past the initial memory check. I've tried to do an Stop-A to get to the eeprom, but can't do that. My next step is to try to send a break from the... (0 Replies)
Discussion started by: zosojohnny
0 Replies

4. UNIX for Dummies Questions & Answers

Linux won't boot

I'm trying to install Fedora 9 on a Dell OptiPlex GX300 machine. The instalation runs properly, but when the computer restarts after the instalation, it simply won't boot, like there's no OS installed. I tried diffrent Linux distributions, but nothing works. This are the partitions, maybe it's... (12 Replies)
Discussion started by: teis
12 Replies

5. AIX

won't mount /usr...won't boot fully

Hello: NOOB here. I attempted to use smit mkcd. Failed on first attempt, not enough space. 2nd attempt tried to place iso on /usr, not enough space there. Cleanup ran for about 5 minutes after aborting. Now AIX won't boot. LCD display on 7029-6E3 says: 0517 MOUNT /USR. Attempted to boot from CD... (11 Replies)
Discussion started by: bbird
11 Replies

6. Solaris

Solaris 10u7 won't boot after hardware change

Hi all, I've somehow gained the idea that I _need_ to run at least 1 box with Solaris, but things don't go as I had planned :-) I pulled this ancient IBM eserver xseries 305 out of the dust, and got myself a fresh copy of the required cd's for Solaris 10u7. FAIL, for some reason the box and the... (7 Replies)
Discussion started by: mr.aart
7 Replies

7. UNIX for Dummies Questions & Answers

SUN Ultra 10 won't boot - Help Please

Folks; My SUN Ultra 10 5.9 won't boot. It only stops after counting the memory on the white screen then hangs there with nothing. even the power button won't take it down from there, i had to unplug it then re-plug it again. i inserted a disk with Solaris 9 iso trying to rebuild it but nothing... (1 Reply)
Discussion started by: Katkota
1 Replies

8. UNIX for Dummies Questions & Answers

New kernel won't boot

I compiled new kernel in linux 10.04 called linux-2.6.26.8-xenomai, it runs alongside the other kernel, but when I want to boot it I get an error message saying: Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/sda5 does not exist. After making the modules and headers I made the... (4 Replies)
Discussion started by: mdop
4 Replies

9. Solaris

Solaris 10 won't boot up "Cannot load drivers for /pci@400.....

This is the error message that I am getting on a Solaris 10 sparc server scsi: no major number cannot load drivers for /pci@400..... Can't load the root filesystem Type 'go' to resume {0} ok Is there a way for me to correct this issue. It looks like I am missing a scsi driver to boot up... (5 Replies)
Discussion started by: trinityforce
5 Replies

10. Hardware

AT&T UNIX PC won't boot

Hello, I am new to the UNIX community, however I have a beginner's level understanding of a majority of the basic commands in UNIX. Today, my teacher gave me her old AT&T UNIX PC. I brought it home, turned it on, and got a completely green screen. I turned it off, and back on and it booted... (12 Replies)
Discussion started by: _dhoepp
12 Replies
bootconf(4)						     Kernel Interfaces Manual						       bootconf(4)

NAME
bootconf - boot device configuration table DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate boot devices should be automatically updated, the administrator must edit the file manually. There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown: disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following: Indicates that the root disk is in LVM or VERITAS Volume Manager (VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file. Indicates that the root disk is in the "whole disk" format with no partitions, but boot and swap space are reserved outside the file system. device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file that references the entire disk. Blank lines are permitted. Any line beginning with a is considered to be a comment. DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self- explanatory; a few warrant additional explanation: If there are no other messages about the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem is. The specified device file does not point to a disk where there is a lif which contains the file Some character other than or is in the first field of a line. As of release 10.0, the boot areas in must all be on the same type of disk layout. There are characters after the device file specification. EXAMPLES
The boot area is on an LVM root disk: l /dev/disk/disk7_p2 The boot area is on a whole disk layout: w /dev/disk/disk7 WARNINGS
All of the boot devices in the file must have the same disk layout. AUTHOR
was developed by the Hewlett-Packard Company. FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7). documentation. bootconf(4)
All times are GMT -4. The time now is 09:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy