Sponsored Content
Full Discussion: ufsrestore T5240
Operating Systems Solaris ufsrestore T5240 Post 302437490 by m_aftab on Thursday 15th of July 2010 08:19:57 AM
Old 07-15-2010
1. Boot from CD
2. Start network services
3. access remote drive or use NFS to restore
 

9 More Discussions You Might Find Interesting

1. Solaris

raidctl on SUN T5240

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

cannot plumb nxge on T5240

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

T5240 netmgmt port not blinking

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

SUN T5240 vs M3000

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

Bizarre Sun T5240 behavior

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

Disable multithreading option on T5240

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

Cannot configure RAID on T5240

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

Question: # of ldoms on T5240 with 2 T2 US 8 core

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

Using a Modem on a T5-2 or a T5240

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
TAPSET::SCSI(3stap)													       TAPSET::SCSI(3stap)

NAME
tapset::scsi - systemtap scsi probe points DESCRIPTION
This family of probe points is used to probe the SCSI activities. It contains the following probe points: scsi.ioentry Fires when SCSI mid layer prepares a SCSI request Arguments: disk_major The major number of the disk disk_minor The minor number of the disk device_state The current state of the device. The possible values could be: SDEV_CREATED = 1, /* device created but not added to sysfs * Only internal commands allowed (for inq) */ SDEV_RUNNING = 2, /* device properly configured * All commands allowed */ SDEV_CANCEL = 3, /* beginning to delete device * Only error handler commands allowed */ SDEV_DEL = 4, /* device deleted * no commands allowed */ SDEV_QUIESCE = 5, /* Device quiescent. No block commands * will be accepted, only specials (which * originate in the mid-layer) */ SDEV_OFFLINE = 6, /* Device offlined (by error handling or * user request */ SDEV_BLOCK = 7, /* Device blocked by scsi lld. No scsi * commands from user or midlayer should be issued * to the scsi lld. */ scsi.iodispatching Fires when the SCSI mid layer dispatches a SCSI command to the low level driver Arguments: host_no The host number channel The channel number lun The lun number dev_id The scsi device id device_state The current state of the device. data_direction The data_direction specifies whether this command is from/to the device. The possible values could be: DMA_BIDIRECTIONAL = 0, DMA_TO_DEVICE = 1, DMA_FROM_DEVICE = 2, DMA_NONE = 3, request_buffer The request buffer address req_bufflen The request buffer length scsi.iodone Fires when a SCSI command is done by low level driver and enqueued into the done queue. Arguments: host_no The host number channel The channel number lun The lun number dev_id The scsi device id device_state The current state of the device data_direction The data_direction specifies whether this command is from/to the device. scsi.iocompleted Fires when SCSI mid layer runs the completion processing for block device I/O requests Arguments: host_no The host number channel The channel number lun The lun number dev_id The scsi device id device_state The current state of the device data_direction The data_direction specifies whether this command is from/to the device. goodbytes The bytes completed. SEE ALSO
stap(1), stapprobes(3stap) IBM
TAPSET::SCSI(3stap)
All times are GMT -4. The time now is 03:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy