Sponsored Content
Operating Systems Solaris Bad magic number in disk label. Post 302946528 by MadeInGermany on Wednesday 10th of June 2015 03:56:40 AM
Old 06-10-2015
ATA transport errors?
Your disk is broken!
(Or the IDE cable is broken; but this can only happen if the box was physically treated.)
 

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
PCIIDE(4)						   BSD Kernel Interfaces Manual 						 PCIIDE(4)

NAME
pciide -- PCI IDE disk controllers driver SYNOPSIS
pciide* at pci? dev ? function ? flags 0x0000 pciide* at pnpbios? index ? DESCRIPTION
The pciide driver supports the PCI IDE controllers as specified in the "PCI IDE controller specification, revision 1.0" draft, and provides the interface with the hardware for the ata driver. Please use the chip-specific drivers for the following controllers for enhanced and DMA support: - Acard ATP850 (Ultra/33) and ATP860 (Ultra/66) IDE Controllers: acardide(4) - Acer labs M5229 IDE Controller: aceride(4) - Advanced Micro Devices AMD-756, 766, and 768 IDE Controllers: viaide(4) - Advanced Micro Devices Geode IDE Controllers: geodeide(4) - CMD Tech PCI0643, PCI0646, PCI0648, and PCI0649 IDE Controllers: cmdide(4) - Contaq Microsystems/Cypress CY82C693 IDE Controller: cypide(4) - HighPoint HPT366 Ultra/66, HPT370 Ultra/100, HPT372, and HPT374 Ultra/133 IDE controller: hptide(4) - Intel PIIX, PIIX3, and PIIX4 IDE Controllers: piixide(4) - Intel i31244 Serial ATA controller: artsata(4) - Intel 82801 (ICH/ICH0/ICH2/ICH3/ICH4/ICH5/ICH6) IDE Controllers: piixide(4) - Intel SCH IDE Controllers: schide(4) - NVIDIA nForce/nForce2 IDE Controllers: viaide(4) - OPTi 82c621 (plus a few of its derivatives) IDE Controllers: optiide(4) - Promise PDC20246 (Ultra/33), PDC20262 (Ultra/66), PDC20265/PDC20267 (Ultra100), PDC20268 (Ultra/100TX2 and Ultra/100TX2v2), Ultra/133, Ultra/133TX2 and Ultra/133TX2v2 PCI IDE controllers: pdcide(4) - Serverworks K2 SATA controllers: svwsata(4) - Silicon Image 0680 IDE controller: cmdide(4) - Silicon Image SATALink 3112 Serial ATA controller: satalink(4) - Silicon Image SteelVine 3124/3132/3531 Serial ATA II controller: siisata(4) - Silicon Integrated System 5597/5598 IDE controller: siside(4) - Symphony Labs 82C105 and Winbond W83C553F IDE controller: slide(4) - VIA Technologies VT82C586, VT82C586A, VT82C596A, VT82C686A, VT8233A, and VT8235 IDE Controllers: viaide(4) The 0x0001 flag forces the pciide driver to use DMA when there is no explicit DMA mode setting support for the controller but DMA is present. If the BIOS didn't set up the controller properly, this can cause a machine hang. The 0x0002 flag forces the pciide driver to disable DMA on chipsets for which DMA would normally be enabled. This can be used as a debugging aid, or to work around problems where the IDE controller is wired up to the system incorrectly. SEE ALSO
acardide(4), aceride(4), artsata(4), ata(4), atapi(4), cmdide(4), cypide(4), geodeide(4), hptide(4), intro(4), optiide(4), pci(4), pdcide(4), piixide(4), pnpbios(4), satalink(4), schide(4), siisata(4), siside(4), slide(4), viaide(4), wd(4), wdc(4) BSD
November 7, 2010 BSD
All times are GMT -4. The time now is 11:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy