Sponsored Content
Top Forums UNIX for Dummies Questions & Answers boot up failure unix sco after power failure Post 302614697 by fredthayer on Wednesday 28th of March 2012 05:43:01 PM
Old 03-28-2012
Question 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.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

boot failure SCO 5.0.6 OpenServer

hello guys. I just installed SCO 5.0.6 OpenServer it went all the way to the end of the installation and the first boot try it gave me this message. not a directory boot not found cannot open stage 1 boot failure: error loading hd (40)/boot (2 Replies)
Discussion started by: josramon
2 Replies

2. UNIX for Dummies Questions & Answers

Restart on power failure

How do I configure my workstation (Solaris 9) to restart and perform any check disk automatically if there is a power failure? Thanks. (1 Reply)
Discussion started by: here2learn
1 Replies

3. 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

4. Solaris

Automatic reboot does not work after power failure

Hi all, I have a server SUN FUJITSU in solaris 10 ; result of uname -a is : SunOS MOBD1 5.10 Generic_118833-03 sun4us sparc FJSV,GPUZC-M I have configured the eeprom to auto-boot as usual and this automatic reboot does not work in case of power failure. I must type "boot" on the prompt "ok"... (5 Replies)
Discussion started by: aribault
5 Replies

5. 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

6. 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

7. 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

8. Solaris

Failure to boot v445

Hi Guys, I have a small problem with a v445 which I have been informed will only boot with the reconfigure option enabled. It is attached to HP SAN storage using qla2300 FCA's with a Veritas encapsulated rootvoldg (No Laughing here please) when I try a reboot I get the following error. ... (5 Replies)
Discussion started by: gull04
5 Replies

9. Solaris

After power failure, SunFireV240 with SOLARIS 5.9 cannot start

SUNW, Sun Fire V240 Spare Sun OS Release 5.9 After a power failure we try to start the server We have the following messages: Thanks for your assistance (7 Replies)
Discussion started by: doudou2012
7 Replies

10. UNIX for Dummies Questions & Answers

Power failure: file damage?

~#hello -all, Many UNIX/Linux/BSD/etc books warn about turn off the puter without a proper shutdown. This can damage files which are open at that moment. Seems logical to me. My question is.. does the system warn you when there are damaged files when the system is up again? I had a power failure... (7 Replies)
Discussion started by: raylier
7 Replies
errors(4)						     Kernel Interfaces Manual							 errors(4)

NAME
errors - Contains a record of uucico daemon errors SYNOPSIS
/usr/spool/uucp/.Admin/errors DESCRIPTION
The /usr/spool/uucp/.Admin/errors file contains a record of uucico daemon errors that the uucp program cannot correct. For example, if the uucico daemon is unable to access a directory that is needed for a file transfer, the uucp program records this in the errors file. If debugging is enabled for the uucico daemon, the uucp program sends the error messages to standard output instead of to the errors file. EXAMPLES
Following is the text of an error that might appear in the errors file: ASSERT ERROR (uucico) pid: 303 (7/18-8:25:09) SYS- TAT OPEN FAIL /usr/spool/uucp/.Status/ (21) [SCCSID: @(#)systat.c 7.2 87/07/08 16:43:37, FILE: systat.c, LINE:100] This error occurred on July 18 at 8:25:09 a.m. [(7/18-8:25:09)] when the uucico daemon, running as process 303 [(uucico) pid: 303], could not open the /usr/spool/uucp/.Status directory [SYSTAT OPEN FAIL /usr/spool/uucp/.Status/]. To prevent this error from occurring again, you should make sure the permissions for the .Status directory are correct. It should be owned by the uucp login ID and group uucp, with permissions of 777 (read, write, and execute for owner, group, and all others). FILES
Contains the errors file and other uucp administrative files Lists the last time a remote system was contacted and the minimum time until the next retry RELATED INFORMATION
Commands: uudemon.cleanu(4) Daemons: uucico(8) delim off errors(4)
All times are GMT -4. The time now is 06:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy