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
HP(4) Kernel Interfaces Manual HP(4)
NAME
hp - RH-11/RP04, RP05, RP06 moving-head disk
DESCRIPTION
The octal representation of the minor device number is encoded idp, where i is an interleave flag, d is a physical drive number, and p is a
pseudodrive (subsection) within a physical unit. If i is 0, the origins and sizes of the pseudodisks on each drive, counted in cylinders
of 418 512-byte blocks, are:
disk start length
0 0 23
1 23 21
2 0 0
3 0 0
4 44 386
5 430 385
6 44 367
7 44 771
If i is 1, the minor device consists of the specified pseudodisk on drives numbered 0 through the designated drive number. Successively
numbered blocks are distributed across the drives in rotation.
Systems distributed for these devices use disk 0 for the root, disk 1 for swapping, and disk 4 (RP04/5) or disk 7 (RP06) for a mounted user
file system.
The block files access the disk via the system's normal buffering mechanism and may be read and written without regard to physical disk
records.
A `raw' interface provides for direct transmission between the disk and the user's read or write buffer. A single read or write call
results in exactly one I/O operation and therefore raw I/O is considerably more efficient when many words are transmitted. The names of
the raw files conventionally begin with an extra `r.' In raw I/O the buffer must begin on a word boundary, and raw I/O to an interleaved
device is likely to have disappointing results.
FILES
/dev/rp?, /dev/rrp?
SEE ALSO
rp(4)
BUGS
In raw I/O read and write(2) truncate file offsets to 512-byte block boundaries, and write scribbles on the tail of incomplete blocks.
Thus, in programs that are likely to access raw devices, read, write and lseek(2) should always deal in 512-byte multiples.
Raw device drivers don't work on interleaved devices.
HP(4)