Sponsored Content
Operating Systems SCO Need Help With System Recovery After HD Errors Post 302992708 by jgt on Tuesday 28th of February 2017 08:02:48 PM
Old 02-28-2017
The boot file system is EAFS, the root and any other (/u) file systems default to HTFS.
You cannot re-size an HTFS partition without losing the data that is on it. So you will not be able to add the /u file system without doing a full backup and standalone restore.
From an operational point of view, it will make no difference if /u is a file system, or simply another directory in the root file system.
If you must, do a full backup, boot from the Edge recovery media, re-size the partitions, and do full restore.

---------- Post updated at 08:02 PM ---------- Previous update was at 07:20 PM ----------

I now what happened. When you restored the old data, you restored /etc/default/filesys, which has the file system configuration. Unfortunately the one that has been restored contains info on /u but that file system no longer exists.
Just use a text editor and remove the references to /u.
 

8 More Discussions You Might Find Interesting

1. HP-UX

Automatic system recovery?

Hi all! I've a strange problem. I would use the GNU Make tool on HPUX 11.11. To archive this, i have compiled the sourcecode and renamed HP make in /usr/bin from make to make_old. Now i have make a softlink from /usr/local/bin/make (GNU version) to /usr/bin/make. All things here are ok, but... (1 Reply)
Discussion started by: coredump2003
1 Replies

2. UNIX for Advanced & Expert Users

Adapter Errors and Link Errors

$ errpt | more IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION 3074FEB7 0802050205 T H fscsi1 ADAPTER ERROR B8113DD1 0802050205 T H fcs1 LINK ERROR B8113DD1 0802050205 T H fcs1 LINK ERROR 3074FEB7 0802050205 T H fscsi0 ADAPTER ERROR B8113DD1 ... (0 Replies)
Discussion started by: mcastill66
0 Replies

3. AIX

make a recovery CD/DVD - system has no writable devices

Hi, Has anyone please got some advise as to how I can make a CD/DVD on an AIX 5.3 system so that it can be fully recoverd just by inserting the backed up system. The system that I need to recover has no writable devices, not even a tape drive (it wasn't specified by me btw). I am trying to... (0 Replies)
Discussion started by: stevek007
0 Replies

4. AIX

System recovery

Hi everyone I'm green AIX user or rather beginner (light green). Unfortunately I have to restore my system + data from scratch (things happen) and make it up and running. I've never done it before. Can someone of you provide me with link/procedure/instruction how to do it? Now I know only:... (3 Replies)
Discussion started by: fraydey
3 Replies

5. UNIX for Advanced & Expert Users

Data Recovery from file system overwritten with LVM.

Hey peeps, Here is somethin u might find interestin.... Is it possible to recover data from a partition which used to be an ext3 file sytem with some nice forgotten backups, which now is an lvm partion containg root partition of another OS. :) I couldn't create any mess better than this, can... (2 Replies)
Discussion started by: squid04
2 Replies

6. UNIX for Advanced & Expert Users

linux system recovery after overriding connect() by "ld.so.preload"

dear fellows; i have used ld.so.preload file to override connect() function, dynamic library overriding, it did worked really fine ...... but i went on to struck in a situation ... within the overrided connect() i have used printf once to see IP and Port to whom the connect request is being... (1 Reply)
Discussion started by: mzeeshan
1 Replies

7. UNIX for Advanced & Expert Users

fsck.gfs2 outputs "RG recovery impossible; I can't fix this file system"

I have a CentOS release 5.2 (Final)host running kernel 2.6.18-92.el5 with at raid 10 that had two mirrored drives fail. The drives were re-inserted and now the raid shows healthy (for now). I tried to mount but got an Input/output error. I then attempted a fsck: fsck.gfs2 -y /dev/vg_01/uss_vol... (0 Replies)
Discussion started by: king_hippo
0 Replies

8. Red Hat

Linux system hangs giving ntp errors

Hi folks, I am facing issue of my system (host1) getting hanged after throwing following ntpd messages. I am not able to ssh to the server there after. only option is to restart the host: Dec 29 02:58:51 host1 ntpd: time reset -0.207907 s Dec 29 02:58:51 host1 ntpd: synchronisation lost Dec 29... (0 Replies)
Discussion started by: SiddhV
0 Replies
RESTOREVOL(1)						       AFS Command Reference						     RESTOREVOL(1)

NAME
       restorevol - Restore a volume from vos dump to the local file system

SYNOPSIS
       restorevol [-file <dump file>] [-dir <restore dir> ]
	   [-extension <name extension>]
	   [-mountpoint <mount point root>]
	   [-umask <mode mask>] [-verbose] [-help]

DESCRIPTION
       restorevol takes an AFS volume in the format produced by vos dump and restores it to the local file system.  Normally, the contents of a
       volume are maintained by the AFS File Server in an opaque format and copying a volume's raw data does not make it easily accessible.  This
       utility will produce a directory tree that is equivalent to that seen via an AFS client, but without preserving the AFS-specific Access
       Control Lists (ACLs).  It's primary use is to recover data from a volume dump or backup and make it available via a filesystem other than
       AFS.

       The dump output will read from standard input, or from a file if -file is specified.

       The restore process is as follows:

       1.  The dump file will be restored within the current directory or that specified with -dir.

       2.  Within this directory, a subdir is created.	It's name is the RW volume name that was dumped.  An extension can be appended to this
	   directory name with -extension.

       3.  All mountpoints will appear as symbolic links to the volume name.  The path name to the volume will be either that in -mountpoint, or
	   -dir.  Symbolic links remain untouched.

       4.  You can change your umask during the restore with -umask.  Otherwise, restorevol uses your current umask.  Mode bits for directories
	   are 0777 (then AND'ed with the umask).  Mode bits for files are the owner mode bits duplicated accross group and user (then AND'ed with
	   the umask).

       5.  For restores of full dumps, if a directory says it has a file and the file is not found, then a symbolic link AFSFile-<#> will appear
	   in that restored tree.  Restores of incremental dumps remove all these files at the end (expensive because it is a tree search).

       6.  If a file or directory was found in the dump but found not to be connected to the hierarchical tree, then the file or directory will be
	   connected at the root of the tree as __ORPHANEDIR__.<#> or __ORPHANFILE__.<#>.

       7.  ACLs are not restored.

CAUTIONS
       Normally, use vos_restore(1) instead of this command.  restorevol is a tool of last resort to try to extract data from the data structures
       stored in a volume dumpfile and is not as regularly tested or used as the normal vos_restore(1) implementation.	Using restorevol bypasses
       checks done by the fileserver(8) and salvager(8).

OPTIONS
       -file <dump file>
	   Specifies the volume dump file to be read and restored to the local filesystem.  If this option is not given, the volume dump will be
	   read from standard input.

       -dir <restore dir>
	   Names the directory in which to create the restored filesystem.  The current directory is used by default.  Note that any mountpoints
	   inside the volume will point to the same directory unless the -mountpoint option is also specified.

       -extension <name extension>
	   By default, the name of the directory created matches the RW volume name of the volume in the dump file.  If this option is used, the
	   directory name will be the RW volume name name extension as the suffix.

       -mountpoint <mount point root>
	   By default, mountpoints inside the volume being restored point to the value given by -dir.  This option allows mountpoints to be
	   resolved relative to another path.  A common use for this would be to specify a path under /afs as the mount point root so that
	   mountpoints inside the restored volume would be resolved via AFS.

	   The mount point root must exist, and the process running the command have read access to that directory, or the command will fail.

EXAMPLES
       The following command restores the contents of the dumpfile in sample.dump to the directory /tmp/sample.2009-05-17, but having all
       mountpoints inside the volume point to AFS (note that this requires knowledge of where sample is mounted in AFS):

	  % restorevol -file sample.dump -dir /tmp -extension .2009-05-17 
	      -mountpoint /afs/example.org/sample
	  Restoring volume dump of 'sample' to directory '/tmp/sample.2009-05-17'

PRIVILEGE REQUIRED
       The issuer must have read access to the dump file and write access to the directory into which the dump is restored.  If the -mountpoint
       flag is given, the issuer must also have read access to that directory.

SEE ALSO
       salvager(8), voldump(8), vos_dump(1), vos_restore(1)

COPYRIGHT
       Copyright 2009 Steven Jenkins <steven@endpoint.com>

       This documentation is covered by the BSD License as written in the doc/LICENSE file. This man page was written by Steven Jenkins for
       OpenAFS.

OpenAFS 							    2012-03-26							     RESTOREVOL(1)
All times are GMT -4. The time now is 08:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy