Sponsored Content
Full Discussion: M5000 won't power up
Special Forums Hardware M5000 won't power up Post 303018942 by DukeNuke2 on Tuesday 19th of June 2018 02:09:58 PM
Old 06-19-2018
Quote:
Originally Posted by goya
no support since its older. just a company that swaps parts. I did try the power on each domain and same result , did no reset fault, what command does that? I will try and find it.
From the XSCF use the command version -c xcp and send the output. Depending on the version you might not be able to reset the error...
This User Gave Thanks to DukeNuke2 For This Post:
 

9 More Discussions You Might Find Interesting

1. AIX

won't mount /usr...won't boot fully

Hello: NOOB here. I attempted to use smit mkcd. Failed on first attempt, not enough space. 2nd attempt tried to place iso on /usr, not enough space there. Cleanup ran for about 5 minutes after aborting. Now AIX won't boot. LCD display on 7029-6E3 says: 0517 MOUNT /USR. Attempted to boot from CD... (11 Replies)
Discussion started by: bbird
11 Replies

2. Solaris

M5000 Question

Hi, I 've a fully loaded M5000 which i would like to partition in 4 domains but i have a concern that since we have only 4 internal disks how can we partition the box in for domains with 2 disks ( mirrored ) in each domain. Should i go ahead with 1 Lun from SAN and 1 internal disk for each of 4... (3 Replies)
Discussion started by: fugitive
3 Replies

3. Solaris

M5000 Question

Hi i 've a M5000 running 2 domains in my Lab with following hardconf SPARC Enterprise M5000; Memory_Size:128 GB; +-----------------------------------+------------+ | FRU | Quantity | +-----------------------------------+------------+ | MBU_B... (3 Replies)
Discussion started by: fugitive
3 Replies

4. Solaris

Unable to start SunVTS on M5000

Please advise. Thank you bash-3.00# cd /usr/sunvts/bin/ bash-3.00# ls bios.bin iobushangscript.sh stopsunvts vtsprobe cmos.bin javabridge.jar sunlink vtsreportgenerate dispatcher loadVtsServer svmVolDiskList vtstalk env6test... (6 Replies)
Discussion started by: incredible
6 Replies

5. Hardware

Sun/Oracle M5000 Question

I have an M5K with disk issues I'm trying to troubleshoot, and it's causing me some confusion. I know the host has four on-board HDDs, but the format command's output shows c0t0d0, c0t1d0, c3t0d0, and c3t1d0. cfgadm -al shows c0t3d0 as the DVD-ROM drive, and c1 and c2 as SAN disks. Confused yet? ... (2 Replies)
Discussion started by: desertdenizen
2 Replies

6. IP Networking

M5000 Xscf

I took over an M5000 and have a jumper server with a nic to connect to the console IP of an M5000. access via ssh user@ip. it was working fine, another person can connect remotely on the subnet, but when I ssh,it just hangs and then times out. so my question is, any ideas of what I might... (4 Replies)
Discussion started by: rrodgers
4 Replies

7. Solaris

M5000 fails to boot

I have an m5000 that Is down. I have access to XSCF> and was able to get to the ok prompt. However, on >ok boot it failed to boot. erred with : svc.startd: svc:/system/device/fc-fabric:default: Method "/lib/svc/method/fc-fabric" failed due to signal KILL. Nov 29... (3 Replies)
Discussion started by: goya
3 Replies

8. AIX

IBM Power 740 won't boot after firmware update

A team member installed the wrong version of License Code on a Power 740 system used in our Development environment. The system will no longer boot. Does anyone have IBM documentation or experience to share on recovering a system that currently reports "Unsupported License Code version... (1 Reply)
Discussion started by: kevinedailey
1 Replies

9. UNIX for Beginners Questions & Answers

Bash script won't run because hardware won't produce display

Can anyone offer any advice on how to modify the script below to work on a new system we have, that has no graphics capability? We admin the system through a serial RAS device. I've tried running the below script through the RAS and through an ssh -X session. It failed with something like "GTK... (3 Replies)
Discussion started by: yelirt5
3 Replies
SG_RESET(8)							     SG3_UTILS							       SG_RESET(8)

