09-11-2009
It is hard to tell what is going on for sure from the info you have. Here are a couple hints/starting points.
The Unix equivalent of scandisk is called "fsck". I've run it many times and never seen output like you're getting so I doubt is is a disk check. You could google that to familiarize yourself with it so you can be sure.
Based on all the hex addresses you're getting I would guess you're getting a panic - analagous to the "blue screen of death" from Windows. This is often caused by a software problem (writing to restricted memory, illegal instruction, etc.) but can also be caused by hardware errors. If this is a server with a service processor of some kind try to access that and see if it logged any hardware faults or messages. If it's just a PC obviously that won't work.
You probably need to reboot or power cycle in either case. Carefully watch the messages and see if you can find a clue there.
Good luck.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello All
We are using Tru64 Unix V4.0D on a Digital Alpha 1200 machine, which by coincidence, crashed last night! Completely out of the Blue!!! After rebooting the system and recovering the databases everything seemed to work ok. It is however, discomforting not to know how or why the system... (2 Replies)
Discussion started by: Ivo
2 Replies
2. Filesystems, Disks and Memory
I need some expert help, and would appreciate any feedback on the following problem:
After power outage the machine didn't allow the login. When we checked it , it looked like both disks were completely empty. Luckily, we have a backup machine, and we can restore the disks.
Has anybody seen... (3 Replies)
Discussion started by: DGoubine
3 Replies
3. HP-UX
Hi,
First of all, thanks for your help. I have downloaded freeBSD to study unix
I'm here again 'cause my HP-UX 10.x has "broken". It raise this error:
----------------------------------------------------
Diagnostic System warning:
= 0x1f005000 is POWERFAILED The diagnostic logging... (1 Reply)
Discussion started by: efrenba
1 Replies
4. UNIX for Dummies Questions & Answers
helo,
suppose u have well build in product system which is build in linux o.s. now due to reason system automatically become crash(software crash),then how do u handle such crash. which is better way to handle such crash.
amit (0 Replies)
Discussion started by: amitpansuria
0 Replies
5. AIX
Hello everyone
I have a partition with the TL 5300-06-01-0000 and try to update to this TL 5300-09-03-0918 but suddenly the update dont work more. I get in to the HMC and I see this code error 888 102 700 0C5
I try to restart my partition but doesnt work.
Theres someone who has this... (9 Replies)
Discussion started by: lo-lp-kl
9 Replies
6. Programming
hello all,
I have developed a server application in C for ulinux kernel 2.6.It works very fine; creating a socket, binding it to a port, listening for incoming sockets and accepting them ,all finish without any error.
But there is a problem regarding application crash.After an intentionally... (1 Reply)
Discussion started by: Sedighzadeh
1 Replies
7. HP-UX
Hi all,
I have a server running HP-UX 11i V1 (11.11).
We had a problem with the system disk which cannot boot and the recovery with the CD failed too.
the only solution was to re-install the system on a new disk.
The problem now is to get access to the data which are on other disks, not... (2 Replies)
Discussion started by: aribault
2 Replies
8. Solaris
Hey all
what is the command to check "Check for existence of crash/coredump files in /var/crash/"hostname" directory"
thanks for help (4 Replies)
Discussion started by: gema.utama
4 Replies
9. OS X (Apple)
MacPro (2013) 12-Core, 64GB RAM (today's crash):
panic(cpu 2 caller 0xffffff7f8b333ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (318824 seconds ago): 31883, last successful... (3 Replies)
Discussion started by: Neo
3 Replies
LEARN ABOUT OPENDARWIN
fsck_msdos
FSCK_MSDOS(8) BSD System Manager's Manual FSCK_MSDOS(8)
NAME
fsck_msdos -- DOS/Windows (FAT) file system consistency check
SYNOPSIS
fsck_msdos -q special ...
fsck_msdos -p [-f] special ...
fsck_msdos [-fny] special ...
DESCRIPTION
The fsck_msdos utility verifies and repairs FAT file systems (more commonly known as DOS file systems).
The first form of fsck_msdos quickly checks the specified file systems to determine whether they were cleanly unmounted.
The second form of fsck_msdos preens the specified file systems. It is normally started by fsck(8) run from /etc/rc.boot during automatic
reboot, when a FAT file system is detected. When preening file systems, fsck_msdos will fix common inconsistencies non-interactively. If
more serious problems are found, fsck_msdos does not try to fix them, indicates that it was not successful, and exits.
The third form of fsck_msdos checks the specified file systems and tries to repair all detected inconsistencies, requesting confirmation
before making any changes. The default behavior is to always ask for confirmation of each change. Use the -n or -y options to override this
default behavior.
The options are as follows:
-q Causes fsck_msdos to quickly check whether the volume was unmounted cleanly. If the volume was unmounted cleanly, then the
exit status is 0. If the volume was not unmounted cleanly, then the exit status will be non-zero. In either case, a message
is printed to standard output describing whether the volume was clean or dirty.
-f This option is ignored by fsck_msdos and is present only for compatibility with programs that check other file system types for
consistency.
-n Causes fsck_msdos to assume no as the answer to all operator questions, except ``CONTINUE?''.
-p Preen the specified file systems.
-y Causes fsck_msdos to assume yes as the answer to all operator questions.
SEE ALSO
fsck(8)
BUGS
fsck_msdos is still under construction.
NetBSD August 13, 1995 NetBSD