I have a Sun Sparc T2000 (Solaris 10 05-08) and have installed a PCI-X 4GB Single Port HBA card in it.
I have one StorageTek 2540 array that I would like to connect to the T2000.
For the moment it would be a single path connection, but I've ordered a 2nd HBA, so eventually it would be... (4 Replies)
Hi Guyz,
I recently downloaded sol-10-u6-ga1-sparc-dvd.iso from Sun. I burned the disk as cd .iso.
When trying to boot at the ok> boot cdrom
i get the following error:
-----------------------------------------------------------------------
Boot device:... (2 Replies)
Hi, i am really 'fresh' to Solaris or any UNIX OS. My role as web developer but i need slightly involve to Solaris support. It is harder for me to understand it and i recently encounter a problems.
/var file system (/dev/md/rdsk/d425) is being checked.
run fsck -F ufs /dev/md/rdsk/d425
... (8 Replies)
Hi All
I have a problem on T2000 server.
bash-3.00# uname -a
SunOS 5.10 aaa Generic_120011-14 sun4v sparc SUNW,Netra-T2000After the initial solaris installation server failed to boot:
Rebooting with command: boot
Boot device: disk:b File and args:
The file just loaded does not appear... (1 Reply)
This may be a stupid question, but I don't want to take any chances.
I have a Sun T2000 in production. I want to run the "resetsc" command on the ALOM controller to active an IP address change. Will resetting ALOM affect the running OS?
Thanks (2 Replies)
Hi All
I have a Sun T2000 server. Couple of years ago I had configured and mirrored the boot drive with an other drive using hardware RAID 1 using raidctl command.
Following is the hardware RAID output.
root@oracledatabaseserver / $ raidctl
RAID Volume RAID RAID Disk... (0 Replies)
Hi folks,
I was patching Sun server (SunOS suns121 5.10 Generic_144488-17 sun4v sparc SUNW,Sun-Fire-T200) with the lateset bundle. It was completed with no errors. Server was restarted with shutdown command
(/usr/sbin/shutdown -y -i6 -g0) after patching was complete. However, after that,... (3 Replies)
Hello All
I have a SunFire T2000 running f/w 6.3.2
The activity led is in slow blink mode.
this typically indicates that the domain is down, however it is up and running.
I had this issue before and resetting the sc fixes the issue, but now it has come back. showfaults from the sc indicatess... (1 Reply)
Discussion started by: gls5161
1 Replies
LEARN ABOUT NETBSD
drvctl
DRVCTL(8) BSD System Manager's Manual DRVCTL(8)NAME
drvctl -- tool to rescan busses and detach devices on user request
SYNOPSIS
drvctl -r [-a attribute] busdevice [locator ...]
drvctl -d device
drvctl [-nt] -l [device]
drvctl [-n] -p device [property ...]
drvctl -Q device
drvctl -R device
drvctl -S device
DESCRIPTION
The drvctl program works with the drvctl(4) pseudo-driver, and allows to rescan busses and to detach drivers from devices.
The following options are available:
-a Give the interface attribute where children are to be attached to (and which defines the interpretation of the locator information).
This will only be needed in rare cases where the bus has multiple attributes. If there are multiple attributes, and one is not spec-
ified, drvctl will return an Invalid argument. In such cases, the -p option can be used to determine the available interface
attributes.
-d Detach the device driver from the device given by the device argument.
-l List the children of the device specified by the device argument. If device is not specified, list roots of the device tree instead.
Output comes in two columns. The first column is device, or ``root'' if device is not specified. The second column is the child.
-n Suppress first column in -l output. Suppress non-XML headers in -p output.
-p Get properties for the device specified by the device argument. If property is specified, the value of that property is printed,
otherwise the properties are displayed as an XML property list.
-Q Resume the ancestors of device, device itself, and all of its descendants.
-R Resume both the ancestors of device and device itself.
-r Rescan the bus given by the busdevice argument. The scan range can be restricted by an optional locator list.
-S Suspend both the descendants of device and device itself.
-t Print a tree of devices in -l output.
FILES
/dev/drvctl
SEE ALSO proplib(3), autoconf(9)BUGS
Currently, there is no good way to get information about locator lengths and default values (which is present at kernel configuration time)
out of a running kernel. Thus the locator handling is less intelligent than it could be.
BSD January 16, 2012 BSD