Sponsored Content
Operating Systems SCO SCO Open Server 6 - System Halt Post 302436535 by virgani on Monday 12th of July 2010 09:52:23 AM
Old 07-12-2010
Hi Jgt,

Thanks for the reply.
1. Re-installing the system: Honestly, hope it'll be the last option
2. Install a new server: hmmm, I just hope I can figure out the problem with install a new server and then mount the original disk and hopefully fix the problem with original disk
3. Complete system backup: *sigh* I worried not, the system is manage by other person

Errr how about recovery diskette ? do you think it's possible to boot the system with recovery diskette and then try to fix the problem ?

For now, I'm looking for any solution so I can enter the system as a root.

Warmest Regards,
Virgani Dhirgacahya

---------- Post updated at 08:52 AM ---------- Previous update was at 08:36 AM ----------

All,

After dig and dig and dig, will try this:
Backup and Restore

Will inform you later with the result.

Warmest Regards,
Virgani Dhirgacahya
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

sco open server 5.0.6

I'm new to the whole Unix thing and have inherited a network running Macs, Windows 2000 and Unix. The Unix side is very suspect at this point and I want to change out the server. I'd love to use one of the new Apple servers but can't find any info on what "flavors" of Unix it will run. Specificly... (3 Replies)
Discussion started by: matthewd
3 Replies

2. UNIX for Advanced & Expert Users

SCO Open Server 5.05 Installaltuion

I'm in the process of installing SCO Open Server 5.05 on the following platform: Hardware: IBM 300PL 64 MB RAM Yamaha 16/4/16 CDRW (Internal defined on SCSI ID 3 LUN 0) I'm able to boot from the CD and advance to the Installation screen but when it asks for where the media source will... (3 Replies)
Discussion started by: budrito
3 Replies

3. SCO

SCO Open Server.

Dear All, I am considering installing SCO Open Server as an alternative to MS Exchange. Has anybody had any real world experience of using Open Office? Thanks, TC. (1 Reply)
Discussion started by: TCuk
1 Replies

4. SCO

Sco Open Server 5.05

How can I to know procesor type. (1 Reply)
Discussion started by: Batya
1 Replies

5. SCO

How to activate/use networkcards SCO Open Server

Hi, in our business we have a formerly (few years ago) installed computer with an openserver SCO 5.05 there are 3 network cards in it. one on board and two 3Com-cards Looking with ifconfig (or scoadmin) they seemed to be installed correctly. IP-Adress, netmask broadcas looks OK. But no... (3 Replies)
Discussion started by: klex
3 Replies

6. SCO

Purchase of SCO Open Server 6.0

I have to purchase SCO Open Server 6.0, so I want to know from where I can get SCO Open Server 6.0 and what is the min. cost in which I can avail this. Thanks and Regards Himanshu Software Engineer R&D Department (4 Replies)
Discussion started by: ghimanshu
4 Replies

7. Programming

GCC Compiler for SCO Open Server 5.0.7

If only SCO UNIX was as easy as Debian :mad: I intend to compile some c scripts but realized that I hadn't installed GCC on my SCO UNIX, after trying to install the package from a CD (Development Kit) and failing (Something to do with the License) ... I decided to download a Media image from... (2 Replies)
Discussion started by: itmon
2 Replies

8. SCO

SCO Open Server

Hi, Completely new to UNIX - so be gentle Cut a long story short, we have a micros 8700 system (eclipse) that needs the Micros 8700 software installed. The system needs UNIX and I have downloaded and successfully installed SCO open Server 6 and can log into root e.t.c. Now I have... (13 Replies)
Discussion started by: kennyruss
13 Replies

9. UNIX for Advanced & Expert Users

SCO Open Server 6 - System Halt

========================================================= Errrr previously post: https://www.unix.com/sco/140055-sco-open-server-6-system-halt.html Then I think it's better to post here. If I wrong, please ignore. ========================================================= Dear All, Newbie... (1 Reply)
Discussion started by: virgani
1 Replies

10. SCO

Foxbase 2.1.2d in Sco Unix Open Server 5.0.7

Hi my name is Danilo. I'm trying to install Sco foxbase + 2.1.2d. When i tried to install it with "custom" command, i receive the error: "sed: cannot open: ./tmp/perms/prep/*/prep.message: No such file or directory (error 2) The Operative System is Sco Open Server 5.0.7v (the virtualized version... (1 Reply)
Discussion started by: danilosevilla
1 Replies
mkfs_pcfs(1M)															     mkfs_pcfs(1M)

NAME
mkfs_pcfs - construct a FAT file system SYNOPSIS
mkfs -F pcfs [generic_options] [-o FSType_specific_options] raw_device_file The pcfs-specific module of mkfs constructs a File Allocation Table (FAT) on removable media (diskette, JAZ disk, ZIP disk, PCMCIA card), a hard disk, or a file (see ). FATs are the standard MS-DOS and Windows file system format. Note that you can use fdformat(1) to construct a FAT file system only on a diskette or PCMCIA card. mkfs for pcfs determines an appropriate FAT size for the medium, then it installs an initial boot sector and an empty FAT. A sector size of 512 bytes is used. mkfs for pcfs can also install the initial file in the file system (see the pcfs-specific -o i option). This first file can optionally be marked as read-only, system, and/or hidden. If you want to construct a FAT with mkfs for pcfs on a medium that is not formatted, you must first perform a low-level format on the medium with fdformat(1) or format(1M). Non-diskette media must also be partitioned with the fdisk(1M) utility. Note that all existing data on the diskette or disk partition, if any, is destroyed when a new FAT is constructed. generic_options are supported by the generic mkfs command. See mkfs(1M) for a description of these options. raw_device_file indicates the device on which to write unless the -o N option has been specified, or if the -V or -m generic options are passed from the generic mkfs module. See mkfs(1M) for the list of supported generic options. The following options are supported: -o FSType_specific_options Specify pcfs file system-specific options in a comma-separated list with no intervening spaces. If invalid options are specified, a warning message is printed and the invalid options are ignored. b=label Label the media with volume label. The volume label is restricted to 11 uppercase characters. B=filename Install filename as the boot loader in the file system's boot sector. If you don't specify a boot loader, an MS-DOS boot loader is installed. The MS-DOS boot loader requires specific MS-DOS system files to make the diskette bootable. See NOTES for more information. fat=n The size of a FAT entry. Currently, 12, 16, and 32 are valid values. The default is 12 for diskettes, 16 for larger media. h Mark the first file installed as a hidden file. The -i option must also be specified. hidden=n Set the number of hidden sectors to n. This is the number of sectors on the physical disk preceding the start of the volume (which is the boot sector itself). This defaults to 0 for diskettes or a computed valued (based on the fdisk ta- ble) for disks. This option may be used only in conjunction with the nofdisk option. i=filename Install filename as the initial file in the new file system. The initial file's contents are guaranteed to occupy con- secutive clusters at the start of the files area. When creating bootable media, a boot program should be specified as the initial file. nofdisk Do not attempt to find an fdisk table on the medium. Instead rely on the size option for determining the partition size. By default, the created FAT is 16 bits and begins at the first sector of the device. This origination sector can be modified with the hidden option (-h). nsect=n The number of sectors per track on the disk. If not specified, the value is determined by using a dkio(7I) ioctl to get the disk geometry, or (for diskette) from the results of an FDIOGCHAR ioctl. ntrack=n The number of tracks per cylinder on the disk. If not specified, the value is determined by using a dkio(7I) ioctl to get the disk geometry, or (for diskette) from the results of an FDIOGCHAR ioctl. N No execution mode. Print normal output, but do not actually write the file system to the medium. This is most useful when used in conjunction with the verbose option. r Mark the first file installed as read-only. The -i option must also be specified. reserve=n Set the number of reserved sectors to n. This is the number of sectors in the volume, preceding the start of the first FAT, including the boot sector. The value should always be at least 1, and the default value is exactly 1. s Mark the first file installed as a system file. The -i option must also be specified. size=n The number of sectors in the file system. If not specified, the value is determined from the size of the partition given in the fdisk table or (for diskette) by way of computation using the FDIOGCHAR ioctl. spc=n The size of the allocation unit for space within the file system, expressed as a number of sectors. The default value depends on the FAT entry size and the size of the file system. v Verbose output. Describe, in detail, operations being performed. FILES
raw_device_file The device on which to build the FAT. The device name for a diskette must be specified as /dev/rdiskette0 for the first diskette drive, or /dev/rdiskette1 for a second diskette drive. For non-diskette media, a disk device name must be qualified with a suffix to indicate the proper partition. For example, in the name /dev/rdsk/c0t0d0p0:c, the :c suffix indicates that the first partition on the disk should receive the new FAT. For a file, raw_device_file is the block device name returned by lofiadm(1M). EXAMPLES
The media in these examples must be formatted before running mkfs for pcfs. See for more details. Example 1: Creating a FAT File System on a Diskette The following command creates a FAT file system on a diskette: mkfs -F pcfs /dev/rdiskette Example 2: Creating a FAT File System on a Disk The following command creates a FAT file system on the second fdisk partition of a disk attached to an based system: mkfs -F pcfs /dev/rdsk/c0d0p0:d Example 3: Creating a FAT File System on a ZIP Disk The following command creates a FAT file system on a ZIP disk located on a SPARC based system: mkfs -F pcfs /dev/rdsk/c0t4d0s2:c Example 4: Creating a FAT File System on a JAZ Disk The following command creates a FAT file system on a JAZ disk located on a SPARC based system and overrides the sectors/track and tracks/cylinder values obtained from the device's controller: mkfs -F pcfs -o nsect=32,ntrack=64 /dev/rdsk/c0t3d0s2:c See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWesu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ fdformat(1), fdisk(1M), format(1M), lofiadm(1M), mkfs(1M), attributes(5), fd(7D), dkio(7I), fdio(7I) NOTES
The default MS-DOS boot loader, which is installed by default if -o B is not specified, requires specific MS-DOS system files to make the diskette bootable. These MS-DOS files are not installed when you format a diskette with mkfs for pcfs, which makes a diskette formatted this way not bootable. Trying to boot from it on an based system will result in the following message: Non-System disk or disk error Replace and strike any key when ready You must format a diskette with the DOS format command to install the specific MS-DOS system files required by the default boot loader. You can use lofiadm to create a file that appears to a mkfs command (for example, mkfs_pcfs or mkfs_ufs) as a raw device. You can then use a mkfs command to create a file system on that device. See lofiadm(1M) for examples of creating a UFS and a PC (FAT) file system on a device created by lofiadm. 1 Dec 2003 mkfs_pcfs(1M)
All times are GMT -4. The time now is 06:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy