This may be a dumb question, but if you make a cpio tape archive from
data on an SCO system (HTFS filesystem), you can still restore the data
off the tape to another system, like FreeBSD with a UFS filesystem,
right?
This should work. If you run into any issues they will be
This may be a dumb question, but if you make a cpio tape archive from
data on an SCO system (HTFS filesystem), you can still restore the data
off the tape to another system, like FreeBSD with a UFS filesystem,
right?
And the followup, can FreeBSD run SCO binaries (SCO Unix 5.0.1)? I am
going
This may be a dumb question, but if you make a cpio tape archive from
data on an SCO system (HTFS filesystem), you can still restore the data
off the tape to another system, like FreeBSD with a UFS filesystem,
right?
This should work. If you run into any issues they will be incompatibilities
On Fri, 8 Oct 2004, Sergey Babkin wrote:
Try to use the Verify menu from the Adaptec BIOS. It finds and tries
to re-map the bad sectors (it tries to preserve data during this too,
unless the sector is completely unreadable).
The verify commands issued by the BIOS are virtually useless
I was able to use the badtrk utility in SCO to identify bad blocks and
put them in the bad block table.
The SCSI card is an old Adaptec, AIC-7880 and I believe it does not
support automatic bad block detection/redirection.
This disk came from a spares kits, so even though it is new and never
On Sat, 9 Oct 2004, John Von Essen wrote:
The SCSI card is an old Adaptec, AIC-7880 and I believe it does not
support automatic bad block detection/redirection.
If it has a BIOS it should have the verify tool in there...
All the verify tool does, though, is issue a verify command to each
Gotta love when you reply to your own posts... :)
On Sat, 9 Oct 2004, Doug Russell wrote:
If it has a BIOS it should have the verify tool in there...
All the verify tool does, though, is issue a verify command to each
sector. You can do this yourself, even on a running system, also.
I
Doug Russell wrote:
On Thu, 7 Oct 2004, John Von Essen wrote:
Well, I eventually got this SCO system working. But today, some errors
appeared:
505k:unrecover error reading SCSI disk on 0 Dev - 1/42
cha = 0 id = 0 1 on = 0
Block 6578
medium error unrecovered read error
HTFS
Well, I eventually got this SCO system working. But today, some errors
appeared:
505k:unrecover error reading SCSI disk on 0 Dev 1/42
cha = 0 id = 0 1 on = 0
Block 6578
medium error unrecovered read error
HTFS i/o failure occurred while trying to upgrade 1 node 26302 on
HTFS. Dev hd 1/42
Well, I eventually got this SCO system working. But today, some errors
appeared:
505k:unrecover error reading SCSI disk on 0 Dev 1/42
cha = 0 id = 0 1 on = 0
Block 6578
medium error unrecovered read error
HTFS i/o failure occurred while trying to upgrade 1 node 26302 on
HTFS. Dev hd
On Thu, 7 Oct 2004, John Von Essen wrote:
Well, I eventually got this SCO system working. But today, some errors
appeared:
505k:unrecover error reading SCSI disk on 0 Dev 1/42
cha = 0 id = 0 1 on = 0
Block 6578
medium error unrecovered read error
HTFS i/o failure occurred while
John Von Essen wrote:
Unfortunately, I have inherited a Intel P200 with SCO OpenServer 5.0.4
with a 4Gb SCSI drive.
Condolences ! SCO is Horrible to work on, a waste of time, erase ASAP !
SCO is of no help, they cant provide replacement boot floppy, only sell
me complete
Unfortunately, I have inherited a Intel P200 with SCO OpenServer 5.0.4
with a 4Gb SCSI drive.
I have to get the machine back up and running. Here is my dilemma and
progress:
I have a cpio archive on DDS-2 tape that is valid. I have been able to
extract files onto a test disk with FreeBSD.
On Mon, 27 Sep 2004, John Von Essen wrote:
I have a new replacement 4Gb disk. With a FreeBSD boot CD I did a dd
and was able to get the new disk setup with all of the old disks
partition maps, boot data, etc.,. The new disk actually boots into SCO
but fails because it only has 100Mb or so of
Oh, I love replying to my own posts :)
On Mon, 27 Sep 2004, Doug Russell wrote:
Try addingconv=sync,noerrorto your dd line. If most of the data
after the defect(s) can be read, you'll end up with an almost complete
partition which will likely run. You can then fsck and restore
Well,
I was able to get a boot/install floppy made. Then install a fresh SCO.
Then create recovery floppies, then boot with recovery floppy and try
to cpio tape data to /mnt.
However, in both the recover floppy and the real SCO system I have to
configure the tape drive apparently. As of right
I believe DAT is what you want to tell SCO.
--
Matt
- Original Message -
From: John Von Essen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 27, 2004 6:33 PM
Subject: Re: hacking SCO
Well,
I was able to get a boot/install floppy made. Then install a fresh SCO
17 matches
Mail list logo
