08-06-2002
mirroring problem
My company had purchased a Pro Model hard disk duplicator a couple of years ago and has used it successfully until our disk drive vendor stopped production of the currently used drives and offered us what they considder to be a direct replacement drive.
On these new drives everything matches the old drives except for the drive sizes. the Old drives hold 18,353 KBytes and the new drives hold 18,211 KBytes. Because the new drives are smaller in size the mirror machine will not copy the drives.
Is there a way to copy the old drives to the new drives without having to format the drives;
1 without losing all the information on the disk ???
2 without re building the drives from nothing ???
3 without purchasing new drive ???
I was thinking maybe using the dd command.
We are using two Unix flavors
1 Sun Solaris (takes about 8 hours to format and partition)
2 HP-UX 10X
I appreciate any help that is offered
10 More Discussions You Might Find Interesting
1. Solaris
I am running Solaris 10 and i need to mirror a 73 gig HD. How do you mirror one in Solaris? (2 Replies)
Discussion started by: dewsdwarfs
2 Replies
2. SCO
How Can I Do Mirroring In Unix? (0 Replies)
Discussion started by: DIMITRIOSDOUMOS
0 Replies
3. HP-UX
Im following the directions from
Mirroring the Root File System and Primary Swap
#
Mirror the root logical volume to the above disk:
lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c0t3d0
#
Mirror the primary swap logical volume:
lvextend -m 1 /dev/vg00/prswaplv /dev/dsk/c0t3d0
#
... (1 Reply)
Discussion started by: csaunders
1 Replies
4. Solaris
Hello,
i'm pretty new in using solaris (5.10) and i'm kind of stuck with one problem. I'm trying to create a disk mirror cause of data redundancy. I've installed second disk in my system, prepared everything for creating a mirror (by following the instructions) and don't get any responce for... (7 Replies)
Discussion started by: n00b
7 Replies
5. Shell Programming and Scripting
I'm not sure how to best explain what I'd like to do, so let me give an example. I used to work in a department that deals with internet security. This department had an "internal" website (only people in the building can get on it) and an "external" website (anyone in the world can get on it --... (1 Reply)
Discussion started by: sstevens
1 Replies
6. Solaris
hi every body
I'm new to solaris and I need your help in how to configure disk mirroring for 4 hard disks so that two of them will be replica to the other two ...???
Thanxx (7 Replies)
Discussion started by: mm00123
7 Replies
7. AIX
Hello,
On a RS6000 server I have two disks (hdisk0 and hdisk1) which are mirrored in a logical volume rootvg.
Yesterday one of these disks failed. Diagnosis, physical death.
It has therefore been replaced by a brand-new.
In terms of parameters, hdisk1 is now N# 1 in bootlist,... (2 Replies)
Discussion started by: titione
2 Replies
8. Solaris
Hi All
i wish to mirror the root disk, but i face the below error.
root@saturn # metainit d11 1 1 c0t0d0s0
metainit: saturn: c0t0d0s0: is mounted on /
kindly assist... (27 Replies)
Discussion started by: SmartAntz
27 Replies
9. Solaris
Hello,
I just build a Solaris 10 server on an x86 box. I forgot to mirror the two disks when I install the OS. Can I get some help with this?
I have this
# zpool list
rpool 278G 5.77G 272G 2% ONLINE -
# zpool status
pool: online
state: ONLINE
scan: none requested
config:
... (12 Replies)
Discussion started by: bitlord
12 Replies
10. Solaris
Hello,
I need some help mirroring my rpool.
I have a 60gb ssd running the rpool alone and want to mirror it for redundancy so I bought a 120gb ssd that I found for a good price. 60gb drives aren't as easy to find at a good price anymore it seems.
I (a bit naively) thought after reading... (9 Replies)
Discussion started by: Zorken
9 Replies
CD(9) BSD Kernel Developer's Manual CD(9)
NAME
cd -- CDROM driver for the CAM SCSI subsystem
DESCRIPTION
The cd device driver provides a read only interface for CDROM drives (SCSI type 5) and WORM drives (SCSI type 4) that support CDROM type com-
mands. Some drives do not behave as the driver expects. See the QUIRKS section for information on possible flags.
QUIRKS
Each CD-ROM device can have different interpretations of the SCSI spec. This can lead to drives requiring special handling in the driver.
The following is a list of quirks that the driver recognize.
CD_Q_NO_TOUCH This flag tells the driver not to probe the drive at attach time to see if there is a disk in the drive and find out what
size it is. This flag is currently unimplemented in the CAM cd driver.
CD_Q_BCD_TRACKS This flag is for broken drives that return the track numbers in packed BCD instead of straight decimal. If the drive seems
to skip tracks (tracks 10-15 are skipped) then you have a drive that is in need of this flag.
CD_Q_NO_CHANGER This flag tells the driver that the device in question is not a changer. This is only necessary for a CDROM device with
multiple luns that are not a part of a changer.
CD_Q_CHANGER This flag tells the driver that the given device is a multi-lun changer. In general, the driver will figure this out auto-
matically when it sees a LUN greater than 0. Setting this flag only has the effect of telling the driver to run the initial
read capacity command for LUN 0 of the changer through the changer scheduling code.
CD_Q_10_BYTE_ONLY
This flag tells the driver that the given device only accepts 10 byte MODE SENSE/MODE SELECT commands. In general these
types of quirks should not be added to the cd(4) driver. The reason is that the driver does several things to attempt to
determine whether the drive in question needs 10 byte commands. First, it issues a CAM Path Inquiry command to determine
whether the protocol that the drive speaks typically only allows 10 byte commands. (ATAPI and USB are two prominent exam-
ples of protocols where you generally only want to send 10 byte commands.) Then, if it gets an ILLEGAL REQUEST error back
from a 6 byte MODE SENSE or MODE SELECT command, it attempts to send the 10 byte version of the command instead. The only
reason you would need a quirk is if your drive uses a protocol (e.g., SCSI) that typically does not have a problem with 6
byte commands.
FILES
/sys/cam/scsi/scsi_cd.c is the driver source file.
SEE ALSO
cd(4), scsi(4)
HISTORY
The cd manual page first appeared in FreeBSD 2.2.
AUTHORS
This manual page was written by John-Mark Gurney <jmg@FreeBSD.org>. It was updated for CAM and FreeBSD 3.0 by Kenneth Merry
<ken@FreeBSD.org>.
BSD
March 25, 2014 BSD