Sponsored Content
Operating Systems Solaris Bad magic number in disk label. Post 302944672 by SHuKoSuGi on Thursday 21st of May 2015 06:22:44 AM
Old 05-21-2015
Hello hicksd8...thanks for the time answering. Yes we've done re-seating, also replacing the cable. The drive type is ATA. Unfortunately, we misplaced the CD. Can we download it online? Or can get it somewhere? Hoping for your response.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

bad magic number

Hi, when installing a piece of third part software I get the error "Bad magic number" at one point when it tries to use libraries from the bea tuxedo server. Am I correct that this means that the software is expecting 32bit while I'm on 64bit? Is there a way around it or can it only be solved... (5 Replies)
Discussion started by: rein
5 Replies

2. Solaris

Big UH-OH "Bad magic number in disk label"

I tried rebooting my Sun server just a few minutes ago and I got the following at boot: -- Sun Fire 280R (UltraSPARC-III+) , No Keyboard Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.5, 1024 MB memory installed, Serial #xxxxxxxxx Ethernet address... (6 Replies)
Discussion started by: deckard
6 Replies

3. Filesystems, Disks and Memory

Bad Magic Number

Dear All, i have a SCSI hard disk drive i'm installing on it solaris 5 and the workstation is sun sparc, i made an image of this H.D using Norton Ghost 6, so i took off the SCSI H.D from the sun workstation and put it on a Compaq server then i booted the server from the Norton Ghost floppy disk... (0 Replies)
Discussion started by: wesweshahaha
0 Replies

4. UNIX for Advanced & Expert Users

Bad magic number on /dev/md0

Hello All, (RHEL4) Few weeks ago I had posted a message in this forum about the problem I had when I replaced my two scsi disks and tried rebuild raid1 array. I somehow managed to up the system with working raid1 array. But the main problem persisted.. i.e when I reboot the system, mounting... (0 Replies)
Discussion started by: ravinandan
0 Replies

5. Solaris

BAD magic number in disc label...

Hello All, I m very new to this forum. i m having SUN NETRA X1 server with 40 GB HDD (Seagate) & 128 MB RAM. i m trying this server for SUN 10 Practise. As i m installing SUN 9 /10 with CD ,its giving me error after OK propmt *************************** #boot cdrom or #boot cdrom... (16 Replies)
Discussion started by: amrut_k
16 Replies

6. Solaris

Help:"Bad checksum in disk label" and "Can't open disk label package"?

Hello, I'm brand new to Sun/Solaris. I have a Sun Blade 150, with SunOS 5.8. I wanted to make a backup to prevent future data loss, so I put the disk in a normal PC with Windows XP to try to make a backup with Norton Ghost, the disk was detected, but not the file volume, so I place the disk... (6 Replies)
Discussion started by: Resadija
6 Replies

7. Solaris

Solaris 8.2 Bad magic number

I'll keep it fairly straight forward. I work with a Solaris server and magically today it decided to take a dump on me. At first it give a long list of files that couldn't be acessed before terminating the boot process and returning to the 'ok' prompt. Booting in single-user mode allowed me to run... (4 Replies)
Discussion started by: Aon
4 Replies

8. Solaris

corrupt label - wrong magic number

I have created 1 LUN. 1)LUN 00BB 200GB /dev/rdsk/c1t3d44 /dev/rdsk/c2t28d44 /dev/rdsk/c3t19d44 /dev/rdsk/c4t12d44 2) Already added the new entry into sd.conf and rebooted. 3) Already done these: powercf –q power config 4) power display dev=all I can see the new Symmetrix device.... (1 Reply)
Discussion started by: sirius20d
1 Replies

9. Solaris

Recover label, wrong magic number

Is there a way to recover label? I could install (sparc) Solaris again, but it would take a lot of time. (5 Replies)
Discussion started by: orange47
5 Replies

10. Solaris

Bad magic number error

So we have a new to us v240 server with no OS installed. It has an outdated version of OB and ALOM so before we install the OS we want to update both. We have a DVD with the latest OB patch burned on it. We do the boot cdrom command but receive the Bad Magic Number Error. Does an OS need to... (2 Replies)
Discussion started by: dunkpancakes
2 Replies
SG_SAT_PHY_EVENT(8)						     SG3_UTILS						       SG_SAT_PHY_EVENT(8)

NAME
sg_sat_phy_event - Sends an ATA READ LOG EXT command via a SAT pass through to fetch log page 11h which contains 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 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. The SATL may be in an operating system driver, in host bus adapter firmware or in some external enclosure. 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"). 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 Doug Gilbert REPORTING BUGS
Report bugs to <dgilbert at interlog dot com>. COPYRIGHT
Copyright (C) 2006-2007 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.26 December 2007 SG_SAT_PHY_EVENT(8)
All times are GMT -4. The time now is 08:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy