Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory Need help with MOD Disk copying Post 302413939 by bakunin on Monday 19th of April 2010 05:49:07 AM
Old 04-19-2010
All these three possibilities will work, but probably (and depending on the number of disks involved) the disk duplicator will be the one least costly, because it can work automatically.

You can verify a medium (any medium, including your MODs) by simply reading from it. Put the newly copied MOD in a drive, and use something similar to this script:

Code:
#! /bin/ksh

mount /dev/<whatever the devicename of the MOD is> /tmp/disktest

if [ $(tar -cvf - /tmp/disktest >/dev/null 2>&1 ; print - $?) -gt 0 ] ; then
     print - "ERROR: Disk has read errors"
else
     print - "Disk passed read test"
fi

umount /tmp/disktest
exit 0

Quote:
Originally Posted by drew_holm
[...] and have limited IRIX skills
May i ask then, why you post in the experts forum? It surely can't be because of the nature of your problem, which is entry-level at best, yes?

I hope this helps.

bakunin

---------- Post updated 04-19-10 at 11:49 AM ---------- Previous update was 04-18-10 at 06:53 PM ----------

After doing some searching i found no such thing as a media duplicator for MO-media, so perhaps such a thing isn't being produced.

You could build such a device (at least half-automated, that is) yourself by installing two MO-drives in one system. It doesn't even have to be a SGI-workstation, a simple Linux workstation would suffice, which would probably lower the price tremenduously.

Then start the following script (or some variant of it) as root. I have:

Code:
#! /bin/ksh

typeset chInDev="/dev/sdb1"         # these are assumptions, probably have to be changed
typeset chOutDev="/dev/sdc1"

typeset fInPath="/tmp/DiskIn"
typeset fOutPath="/tmp/DiskOut"

mkdir -p "$fInPath"
mkdir -p "$fOutPath"

while : ; do
     print - "-- Load both drives, then press ENTER --" ; read junk
     sleep 20            # give the drives time to spin up, maybe required, maybe not

     mount "$chInDev" "$fInPath"
     mount "$chOutDev" "$fOutPath"

     cd "$fInPath"
     tar -cf - * | (cd "$fOutPath" ; tar -xf - )
     if [ $? -gt 0 ] ; then
          print - "ERROR: could not copy disk!"
     else
          print - "Disk successfully duplicated."
     fi
     cd -

     umount "$fInPath"
     umount "$fOutPath"
done

exit 0

You can stop this script by pressing "CTRL-C", otherwise it will loop forever, asking for one disk after the other.

I hope this helps.

bakunin

Last edited by bakunin; 04-18-2010 at 01:59 PM..
 

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

copying oracle tables from raw disk

I have been tasked with archiving Oracle tables. The data is on raw devices, and possibly will span multiple logical volumes. Has anyone ever had to do this? How did you accomplish it? Any references to accomplish this would be greatly appreciated. Thanks, (2 Replies)
Discussion started by: isenhart
2 Replies

2. UNIX for Dummies Questions & Answers

Copying files unto a usb pendrive/external disk from Solaris 9

Hi all, Can anybody help me with how I can connect a usb pendrive or external disk to a Sun Server which runs on Solaris 9? I am able to connect the usb drive to a windows server easily and copy files but am wondering if it is possible to do that with Solaris. Any help will be appreciated. thanks. (3 Replies)
Discussion started by: rahmantanko
3 Replies

3. UNIX for Advanced & Expert Users

Listing/copying files from magnetic optical disk

I am trying to list the name of files on an MOD - I use the command tar vtf /MOD_DRIVE|more and I get a nice list of filenames/directories on this particular MOD. When I put in another MOD that contains software options I get the error "directory checksum error". I would like to be able to... (2 Replies)
Discussion started by: drew_holm
2 Replies

4. Solaris

Solaris 6.5 MOD disk copy help needed

Hello, we are running Irix 6.5 on our octane/sgi computers - these computers come with an external Sony MOD drive attached via a scsi cable. We have backed info to 2.3 gig MOD disks over the years and woule like to duplicate the MOD's. I believe there are 3 ways to do this: add a second... (1 Reply)
Discussion started by: drew_holm
1 Replies

5. Solaris

Copying disk - dd or lucreate?

Got server that I want to have an 'image' of disk to keep in case of failure. What I want to be able to do is, in the event of disk failure, remove system disk replace with cloned disk (same slot) and reboot. Trouble is I cant take this server down to single user. Is dd still a viable... (6 Replies)
Discussion started by: psychocandy
6 Replies
fd(4)							     Kernel Interfaces Manual							     fd(4)

NAME
fd - file descriptor files DESCRIPTION
The /dev/fd file system is a pseudo-file system layered beneath the Virtual File System (VFS). The file descriptor files (fd*) are those files that are accessible through file descriptors. The file descriptors use the naming convention /dev/fd/0, /dev/fd/1, /dev/fd/2 and so on up to any number. To make the /dev/fd file system known to the operating system, you must create the directory with the correct privileges, then you must mount the file system. The following steps describe how to create the directory, mount the file system both manually and automatically, and how to dismount the file system: Create the directory using the mkdir and chmod commands: mkdir /dev/fd; chmod 777 /dev/fd Mount the file system manually using the mount command: mount -t fdfs /dev/fd /dev/fd Mount the file system automatically by editing either the /etc/fstab file or the /sbin/bcheckrc file. Add the following entry to the /etc/fstab file: /dev/fd /dev/fd fdfs rw 0 0 This entry mounts the pseudodevice /dev/fd on the /dev/fd directory with read/write privileges. The file system type is fdfs and the zeros (0) in the remaining fields specify that the file system is not to be backed up nor can file system checks be performed by the fsck command as this is a virtual file system. Add the following entry to the /sbin/bcheckrc file: # # mount fdfs # echo 'Mounting /dev/fd filesystem' /sbin/mount -a -v -t fdfs Again, the /dev/fd file system should not be mounted in this manner if an entire system is to be backed up starting from the root directory. Dismount the file system using the umount command: umount /dev/fd For correct truncate() behavior on fd files, you must load your program using the -lsys5 flag. RESTRICTIONS
The /dev/fd file descriptors should not be exported. EXAMPLES
The following example show how the open and dup functions have the same effect if file descriptor n is opened: fd = open("/dev/fd/n", mode); fd = dup(n); In the above example, the open function is equal to the creat function and mode is ignored. Using the dup function, subsequent reads or writes on the fd file descriptor files fail unless the original file descriptor enables the operation. ERRORS
The following error condition exists: The file descriptor is not valid. RELATED INFORMATION
Commands: chmod(1), mkdir(1), mount(8). Functions: creat(2), dup(2), open(2). delim off fd(4)
All times are GMT -4. The time now is 04:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy