Sponsored Content
Operating Systems SCO Need Help With System Recovery After HD Errors Post 302992700 by spock9458 on Tuesday 28th of February 2017 06:19:57 PM
Old 02-28-2017
I did a full backup of the system after my reinstall, before doing the Restore from my tape. I had to clean the heads of my tape drive, luckily I still had a cleaning tape and it worked. I restored everything except /etc/conf and the job completed "with exceptions" - but I don't know what they were or if important.

The one problem is that /u is a File System, I know this for a fact, but I don't remember what type of File System. After the restore and reboot, it looks like it tried and failed to mount the /u filesystem - it just said "failed to mount". I know this is where most of the inner workings of my legacy application live, so can you tell me what steps to take in order to try and remount this /u file system?

Thanks - you have been VERY helpful and I appreciate it.

---------- Post updated at 04:19 PM ---------- Previous update was at 02:11 PM ----------

Been reading up a little, it looks like I need to run divvy to create the u division on the disk. Old system had root from 539648 - 10000025, and u from 10000026 - 38973679 (40 GB hard drive)

Current system shows root from 539648 -134070446 (140 GB hard drive) I think divvy will let me create the u division and I can probably figure a size. If this is the correct action, should I first delete everything I "restored" to the /u directory? Then would I create and mount the file system, and do a new restore of the /u on the backup tape?

Let me know if I am on the right track, or what else to do. Thanks again.
 

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
iv_thread(3)						    ivykis programmer's manual						      iv_thread(3)

NAME
iv_thread_create, iv_thread_set_debug_state - ivykis thread convenience functions SYNOPSIS
#include <iv_thread.h> int iv_thread_create(char *name, void (*start_routine)(void *), void *arg); void iv_thread_set_debug_state(int state); DESCRIPTION
iv_thread_create is a wrapper around pthread_create(3) which will maintain an ivykis main loop reference in the calling thread (which must be an ivykis(3) thread, i.e. have had iv_init(3) called in it) for as long as the created thread is alive. Maintaining a reference on the calling thread's ivykis event loop makes sure that the calling thread will not return from its ivykis main loop before the created thread exits, as that could cause cleanup still happening in the created thread to be interrupted when the calling thread subsequently calls exit(3). The created thread need not be an ivykis thread. Enabling debugging by calling iv_thread_set_debug with a nonzero argument will print a debug message to standard error whenever a thread is created via iv_thread_create, whenever a thread so created terminates normally by returning from its start_routine, self-terminates by calling pthread_exit(3), or is successfully canceled by pthread_cancel(3), and whenever destruction of such a thread is signaled back to the calling thread. For inter-thread signaling, iv_thread uses iv_event(3). SEE ALSO
ivykis(3), iv_event(3), exit(3), pthread_cancel(3), pthread_create(3), pthread_exit(3) ivykis 2010-09-13 iv_thread(3)
All times are GMT -4. The time now is 09:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy