Sponsored Content
Top Forums UNIX for Dummies Questions & Answers boot up failure unix sco after power failure Post 302615609 by edfair on Thursday 29th of March 2012 10:24:36 PM
Old 03-29-2012
This is a hardware failure long before you get to SCO.

From the error message talking about ROM shadow it appears that that you have a memory problem where it is attempting to load ROM code into a RAM segment.

Think I saw one of these a long time ago but didn't get interested in the hardware details.

You may want to look at the OS version again. Don't recall a 5.0.06 but SCO put letters at the end of the version on the boot floppy that created confusion. I suspect you have 5.0.0.

If it is a memory problem you may have issues getting parts. You might consider replacing the hardware. DELL stuff that will handle the OS is selling on the used market for under $25 if you can reuse the I/O gear and reload the operating system and applications.
 

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
SEGATTACH(2)							System Calls Manual						      SEGATTACH(2)

NAME
segattach, segdetach, segfree - map/unmap a segment in virtual memory SYNOPSIS
#include <u.h> #include <libc.h> long segattach(int attr, char *class, void *va, ulong len) int segdetach(void *addr) int segfree(void *va, ulong len) DESCRIPTION
Segattach creates a new memory segment, adds it to the calling process's address space, and returns its lowest address (as an integer). Segments belong to system-dependent classes. Segment classes memory (plain memory) and shared (shared memory) are available on all sys- tems. Shared segments are inherited by the children of the attaching process and remain untouched across a fork(2). An exec(2) will release a shared segment if it overlaps the segments in the file being exec'ed; otherwise the segment will be inherited. Some machines provide a segment class lock. Lock segments allow access to special lock hardware provided by some multiprocessors, in par- ticular the SGI Power Series machines. Systems may also provide interfaces to special hardware devices like frame buffers through the segattach interface. Device memory mapped by this method is typically uncached by default. If the specified class is unknown, segattach draws an error. Attr specifies the new segment's attributes. The only attributes implemented on all classes of segment is SG_RONLY, which allows only read access on the segment, and SG_CEXEC, which causes the segment to be detached when the process does an exec(2). Specific devices may imple- ment attributes to control caching and allocation, but these will vary between devices. Va and len specify the position of the segment in the process's address space. Va is rounded down to the nearest page boundary and va+len is rounded up. The system does not permit segments to overlap. If va is zero, the system will choose a suitable address. Segdetach removes a segment from a process's address space. Memory used by the segment is freed. Addr may be any address within the bounds of the segment. The system will not permit the text and stack segments to be detached from the address space. Segfree allows specific areas of a segment's memory to be returned to the system, but leaves that portion of the process's address space valid, to be reconnected to initialized memory of the appropriate type if addressed again. Va and len are interpreted as in segattach but need not refer to the entire segment. The MIPS R2000 and R3000 have no hardware instructions to implement locks. The following method can be used to build them from software. First, try to segattach a segment of class lock. If this succeeds, the machine is an SGI Power Series and the memory contains hardware locks. Each 4096-byte page has 64 long words at its beginning; each word implements a test-and-set semaphore when read; the low bit of the word is zero on success, one on failure. If the segattach fails, there is no hardware support but the operating system helps: Any COP3 instruction will be trapped by the kernel and interpreted as a test-and-set. In the trap, R1 points to a long; on return, R1 is greater or equal zero on success, negative on failure. The following assembly language implements such a test-and-set. /* * MIPS test and set */ TEXT tas(SB), $0 MOVW R1, sema+0(FP) /* save arg on stack */ btas: MOVW sema+0(FP), R1 MOVB R0, 1(R1) NOR R0, R0, R0 /* NOP */ WORD $(023<<26) /* MFC3 R0, R0 */ BLTZ R1, btas RET SOURCE
/sys/src/libc/9syscall SEE ALSO
lock(2), segbrk(2), segflush(2) /proc/*/segment DIAGNOSTICS
These functions set errstr. BUGS
The return type of segattach is peculiar. Also, segattach returns -1 on error; beware that on some systems other negative values might be legal addresses. There is a small fixed limit on the number of segments that may be attached, as well as a maximum segment size. SEGATTACH(2)
All times are GMT -4. The time now is 04:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy