Sponsored Content
Operating Systems Solaris Bad magic number in disk label. Post 302952619 by hicksd8 on Thursday 20th of August 2015 11:56:06 AM
Old 08-20-2015
That sounds like the disk is NOT communicating. Analyze should take hours to run!!!

You've reseated the drive cables, etc so time to get the drive tested. Does it sound okay? Is it spinning? You may have a dead drive here (as MadeInGermany has already said).

Can you or a friend test the drive (perhaps in another machine) without writing to it. Just see if it's recognised.
 

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
HD(4)							     Linux Programmer's Manual							     HD(4)

NAME
hd - MFM/IDE hard disk devices DESCRIPTION
The hd* devices are block devices to access MFM/IDE hard disk drives in raw mode. The master drive on the primary IDE controller (major device number 3) is hda; the slave drive is hdb. The master drive of the second controller (major device number 22) is hdc and the slave hdd. General IDE block device names have the form hdX, or hdXP, where X is a letter denoting the physical drive, and P is a number denoting the partition on that physical drive. The first form, hdX, is used to address the whole drive. Partition numbers are assigned in the order the partitions are discovered, and only non-empty, non-extended partitions get a number. However, partition numbers 1-4 are given to the four partitions described in the MBR (the `primary' partitions), regardless of whether they are unused or extended. Thus, the first logi- cal partition will be hdX5. Both DOS-type partitioning and BSD-disklabel partitioning are supported. You can have at most 63 partitions on an IDE disk. For example, /dev/hda refers to all of the first IDE drive in the system; and /dev/hdb3 refers to the third DOS `primary' partition on the second one. They are typically created by: mknod -m 660 /dev/hda b 3 0 mknod -m 660 /dev/hda1 b 3 1 mknod -m 660 /dev/hda2 b 3 2 ... mknod -m 660 /dev/hda8 b 3 8 mknod -m 660 /dev/hdb b 3 64 mknod -m 660 /dev/hdb1 b 3 65 mknod -m 660 /dev/hdb2 b 3 66 ... mknod -m 660 /dev/hdb8 b 3 72 chown root:disk /dev/hd* FILES
/dev/hd* SEE ALSO
mknod(1), chown(1), mount(8), sd(4) Linux 1992-12-17 HD(4)
All times are GMT -4. The time now is 04:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy