02-15-2005
It might be worth booting from the rescue disk, mounting whatever partition /var is on, and taking a look at /var/log/messages and other log files and see what happened at or just before the time the machine froze - see if there are any clues there....
Cheers
ZB
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I had Win98 and Win Xp on a dual boot on my system, I formatted my C: drive to get rid of Win98 and installed Linux Madrake in its Place, it all installed ok but when I boot up I can no longer dual boot and it goes straight into Mandrake Linux. How can I get either a dual boot so I can get to XP... (10 Replies)
Discussion started by: Merv
10 Replies
2. UNIX for Advanced & Expert Users
we have a problem with a server UNIX SUN OS 5.7 :
we tried to reboot it and we have the following error message :
"boot load failed
the file just loaded does not appear to be executable "
we booted the server in single user mode with the cdrom
we made the mirrored disk bootable
we tried... (2 Replies)
Discussion started by: farzolito
2 Replies
3. UNIX for Dummies Questions & Answers
i have instaled a boot loader and win98 on drive c: and linux on drive d: and when i go to boot with the loader into linux nottin happens.is there some way i should install lilo to let it boot of a loader on drive c: ? (5 Replies)
Discussion started by: perleo
5 Replies
4. Solaris
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
5. AIX
Hi Guys
everyone know this problem on P595???
One of my servers, on boot, sleep 10-15 minute on led 0c33.
I know that it's a console problem... but i don't understand how resolve it.
Ideas???
P.S.
Sorry for my english.
Thanks.
Zio (0 Replies)
Discussion started by: Zio Bill
0 Replies
6. Solaris
Hi everyone,
I have sun fire280R machine before i it is installed with solaris5.9 now i want to upgrade it but it not booting from the cd rom ....OK prompt also not comming i dont have solaris keyboard to press stop-A key...i have a intel supported keyboard ...what may be the problem it is... (1 Reply)
Discussion started by: alakshmanrao
1 Replies
7. UNIX for Dummies Questions & Answers
hello
i have a sun server V890 and it stops booting after adding 2 CPUs modules and gives me the following error message:
Enabling system bus....... Done
Initializing CPUs......... Done
Initializing boot memory..
RAM-Copy CRC failure!Can't start: No image found
FATAL: Can't find/decompress... (0 Replies)
Discussion started by: bahjatm
0 Replies
8. Solaris
hello
i have a sun server V890 and it stops booting after adding 2 CPUs modules and gives me the following error message:
Enabling system bus....... Done
Initializing CPUs......... Done
Initializing boot memory..
RAM-Copy CRC failure!Can't start: No image found
FATAL: Can't find/decompress... (12 Replies)
Discussion started by: bahjatm
12 Replies
9. Solaris
Hi all,
I have the the following SCSI diagnostic codes shown in the attached photo
I suspect disk drive failure what can I do further to diagnose the disk. and if possible to boot into OS again. (5 Replies)
Discussion started by: h@foorsa.biz
5 Replies
10. Red Hat
Hi,
My HP machine is using as boot device a disk defined in the Storage (IBM V5000). The connection is done by fiber connected through fiber switch.
No lacal disks are installed.
I'm using redhat 6.6.
I've installed and configured multipath.
Everything seems to work properly, however,... (0 Replies)
Discussion started by: Pazzeo
0 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