If Openserver 5. I'm trying to restore a filesystem on the same type of tape drive but the SCO can't see it on the back up utility. I really appreciate your help thank you. RE: how to config 4mm tape drive on sco Will you clarify the "backup utility" you are using? There are 3 built in commands that can be considered utilities of that type, and 2 commercial utilities that are heavily used.
You might want to run " man tar" or "man cpio" or "man dd" to see what the built ins do. I'm rusty on 5. Happens when you work on hundreds of windows machines between SCO calls.
Ed Fair unixstuff juno. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given. The default block size keeps reverting to 0, even though I've set it to several times using setblk. Can anyone help? Even after remaking the device with mkdev tape, the device will not open in multi user mode, but works fine in single user? Join Date: Apr Your way is right. Are you sure that the tape is connectted to alad? Find all posts by jgt. Now the operating system boot process Help with scsi tape drive problem.
I've had a scsi hard drive, scsi tape drive, and cd rom working off an adaptec controller. Everything worked great until a few days ago. I begin getting tar format errors running sco 5. Hi, i installed a unix tape drive on my alphaserver. I have used the hardware manager and it shows the tape is present. Can anyone help me understand why it cannot pick up the tape as a default? Problems with SCSI card and tape drive. Installing tape drive?
I have Redhat 8. It doesn't even bother to run sconf -v to see if any hardware remotely like what you described is out there. The second invocation after rebooting really goes out and tries to access the physical hardware. Apparently it doesn't find the drive.
That could be because just listing a few things I've done or not done. If this is 5. If it doesn't, you can just manually edit mscsi, relink, and reboot. Note that the order in which sconf displays info is NOT the order used in mscsi!
If you guessed wrong about the controller, bus, or ID, you won't get the screens that ask about the partitions. The controller is the first column after Sdsk, the ID is the second, then lun and bus.
Simply change the appropriate column, and then relink. If you don't feel comfortable with that, at least vi mscsi to remove the line that represents the error. Once you've got that correct, 'mkdev hd' will proceed to the second phase, where you create the Unix partition and then divide it into one or more filesystems. During that second phase, you are asked if you want "block by block control". If you answer that affirmatively, you get to control everything about the division s created, including the name s.
Divvy will use a device name instead like "D". When you run divvy initially, you tell it what device you are working on: scsi id, etc. It writes that information into a "division table" on the disk. When it finds one, it prints that name. It doesn't write anything to the division table except if you change the size of a division or split the disk into more divisions. Changing the TYPE of a division does nothing at all except serve as a flag to divvy if you say "New filesystem", in which case it runs mkfs to match the type you said.
You may want to transfer an existing disk to another system, as for an upgrade. You'll see your divisions; all you need to do is n ame them and proceed from there. IMG file, and we can start the installation by booting from that.
At the serial request I discovered that this version is not the same as regular ODT, and thus the serials I had did not work. I tried extracting a to-be-serialized file from inside the CD. Anyway, after inserting the serial the installation proceeds smoothly, and we can even select to install the Development System:.
The DevSys also requires a serial, and for that I used one found on the archive of Tenox. Since we are at it, we can also modify the params.
0コメント