I use SCO OpenServer 5.07. For the first time since installation, the
drive crashed and I had to do a restore. I booted on my CTAR 2.88 MB
diskettes but the hard drive would not mount; it seems that the CTAR
file diskette is missing some 5.07 files. So then I did the following:

1. booted and rooted with my SCO boot and root diskettes (not CTAR's)
2. mount /dev/hd0root /mnt
3. mkdir /mnt/stand
4. mount /dev/boot /mnt/stand
5. cd /mnt
6. tar xvf /dev/rct0 . [the CTAR files were not compressed]
7. umount /mnt/stand
8. umount /mnt
9. reboot

BUT, ALAS, upon rebooting, everything seems OK until I get WARNING:
exit - /etc/init (PID 1) died, status 0x0000008A. Didn't we have
trouble before with /etc/init in getting the CTAR boot and root
diskettes to work?

Now, what? All of my files are back on the drive. The original
/etc/init (from the tape) is there; so how could it be faulty? I tried
using CTAR's version of /etc/init (54676 bytes vs. 28584 bytes), which
was still on the hard drive (and necessary to make the CTAR boot and
root diskettes) but to no avail. So, now what?

Transpower typed (on Tue, Apr 12, 2005 at 08:39:41AM -0700):
| I use SCO OpenServer 5.07. For the first time since installation, the
| drive crashed and I had to do a restore. I booted on my CTAR 2.88 MB
| diskettes but the hard drive would not mount; it seems that the CTAR
| file diskette is missing some 5.07 files. So then I did the following:
|
| 1. booted and rooted with my SCO boot and root diskettes (not CTAR's)
| 2. mount /dev/hd0root /mnt
| 3. mkdir /mnt/stand
| 4. mount /dev/boot /mnt/stand
| 5. cd /mnt
| 6. tar xvf /dev/rct0 . [the CTAR files were not compressed]
| 7. umount /mnt/stand
| 8. umount /mnt
| 9. reboot
|
| BUT, ALAS, upon rebooting, everything seems OK until I get WARNING:
| exit - /etc/init (PID 1) died, status 0x0000008A. Didn't we have
| trouble before with /etc/init in getting the CTAR boot and root
| diskettes to work?
|
| Now, what? All of my files are back on the drive. The original
| /etc/init (from the tape) is there; so how could it be faulty? I tried
| using CTAR's version of /etc/init (54676 bytes vs. 28584 bytes), which
| was still on the hard drive (and necessary to make the CTAR boot and
| root diskettes) but to no avail. So, now what?

Why was step 3 necessary? Why wasn't there a stand directory already on
the mounted hd0root?


--
JP

Transpower typed (on Tue, Apr 12, 2005 at 08:39:41AM -0700):
| I use SCO OpenServer 5.07. For the first time since installation, the
| drive crashed and I had to do a restore. I booted on my CTAR 2.88 MB
| diskettes but the hard drive would not mount; it seems that the CTAR
| file diskette is missing some 5.07 files. So then I did the following:
|
| 1. booted and rooted with my SCO boot and root diskettes (not CTAR's)
| 2. mount /dev/hd0root /mnt
| 3. mkdir /mnt/stand
| 4. mount /dev/boot /mnt/stand
| 5. cd /mnt
| 6. tar xvf /dev/rct0 . [the CTAR files were not compressed]
| 7. umount /mnt/stand
| 8. umount /mnt
| 9. reboot
|
| BUT, ALAS, upon rebooting, everything seems OK until I get WARNING:
| exit - /etc/init (PID 1) died, status 0x0000008A. Didn't we have
| trouble before with /etc/init in getting the CTAR boot and root
| diskettes to work?
|
| Now, what? All of my files are back on the drive. The original
| /etc/init (from the tape) is there; so how could it be faulty? I tried
| using CTAR's version of /etc/init (54676 bytes vs. 28584 bytes), which
| was still on the hard drive (and necessary to make the CTAR boot and
| root diskettes) but to no avail. So, now what?


Is this a Unitrends version? 803-454-0300
Is this a Microlite version? 724-375-6711
Is this a recent version since you mention support for 2.88 floppies?...
yet you also mention "root and boot" disks which would indicate something
raither old (possibly not supporting SCO 507). All recent versions of
crash recovery do not make you jump through all these hoops.

Best Regards,
Jeffrey Hyman
.--.
___________________________ .-. | | _____________________________________
Lone Star Software Corp. | | | | .-. Home of World Famous LONE-TAR(tm)
Cactus International, Inc. | |_| | | | Backup Software for UNIX and LINUX
Sales: 800.525.8649 _ |___ |_| | 24x7 Support Available
Support: 301.829.1622 _| ~- | ___| RESCUE-RANGER(tm) and AIR-BAG(tm)
http://www.LONE-TAR.com \, _} | | Disaster Recovery Software
-------------------------- \( -- | | --------------------------------------
| |

Jeff Hyman wrote:
> Transpower typed (on Tue, Apr 12, 2005 at 08:39:41AM -0700):
> | I use SCO OpenServer 5.07. For the first time since installation,
the
> | drive crashed and I had to do a restore. I booted on my CTAR 2.88
MB
> | diskettes but the hard drive would not mount; it seems that the
CTAR
> | file diskette is missing some 5.07 files. So then I did the
following:
> |
> | 1. booted and rooted with my SCO boot and root diskettes (not
CTAR's)
> | 2. mount /dev/hd0root /mnt
> | 3. mkdir /mnt/stand
> | 4. mount /dev/boot /mnt/stand
> | 5. cd /mnt
> | 6. tar xvf /dev/rct0 . [the CTAR files were not compressed]
> | 7. umount /mnt/stand
> | 8. umount /mnt
> | 9. reboot
> |
> | BUT, ALAS, upon rebooting, everything seems OK until I get WARNING:
> | exit - /etc/init (PID 1) died, status 0x0000008A. Didn't we have
> | trouble before with /etc/init in getting the CTAR boot and root
> | diskettes to work?
> |
> | Now, what? All of my files are back on the drive. The original
> | /etc/init (from the tape) is there; so how could it be faulty? I
tried
> | using CTAR's version of /etc/init (54676 bytes vs. 28584 bytes),
which
> | was still on the hard drive (and necessary to make the CTAR boot
and
> | root diskettes) but to no avail. So, now what?
>
>
> Is this a Unitrends version? 803-454-0300
> Is this a Microlite version? 724-375-6711
> Is this a recent version since you mention support for 2.88
floppies?...
> yet you also mention "root and boot" disks which would indicate
something
> raither old (possibly not supporting SCO 507). All recent versions
of
> crash recovery do not make you jump through all these hoops.
>
> Best Regards,
> Jeffrey Hyman
> .--.
> ___________________________ .-. | |
_____________________________________
> Lone Star Software Corp. | | | | .-. Home of World Famous
LONE-TAR(tm)
> Cactus International, Inc. | |_| | | | Backup Software for UNIX
and LINUX
> Sales: 800.525.8649 _ |___ |_| | 24x7 Support Available
> Support: 301.829.1622 _| ~- | ___| RESCUE-RANGER(tm) and
AIR-BAG(tm)
> http://www.LONE-TAR.com \, _} | | Disaster Recovery
Software
> -------------------------- \( -- | |
--------------------------------------
> | |
It's Unitrends, and yes I'm in communication with them. And no, they
never notified me of any bug fixes. They knew I was on 5.0.7 because I
needed 2.88 MB floppies to copy the kernel and I needed their /etc/init
to be able to load their file diskette.

I next tried copying the /etc/init file from the SCO file diskette
(using TA#105032). Now, upon booting the HD, I get

PANIC: exit - Cannot exec /etc/init (PID 1), status 0x00000200 Cannot
dump 524175 pages. I don't know if this is progress or not.

The SCO boot/root diskettes work fine and are 5.0.7. I can mount the
HD. So I can copy whatever files you gurus suggest from the file
diskette to the HD. There's got to be a solution to this! I can use
chroot and run an application (filePro) but the system says the
permissions are wrong, so I cannot do any real work in this state.

RWS
transpower@aol.com

----- Original Message -----
From: "Transpower" <transpower@aol.com>
Newsgroups: comp.unix.sco.misc
To: <distro@jpr.com>
Sent: Tuesday, April 12, 2005 11:39 AM
Subject: 5.07 /etc/init Problem


>I use SCO OpenServer 5.07. For the first time since installation, the
> drive crashed and I had to do a restore. I booted on my CTAR 2.88 MB
> diskettes but the hard drive would not mount; it seems that the CTAR
> file diskette is missing some 5.07 files. So then I did the following:
>
> 1. booted and rooted with my SCO boot and root diskettes (not CTAR's)
> 2. mount /dev/hd0root /mnt
> 3. mkdir /mnt/stand
> 4. mount /dev/boot /mnt/stand
> 5. cd /mnt
> 6. tar xvf /dev/rct0 . [the CTAR files were not compressed]
> 7. umount /mnt/stand
> 8. umount /mnt
> 9. reboot
>
> BUT, ALAS, upon rebooting, everything seems OK until I get WARNING:
> exit - /etc/init (PID 1) died, status 0x0000008A. Didn't we have
> trouble before with /etc/init in getting the CTAR boot and root
> diskettes to work?
>
> Now, what? All of my files are back on the drive. The original
> /etc/init (from the tape) is there; so how could it be faulty? I tried
> using CTAR's version of /etc/init (54676 bytes vs. 28584 bytes), which
> was still on the hard drive (and necessary to make the CTAR boot and
> root diskettes) but to no avail. So, now what?

I'm not sure what all happened to you, but I had a problem making A1/A2 ctar
disks on 5.0.7 on 4 boxes in a row, and the problem was I was using the
version downloaded from their website, thinking it was the latest and I
would just apply the customers licence to un-demo later.

The disks would seem to be created OK, but the A2 disk would generate a
error message but then proceed past it and say there was no problem.
Trying to actually use the disk after booting the A1 though crashed at
/etc/init .
The A1 disk gets creayed fine
The A2 disk gets created incomplete

The OS root/boot floppies could be created and they'd work just fine.

The fix was they mailed me current versions of the airbag installer
pre-branded with the customers licence numbers. The long term fix was to
avoid the web site like the plague and wait for the boxed kit in the mail.
Inconvenient since 1985 to operate that way. We've pretty much switched to
BackupEdge (as a policy not just our own box). The disparity in features,
upkeep, support, flexability, accessibility etc... is just too great.

Maybe they (or I, in a pinch) can mail you a generic A2 that won't have your
fs details or scsi driver, but maybe there is a way to do it all generically
with a btld disk and your own knowledge of the fs layout or maybe you don't
need to create new fs's but just restore onto them?

I was not happy with their support when this was happing. I tried to give
the official channels a fair shot and spent several days trading utterly
idiotic emails with someone who kept asking me questions I'd answered
already. Until I got fed up and couldn't afford to hold up shipping 4
customers boxes any longer and squeaky-wheeled myself up to Steve himself,
who guessed what was wrong and knew the fix right away.

I can't say how BE's support compares. I've talked to Tom a few times of
course, including for support, but it was so rare and so little that it's
not enough to rate them by. I can say I just plain haven't needed hardly any
support even though BE is a more complex and more featureful product.

good luck

Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani

Brian K. White wrote:
> ----- Original Message -----
> From: "Transpower" <transpower@aol.com>
> Newsgroups: comp.unix.sco.misc
> To: <distro@jpr.com>
> Sent: Tuesday, April 12, 2005 11:39 AM
> Subject: 5.07 /etc/init Problem
>
>
> >I use SCO OpenServer 5.07. For the first time since installation,
the
> > drive crashed and I had to do a restore. I booted on my CTAR 2.88
MB
> > diskettes but the hard drive would not mount; it seems that the
CTAR
> > file diskette is missing some 5.07 files. So then I did the
following:
> >
> > 1. booted and rooted with my SCO boot and root diskettes (not
CTAR's)
> > 2. mount /dev/hd0root /mnt
> > 3. mkdir /mnt/stand
> > 4. mount /dev/boot /mnt/stand
> > 5. cd /mnt
> > 6. tar xvf /dev/rct0 . [the CTAR files were not compressed]
> > 7. umount /mnt/stand
> > 8. umount /mnt
> > 9. reboot
> >
> > BUT, ALAS, upon rebooting, everything seems OK until I get WARNING:
> > exit - /etc/init (PID 1) died, status 0x0000008A. Didn't we have
> > trouble before with /etc/init in getting the CTAR boot and root
> > diskettes to work?
> >
> > Now, what? All of my files are back on the drive. The original
> > /etc/init (from the tape) is there; so how could it be faulty? I
tried
> > using CTAR's version of /etc/init (54676 bytes vs. 28584 bytes),
which
> > was still on the hard drive (and necessary to make the CTAR boot
and
> > root diskettes) but to no avail. So, now what?
>
> I'm not sure what all happened to you, but I had a problem making
A1/A2 ctar
> disks on 5.0.7 on 4 boxes in a row, and the problem was I was using
the
> version downloaded from their website, thinking it was the latest and
I
> would just apply the customers licence to un-demo later.
>
> The disks would seem to be created OK, but the A2 disk would generate
a
> error message but then proceed past it and say there was no problem.
> Trying to actually use the disk after booting the A1 though crashed
at
> /etc/init .
> The A1 disk gets creayed fine
> The A2 disk gets created incomplete
>
> The OS root/boot floppies could be created and they'd work just fine.
>
> The fix was they mailed me current versions of the airbag installer
> pre-branded with the customers licence numbers. The long term fix was
to
> avoid the web site like the plague and wait for the boxed kit in the
mail.
> Inconvenient since 1985 to operate that way. We've pretty much
switched to
> BackupEdge (as a policy not just our own box). The disparity in
features,
> upkeep, support, flexability, accessibility etc... is just too great.
>
> Maybe they (or I, in a pinch) can mail you a generic A2 that won't
have your
> fs details or scsi driver, but maybe there is a way to do it all
generically
> with a btld disk and your own knowledge of the fs layout or maybe you
don't
> need to create new fs's but just restore onto them?
>
> I was not happy with their support when this was happing. I tried to
give
> the official channels a fair shot and spent several days trading
utterly
> idiotic emails with someone who kept asking me questions I'd answered

> already. Until I got fed up and couldn't afford to hold up shipping 4

> customers boxes any longer and squeaky-wheeled myself up to Steve
himself,
> who guessed what was wrong and knew the fix right away.
>
> I can't say how BE's support compares. I've talked to Tom a few times
of
> course, including for support, but it was so rare and so little that
it's
> not enough to rate them by. I can say I just plain haven't needed
hardly any
> support even though BE is a more complex and more featureful product.
>
> good luck
>
> Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/
> +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
> filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani

Thanks, Brian, for your offer. I was able to tar the files from the
tape to the hard drive, after booting up on SCO's boot and root
diskettes. The problem now is with /etc/init. Even using the one from
the root diskette doesn't help solve the problem. I'm going to call
Unitrends to see what they suggest. I've searched the archive for
/etc/init and tried most of the suggestions.

RWS
transpower@aol.com

Transpower wrote:
> Brian K. White wrote:
> > ----- Original Message -----
> > From: "Transpower" <transpower@aol.com>
> > Newsgroups: comp.unix.sco.misc
> > To: <distro@jpr.com>
> > Sent: Tuesday, April 12, 2005 11:39 AM
> > Subject: 5.07 /etc/init Problem
> >
> >
> > >I use SCO OpenServer 5.07. For the first time since installation,
> the
> > > drive crashed and I had to do a restore. I booted on my CTAR
2.88
> MB
> > > diskettes but the hard drive would not mount; it seems that the
> CTAR
> > > file diskette is missing some 5.07 files. So then I did the
> following:
> > >
> > > 1. booted and rooted with my SCO boot and root diskettes (not
> CTAR's)
> > > 2. mount /dev/hd0root /mnt
> > > 3. mkdir /mnt/stand
> > > 4. mount /dev/boot /mnt/stand
> > > 5. cd /mnt
> > > 6. tar xvf /dev/rct0 . [the CTAR files were not compressed]
> > > 7. umount /mnt/stand
> > > 8. umount /mnt
> > > 9. reboot
> > >
> > > BUT, ALAS, upon rebooting, everything seems OK until I get
WARNING:
> > > exit - /etc/init (PID 1) died, status 0x0000008A. Didn't we have
> > > trouble before with /etc/init in getting the CTAR boot and root
> > > diskettes to work?
> > >
> > > Now, what? All of my files are back on the drive. The original
> > > /etc/init (from the tape) is there; so how could it be faulty? I
> tried
> > > using CTAR's version of /etc/init (54676 bytes vs. 28584 bytes),
> which
> > > was still on the hard drive (and necessary to make the CTAR boot
> and
> > > root diskettes) but to no avail. So, now what?
> >
> > I'm not sure what all happened to you, but I had a problem making
> A1/A2 ctar
> > disks on 5.0.7 on 4 boxes in a row, and the problem was I was using
> the
> > version downloaded from their website, thinking it was the latest
and
> I
> > would just apply the customers licence to un-demo later.
> >
> > The disks would seem to be created OK, but the A2 disk would
generate
> a
> > error message but then proceed past it and say there was no
problem.
> > Trying to actually use the disk after booting the A1 though crashed
> at
> > /etc/init .
> > The A1 disk gets creayed fine
> > The A2 disk gets created incomplete
> >
> > The OS root/boot floppies could be created and they'd work just
fine.
> >
> > The fix was they mailed me current versions of the airbag installer
> > pre-branded with the customers licence numbers. The long term fix
was
> to
> > avoid the web site like the plague and wait for the boxed kit in
the
> mail.
> > Inconvenient since 1985 to operate that way. We've pretty much
> switched to
> > BackupEdge (as a policy not just our own box). The disparity in
> features,
> > upkeep, support, flexability, accessibility etc... is just too
great.
> >
> > Maybe they (or I, in a pinch) can mail you a generic A2 that won't
> have your
> > fs details or scsi driver, but maybe there is a way to do it all
> generically
> > with a btld disk and your own knowledge of the fs layout or maybe
you
> don't
> > need to create new fs's but just restore onto them?
> >
> > I was not happy with their support when this was happing. I tried
to
> give
> > the official channels a fair shot and spent several days trading
> utterly
> > idiotic emails with someone who kept asking me questions I'd
answered
>
> > already. Until I got fed up and couldn't afford to hold up shipping
4
>
> > customers boxes any longer and squeaky-wheeled myself up to Steve
> himself,
> > who guessed what was wrong and knew the fix right away.
> >
> > I can't say how BE's support compares. I've talked to Tom a few
times
> of
> > course, including for support, but it was so rare and so little
that
> it's
> > not enough to rate them by. I can say I just plain haven't needed
> hardly any
> > support even though BE is a more complex and more featureful
product.
> >
> > good luck
> >
> > Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/
> > +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
> > filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
>
> Thanks, Brian, for your offer. I was able to tar the files from the
> tape to the hard drive, after booting up on SCO's boot and root
> diskettes. The problem now is with /etc/init. Even using the one
from
> the root diskette doesn't help solve the problem. I'm going to call
> Unitrends to see what they suggest. I've searched the archive for
> /etc/init and tried most of the suggestions.
>
> RWS
> transpower@aol.com

Brian's A2 diskette loaded fine, so I'm tempted to use it (I would have
to remake the filesystems, etc). However, Unitrends sent me overnight
what they claimed was their latest CD for CTAR and Airbag. (I made a
new, minimal SCO system on the hard drive to prepare for the CTAR
installation. The ad320 BTLD worked with the SCO boot CD, but the SCO
floppy boot didn't work in the 2.88 MB drive.) But in trying Unitrends
CD this afternoon (and getting around their CD menu problem which
doesn't recognize SCO), I learned that they installed an earlier
version of Airbag on the CD, and so there was an error in making the A2
diskette. I tried the new A1 and A2 diskettes anyway, and guess what:
I got the same /etc/init problem I got last year! Nothing was fixed!
So I called them, and this time they assured me they were going to send
me the correct CD, with all problems fixed. Sure, I'm saying to
myself. Maybe they should pay me to switch to Backup Edge! But does
Backup Edge restore CTAR files? And don't say "you 'think' so."

Another thing: the CTAR manual says it's completely compatible with
TAR. If so, then why didn't my TAR restore of the CTAR tape work?

Transpower wrote:
> Brian K. White wrote:
> > ----- Original Message -----
> > From: "Transpower" <transpower@aol.com>
> > Newsgroups: comp.unix.sco.misc
> > To: <distro@jpr.com>
> > Sent: Tuesday, April 12, 2005 11:39 AM
> > Subject: 5.07 /etc/init Problem
> >
> >
> > >I use SCO OpenServer 5.07. For the first time since installation,
> the
> > > drive crashed and I had to do a restore. I booted on my CTAR
2.88
> MB
> > > diskettes but the hard drive would not mount; it seems that the
> CTAR
> > > file diskette is missing some 5.07 files. So then I did the
> following:
> > >
> > > 1. booted and rooted with my SCO boot and root diskettes (not
> CTAR's)
> > > 2. mount /dev/hd0root /mnt
> > > 3. mkdir /mnt/stand
> > > 4. mount /dev/boot /mnt/stand
> > > 5. cd /mnt
> > > 6. tar xvf /dev/rct0 . [the CTAR files were not compressed]
> > > 7. umount /mnt/stand
> > > 8. umount /mnt
> > > 9. reboot
> > >
> > > BUT, ALAS, upon rebooting, everything seems OK until I get
WARNING:
> > > exit - /etc/init (PID 1) died, status 0x0000008A. Didn't we have
> > > trouble before with /etc/init in getting the CTAR boot and root
> > > diskettes to work?
> > >
> > > Now, what? All of my files are back on the drive. The original
> > > /etc/init (from the tape) is there; so how could it be faulty? I
> tried
> > > using CTAR's version of /etc/init (54676 bytes vs. 28584 bytes),
> which
> > > was still on the hard drive (and necessary to make the CTAR boot
> and
> > > root diskettes) but to no avail. So, now what?
> >
> > I'm not sure what all happened to you, but I had a problem making
> A1/A2 ctar
> > disks on 5.0.7 on 4 boxes in a row, and the problem was I was using
> the
> > version downloaded from their website, thinking it was the latest
and
> I
> > would just apply the customers licence to un-demo later.
> >
> > The disks would seem to be created OK, but the A2 disk would
generate
> a
> > error message but then proceed past it and say there was no
problem.
> > Trying to actually use the disk after booting the A1 though crashed
> at
> > /etc/init .
> > The A1 disk gets creayed fine
> > The A2 disk gets created incomplete
> >
> > The OS root/boot floppies could be created and they'd work just
fine.
> >
> > The fix was they mailed me current versions of the airbag installer
> > pre-branded with the customers licence numbers. The long term fix
was
> to
> > avoid the web site like the plague and wait for the boxed kit in
the
> mail.
> > Inconvenient since 1985 to operate that way. We've pretty much
> switched to
> > BackupEdge (as a policy not just our own box). The disparity in
> features,
> > upkeep, support, flexability, accessibility etc... is just too
great.
> >
> > Maybe they (or I, in a pinch) can mail you a generic A2 that won't
> have your
> > fs details or scsi driver, but maybe there is a way to do it all
> generically
> > with a btld disk and your own knowledge of the fs layout or maybe
you
> don't
> > need to create new fs's but just restore onto them?
> >
> > I was not happy with their support when this was happing. I tried
to
> give
> > the official channels a fair shot and spent several days trading
> utterly
> > idiotic emails with someone who kept asking me questions I'd
answered
>
> > already. Until I got fed up and couldn't afford to hold up shipping
4
>
> > customers boxes any longer and squeaky-wheeled myself up to Steve
> himself,
> > who guessed what was wrong and knew the fix right away.
> >
> > I can't say how BE's support compares. I've talked to Tom a few
times
> of
> > course, including for support, but it was so rare and so little
that
> it's
> > not enough to rate them by. I can say I just plain haven't needed
> hardly any
> > support even though BE is a more complex and more featureful
product.
> >
> > good luck
> >
> > Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/
> > +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
> > filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
>
> Thanks, Brian, for your offer. I was able to tar the files from the
> tape to the hard drive, after booting up on SCO's boot and root
> diskettes. The problem now is with /etc/init. Even using the one
from
> the root diskette doesn't help solve the problem. I'm going to call
> Unitrends to see what they suggest. I've searched the archive for
> /etc/init and tried most of the suggestions.
>
> RWS
> transpower@aol.com

Brian's A2 diskette loaded fine, and I'm tempted to use it (I would
have to make a new filesystem, etc.) However, Unitrends sent me
overnight what they said was their latest CD and, after making a new,
minimal SCO system on the HD, I tried it. (By the way, the SCO CD
booted fine and the ad320 BTLD loaded fine, but the SCO boot floppy
would not work in the 2.88 MB drive.) Anyway, I got an error message
in making the new A2 diskette and called Unitrends. They then told me
they copied the wrong version of Airbag on the CD; are they incompetent
or what? I tried the new A1 and A2 diskettes, and guess what: I got
the same /etc/init problem I got a year ago! So another day down the
drain; this is the fifth day my UNIX system has been down because of
the incompetence of Unitrends--they should have alerted me to the
Airbag problem months ago. So maybe they should pay me to switch to
Backup Edge; but does Backup Edge restore CTAR files--don't tell me you
just "think" it does.

Unitrends says they will send me a correct CD overnight. Any bets?

One more thing: the CTAR manual says it's completely compatible with
TAR. If so, then why didn't my TAR restore work with the CTAR
(uncompressed) tape?

RWS
transpower@aol.com

Transpower typed (on Thu, Apr 14, 2005 at 11:05:03AM -0700):
|
| Transpower wrote:
| > Brian K. White wrote:
| > > ----- Original Message -----
| > > From: "Transpower" <transpower@aol.com>
| > > Newsgroups: comp.unix.sco.misc
| > > To: <distro@jpr.com>
| > > Sent: Tuesday, April 12, 2005 11:39 AM
| > > Subject: 5.07 /etc/init Problem
| > >
| > >
| > > >I use SCO OpenServer 5.07. For the first time since installation,
| > the
| > > > drive crashed and I had to do a restore. I booted on my CTAR
| 2.88
| > MB
| > > > diskettes but the hard drive would not mount; it seems that the
| > CTAR
| > > > file diskette is missing some 5.07 files. So then I did the
| > following:
| > > >
| > > > 1. booted and rooted with my SCO boot and root diskettes (not
| > CTAR's)
| > > > 2. mount /dev/hd0root /mnt
| > > > 3. mkdir /mnt/stand
| > > > 4. mount /dev/boot /mnt/stand
| > > > 5. cd /mnt
| > > > 6. tar xvf /dev/rct0 . [the CTAR files were not compressed]
| > > > 7. umount /mnt/stand
| > > > 8. umount /mnt
| > > > 9. reboot
| > > >
| > > > BUT, ALAS, upon rebooting, everything seems OK until I get
| WARNING:
| > > > exit - /etc/init (PID 1) died, status 0x0000008A. Didn't we have
| > > > trouble before with /etc/init in getting the CTAR boot and root
| > > > diskettes to work?
| > > >
| > > > Now, what? All of my files are back on the drive. The original
| > > > /etc/init (from the tape) is there; so how could it be faulty? I
| > tried
| > > > using CTAR's version of /etc/init (54676 bytes vs. 28584 bytes),
| > which
| > > > was still on the hard drive (and necessary to make the CTAR boot
| > and
| > > > root diskettes) but to no avail. So, now what?
| > >
| > > I'm not sure what all happened to you, but I had a problem making
| > A1/A2 ctar
| > > disks on 5.0.7 on 4 boxes in a row, and the problem was I was using
| > the
| > > version downloaded from their website, thinking it was the latest
| and
| > I
| > > would just apply the customers licence to un-demo later.
| > >
| > > The disks would seem to be created OK, but the A2 disk would
| generate
| > a
| > > error message but then proceed past it and say there was no
| problem.
| > > Trying to actually use the disk after booting the A1 though crashed
| > at
| > > /etc/init .
| > > The A1 disk gets creayed fine
| > > The A2 disk gets created incomplete
| > >
| > > The OS root/boot floppies could be created and they'd work just
| fine.
| > >
| > > The fix was they mailed me current versions of the airbag installer
| > > pre-branded with the customers licence numbers. The long term fix
| was
| > to
| > > avoid the web site like the plague and wait for the boxed kit in
| the
| > mail.
| > > Inconvenient since 1985 to operate that way. We've pretty much
| > switched to
| > > BackupEdge (as a policy not just our own box). The disparity in
| > features,
| > > upkeep, support, flexability, accessibility etc... is just too
| great.
| > >
| > > Maybe they (or I, in a pinch) can mail you a generic A2 that won't
| > have your
| > > fs details or scsi driver, but maybe there is a way to do it all
| > generically
| > > with a btld disk and your own knowledge of the fs layout or maybe
| you
| > don't
| > > need to create new fs's but just restore onto them?
| > >
| > > I was not happy with their support when this was happing. I tried
| to
| > give
| > > the official channels a fair shot and spent several days trading
| > utterly
| > > idiotic emails with someone who kept asking me questions I'd
| answered
| >
| > > already. Until I got fed up and couldn't afford to hold up shipping
| 4
| >
| > > customers boxes any longer and squeaky-wheeled myself up to Steve
| > himself,
| > > who guessed what was wrong and knew the fix right away.
| > >
| > > I can't say how BE's support compares. I've talked to Tom a few
| times
| > of
| > > course, including for support, but it was so rare and so little
| that
| > it's
| > > not enough to rate them by. I can say I just plain haven't needed
| > hardly any
| > > support even though BE is a more complex and more featureful
| product.
| > >
| > > good luck
| > >
| > > Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/
| > > +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
| > > filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
| >
| > Thanks, Brian, for your offer. I was able to tar the files from the
| > tape to the hard drive, after booting up on SCO's boot and root
| > diskettes. The problem now is with /etc/init. Even using the one
| from
| > the root diskette doesn't help solve the problem. I'm going to call
| > Unitrends to see what they suggest. I've searched the archive for
| > /etc/init and tried most of the suggestions.
| >
| > RWS
| > transpower@aol.com
|
| Brian's A2 diskette loaded fine, so I'm tempted to use it (I would have
| to remake the filesystems, etc). However, Unitrends sent me overnight
| what they claimed was their latest CD for CTAR and Airbag. (I made a
| new, minimal SCO system on the hard drive to prepare for the CTAR
| installation. The ad320 BTLD worked with the SCO boot CD, but the SCO
| floppy boot didn't work in the 2.88 MB drive.) But in trying Unitrends
| CD this afternoon (and getting around their CD menu problem which
| doesn't recognize SCO), I learned that they installed an earlier
| version of Airbag on the CD, and so there was an error in making the A2
| diskette. I tried the new A1 and A2 diskettes anyway, and guess what:
| I got the same /etc/init problem I got last year! Nothing was fixed!
| So I called them, and this time they assured me they were going to send
| me the correct CD, with all problems fixed. Sure, I'm saying to
| myself. Maybe they should pay me to switch to Backup Edge! But does
| Backup Edge restore CTAR files? And don't say "you 'think' so."
|
| Another thing: the CTAR manual says it's completely compatible with
| TAR. If so, then why didn't my TAR restore of the CTAR tape work?

If needed you can download a free evaluation of LONE-TAR and RESCUE-RANGER
for SCO 5.0.7. The evaluations are fully functional, support 5.0.7, and should
be able to restore the Ctar backup. This may help you until you receive what
you need from Unitrends.


--

Best Regards,
Eric Nicholson
.--.
__________________________ .-. | | _____________________________________
Lone Star Software Corp. | | | | .-. Home of World Famous LONE-TAR(tm)
Cactus International, Inc. | |_| | | | Backup Software for UNIX and LINUX
Sales: 800.525.8649 _ |___ |_| | 24x7 Support Available
Support: 301.829.1622 _| ~- | ___| RESCUE-RANGER(tm) and AIR-BAG(tm)
http://www.LONE-TAR.com \, _} | | Disaster Recovery Software
-------------------------- \( -- | | --------------------------------------
| |

Transpower typed (on Thu, Apr 14, 2005 at 11:16:26AM -0700):
------ clipped ----
| One more thing: the CTAR manual says it's completely compatible with
| TAR. If so, then why didn't my TAR restore work with the CTAR
| (uncompressed) tape?
|
| RWS
| transpower@aol.com

CTAR is compatible with 'tar'. I consider this a good feature.
In most cases users would restore a 'tar' archive using 'ctar'.
However, when restoring a 'ctar' archive using standard 'tar' a few
things must be taken into consideration since 'ctar' out features and
out performs 'tar' in many ways:
1. Is the ctar archive compressed? In your case its not... so no problem.
2. Symlinks?
3. Device files?
4. Named pipe files?

In your case you want to simply restore '/etc/init'.
5. If SCSI, make darn sure the low-level SCSI blocksize matches
what was used to create the tape.
# tape getblk
# tape -a 1024|512|0 setblk /dev/rStp0
Search for string "setblk" below for details.

From what I've read, your problem is not unique to CTAR.
I would bet that tar <==> tar would also be a problem
providing the hardware configurations matched.

I want to let you know that this is no sales pitch to you.
CTAR has been around for over 2 decades and is a great
product to have on any system. BackupEDGE is also a fabulous
product. I am the LONE-TAR guy and do NOT want you or anyone
to think this is an effort to push LONE-TAR. I posted some
LONE-TAR FAQ's below to help... not sell.
You're already in good hands. Call 803-454-0300. Ask for Monica.
Tell her that Jeff Hyman says hi and that you need to talk to Steve.
I'll stay in the background to help should you need it.

Best Regards,
Jeffrey Hyman, CEO/President
.--.
___________________________ .-. | | _____________________________________
Lone Star Software Corp. | | | | .-. Home of World Famous LONE-TAR(tm)
Cactus International, Inc. | |_| | | | Backup Software for UNIX and LINUX
Sales: 800.525.8649 _ |___ |_| | 24x7 Support Available
Support: 301.829.1622 _| ~- | ___| RESCUE-RANGER(tm) and AIR-BAG(tm)
http://www.LONE-TAR.com \, _} | | Disaster Recovery Software
-------------------------- \( -- | | --------------------------------------
| |

################################################## ############################
KEYWORDS: 1021 tar cpio lone-tar lonetar compatible compatibility read restore

QUESTION: If LONE-TAR does not use 'tar' ... then why is it named LONE-TAR?

ANSWER: We intentionally maintain standard 'tar' compatibility. This creates
more of a non-proprietary backup environment. Let's say that you
have a LONE-TAR backup, and need to take this tape to another
site that does NOT have LONE-TAR. Well... you could simply use
the 'tar' command at the other site to restore your tape. There
is no need to be locked into a situation where LONE-TAR is
required on any system where you need to do a backup or restore.

The reverse is also true. If you receive a tape that was created
using regular 'tar'... then LONE-TAR can read it. LONE-TAR
is widely used as an error recovery tool to get past bad spots
on a 'tar' tape. Standard 'tar' leaves you dead in the water,
whereas LONE-TAR has sophisticated ERROR RECOVERY capabilities
to get past these bad spots in most cases.

NOTES: Compression must be turned OFF for a system to be able to restore
a compressed LONE-TAR backup to a system that only has 'tar'.
You can still 'list' a compressed LONE-TAR tape using 'tar',
because LONE-TAR does _not_ compress the file headers.

################################################## ############################
KEYWORDS: 1149 4mm dat portability compatibility convert conversion 8mm tape setblk toggle variable instead expected blocks received

RELEASE: LONE-TAR v3.2.4.1

QUESTION: My company is attempting to restore archive 4mm tapes that
were created out in the field to our new server in house.
I am receiving the following error:

# lone-tar: received only {num} blocks, {num} bytes instead of
expected {num} blocks
Check blocking factor (try {num} ) or volume size not specified
lone-tar: Offset was {num} K

The end of the archive came unexpectedly.
This resulted weither we performed a listing or a restore.

What is causing this error and how do I fix it?

ANSWER: Three things must occur to successfully restore from a 4mm on
one system, to a 4mm on another system:
1. The low-level SCSI block size must match.
# tape getblk /dev/your_device_name
# grep SCSI_Blocksize /log/LAST_Master
# ltmenu
u --> c --> 2
2. The tape drives themselves do not need to be the same,
but MUST be "compatible". Model numbers, firmware, tape
capacity issues are a good start.
3. The 4mm "tapes" must be compatible between the two tape "drives".

Use the 'tape', 'mt' or 'tapecntl' command to toggle the mode of
your tape drive in the event the two tape drives modes do not match.
# tape -a 1024 setblk /dev/your_device_name
# tape -a 512 setblk /dev/your_device_name
# tape -a 0 setblk /dev/your_device_name
... or ...
# mt -f /dev/your_device_name status | grep block <-- LINUX
# tapecntl -f 512 /dev/your_device_name <-- UW7

NOTES: Take a look at shell script '/usr/lone-tar/bu.tapeutil'
specifically at function 'get_commands()'.

To have LONE-TAR preset the low-level SCSI blocksize:
# ltmenu
e --> 8 --> 93 <Enter> e

REFERENCE: FAQ-1018 FAQ-1104
CREATED: Thu May 16 14:55:27 EDT 2002 - JBH
################################################## #############################