12-29-2007
Incorrect Disk Partition - New Install SCO 6.0
New IBM x3400 machine with a raid 5 configuration. Go through the early setup routine to the point where I answer the questions for time zone, machine name. Enter continue and get a message stating :
"Incorrect disk partitioning cannot continue" This is a sco message, refers to the installation guide. There is no information there. I also checked SCO online and have found no reference to this message. Has anyone encountered this problem and have been able to resolve it.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hardware:
IBM 300PL
32MB RAM
60Gig HDD
During the phase in SCO installation where I get to partition my hard disk, SCO only seems to see 8Gig out of the 60 that I have.
Does anyone out there know of a utility or what I need to do to make the the whole 60Gig available.
Thanks (3 Replies)
Discussion started by: budrito
3 Replies
2. UNIX for Dummies Questions & Answers
this question has probly been answered but i could not find it (sad).... anyhow, my question is, that i would like to know how (step by step) i can install mandrake 9.1 on my computer which currently runs win98... the catch is that i need to keep windows 98 on my computer, and the compter must boot... (5 Replies)
Discussion started by: punk000
5 Replies
3. UNIX for Dummies Questions & Answers
Hi All,
While my LINUX SERVER installed we didnt' used all the space for partitions. with what tool I can create a new partition or mount point to use the free space.
I tried the command fdisk and diskdruid. They are not working.
Thanks in advance
With Best regards,
Varma. (2 Replies)
Discussion started by: jarkvarma
2 Replies
4. Solaris
Have a solaris x86 running solaris 9.
Root disk - logical - mirrored.
I added 2 more disks today - and I have mirrored them using array configuration utility.
I did a reconfiguration boot - and now I can see the logical disk using format:
I then partitioned this the way I wanted (I hope)... (4 Replies)
Discussion started by: frustrated1
4 Replies
5. SCO
Hi!
Sorry, but I am'not spesialist in SCO OpenServer. I need to add hard disk from SCO Open Server ( "a") in my SCO OpenServer 5.6. I need data from "a". When I added, I see only swap disk, and didn't see root file system. I need to add IDE and SCSI
Please, help me. How right to add disk?... (0 Replies)
Discussion started by: fedir
0 Replies
6. Solaris
I have 3 disks to partition in following file system.
c1t1d0 = 72gb
/prod1
/prod2
/prod3
/prod4
/prod5
I am first time using "format" command to do this. How can i name with specified size.
-Adeel (1 Reply)
Discussion started by: deal732
1 Replies
7. Filesystems, Disks and Memory
Hi,
Can I partition disk in use or would I damage the file store on it?
Regards
Mehrdad (1 Reply)
Discussion started by: mehrdad68
1 Replies
8. SCO
I'm "attempting" to install SCO 5.0.7 on an HP ML370 G4 server and am ready to bash the keyboard with head now. I keep getting the error message "WARNING hd: no root disk controller found" when running the bootable install cd.
I have a raid 5 array with an online spare created using 4 36.3 GB... (2 Replies)
Discussion started by: FrictionBurn
2 Replies
9. Solaris
Hi,
I have a very frustrating issue! I hope you guys can assist
When a disk is presented out the iSCSI target display a lower disk capacity
SOLARIS VERSION is SOLARIS 10 05/09 Kernel Patch 139555-31
ISCSI Patch 119090-31, 141878-11
Unix Commands To discover Target
bash-3.00# i... (0 Replies)
Discussion started by: capitalexall
0 Replies
10. Shell Programming and Scripting
Hi All,
OS: Linux 86x64 bits Red Hat Linux
I get the email alert for the following when Alert condition is set for 30:
/dev/sda1 99M 21M 74M 22% /boot
-> Below 30%(Should not get the email alert)
Expected output as per E-Mail alert:
/dev/sda3 20G ... (2 Replies)
Discussion started by: a1_win
2 Replies
LEARN ABOUT PHP
systemd-machine-id-commit.service
SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8) systemd-machine-id-commit.service SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)
NAME
systemd-machine-id-commit.service - Commit a transient machine ID to disk
SYNOPSIS
systemd-machine-id-commit.service
DESCRIPTION
systemd-machine-id-commit.service is an early boot service responsible for committing transient /etc/machine-id files to a writable disk
file system. See machine-id(5) for more information about machine IDs.
This service is started after local-fs.target in case /etc/machine-id is a mount point of its own (usually from a memory file system such
as "tmpfs") and /etc is writable. The service will invoke systemd-machine-id-setup --commit, which writes the current transient machine ID
to disk and unmount the /etc/machine-id file in a race-free manner to ensure that file is always valid and accessible for other processes.
See systemd-machine-id-setup(1) for details.
The main use case of this service are systems where /etc/machine-id is read-only and initially not initialized. In this case, the system
manager will generate a transient machine ID file on a memory file system, and mount it over /etc/machine-id, during the early boot phase.
This service is then invoked in a later boot phase, as soon as /etc has been remounted writable and the ID may thus be committed to disk to
make it permanent.
SEE ALSO
systemd(1), systemd-machine-id-setup(1), machine-id(5), systemd-firstboot(1)
systemd 237 SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)