05-29-2008
Google says that this hardware is x86 so maybe Linux? SCO? SUN OS/Solaris?
Is the raid controller setup integrated to the bios?
Does it have an extra CD to set it up?
Maybe the mirror was ok and the setup has to be directed to boot from the other disc or even the mirror was not ok. Maybe there is a log in the firmware/bios.
Else you might try some Linux distribution's boot/rescue/recovery CD (
KNOPPIX Linux Live CD) and try to mount the filesystems containing your data and copy them over the network away to another box, if everything else fails.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
HI ALL,
I need to backup HDD with SCO UNIX. I need to have a full functionaly backup of this hard disk. Does anybody have any tool or subsription how to do it. I tried some SW, but after when I tried to use this copy of my original disk "can not find a root directory". Thanks in advance. (1 Reply)
Discussion started by: jardas
1 Replies
2. Solaris
I've just replaced the secondary disk drive (was 4 Gb) with a Seagate Barracuda 7200 200 Gb. However the OS seems to think this is only 500 Mb and a spin speed of 5400, although it correct recognises the drive as Seagate ST3200822A.
I take it that it still thinks the old drive is attached. How... (5 Replies)
Discussion started by: wiggiesworld
5 Replies
3. UNIX for Dummies Questions & Answers
i have this HDD with SCO 5.0.6 and i'm getting this errors
WARNING: wd0: Error on fixed disk dev 1/42, block=4829, cmd=0x000000C8
Sun Mar 11 05:50:08 2007
status=0x00000040, LBA sector=1285723, cylinder/head=5022/0
WARNING: wd0: Error... (0 Replies)
Discussion started by: josramon
0 Replies
4. Solaris
hello gurus,
i have just installed the os on hdd,
when i write down boot command on ok prompt,
I get following error continuously.
what could be the possible problem
WARNING: /ssm@0,0/pci@18,600000/scsi@2/sd@0,0 (sd0):
auto request sense failed (reason=reset)
WARNING:... (2 Replies)
Discussion started by: sameergrover
2 Replies
5. BSD
Hi,
I have a crappy hard disk and am trying to back up stuff from it onto my newer hopefully less crappy disk. There are dead sectors on the disk and some files can't be read (at all) so OpenBSD downgrades the transfer mode down until PIO mode 4. I noticed the transfer speed slowing down... (0 Replies)
Discussion started by: fiori_musicali
0 Replies
6. UNIX for Dummies Questions & Answers
Over the last few months the HDD spins louder and louder, so I fiqured its time to replace the HDD. Its been running 24/7/365 since 98 :eek:. yes i said since 98 :D
I have an IBM system 43P Model 240. 233 MHz. running AIX Version 4.
The current HDD is an IBM DGHS COMP IEC -950
FRU PN#... (5 Replies)
Discussion started by: Chevy89rocks
5 Replies
7. Solaris
I have somehow taken on the collateral duties of System Administrator for our small internal network. At current we have one main file server with 48 SATA swappable drives under the Solaris 10 OS.
My question is this. Our analysts are bringing back data from the field in Windows formatted... (8 Replies)
Discussion started by: cbrowne20
8 Replies
8. Programming
Hi All,
I came across this error "MIXING ENUM TYPES" when I run my C program against the Coverity Tool. I've made many search relating to the error, but I didnt find the exact solution. Can anyone help me to overcome this.?
Thanks in Advance.!! (3 Replies)
Discussion started by: Parameswaran
3 Replies
9. AIX
Hi Folks,
I am facing an issue with the performance.
P4 with 1 processor and 16 GB RAM and SAN HDD = Oracle report takes 25 minutes
P5 with 2 processors and 16 GB RAM internall HDD with LPAR = Oracle Report takes 1 hour 15 minutes ( please note I have assigned all the max processors and... (7 Replies)
Discussion started by: filosophizer
7 Replies
LEARN ABOUT NETBSD
rescue
RESCUE(8) BSD System Manager's Manual RESCUE(8)
NAME
rescue -- rescue utilities in /rescue
DESCRIPTION
The /rescue directory contains a collection of common utilities intended for use in recovering a badly damaged system. With the transition
to a dynamically-linked root beginning with NetBSD 2.0, there is a real possibility that the standard tools in /bin and /sbin may become non-
functional due to a failed upgrade or a disk error. The tools in /rescue are statically linked and should therefore be more resistant to
damage. However, being statically linked, the tools in /rescue are also less functional than the standard utilities. In particular, they do
not have full use of the locale, pam(3), and nsswitch libraries.
If your system fails to boot, and it shows an error message similar to:
init: not found
try booting the system with the boot flag ``-a'' and supplying /rescue/init, which is the rescue init(8), as the init path.
If your system fails to boot, and it shows a prompt similar to:
Enter full pathname of shell or RETURN for /bin/sh:
the first thing to try running is the standard shell, /bin/sh. If that fails, try running /rescue/sh, which is the rescue shell. To repair
the system, the root partition must first be remounted read-write. This can be done with the following mount(8) command:
/rescue/mount -uw /
The next step is to double-check the contents of /bin, /lib, /libexec, and /sbin, possibly mounting a NetBSD installation CD-ROM and copying
files from there. Once it is possible to successfully run /bin/sh, /bin/ls, and other standard utilities, try rebooting back into the stan-
dard system.
The /rescue tools are compiled using crunchgen(1), which makes them considerably more compact than the standard utilities.
FILES
/rescue Root of the rescue hierarchy.
SEE ALSO
crunchgen(1)
HISTORY
The rescue utilities first appeared in NetBSD 2.0.
AUTHORS
The rescue system was written by Luke Mewburn <lukem@NetBSD.org>. This manual page was written by Simon L. Nielsen <simon@FreeBSD.org>,
based on text by Tim Kientzle <kientzle@FreeBSD.org>.
BUGS
Most of the rescue tools work even in a fairly crippled system. The most egregious exception is the rescue version of vi(1), which currently
requires that /usr be mounted so that it can access the termcap(5) files. Hopefully, a failsafe termcap(3) entry will eventually be added
into the curses(3) library, so that /rescue/vi can be used even in a system where /usr cannot immediately be mounted. In the meantime, the
rescue version of the ed(1) editor can be used from /rescue/ed if you need to edit files, but cannot mount /usr.
BSD
January 20, 2009 BSD