NAME
sg_reset - sends SCSI device, target, bus or host reset; or checks reset state SYNOPSIS
sg_reset [--bus] [--device] [--help] [--host] [--no-esc] [--target] [--verbose] [--version] DEVICE DESCRIPTION
The sg_reset utility with no options (just a DEVICE) reports on the reset state (e.g. if a reset is underway) of the DEVICE. When given a --device, --target, --bus or --host option it requests a device, target, bus or host reset respectively. A device reset is applied to the Logical Unit (LU) corresponding to DEVICE. It is most likely implemented by a Low level Driver (LLD) in Linux as a LOGICAL UNIT RESET task management function. The ability to reset a SCSI target was added in Linux kernel 2.6.27 . A LLD may send Low level Drivers (LLDs) the I_T NEXUS RESET task man- agement function. Alternatively it may use a transport mechanism to do the same thing (e.g. a hard reset on the link containing a SAS tar- get). In the Linux kernel 2.6 and 3 series this utility can be called on sd, sr (cd/dvd), st or sg device nodes; if the user has appropriate per- missions. Users of this utility can check whether a reset recovery is already underway before trying to send a new reset with this utility. Calling this utility with no options, just the DEVICE, will do such a check. OPTIONS
-b, --bus attempt a SCSI bus reset. A bus reset is a SCSI Parallel Interface (SPI) concept not found in modern transports. A recent LLD may implement it as a series of resets on targets that might be considered as siblings to the target on the DEVICE path. -d, --device attempt a SCSI device reset. This would typically involve sending a LOGICAL UNIT RESET task management function to DEVICE. -h, --help print the usage message then exit. -H, --host attempt a host reset. The "host" in this context is often called a Host Bus Adapter (HBA) and contains one or more SCSI initiators. -N, --no-esc without this option, if a device reset (--device) fails then it will escalate to a target reset. And if a target reset (--target) fails then it will escalate to a bus reset. And if a bus reset (--bus) fails then it will escalate to a host reset. With this option only the requested reset is attempted. An alternate option name of --no-escalate is also accepted. -t, --target attempt a SCSI target reset. A SCSI target contains one or more LUs. This would typically involve sending a I_T NEXUS RESET task management function to DEVICE There may be a transport action that is equivalent (e.g. in SAS a hard reset on the link that con- tains the target). -v, --verbose increase the degree of verbosity (debug messages). -V, --version prints the version string then exits. NOTES
The error recovery code within the Linux kernel (SCSI mid-level) when faced with a SCSI command timing out and no response from the device (LU) does the following. First it tries a device reset and if that is not successful tries a target reset. If that is not successful it tries a bus reset. If that is not successful it tries a host reset. The "device,target,bus,host" order is the reset escalation that the --no-esc option attempts to stop. In large storage configurations the escalation may be (very) undesirable. This utility calls the SG_SCSI_RESET ioctl and as of lk 3.10.7 the --no-esc option is not supported. Patches to implement this functional- ity have not been accepted. If you want it, post your concern to linux-scsi@vger.kernel.org which is the linux-scsi list. SAM-4 and 5 define a hard reset, a LOGICAL UNIT RESET and a I_T NEXUS RESET. A hard reset is defined to be a power on condition, a microcode change or a transport reset event. LOGICAL UNIT RESET and I_T NEXUS RESET can be requested via task management functions (and support for LOGICAL UNIT RESET is mandatory). In Linux the SCSI subsystem leaves it up to the LLDs as to exactly what type (if any) of reset is performed. The "bus reset" is SCSI Parallel Interface (SPI) concept that may not map well to recent SCSI transports so it may be a dummy operation. A "host reset" attempts to re-initialize the HBA that the request passes through en route to the DEVICE. Note that a "host reset" and a "bus reset" may cause collateral damage. This utility does not allow individual SCSI commands to be aborted. SAM-4 defines ABORT TASK and ABORT TASK SET task management functions for that. Prior to SAM-3 there was a TARGET RESET task management function. And in SAM-4 I_T NEXUS RESET appeared which seems closely related: the "I_T" stands for Initiator-Target. Transports may have their own types of resets not supported by this utility. For example SAS has a link reset in which both ends of a physical link (e.g. between a SAS expander and a SAS tape drive) renegotiate their connection. Prior to version 0.57 of this utility the command line had short options only (e.g. -d but not --device). Also -h invoked a host reset while in the current version -h is equivalent to --help and both -H and --host invoke a host reset. For backward compatibility define the environment variable SG3_UTILS_OLD_OPTS or SG_RESET_OLD_OPTS . In this case -h will invoke a host reset and the output will be verbose as it was previously (equivalent to using the --verbose option now). For example: SG_RESET_OLD_OPTS=1 sg_reset -h /dev/sg1 sg_reset: starting host reset sg_reset: completed host reset AUTHORS
Written by Douglas Gilbert. COPYRIGHT
Copyright (C) 1999-2013 Douglas Gilbert This software is distributed under the GPL version 2. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR- POSE. sg3_utils-1.37 August 2013 SG_RESET(8)
All times are GMT -4. The time now is 10:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy