Sponsored Content
Operating Systems SCO PANIC 0x0000020 got a solution? Post 302185333 by jgt on Monday 14th of April 2008 06:46:43 PM
Old 04-14-2008
/etc is in the root file system, and on the first disk drive.
Does the machine boot into single user mode?
Also you should create the swap space greater than the amount of memory, otherwise a dump will use all the swap space, and (depending on the OS version) then continue writing onto the root filesystem.
What procedure do you use to backup your system?
Does the disk drive make any noise that is different from its usual operation?
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Panic

Hi All, When I came officce this morning I saw this error messages on the screen ----- PANIC:srmountfun - Error 6 mounting rootdev hd (1/42) Cannot dump 32639 pages to dumpdev hd (1/41) : space for only 0 pages Dump not completed -------- and machine was reboot mode. Why this problem... (3 Replies)
Discussion started by: alisev
3 Replies

2. SCO

Panic :

Hi Friends , i am getting the following error when iam booting a sco unix system. ------------------ H init PANIC : srmountfun --Error 22 mounting rootdev hd(1/42) cannot dump 40863 pages to dempdev hd(1/41) : space for only 0 pages. Dump not completed. Safe to power off.... (1 Reply)
Discussion started by: sveera
1 Replies

3. Linux

kernel panic

I have compiled kernel version 2.6.12 in my linux box mandrake 10.1. I have followed www.digitalhermit.com/linux/Kernel-Build-HOWTO.html instructions. I have copied .config file from /usr/src/linux and lightly modified it (only the processor type) by xconfig. I have compiled the source and modules.... (3 Replies)
Discussion started by: Davide71
3 Replies

4. SCO

ML570 Panic

Brief scenario of problem working on contract for customer with supposedly identical setups in US and Europe 3 HP ML570 servers running SCO 5.07 networked together servers 1 & 2 run the user applications , server 3 acts as backup / tape transport system between tape libraries US side all... (0 Replies)
Discussion started by: ccarcher
0 Replies

5. Solaris

Savemail panic - Need help

Hi All, I've been troubleshooting this sendmail panic I'm getting on my dmesg. The errors are: Feb 16 09:44:17 fakeserver_name sendmail: l1G1hGuD000884: Losing ./qfl1G1hGuD000884: savemail panic Feb 16 09:44:17 fakeserver_name sendmail: l1G1hGuD000884: SYSERR(root): savemail: cannot save... (2 Replies)
Discussion started by: grumash
2 Replies

6. Solaris

What is system panic?

Hello experts.. What is system panic? If a system is in that state.. what will happen? Why is it goes to panic condition? Just give me information about Panic condition.. How can i resolve this issue..? If you know any links(URL) or Books...? replay me back.... Thanks in... (5 Replies)
Discussion started by: younus_syed
5 Replies
RP(4)							     Kernel Interfaces Manual							     RP(4)

NAME
rp - RP-11/RP03 moving-head disk DESCRIPTION
The files rp0 ... rp7 refer to sections of RP disk drive 0. The files rp8 ... rp15 refer to drive 1 etc. This allows a large disk to be broken up into more manageable pieces. The origin and size of the pseudo-disks on each drive are as follows: disk start length 0 0 81000 1 0 5000 2 5000 2000 3 7000 74000 4-7 unassigned Thus rp0 covers the whole drive, while rp1, rp2, rp3 can serve usefully as a root, swap, and mounted user file system respectively. The rp files access the disk via the system's normal buffering mechanism and may be read and written without regard to physical disk records. There is also a `raw' interface which 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 RP files begin with rrp and end with a number which selects the same disk section as the corresponding rp file. In raw I/O the buffer must begin on a word boundary. FILES
/dev/rp?, /dev/rrp? SEE ALSO
hp(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. RP(4)
All times are GMT -4. The time now is 05:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy