11-21-2001
Disk Crash
We have a Unix system with two hard drives. When we tried to access it this morning it had frozen, and when we rebooted it couldn't find one of the hard drives, and had quite a few bad data blocks on the other. Of course we fear the worst: that the drive is completely gone, but were not sure how to be sure. I don't have much experience in this area and can't find anything in my books. Can any of you recommend a course of action?
10 More Discussions You Might Find Interesting
1. 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
2. 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
3. Solaris
I installed solaris 5.9 on a machine SunBlade100 512Mo of RAM and 18Go of hard disc, after the installation I have remark that the machine starts again after 10mn with 15 mn of walk, I downloaded and installed the last patchs on the machine but the poblème persists. someone can help me and tell me... (0 Replies)
Discussion started by: toufik
0 Replies
4. Solaris
Can anyone of you help me in enabling crash dump on Solaris 5.5.1 (1 Reply)
Discussion started by: csreenivas
1 Replies
5. Filesystems, Disks and Memory
Hi, First post. I am not to experienced in the Unix or HP-UX world but I'm learning.
We have some problem with a HP rx4640 server. During boot it states the following:
Checking for LVM volume groups and Activating (if any exist)
Volume group "/dev/vg00" has been successfully changed.
vgchange:... (7 Replies)
Discussion started by: hoff
7 Replies
6. Solaris
hi ,
i have machine that is crashed
how i can enable core dump file & how can i find it ? :confused: (4 Replies)
Discussion started by: lid-j-one
4 Replies
7. Solaris
Hi all,
I want to put a local disk on a Sun Cluster node but scconf command explodes :eek:
My system:
* two node cluster on two VMWare virtual machines
* Solaris 10 SunOS 5.10 Generic_141415-05 i86pc i386 i86pc
* Sun Cluster 3.2 u2
* Veritas Volume manager
The situation... (2 Replies)
Discussion started by: gxmsgx
2 Replies
8. Solaris
I am supporting a server running Solaris 4.3.The server is not having ddicated system administrator and i am requred to do minor maintenance tasks.l From few days, The server is automatically crashing and i just reboot the server. I also do not see anything in /var/adm/messages that can give an... (1 Reply)
Discussion started by: asalman.qazi
1 Replies
9. SCO
Hi,
I need help, one of our servers is down, and all data in that Server are critical:
The Scenario:
-------------
I have a computer with the next architecture:
architecture=IA32
bus_types=PCI2.10,ISA,PnP1.0
hostname=xxx.xxx.xxx (the real name is hidden)
hw_provider=Generic AT... (2 Replies)
Discussion started by: danilosevilla
2 Replies
10. Solaris
Hello all;
We have a SunFire V240 with three disks that were part of a metadb. One of those disks, the boot disk, experienced a horrible death Monday night and we're now trying to recover from that.
I know very little about metadb stuff, so please be gentle with me...
I'm assuming... (3 Replies)
Discussion started by: Handon
3 Replies
HALT(8) Linux System Administrator's Manual HALT(8)
NAME
halt, reboot, poweroff - stop the system.
SYNOPSIS
/sbin/halt [-n] [-w] [-d] [-f] [-i] [-p] [-h]
/sbin/reboot [-n] [-w] [-d] [-f] [-i]
/sbin/poweroff [-n] [-w] [-d] [-f] [-i] [-h]
DESCRIPTION
Halt notes that the system is being brought down in the file /var/log/wtmp, and then either tells the kernel to halt, reboot or power-off
the system.
If halt or reboot is called when the system is not in runlevel 0 or 6, in other words when it's running normally, shutdown will be invoked
instead (with the -h or -r flag). For more info see the shutdown(8) manpage.
The rest of this manpage describes the behaviour in runlevels 0 and 6, that is when the systems shutdown scripts are being run.
OPTIONS
-n Don't sync before reboot or halt. Note that the kernel and storage drivers may still sync.
-w Don't actually reboot or halt but only write the wtmp record (in the /var/log/wtmp file).
-d Don't write the wtmp record. The -n flag implies -d.
-f Force halt or reboot, don't call shutdown(8).
-i Shut down all network interfaces just before halt or reboot.
-h Put all hard drives on the system in stand-by mode just before halt or power-off.
-p When halting the system, switch off the power. This is the default when halt is called as poweroff.
DIAGNOSTICS
If you're not the superuser, you will get the message `must be superuser'.
NOTES
Under older sysvinit releases , reboot and halt should never be called directly. From release 2.74 on halt and reboot invoke shutdown(8) if
the system is not in runlevel 0 or 6. This means that if halt or reboot cannot find out the current runlevel (for example, when
/var/run/utmp hasn't been initialized correctly) shutdown will be called, which might not be what you want. Use the -f flag if you want to
do a hard halt or reboot.
The -h flag puts all hard disks in standby mode just before halt or power-off. Right now this is only implemented for IDE drives. A side
effect of putting the drive in stand-by mode is that the write cache on the disk is flushed. This is important for IDE drives, since the
kernel doesn't flush the write cache itself before power-off.
The halt program uses /proc/ide/hd* to find all IDE disk devices, which means that /proc needs to be mounted when halt or poweroff is
called or the -h switch will do nothing.
AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl
SEE ALSO
shutdown(8), init(8)
Nov 6, 2001 HALT(8)