Kenneth Porter wrote: > I have a friend who needs to recover some data from a SCSI drive from a > SCO system, and he wants to make sure nothing writes to the drive if he > mounts it on his Linux system. I just want to verify that mounting it > read-only is sufficient and won't attempt to write anything to it. (I > recall in the old days when HD's had a write-protect jumper to protect > it at the firmware level.) Are there other measures he should take? Kenneth, Many SCSI disks still have write protect jumpers, typically on the same block that selects the SCSI id of the parallel interface. From recent SCSI disk product manuals, I can see that Maxtor supports the Software Write Protect (SWP) bit in the control mode page. A tool like sdparm could be used to set SWP: # sdparm --set=SWP --save /dev/sda You need to be careful that the system you do this on (or the following dd suggestion) does not automount file systems. To be safe, you could copy the contents of the SCSI disk to the same size or larger disk (ATA or SCSI). Something like: # dd if=/dev/sda of=/dev/hdb bs=512 where /dev/sda is your reference disk and /dev/hdb has nothing important on it and is the same size or larger than /dev/sda ** Then power down the system, remove /dev/sda, power up and try and mount the SCO partition on /dev/hdb . After getting the data from /dev/hdb you may need to use fdisk to repartition it (so that its extra size is not wasted). ** Using a command like 'fdisk -ul', is one way of checking that a disk has been copied. Keeping the first 63 sectors of the original /dev/hdb may also be prudent: "dd if=/dev/hdb of=hdb_0_62.img bs=512 count=63" Doug Gilbert - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
