08-15-2002
Solaris Server Crash
We have had a server (Solaris 2.6) hardisk crash. When booting the server we get:
ok> boot -S
Boot Device: /sbus/espdmc@e, 8400000/esp@e,8800000/sd@0,0
short read 0x2000 chars read
disk read error
The only way we can get into the console is to
ok> boot cdrom
whereby everything (e.g. /mnt) is read-only.
It seems the /devices are not mounting due to the kernal reading a faulty block upon normal startup (I assume the block holding the kernal is ok, because we can boot the cd-rom).
We've also tried fsck, but no luck as the block in question is not mounted.
Do we fear the worst and look to re-install the OS?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi
I faced a problem while booting linux which is as follows;-
*************************************************
Inode 146180 has illegal block(s)
xauth:error in locking authority file /home/root/.Xauthority
Fatal Server Error:
Could not create lock file in /tmp/tXo-lock
... (1 Reply)
Discussion started by: Abhishek
1 Replies
2. UNIX for Dummies Questions & Answers
Our SUn Solaris Server has crashed second time in 2 days, reason is not known , we are trying to determine what could have gone wrong, any ideas, the power supply seems to be fine, there is no response from keyboard,monitor etc and we had to do a hot boot yesterday..
Any suggestions what could be... (9 Replies)
Discussion started by: knarayan
9 Replies
3. Programming
Problem
- Linux Client/Server Socket Application: Preventing Client from quitting on server crash
Hi,
I am writing a Linux socket Server and Client using TCP protocol on Ubuntu 9.04 x64.
I am having problem trying to implement a scenario where the client should keep running even when the... (2 Replies)
Discussion started by: varun.nagpaal
2 Replies
4. Solaris
My sparc solaris 8 server crashed/rebooted yesterday and I have the vmcore files. I have some initial output from SCAT and ACT. I have not included all but any info would be helpful. I can supply more output if necessary.
Thanks you.
Can I have any information about this ACT and SCAT... (2 Replies)
Discussion started by: csgonan
2 Replies
5. SCO
Hi there.
Well i have a really bad problem with my server:
UnixWare Version 5 Release 7
The system crash :wall: and show the error:
Panic: Kernel-mode address fault on user address 0x00000004 :eek:
If anyone knows about the reason of this error please give me a help
Sorry by my english.... (3 Replies)
Discussion started by: danilosevilla
3 Replies
6. Programming
The steps to test the problem
1. Open TCP Server
2. Open TCP Client
3. TCP Client sends data to Server.
4. Close TCP Server and the client also crash without any notification
Second wonderful test:
1. Comment the following statement in Client.c (at line 168) and compile it
Writen(... (1 Reply)
Discussion started by: sehang
1 Replies
7. Red Hat
hi,
i would like to configure netdump, but saving the var/crash in the server itself, not in another server.
could anybody tell me if this is possible?
thanks (4 Replies)
Discussion started by: pabloli150
4 Replies
8. Solaris
Hello all.
I am new hear and would like to ask a question regarding to the Solaris Crash Analysis Tool.
We are analyzing the results of "thread summary" but not quite sure what the asterisk represents.
Following are the items that asterisk were attached.
50* threads sleeping on a semaphore (49... (1 Reply)
Discussion started by: YuW
1 Replies
9. Solaris
Hello,
I an triyng to write an emergency procedure, and I need your help, or point of view.
I trying to find a way to get connected to an U10 Sun Solaris by the serial port to be able to get access to the system to debug systeme crash before restarting the server.
The SUN U10 does not... (3 Replies)
Discussion started by: Aswex
3 Replies
10. 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
LEARN ABOUT CENTOS
backup_volinfo
BACKUP_VOLINFO(8) AFS Command Reference BACKUP_VOLINFO(8)
NAME
backup_volinfo - Displays a volume's dump history from the Backup Database
SYNOPSIS
backup volinfo -volume <volume name> [-localauth]
[-cell <cell name>] [-help]
backup voli -v <volume name>
[-l] [-c <cell name>] [-h]
DESCRIPTION
The backup volinfo command displays a dump history of the specified volume, reporting information such as the date on which the volume was
dumped and the tapes that contain it. Include the ".backup" extension on the volume name if the backup version of the volume was dumped.
OPTIONS
-volume <volume name>
Names the volume for which to display the dump history. Include the ".backup" or ".readonly" extension if the backup or read-only
version of the volume was dumped.
-localauth
Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The backup command interpreter presents it to
the Backup Server, Volume Server and VL Server during mutual authentication. Do not combine this flag with the -cell argument. For more
details, see backup(8).
-cell <cell name>
Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see backup(8).
-help
Prints the online help for this command. All other valid options are ignored.
OUTPUT
The output includes a line for each Backup Database dump record that mentions the specified volume, order from most to least recent. The
output for each record appears in a table with six columns:
dumpID
The dump ID of the dump that includes the volume.
lvl The depth in the dump hierarchy of the dump level at which the volume was dumped. A value of 0 indicates a full dump. A value of 1 or
greater indicates an incremental dump made at the specified depth in the dump hierarchy.
parentid
The dump ID of the dump's parent dump. A value of 0 indicates a full dump, which has no parent; in this case, the value in the "lvl"
column is also 0.
creation date
The date and time at which the Backup System started the dump operation that created the dump.
clone date
For a backup or read-only volume, the time at which it was cloned from its read/write source. For a read/write volume, the same as the
value in the "creation date" field.
tape name
The name of the tape containing the dump: either the permanent tape name, or an AFS tape name in the format
volume_set_name.dump_level_name.tape_index where volume_set_name is the name of the volume set associated with the initial dump in the
dump set of which this tape is a part; dump_level_name is the name of the dump level at which the initial dump was backed up;
tape_index is the ordinal of the tape in the dump set. Either type of name can be followed by a dump ID in parentheses; if it appears,
it is the dump ID of the initial dump in the dump set to which this appended dump belongs.
EXAMPLES
The following example shows part of the dump history of the Backup volume "user.smith.backup":
% backup volinfo -volume user.smith.backup
DumpID lvl parentID creation date clone date tape name
924600000 1 924427600 04/20/1999 05:20 04/20/1999 05:01 user_incr_2 (924514392)
924514392 1 924427600 04/19/1999 05:33 04/19/1999 05:08 user_incr_2
924427600 0 0 04/18/1999 05:26 04/18/1999 04:58 user_full_6
. . . . . . . .
. . . . . . . .
PRIVILEGE REQUIRED
None
SEE ALSO
backup(8), backup_dumpinfo(8), backup_volrestore(8)
COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas
Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.
OpenAFS 2012-03-26 BACKUP_VOLINFO(8)