Sponsored Content
Operating Systems Solaris Problem with 280R not booting Post 82507 by 98_1LE on Thursday 1st of September 2005 09:26:23 PM
Old 09-01-2005
Problem with 280R not booting

The box is in Houston, and I am in Dallas. Anyway, I do have serial access to the console. The box is hanging just after the WARNING's for the SDS modules not loading (normal boot message). I booted off CD, and mounted up all the file systems. Everything looked normal, and I could not find any problems in /etc/system or anywhere else.

It is Solaris 8, and very important to our business. I am hold with Sun now, but was hoping someone might be able help.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Problem with booting

Hi! I installed Slackware on my computer so I thought I could have dual booting with ME, but that didn't work. So I installed another bootmanager that I find on internet. When I startup my computer the second bootmangaer that I did find on internet lets me choose system. When I have choosen... (3 Replies)
Discussion started by: Mr.Rudiment
3 Replies

2. UNIX for Advanced & Expert Users

Booting Problem

Hai I have installed win 98 o.s in my system after that i have installed Red Hat Linux 7.0,there is a problem in dual booting,by default win98 is being booted, when i insert bootable linux floppy linux is loaded My doubt how to overwrite windows MBR and palce the lilo in MBR.so that it... (2 Replies)
Discussion started by: rajashekaran
2 Replies

3. UNIX for Advanced & Expert Users

Sun Booting problem

I was trying to test run a /bin/bash script i had just written when my monitor suddenly went blank.I had to shut down the machine from the systems main power. I was unable to boot afterwards and soo i went for the interactive boot process by typing boot -a. I succeded in the first stage of the... (1 Reply)
Discussion started by: lealyz
1 Replies

4. Solaris

Booting problem Veritas

Hi , I am having 490 Sun Fire Server ,Server having Two 72 GB each Disk.Disk are under veritas VM 4 control. Both disk are mirred with veritas VM4. Fisrt disk is encapsulate and other disk is mirred.System is working Fine but when I removed Fitrst Disk and reboot the system it does not boot from... (4 Replies)
Discussion started by: pradeeprajput_k
4 Replies

5. Solaris

booting problem

any one can help me. my system running on solaris 2.7. recently there is sudden power failure while system running. after that unable to boot the system. it is giving comment that "can not open /etc/path_to_inst" and then returning back to "OK" after comment of termination. The processor is... (10 Replies)
Discussion started by: prabir
10 Replies

6. UNIX for Dummies Questions & Answers

problem booting

Dear List, While I was adding second hard disk to my system, I changed the /etc/fstab file by adding the following line: /mnt/sdb1 /dev/sdb1 ext3 default 2 1 Now system does not boot and gives the following error: Checking filesystems /: Clean, 309260/18495840 files, 1064776/18486790... (2 Replies)
Discussion started by: siavoush
2 Replies

7. Solaris

Sunfire 280R Solaris 5.9 booting

Hi, I have to question: 1) when O/S is booting, i see messages: /dev/rdsk/c1t0d0s5: is logging /dev/rdsk/c1t0d0s3: is logging /dev/rdsk/c1t0d0s7: is logging i partitioned these slices during installation of O/S 5.9. I can access to these mountpoint no problem. But... (3 Replies)
Discussion started by: lamoul
3 Replies

8. AIX

AIX Booting problem

Hi, I have IBM RS/6000 44P MODEL 170 server with Aix 5.1 Till the morning server is working fine, i turned off properly but now i tried to start it is showing below error on LED and going down (power off) E051 >>>E0E0 >>>> E0E1>>>> 种种种种 >>>> 40210014 P1-C1-F1 ccccccc >>>> 40210014 >>>>E043... (3 Replies)
Discussion started by: ANAND KURADE
3 Replies

9. AIX

Booting problem

Dears, I have a problem when i reboot the machine last time "AIX 5.3", that after rebooting it not login to graphical desktop, it just stop at console login command line. Kindly find the attached screenshot. Anyway to let it login automatically to Desktop? Would appreciate any pointers to... (1 Reply)
Discussion started by: moudmm
1 Replies
GPTBOOT(8)						    BSD System Manager's Manual 						GPTBOOT(8)

NAME
gptboot -- GPT bootcode for UFS on BIOS-based computers DESCRIPTION
gptboot is used on BIOS-based computers to boot from a UFS partition on a GPT-partitioned disk. gptboot is installed in a freebsd-boot par- tition with gpart(8). IMPLEMENTATION NOTES
The GPT standard allows a variable number of partitions, but gptboot only boots from tables with 128 partitions or less. PARTITION ATTRIBUTES
gptboot checks and manages several attributes of GPT UFS partitions. bootme Attempt to boot from this partition. If more than one partition has the bootme attribute set, gptboot will attempt to boot each one until successful. bootonce Attempt to boot from this partition only one time. Setting this attribute with gpart(8) automatically also sets the bootme attribute. Multiple partitions may have the bootonce and bootme attributes set. bootfailed The bootfailed attribute marks partitions that had the bootonce attribute set, but failed to boot. This attribute is managed by the system. See BOOTING and POST-BOOT ACTIONS below for details. USAGE
For normal usage, the user does not have to set or manage any of the partition attributes. gptboot will boot from the first UFS partition found. The bootonce attribute can be used for testing an upgraded operating system on an already-working computer. The existing system partition is left untouched, and the new version of the operating system to be tested is installed on another partition. The bootonce attribute is set on that new test partition. The next boot is attempted from the test partition. Success or failure will be shown in the system log files. After a successful boot of the test partition, a user script can check the logs and change the bootme attributes so the test partition becomes the new system partition. Because the bootonce attribute is cleared after an attempted boot, a failed boot will not leave the system attempting to boot from a partition that will never succeed. Instead, the system will boot from the older, known-working operating system that has not been modified. If the bootme attribute is set on any partitions, booting will be attempted from them first. If no partitions with bootme attributes are found, booting will be attempted from the first UFS partition found. BOOTING
gptboot first reads the partition table. All freebsd-ufs partitions with only the bootonce attribute set, indicating a failed boot, are set to bootfailed. gptboot then scans through all of the freebsd-ufs partitions. Boot behavior depends on the combination of bootme and bootonce attributes set on those partitions. bootonce + bootme Highest priority: booting is attempted from each of the freebsd-ufs partitions with both of these attributes. On each partition, the bootme attribute is removed and the boot attempted. bootme Middle priority: booting is attempted from each of the freebsd-ufs partitions with the bootme attribute. If neither bootonce nor bootme attributes are found on any partitions, booting is attempted from the first freebsd-ufs partition on the disk. POST-BOOT ACTIONS The startup script /etc/rc.d/gptboot checks the attributes of freebsd-ufs partitions on all GPT disks. Partitions with the bootfailed attribute generate a ``boot from X failed'' system log message. Partitions with only the bootonce attribute, indicating a partition that successfully booted, generate a ``boot from X succeeded'' system log message. The bootfailed attributes are cleared from all the partitions. The bootonce attribute is cleared from the partition that successfully booted. There is normally only one of these. FILES
/boot/gptboot bootcode binary /boot.config parameters for the boot blocks (optional) EXAMPLES
gptboot is installed in a freebsd-boot partition, usually the first partition on the disk. A ``protective MBR'' (see gpart(8)) is typically installed in combination with gptboot. Install gptboot on the ada0 drive: gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0 gptboot can also be installed without the PMBR: gpart bootcode -p /boot/gptboot -i 1 ada0 Set the bootme attribute for partition 2: gpart set -a bootme -i 2 ada0 Set the bootonce attribute for partition 2, automatically also setting the bootme attribute: gpart set -a bootonce -i 2 ada0 SEE ALSO
boot.config(5), rc.conf(5), boot(8), gpart(8) HISTORY
gptboot appeared in FreeBSD 7.1. AUTHORS
This manual page written by Warren Block <wblock@FreeBSD.org>. BSD
February 5, 2014 BSD
All times are GMT -4. The time now is 08:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy