Sponsored Content
Operating Systems SCO Expanding the root area on SCO 5.07? Post 302245701 by jpradley on Friday 10th of October 2008 06:00:00 PM
Old 10-10-2008
get BackupEDGE from microlite.com, save your system,. then use RevcioverEDGE to change the disk arrangment before restoring.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Fortgot root password SCO 5.0.

hello guys The company i work for just got a new client, there old datebase is in Unix SCO openserver 5.0.5. The manager of this new client can login but not as a root , they forgot there own root password. There old IT company never gave it to them and they have no way of getting a hold of them ... (2 Replies)
Discussion started by: josramon
2 Replies

2. SCO

Maximum size of root filesystem in SCO 5.0.7

Does anyone know the maximum size of the root filesystem in SCO 5.0.7.? It used to be 1GB max. SCO 5.0.7 with Development System does not fit in 1GB. Is there a limit or has it been removed and the documenation just was not updated? TIA, Dan (2 Replies)
Discussion started by: njsco
2 Replies

3. SCO

sco openserver 5.0.0 boot / root disk

Hi, I have an openserver 5.0.0 machine in the office. The sysad of that machine left years ago without leaving the password to anyone. I was wondering if someone has a copy of the boot / root diskettes (rescue) for this version? Or perhaps if anyone knows a download link / location in the... (0 Replies)
Discussion started by: marcpascual
0 Replies

4. SCO

Root Folder Space Maintenance (SCO)

We have SCO Unix (realease 5.0.5b), Please advise which files can be safely deleted on the system root folder / to create space? These are mainly spool/message/history etc log files. Where they located and can they be deleted using rm? The server has been operational for the past 4 years. ... (17 Replies)
Discussion started by: othman
17 Replies

5. SCO

Overwritten /dev/root -recovery of SCO OpenServer 5.0.4

Due to my own stupidity I managed to overwrite my /dev/root device using dd (don't ask). Current state is - Have current backup created using cpio (command used was 'find . -mount -depth -print|cpio -ocB > $TAPE') - Once I realised what was happening powered off the server but this was too... (2 Replies)
Discussion started by: ok2
2 Replies

6. SCO

SCO 5.0.7 no root disk controller found error during install

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

7. SCO

root out of space in sco 5

DEAR Team, I need some help in sco open server 5 while booting server beloow message giving server HTFS no space dev HD 1/42 Thanks Skb (4 Replies)
Discussion started by: sudhir69
4 Replies

8. SCO

Reset root OR crack old sco 3.2 machine

I have an old compaq running sco 3.2. the old IT guy died and we need to reset the password OR crack into the machine. I have tried mscreen and at exploits but can't seem to get them to work. I have access with other user accounts. This is a machine we own. (4 Replies)
Discussion started by: herot
4 Replies

9. SCO

SCO Openserver 5 root password and disk full

Hi, We have an old SCO Openserver 5.0.7 server that I have inherited that currently has two issues that we are trying to resolve. 1. We do not know the root password. I have contacted the old admin, looked for rescue disk and documentation but there appears to be nothing. I have tried... (1 Reply)
Discussion started by: acerimmer10
1 Replies

10. SCO

SCO unresponsive after root disk

I am working on a system that uses SCO Unix 5. I started later in this troubleshooting process so I have had to play catch up on some of the earlier mistakes that were made. The HD was formatted using the SCSI controller cards bios. I have 2 recovery floppies the boot and the root. After... (19 Replies)
Discussion started by: graysona
19 Replies
volsave(8)						      System Manager's Manual							volsave(8)

NAME
volsave - Saves a Logical Storage Manager (LSM) configuration SYNOPSIS
/usr/sbin/volsave [-d dir] OPTIONS
Directs the backup information to the directory specified by dir. This directory must not already exist. DESCRIPTION
You can save the LSM configuration records for a disk group by saving the output of the volprint(8) utility in a description file that the volmake(8) utility can use. The volsave command provides an easy way to save this configuration information for all disk groups. In addi- tion, volsave saves a list of the disks that are under LSM control and their attributes. The LSM configuration can be restored using the volrestore command. The volsave command creates an LSM description set that consists of a header file and other files containing information about the LSM con- figuration (allvol.DF, voldisk.list, and volboot). Refer to the FILES section for details on the contents of these files. By default, the description set is saved to a timestamped directory in /usr/var/lsm/db (for example, /usr/var/lsm/db/lsm.19970727131520.skylark). The -d option can be used with volsave to specify a particular directory for the saved configuration. In this case, the -d option must also be used with volrestore when restoring the configuration. ERRORS
You may receive the following error message when using the -d dir option with the volsave command: Directory dir already exists This message indicates that the directory you specified is already in use. The LSM configuration can only be saved to a directory that does not yet exist. You can specify a new directory name, or enter the volsave command without the -d option and let volsave create a new, timestamped directory in /usr/var/lsm/db. FILES
Default directory containing timestamped subdirectories with LSM description sets. A volmake description file for all volumes, plexes, and subdisks in a disk group. The volsave command creates a separate subdirectory and description file for each disk group on the system. A description of the disks. This file is the output of the voldisk list command. The contents of the /etc/vol/volboot file. A header file for the description set, containing a checksum, a magic number, the date of the file's creation, and the version of the volsave command. SEE ALSO
volmake(4), volrestore(8), volprint(8), volmake(8) Logical Storage Manager volsave(8)
All times are GMT -4. The time now is 12:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy