Sponsored Content
Full Discussion: Help with booting SUN Box
Operating Systems Solaris Help with booting SUN Box Post 302374263 by incredible on Tuesday 24th of November 2009 02:09:43 AM
Old 11-24-2009
reset-all at the OBP and try again. If failed, try using a different dvd.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Sun Booting problem

I was trying to test run a /bin/bash script i had just written when my monitor suddenly went blank.I had to shut down the machine from the systems main power. I was unable to boot afterwards and soo i went for the interactive boot process by typing boot -a. I succeded in the first stage of the... (1 Reply)
Discussion started by: lealyz
1 Replies

2. UNIX for Dummies Questions & Answers

Booting off of a cd on a Sun Box

I have a Sun box that I am trying to get started up, but everytime it will crap out because it is bound to an NIS domain that no longer exists. The Master for that domain was put out of commission. It was suggested to me that I could boot off of the Installation cd for the OS (Solaris 8) and... (4 Replies)
Discussion started by: Jody
4 Replies

3. UNIX Benchmarks

move from an HP box to Sun Box

I could write a long spec here, however.....we are looking at investing in one of thise shiny blue Sun V440's. Rediculousely expensive, however possibly more cost effective over time...too much time listening to salesmen. To the point has anyone actually performed a comparison for Oracle running on... (4 Replies)
Discussion started by: luker
4 Replies

4. Solaris

Booting problem on Sun 3500

Hi, I have a Sun 3500 server on which i installed solaris 8 and have also installed veritas 4.0 on it. i dont know why from the time i have built this server whenever i try to boot it, the server doesnot come back smooth.... i have got to connect a laptop to the serial port of the server and... (3 Replies)
Discussion started by: ishila
3 Replies

5. UNIX for Dummies Questions & Answers

difference between AIX box and Sun Solaris box

Hi, I need a clarification. Is there any difference between AIX box and Sun Solaris box? The bzip command with -c option works in AIX box and the same does not work in Sun Solaris box. Can anyone please explain if there is an implementation difference in both these boxes for the shell... (1 Reply)
Discussion started by: nisha4680
1 Replies

6. Solaris

Sun Solaris Ultra 10 Not booting!

Hello I have Sun Ultra 10 with Solaris 7 installed on it. Sometimes back after that the machine use to get hang .Even after rebooting the system was not booting. I have manually switch on /off many times from the power board itself .Once in a while it use to boot .After... (12 Replies)
Discussion started by: turki_00
12 Replies

7. UNIX for Dummies Questions & Answers

Sun Server: loop while booting

Hello Everyone, First: English is not my native language, sorry. I was given today on the work of a SUN Enterprse 220r, then I was going to install Debian-sparc, but the server remains in the boot process in a loop of the Fork interpreter depends (begin to load with power-up) starts the... (4 Replies)
Discussion started by: snap
4 Replies

8. AIX

AIX 5.1 Box not booting

Quick backgound. We just moved the Datacenter. I attempted to boot one of our older AIX machines backup and it stops at a 518 Error code. Which is fine I need to run fsck on the volumes. The issue is I can't find the original media with the appropriate Date that was originally installed(previous... (1 Reply)
Discussion started by: jcompguru
1 Replies

9. Solaris

Booting problem on Sun 3500

Booting problem on Sun 3500 Hi, I have a Sun 3500 server on which i installed solaris 5.2 installed . i dont know why from the time i have built this server whenever i try to boot it, the server doesnot come back smooth.i got a message Sync file system than restart some times showing ok... (2 Replies)
Discussion started by: najeer
2 Replies

10. Solaris

Sun Server not booting into OS

Hello I have an old sun fire v250 server that I am trying to revive. I am trying to boot it from cdrom to install the OS (Solaris 10). The original data in the disk is corrupt and I am trying to do a new clean install. However I encounter the following errors. Does it look like the disk itself... (1 Reply)
Discussion started by: br1an
1 Replies
SG_SAT_PHY_EVENT(8)						     SG3_UTILS						       SG_SAT_PHY_EVENT(8)

NAME
sg_sat_phy_event - use ATA READ LOG EXT via a SAT pass-through to fetch SATA phy event counters SYNOPSIS
sg_sat_phy_event [--ck_cond] [--extend] [--help] [--hex] [--ignore] [--len={16|12}] [--raw] [--reset] [--verbose] [--version] DEVICE DESCRIPTION
This utility sends an ATA READ LOG EXT with the log page ("address") set to 11h to DEVICE and outputs the response. Log page 11h is defined in the SATA 2.5 standard and contains phy event counters. Rather than send this command directly to the DEVICE, are sent via a SCSI trans- port which is assumed to contain a SCSI to ATA Translation (SAT) Layer (SATL). The SATL may be in an operating system driver, in host bus adapter firmware or in some external enclosure. The SAT standard (SAT ANSI INCITS 431-2007, prior draft: sat-r09.pdf at www.t10.org) defines two SCSI "ATA PASS-THROUGH" commands: one using a 16 byte "cdb" and the other with a 12 byte cdb. This utility defaults to using the 16 byte cdb variant. SAT-2 is also a standard: SAT-2 ANSI INCITS 465-2010 and the draft prior to that is sat2r09.pdf . The SAT-3 project has started and the most recent draft is sat3r01.pdf . OPTIONS
Arguments to long options are mandatory for short options as well. -c, --ck_cond sets the CK_COND bit in the ATA PASS-THROUGH SCSI cdb. The default setting is clear (i.e. 0). When set the SATL should yield a sense buffer containing a ATA Result descriptor irrespective of whether the command succeeded or failed. When clear the SATL should only yield a sense buffer containing a ATA Result descriptor if the command failed. -e, --extend sets the EXTEND bit in the ATA PASS-THROUGH SCSI cdb. The default setting is clear (i.e. 0). When set a 48 bit LBA command is sent to the device. This option has no effect when --len=12. -h, --help outputs the usage message summarizing command line options then exits. Ignores DEVICE if given. -H, --hex outputs the ATA READ LOG EXT response in hex. The default action (i.e. without any '-H' options) is to output the response in hex, grouped in 16 bit words (i.e. the ATA standard's preference). When given once, the response is output in ASCII hex bytes (i.e. the SCSI standard's preference). When given twice (i.e. '-HH') the output is in hex, grouped in 16 bit words, the same as the default but without a header. -i, --ignore usually the phy counter identifier names are decoded. When this option is given, the numeric value of the identifier is output, the vendor flag, the data length (in bytes) and the corresponding value. -l, --len={16|12} this is the length of the SCSI cdb used for the ATA PASS-THROUGH commands. The argument can either be 16 or 12. The default is 16. The larger cdb size is needed for 48 bit LBA addressing of ATA devices. On the other hand some SCSI transports cannot convey SCSI commands longer than 12 bytes. -r, --raw output the ATA READ LOG EXT response in binary. The output should be piped to a file or another utility when this option is used. The binary is sent to stdout, and errors are sent to stderr. -R, --reset reset the counters after the current values are returned, decoded and displayed. -v, --verbose increases the level or verbosity. -V, --version print out version string NOTES
The SCSI ATA PASS-THROUGH (12) command's opcode is 0xa1 and it clashes with the MMC set's BLANK command used by cd/dvd writers. So a SATL in front of an ATAPI device that uses MMC (i.e. has peripheral device type 5) probably should treat opcode 0xa1 as a BLANK command and send it through to the cd/dvd drive. The ATA PASS-THROUGH (16) command's opcode (0x85) does not clash with anything so it is a better choice. In the 2.4 series of Linux kernels the DEVICE must be a SCSI generic (sg) device. In the 2.6 series block devices (e.g. disks and ATAPI DVDs) can also be specified. For example "sg_inq /dev/sda" will work in the 2.6 series kernels. From lk 2.6.6 other SCSI "char" device names may be used as well (e.g. "/dev/st0m"). Prior to lk 2.6.29 USB mass storage limited sense data to 18 bytes which made the --ck_cond option yield strange (truncated) results. EXIT STATUS
The exit status of sg_sat_identify is 0 when it is successful. Otherwise see the sg3_utils(8) man page. AUTHOR
Written by Douglas Gilbert REPORTING BUGS
Report bugs to <dgilbert at interlog dot com>. COPYRIGHT
Copyright (C) 2006-2013 Douglas Gilbert This software is distributed under a FreeBSD license. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR- POSE. SEE ALSO
sg_sat_identify(sg3_utils), smp_rep_phy_err_log(smp_utils), sdparm(sdparm), hdparm(hdparm) sg3_utils-1.37 June 2013 SG_SAT_PHY_EVENT(8)
All times are GMT -4. The time now is 07:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy