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
disklabel(4)						     Kernel Interfaces Manual						      disklabel(4)

NAME
disklabel - Disk pack label SYNOPSIS
#include <sys/disklabel.h> DESCRIPTION
Each disk or disk pack on a system may contain a disk label which provides detailed information about the geometry of the disk and the par- titions into which the disk is divided. It should be initialized when the disk is formatted, and may be changed later with the disklabel program. This information is used by the system disk driver and by the bootstrap program to determine how to program the drive and where to find the file systems on the disk partitions. Additional information is used by the file system in order to use the disk most effi- ciently and to locate important file system information. The description of each partition contains an identifier for the partition type (standard file system, swap area, etc.). The file system updates the in-core copy of the label if it contains incomplete information about the file system. The label is located in sector number LABELSECTOR of the drive, usually sector 0 (zero) where it may be found without any information about the disk geometry. It is at an offset LABELOFFSET from the beginning of the sector, to allow room for the initial bootstrap. The disk sector containing the label is normally made read-only so that it is not accidentally overwritten by pack-to-pack copies or swap opera- tions; the DIOCWLABEL ioctl, which is done as needed by the disklabel program, allows modification of the label sector. A copy of the in-core label for a disk can be obtained with the DIOCGDINFO ioctl; this works with a file descriptor for a block or charac- ter (raw) device for any partition of the disk. The in-core copy of the label is set by the DIOCSDINFO ioctl. The offset of a partition cannot generally be changed, nor made smaller while it is open. One exception is that any change is allowed if no label was found on the disk, and the driver was able to construct only a skeletal label without partition information. Finally, the DIOCWDINFO ioctl operation sets the in-core label and then updates the on-disk label; there must be an existing label on the disk for this operation to succeed. Thus, the initial label for a disk or disk pack must be installed by writing to the raw disk. All of these operations are normally done using the disklabel program. RELATED INFORMATION
Files: disktab(4) Commands: disklabel(8) delim off disklabel(4)
All times are GMT -4. The time now is 08:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy