06-15-2010
ufsrestore T5240
Hi,
Scsi Tape drive is connected with other Sun V440 Server, i have taken the root filesystem ufsdump through ufsdump -0uf servername:/dev/rmt/0n /
if we need to do ufsrestore the root filesystem means need to boot the server using bood cdrom -s then mount the root slice in /mnt and then ufsrestore -rvf /dev/rmt/0n
My query is if we booted the server with cdrom ( single user ) means whether i can able to access remote tape drive
ufsrestore -rvf servername:/dev/rmt/0n this command will work?
Rajasekar
9 More Discussions You Might Find Interesting
1. Solaris
Setting up a T5240 with two disks c1t0d0 and c1t1d0.
I am trying to use raidctl but when I issue.
raidctl -l
I get
Controller 1
Disk: 0.0.0
Disk: 0.1.0
So I try
raidctl -c '0.0.0 0.1.0' -r 1 1
and I get "Array in use."
I try (4 Replies)
Discussion started by: photon
4 Replies
2. Solaris
its a fresh installation. during the OS setup, it did not prompt for IP, netmask and gateway. using Solaris 10 08/07 update 4. I tried to plumb manually but encountered no such interface error. but nxge interfaces can be greped from the /etc/path_to_inst file.
getting similar error on... (3 Replies)
Discussion started by: incredible
3 Replies
3. Solaris
I was trying to configure the netmgmt from the serial and set commitpending to true. However, the netmgmt port is not up and blinking.
I tried to connect using my notebook directly to the netmgmt port and am not able to ping as well. Previouly i was doing the firmware upgrade using the webconsole.... (20 Replies)
Discussion started by: incredible
20 Replies
4. Solaris
Hi,
We are planning to buy new server for our data center. Sun T5240 or M3000 which one have better performance, we are going to create many dt sessions in this server. So, i need your suggestions.
RJS (4 Replies)
Discussion started by: rajasekg
4 Replies
5. Solaris
Hi -
I have a T5240 with 7 LDOMS configured. One night, network comm was broken somehow. Nobody was doing anything on the machine at the time. Here is what I saw in messages:
WARNING: nxge3 : nxge_dma_mem_alloc: ddi_dma_mem_alloc kmem alloc failed
WARNING: nxge3 : nxge_alloc_rx_buf_dma:... (2 Replies)
Discussion started by: pyroman
2 Replies
6. Solaris
Hi Gurus
Can any one tell me the process of disabling the multithreading option on T5240 server and my OS is on LDOM, having one physical processor with 8 core & 8 thread per core
Regards (3 Replies)
Discussion started by: amity
3 Replies
7. Solaris
Hi !
I've been given a T5240 with 4 disks and 2 HBA cards (but no array connected). I did a factory reset on SP and NVRAM clean on OBP because the server had been used before.
I boot cdrom in single mode and try to create a hw mirror with disks from c1... but only c2 is seen by raidctl.
... (2 Replies)
Discussion started by: delavega
2 Replies
8. Solaris
I have a T5240 with 2 T2 US 8 core.. Theoretically how many ldoms can I configure? (5 Replies)
Discussion started by: Iftikhar Barrie
5 Replies
9. Solaris
Hi Folks,
Just a quick question - hopefully!
I have an application currently running on a V890 with Solaris 9, I'd like to move this to either one of our T-5's or one of the T5240's in a Legacy container on an LDOM - but the fly in the ointment is the application still uses a standard Hayes... (3 Replies)
Discussion started by: gull04
3 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)