08-19-2002
Fatal error in disk
I have a doubt with an error message, and i want to be sure if this is a normal situation or not.
Situation: I was formating and installing a SCSI 36Gb HD with UNIX SCO 5.05, the problem happens when is making the division and filesystem on disk 1, and the message error is "Exit value 139 Status Value -29952"
"Fatal error in diskinfo.c line 3525"
"Function DIAdJust Division: Cannot adjust division to fit in the usable space: Disk0"
[IGNORE] [RETURN TO IQM]
My questions are: What is the recomended size of the divisions that i have to make?, The problem is the size of the HardDisk? or Maybe this HardDisk is not supported by UNIX SCO 5.05
example: this are the divisions that i made
DISK 1
boot -- 50 mb
swap -- 1Gb
root -- 1Gb
/u -- 22Gb
/u2 -- 10Gb
DISK 2
/a -- 20Gb
/a2 -- 14Gb
The error mesage appears in both disks
Any comment about this problem itīs gonna be very useful for us,
thanks.
10 More Discussions You Might Find Interesting
1. Programming
dear all ,
iam trying to compile a progam using gcc compiler on a sun 280 R machine running solaris 9 .
iam getting an error in the last step when the compiler tries to link the objects , although the compiler executes some applicarions that contains no objects smoothly,
the error that... (1 Reply)
Discussion started by: ppass
1 Replies
2. UNIX for Advanced & Expert Users
Hi ,
attempting to purify code on the link line generates a fatal error
like this
#ERROR: (fatal) Cannot find libtest.so in the search path .
command line:
-------------
purify -show-directory=yes -always-use-cache-dir -cache-dir=/ppic/users/avadhani/sgi/pure /usr/bin/CC -n32 -mips3... (2 Replies)
Discussion started by: avadhani
2 Replies
3. Shell Programming and Scripting
Hi ,
I a stuck with this problem. I am trying to execute this script1 on SERVER 1 from SERVER 2 using script2
script1 on SERVER 1
#!/usr/bin/ksh
/opt/perf/bin/glance -f -adviser_only -iterations 2 -maxpages 2 > /home/user/scripts/glance.op
cpuval1=`grep ^CPU... (4 Replies)
Discussion started by: newbie07
4 Replies
4. Programming
Hi,
I just pulled out my code from source control, then I compiled, the compilation is successful at that time.
Then I modified one of the source file, Then I compiled, I got the following error
ld: fatal: Symbol referencing errors. No output written to ../../CM/bin/cato
Before... (1 Reply)
Discussion started by: sarwan
1 Replies
5. Programming
i am trying to compile my program using a makefile and i keep getting this message:
Undefined first referenced
symbol in file
main
/usr/local/lib/gcc-lib/sparc-sun-solaris2.9/3.3/crt1.o
ld: fatal: Symbol referencing errors. No output written to prog5
collect2: ld returned 1 exit status
***... (2 Replies)
Discussion started by: betterdayz
2 Replies
6. AIX
Background
-------------
Os: IBM AIXL 5.1 (Unix)
Problem
-------------
I run the dbx in csh as follows
% dbx mainprog
-- The following is the systemm replay
Type 'help' for help.
reading symbolic information ...warning: stab entry unrecognized: name ,type 45, class a8, value 0'
... (1 Reply)
Discussion started by: skfn1203
1 Replies
7. UNIX for Dummies Questions & Answers
Hi all
I'm trying to install sudo. When I first ran the sudo configure script it errored saying that I didn't have a C compiler. I have since installed the GCC 3.4.6 package for sol8 from sun freeware.
Doing that resolved the no C complier found error. I was then getting an error saying... (1 Reply)
Discussion started by: Donkey25
1 Replies
8. Linux
Hi guys,
i am using the below command to send mail
mail -s "HI" abcd@how.com < temp_mail.txt
I am getting the below error
send-mail: fatal: bad string length 0 < 1: myorigin =
My os version is as
Linux
Help me with ur suggestion guys thank u. (3 Replies)
Discussion started by: mohanalakshmi
3 Replies
9. HP-UX
I have a B.11.31 U ia64 system where I swremove the disk driver "SerialSCSI-00 B.11.31.1303 PCI-X/PCI-E SerialSCSI" (by mistake). afterwards the system won;t boot because of the missing disk drivers. I'm trying to recover my kernel by using the image HP-ux_11_31_disc_1.iso
Run an Expert... (1 Reply)
Discussion started by: black_fender
1 Replies
10. What is on Your Mind?
Today, I noticed some errors in our SSL cert renewal log files, mostly related to domains where the IP address had changed. Concerned about this, rebuilt out SSL cert, which normally goes well without a hiccup.
However, for today, for some reason which I cannot explain, there was a PHP error... (0 Replies)
Discussion started by: Neo
0 Replies
LEARN ABOUT HPUX
bootconf
bootconf(4) Kernel Interfaces Manual bootconf(4)
NAME
bootconf - boot device configuration table
DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control
scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware
and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate
boot devices should be automatically updated, the administrator must edit the file manually.
There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown:
disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following:
Indicates that the root disk is in LVM or VERITAS Volume Manager
(VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file.
Indicates that the root disk is in the
"whole disk" format with no partitions, but boot and swap space are reserved outside the file system.
device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root
disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file
that references the entire disk.
Blank lines are permitted. Any line beginning with a is considered to be a comment.
DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self-
explanatory; a few warrant additional explanation:
If there are no other messages about
the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem
is.
The specified device file does not point to a disk where there is a
lif which contains the file
Some character other than
or is in the first field of a line.
As of release 10.0, the boot areas in
must all be on the same type of disk layout.
There are characters after the
device file specification.
EXAMPLES
The boot area is on an LVM root disk:
l /dev/disk/disk7_p2
The boot area is on a whole disk layout:
w /dev/disk/disk7
WARNINGS
All of the boot devices in the file must have the same disk layout.
AUTHOR
was developed by the Hewlett-Packard Company.
FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7).
documentation.
bootconf(4)