Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Failure to boot v445
Operating Systems Solaris Failure to boot v445 Post 302612285 by gull04 on Sunday 25th of March 2012 02:15:00 PM
Old 03-25-2012
Hi DukeNuke2,

I thought that as well at the begining of this, but the muppet that built this system didn't build a separate /usr file system it's all under the root fs.

The /etc/vfstab file is valid (I think, but messy) as far as I can see, just to let you know I have been called out on this system - the last time I worked on it was about 10 years ago when it was on an E10K.

The /etc/vfstab file looks like;

Code:
ss071a-root>cat vfstab
#device         device          mount           FS      fsck    mount   mount
#to mount       to fsck         point           type    pass    at boot options
#
fd      -       /dev/fd fd      -       no      -
/proc   -       /proc   proc    -       no      -
/dev/vx/dsk/bootdg/swapvol      -       -       swap    -       no      nologging
/dev/vx/dsk/bootdg/rootvol      /dev/vx/rdsk/bootdg/rootvol     /       ufs     1       no      nologging
/dev/vx/dsk/bootdg/var  /dev/vx/rdsk/bootdg/var /var    ufs     1       no      -
/dev/vx/dsk/bootdg/opt  /dev/vx/rdsk/bootdg/opt /opt    ufs     2       yes     -
/dev/vx/dsk/bootdg/local        /dev/vx/rdsk/bootdg/local       /usr/local      ufs     2       yes     -
/dev/vx/dsk/bootdg/oraagent     /dev/vx/rdsk/bootdg/oraagent    /oracle/AGENT   ufs     2       yes     -
/devices        -       /devices        devfs   -       no      -
ctfs    -       /system/contract        ctfs    -       no      -
objfs   -       /system/object  objfs   -       no      -
swap    -       /tmp    tmpfs   -       yes     -
#NOTE: volume rootvol (/) encapsulated partition c0t0d0s0
#NOTE: volume swapvol (swap) encapsulated partition c0t0d0s1
#NOTE: volume local (/usr/local) encapsulated partition c0t0d0s5
#NOTE: volume opt (/opt) encapsulated partition c0t0d0s6
#NOTE: volume var (/var) encapsulated partition c0t0d0s7
## /cis/nbsp removed as not required. Awaiting confirmation from John Hibbs/Dave Dunn
## IM5740366
#/dev/vx/dsk/bootdg/nbsptmp     /dev/vx/rdsk/bootdg/nbsptmp     /cis/nbsp       ufs     2       yes     -
/dev/vx/dsk/nbs1dg/cis  /dev/vx/rdsk/nbs1dg/cis /cis    vxfs    2       yes     -
/dev/vx/dsk/nbs1dg/sag  dev/vx/rdsk/nbs1dg/sag  /sag    vxfs    2       yes     -
/dev/vx/dsk/nbs1dg/nbsp /dev/vx/rdsk/nbs1dg/nbsp        /cis/nbsl       vxfs    2       yes     -
/dev/vx/dsk/nbs1dg/u11 /dev/vx/rdsk/nbs1dg/u11 /u11 vxfs        2       yes     -
/dev/vx/dsk/nbs1dg/u12 /dev/vx/rdsk/nbs1dg/u12 /u12 vxfs        2       yes     -
/dev/vx/dsk/nbs1dg/u13 /dev/vx/rdsk/nbs1dg/u13 /u13 vxfs        2       yes     -
/dev/vx/dsk/nbs1dg/u14 /dev/vx/rdsk/nbs1dg/u14 /u14 vxfs        2       yes     -
/dev/vx/dsk/nbs1dg/u15 /dev/vx/rdsk/nbs1dg/u15 /u15 vxfs        2       yes     -
/dev/vx/dsk/nbs1dg/u16 /dev/vx/rdsk/nbs1dg/u16 /u16 vxfs        2       yes     -
/dev/vx/dsk/nbs1dg/u17 /dev/vx/rdsk/nbs1dg/u17 /u17 vxfs        2       yes     -
/dev/vx/dsk/nbs1dg/u18 /dev/vx/rdsk/nbs1dg/u18 /u18 vxfs        2       yes     -
/dev/vx/dsk/nbs1dg/ehome /dev/vx/rdsk/nbs1dg/ehome /home vxfs   2       yes     -
/dev/vx/dsk/nbs1dg/projberyl /dev/vx/rdsk/nbs1dg/projberyl /proj/beryl vxfs     2       yes     -
##-----------------------------------------------
#/dev/vx/dsk/nbsappsdg/berylapps /dev/vx/rdsk/nbsappsdg/berylapps /proj/beryl vxfs      2       yes     -
#/dev/vx/dsk/nbsappsdg/egateapps /dev/vx/rdsk/nbsappsdg/egateapps /egate vxfs   2       yes     -
##/dev/vx/dsk/nbsexportdg/nbsexport /dev/vx/rdsk/nbsexportdg/nbsexport /nbsexport vxfs 2 yes suid
##/dev/vx/dsk/nbstempdg/nbstemp /dev/vx/rdsk/nbstempdg/nbstemp /nbstemp vxfs 2 yes suid

So as you'll be able to see there isn't a separate mount for the /usr file system.

Regards

Dave
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

HP-UX respawning boot failure

Hello. System is a HP Visualize C3600 running X11 and after a power failure machine will not boot (see error messages below) From what I've read, this may be caused by a corrupted etc/inittab file. Solution suggested on other websites is to boot in single user mode and edit file inittab... (2 Replies)
Discussion started by: westcoast
2 Replies

2. Linux

Boot failure

Hi all I used a dual boot operating system and it works fine for me. Now , i install a Ati radeon 9250 Agp card on my system and this results in boot failure of fedora 6. The graphics card is working fine with windows XP , i.e i have no compatibility issues.The system also refuses to boot when i... (2 Replies)
Discussion started by: joshighanshyam
2 Replies

3. Solaris

INT18 boot failure

I installed solaris virtually and tried to format the partitions .. I dont know what went wrong, It got rebooted and hangs in the screen "No partitions" and after pressing Enter button it goes to "INT18 boot failure" and hangs there once again . Could any one of you suggest why this has happened... (3 Replies)
Discussion started by: priky
3 Replies

4. Solaris

Boot failure

I have installed Solaris 10 OS in Sun Virtual Box that uses x86 32 bit system. After an abnormal shutdown i'm getting the following message on the console when i try to boot. SunOS Release 5.10 Version Generic_127128_11 32-bit Copyright 1983-200 Sun Microsystems, Inc. All rights reserrved. Use... (3 Replies)
Discussion started by: Sesha
3 Replies

5. SCO

stage 1 boot failure: error loading hd (40)/boot

hi SCO Unix 5.0.6 doesn't boot due to this problem: not a directory boot not found cannot open stage 1 boot failure: error loading hd (40)/boot Knows someone howto solve it? (16 Replies)
Discussion started by: ccc
16 Replies

6. Solaris

V445 unable to boot because of an error

This is what is displayed on the screen as the system tries to boot and then hangs: 0>Test CPU(s)....Done 0>Interrupt Crosscall....| SC Alert: DHCP negotiation failed, perhaps misconfigured or no DHCP server avail able Done 0>Init Memory....| SC Alert: Host System has Reset 'Done 0>PLL... (2 Replies)
Discussion started by: kenosongo
2 Replies

7. UNIX for Dummies Questions & Answers

boot up failure unix sco after power failure

hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies

8. Solaris

OpenSolaris GRUB> boot failure HELP

Hi, i am running an old Opensolaris 5.11 snv_111b on an x86 server. After almost 4 years of successful service, last night out of the blue started to refuse all connections to it's services, ssh, http,etc. The only visible solution at that time was a restart. But now instead of booting the... (2 Replies)
Discussion started by: d_oilen
2 Replies

9. HP-UX

HPUX Boot failure.

When I login to the live console of my server and go to the console, I am getting the below message Processor is booting from the first available device. To discontinue, press any key within 10 seconds. 10 seconds expired. Proceeding... Trying Primary Boot Path... (11 Replies)
Discussion started by: chacko193
11 Replies

LEARN ABOUT CENTOS

grub2-bios-setup

GRUB-BIOS-SETUP(3)					     Library Functions Manual						GRUB-BIOS-SETUP(3)

NAME

       grub-bios-setup -- Set up images to boot from a device.

SYNOPSIS

       grub-bios-setup [-a | --allow-floppy] [-b | --boot-image=FILE]
			[-c | --core-image=FILE] [-d | --directory=DIR]
			[-f | --force] [-m | --device-map=FILE]
			[-s | --skip-fs-probe] [-v | --verbose] DEVICE

DESCRIPTION

       You should not normally run this program directly.  Use grub-install instead.

OPTIONS

       --allow-floppy
	      Make  the device also bootable as a floppy.  This option is the default for /dev/fdX devices.  Some BIOSes will not boot images cre-
	      ated with this option.

       --boot-image=FILE
	      Use FILE as the boot image.  The default value is boot.img.

       --core-image=FILE
	      Use FILE as ther core image.  The default value is core.img.

       --directory=DIR
	      Use GRUB files in the directory DIR.  The default value is /boot/grub.

       --force
	      Install even if problems are detected.

       --device-map=FILE
	      Use FILE as the device map.  The default value is /boot/grub/device.map .

       --skip-fs-probe
	      Do not probe DEVICE for filesystems.

       --verbose
	      Print verbose messages.

SEE ALSO

       info grub

								  Wed Feb 26 2014						GRUB-BIOS-SETUP(3)
All times are GMT -4. The time now is 12:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy