Sponsored Content
Operating Systems Solaris Serious problem to fail boot up Post 303015890 by linux_user on Monday 16th of April 2018 12:22:47 AM
Old 04-16-2018
Lightbulb Serious problem to fail boot up

My current OS using the solaris 9 and find the reboot , it returns the message even i restore , and boot -s

Code:
Hardware watchdog enabled 
Configuring ATM interfaces: 
NOTICE: VxVM not started 
configuring IPv4 interfaces: bge0 bge3 ce0 ce3. 
Hostname: devuardms01 
mount: mount-point /usr does not exist. 
/sbin/rcS: /usr/sbin/devfsadm: not found 
/sbin/rcS: /usr/bin/loadkeys: not found 
/etc/rcS.d/S35svm.init: rm: not found 
/etc/rcS.d/S35svm.init: grep: not found 
/etc/rcS.d/S35vxvm-startup1: /usr/lib/vxvm/voladm.d/lib/vxadm_lib.sh: not found 
/sbin/swapadd: expr: not found 
/sbin/swapadd: swap: not found 

WARNING - /usr/sbin/fsck not found. Most likely the 
mount of /usr failed or the /usr filesystem is badly 
damaged. The system is being halted. Either reinstall 
the system or boot with the -b option in an attempt 
to recover. 

syncing file systems... done 
Program terminated


Moderator's Comments:
Mod Comment Please use CODE tags as required by forum rules!

Last edited by RudiC; 04-16-2018 at 04:22 AM.. Reason: Added CODE tags.
 

10 More Discussions You Might Find Interesting

1. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies

2. Solaris

Solaris 9 install cd boot fail

Hi I hv try to install Solaris 9 on a SPARC machine. The machine now is with Solaris 10 OS. I try to load a Solaris 9 installation cd in and use "boot cdrom" on ok promt, but it give me "no boot device found" when it boot up. and when i use fsck, the system show me an error with the... (2 Replies)
Discussion started by: niuniu
2 Replies

3. Solaris

Solaris 10 x86 1/06 CD1 boot fail

Hello all. I download last version from sun.com, unzip iso's and burn their to cd's. When i try to load (on different machines) from first cd i receive this errors: /kernel/fs/specfs: undefined symbol '' /kernel/fs/specfs: undefined symbol '' ... several screens same message ....... (1 Reply)
Discussion started by: mozheyko_d
1 Replies

4. UNIX for Advanced & Expert Users

connect problem for sctp socket (ipv6 socket) - Runtime fail Invalid Arguments

Hi, I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime. To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
Discussion started by: chandrutiptur
0 Replies

5. Solaris

Fail to up network interface after system boot

Hi! I have Sun SPARC Enterprise T5140 with Solaris 10 and it unable to up network interface after boot, but after issuing ifconfig interface begins to work... svcs -xv says that service svc:/network/physical:default is failed to start and service log stores something like "service method... (5 Replies)
Discussion started by: Sapfeer
5 Replies

6. BSD

kernel fail to boot after recompile it

Salamo Alikom after recompilation my kernel does not boot and display msg said : enter full path to bash : /bin/sh i try fsck -r ,fsck -y but the problem is steel . my make.conf : PERL_VER=5.8.8 OVERRIDE_LINUX_BASE_PORT=f8 PERL_VERSION=5.8.8 MODULES_OVERRIDE = linux acpi accf_http pccard msdosfs... (1 Reply)
Discussion started by: SIFE
1 Replies

7. HP-UX

fail to boot HPUX

HPUX running in D-Class (L1000), pretty old HPUX version - hpux 11.00 Attempt 1 -- To boot from normal (primary) Unable to boot - system complains failure SYSTEM ALERT System Name : uninitialized DATE : 10/22/2011 Time : 03/41:12 Alert Level 15 = Fatal hardware or configuration... (12 Replies)
Discussion started by: ckwan
12 Replies

8. Red Hat

RHEL6 Diskless Remote boot fail

Hi guys, I've been trying to set up a server for disk-less booting of remote machines on a network. The server host OS is RHEL6 and I have configured dhcp, tftp and nfs services which are proven to be working since I am able to install RHEL6 through pxe boot. Now I want it to serve for disk-less... (0 Replies)
Discussion started by: aninmuk
0 Replies

9. Red Hat

System fail to boot

Hi im using centos 6.4 starting yesterday i have a strange issue that im unable to resolve. the system is booting to GRUB menu and the os is not starting. i tried to run a repair install and the message attached is what i get, what can cause this? thanks, (1 Reply)
Discussion started by: guy3145
1 Replies

10. UNIX for Beginners Questions & Answers

SPARC T4-1 "ERROR: boot-read fail"

Either I try to boot from USB bootable drive or from a bootable dvdrom, I am receiving a message ERROR: boot-read fail {0} ok probe-scsi-all This command may hang the system if a Stop-A or halt command has been executed. Please type reset-all to reset the system before executing this... (18 Replies)
Discussion started by: z_haseeb
18 Replies
rcS(5)							   Debian Administrator's Manual						    rcS(5)

NAME
rcS - variables that affect the behavior of boot scripts DESCRIPTION
The /etc/default/rcS file contains variable settings in POSIX format: VAR=VAL Only one assignment is allowed per line. Comments (starting with '#') are also allowed. OPTIONS
The following variables can be set. TMPTIME On boot the files in /tmp will be deleted if their modification time, file status time and access time are all at least TMPTIME days ago. A value of 0 means that files are removed regardless of age. If you don't want the system to clean /tmp then set TMPTIME to a negative value (e.g., -1) or to the word infinite. SULOGIN Setting this to yes causes init to spawn a sulogin on the console early in the boot process. If the administrator does not login then the sulogin session will time out after 30 seconds and the boot process will continue. DELAYLOGIN Normally the system will not let non-root users log in until the boot process is complete and the system has finished switching to the default runlevel (usually level 2). However, in theory it is safe to log in a bit earlier, namely, as soon as inetd has started. Setting the variable to no allows earlier login; setting the variable to yes prevents it. Some details: The DELAYLOGIN variable controls whether or not the file /var/lib/initscripts/nologin is created during the boot process and deleted at the end of it. /etc/nologin is normally a symbolic link to the latter location, and the login(1) program refuses to allow non-root logins so long as (the target of) /etc/nologin exists. If you set the variable to no then it is advisable to ensure that /var/lib/initscripts/nologin does not exist. VERBOSE Setting this option to no (in lower case) will make the boot process a bit less verbose. Setting this option to yes will make the boot process a bit more verbose. FSCKFIX When the root and all other file systems are checked, fsck is invoked with the -a option which means "autorepair". If there are major inconsistencies then the fsck process will bail out. The system will print a message asking the administrator to repair the file system manually and will present a root shell prompt (actually a sulogin prompt) on the console. Setting this option to yes causes the fsck commands to be run with the -y option instead of the -a option. This will tell fsck always to repair the file sys- tems without asking for permission. ASYNCMOUNTNFS Set this to 'no' to disable asynchronous mounting of network drives when the network interfaces are mounted, and instead do it only once when the machine boots. The default is 'yes'. It is useful to disable this on machines where the root file system is NFS, until ifup from ifupdown works properly in such setup. NOTE
The EDITMOTD, RAMRUN and UTC variables are no longer used. The RAMLOCK, RAMSHM and RAMTMP variables have been moved to /etc/default/tmpfs; RAMSHM and RAMTMP settings in rcS are used (if set) for backward compatibility, but will be overridden by settings enabled in /etc/default/tmpfs. See tmpfs(5) for further details. The settings are not automatically migrated to /etc/default/tmpfs. Please update /etc/default/tmpfs appropriately. The UTC setting is replaced by the UTC or LOCAL setting in /etc/adjtime, and should have been migrated automatically. See hwclock(5) and hwclock(8) for further details on configuring the system clock. AUTHOR
Miquel van Smoorenburg <miquels@cistron.nl> Roger Leigh <rleigh@debian.org> SEE ALSO
hwclock(5), hwclock(8), inetd(8), init(8), inittab(5), login(1), tmpfs(5). 21 May 2012 rcS(5)
All times are GMT -4. The time now is 09:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy