Hi all,
this time I'd need a help from an advanced Solaris system admin
I attached a HP StorageWorks Ultrium 215 Tape Drives - Overview - c00059530 - HP Business Support Center to my Sun E220R and it got recognized immediately (probe-scsi-all).
Now the operating system boot process finished, I logged in with root and in dmesg I can see the drive:
Here are the questions:
How can I read the tape content?
How can I eject it with a shell command?
Can I load an already ejected tape?
Do I neccessarily need a proper/commercial Backup Software?
Can't I simply do the backup using dd command?
How would I do a full backup of the main harddisk sd0 ?
How would I do a full restore of the main harddisk sd0 ?
---------- Post updated at 18:41 ---------- Previous update was at 18:40 ----------
Thank you in advance for your attempt to help me! :-)
---------- Post updated at 18:44 ---------- Previous update was at 18:41 ----------
Please also note this is 100% my personal hobbyist problem!
It's definately not a real-world problem and of course this is not a homework or something.
I'm running SCO OS 505 on a Compaq proliant 1600, and my tape drive will just not work. It was working properly and whent to Sh?ts when I tried to get the cd rom working. I have uninstalled any configured tape drive and rebooted and then configured a tape drive and rebooted still nothing. I'm... (4 Replies)
I'm researching a tape drive + backup software to work across my unix/linux network. Was thinking about a dds4 tape drive (sony's) on my solaris ultra2, with some kind of software that would work across the network to back up my other 2 solaris boxes, plus my 2 linux boxes. What do others use... (3 Replies)
Hi all, please help I am stuck.
I have installed a external unipack scsi tape drive. The tape drive is Exabyte Eliant 820. All I did was connected scsi cable and power it on. When issued "probe-scsi-all" command, the tape is correctly identified. However, when issued "dmesg | more" command, the... (4 Replies)
hi-
I just installed a quad gigaswift ethernet scsi card to my sunblade 150. I checked with the docs, and got all of the required drivers on the box. Now, I'm trying to mount an external scsi tape drive with no luck. I set the scsi address on the external drive to 0. Here's what I'm coming... (9 Replies)
Currenty running SCO Openserver 6 at a Dell PowerEdge T300. I recently installed a driver for an Adaptec SCSI card (adpu320). When I connect a tape drive to it and re-start the system,it freezes and displays the following message: "WARNING: adpu320: Command timed out (ha= 4)" and the system... (2 Replies)
I have 2 servers in my office which are p570 and p550. Both run under AIX 5300-07. And I only have 1 x SCSI Ultrium LTO3 Tape Drive. For syncronization purposes, I always backup p570 server's database and restore into p550 server.
And due to the frequent process of syncronization, I require to... (1 Reply)
I've had a scsi hard drive, scsi tape drive, and cd rom working off an adaptec 29160 controller. Everything worked great until a few days ago. I begin getting tar format errors (running sco 5.0.6) on the tape drive and occasionally the entire system would hang up while trying to access data on... (0 Replies)
i connect an ibm ultrium lto 5 (sas) to an 8204-e8a (v6.1 TL5 SP 1)
then i do an cfgmgr and get message about missing filesets
devices.pciex.1410ca03
devices.pciex.pciexclass.00107
devices.pciex.00107200
devices.pciex.pciex100.72.3
and a few others
i try to find the filesets on the two OS... (1 Reply)
Discussion started by: AIXBlueCat
1 Replies
LEARN ABOUT DEBIAN
scsi-spin
scsi-spin(8) System Manager's Manual scsi-spin(8)NAME
scsi-spin - spin up and down a SCSI device
SYNOPSIS
scsi-spin [-options...] [device]
DESCRIPTION
scsi-spin let the user to manually spin up and down a SCSI device.
This command is particularly useful if you've got noisy (or hot) drives in a machine that you rarely need to access. This is not the same
as the kernel patch that's floating around that will automatically spin down the drive after some time. scsi-spin is completely manual,
and spinning down a drive that's in use, especially the one containing the scsi-spin binary, is probably a really bad idea.
To avoid running in trouble with such cases, scsi-spin verifies that the device to work on is not currently in use by scanning the mounted
file system description file for a partition living on it and issue an error if this the case.
OPTIONS -u, --up
spin up device.
-d, --down
spin down device.
-e, --loej
load or eject medium from drive (use along with -u or -d )
-w, --wait=[n]
wait up to n seconds for the spin up/down command to complete. Default is to return immediately after the command was sent to the
device. Either repeat -w n times or set n to define the time to wait before to report a timeout.
-l, --lock
prevent removal of medium from device.
-L, --unlock
allow removal of medium from device.
-I, --oldioctl
use legacy ioctl interface instead of SG_IO to dialog with device (could not be supported on all platforms). -e and -w are not
allowed with this option.
-v, --verbose=[n]
verbose mode. Either repeat -v or set n accordingly to increase verbosity. 1 is verbose, 2 is debug (dump SCSI commands and Sense
buffer).
-f, --force
force spinning up/down the device even if it is in use.
-n, --noact
do nothing but check if the device is in use.
-p, --proc
use /proc/mounts instead of /etc/mtab to determine if the device is in use or not.
device the device is any name in the filesystem which points to a SCSI block device (sd, scd) or generic SCSI device (sg). See section
below.
SCSI devices naming convention
Old kernel naming convention
It is typically /dev/sd[a-z] , /dev/scd[0-9]* or /dev/sg[0-9]*.
scsidev naming convention
It is typically /dev/scsi/s[rdg]h[0-9]*-e????c?i?l? or /dev/scsi/<aliasname>.
devfs naming convention
It is typically /dev/scsi/host[0-9]/bus[0-9]/target[0-9]/lun[0-9]/disc (same for cd and generic devices) or short name
/dev/sd/c[0-9]b[0-9]t[0-9]u[0-9] when devfsd "new compatibility entries" naming scheme is enabled.
SEE ALSO scsiinfo(8), sg_start(8), sd(4), proc(5),
AUTHORS
Eric Delaunay <delaunay@debian.org>, 2001
Rob Browning <rlb@cs.utexas.edu>, 1998
03 September 2001 scsi-spin(8)