Sponsored Content
Operating Systems Solaris Bad magic number in disk label. Post 302947443 by hicksd8 on Thursday 18th of June 2015 04:38:17 AM
Old 06-18-2015
Are you saying that there is data on this disk that you would like to save and that you have no backup?

If so, you may need to take some kind of image of the drive first (do you have any software which can do that?) so that you can recover to this position should anything we try fail.
 

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
vxconfigbackupd(1M)													       vxconfigbackupd(1M)

NAME
vxconfigbackupd - disk group configuration backup daemon SYNOPSIS
vxconfigbackupd [-l] DESCRIPTION
The vxconfigbackupd daemon automatically backs up information about a disk group's new configuration whenever the configuration is changed. OPTIONS
-l Logs backup daemon activities to the file /etc/vx/cbr/bkdaemonLog. FILES
/sbin/init.d/vxvm-recover Startup file for vxconfigbackupd. /etc/vx/cbr/bk/dgname.dgid/dgid.dginfo Location of backup file for disk group information. /etc/vx/cbr/bk/dgname.dgid/dgid.diskinfo Location of backup file for disk attributes. /etc/vx/cbr/bk/dgname.dgid/dgid.binconfig Location of backup file for binary configuration copy. /etc/vx/cbr/bk/dgname.dgid/dgid.cfgrec Location of backup file for configuration records in vxprint -m format. NOTES
The vxconfigbackup command can be used to back up a disk group's configuration manually at any desired time. The disk group configuration backup and restore utilities do not save any data in the public region. This includes file system or other application data that is configured within VxVM objects. When a disk group is destroyed, its configuration backup information (including the backup directory) is also removed. The only exception to this behavior is when the disk group is in the precommit state of restoration. The backup directory should be large enough to accommodate copies of all the currently imported disk groups. The minimum recommended size of the backup directory is P * (N + 1) megabytes, where P is the private region in megabytes (by default, 32MB), and N is the number of disk groups. The additional P megabytes is required to hold a temporary copy of the disk group configuration when a disk group is imported or a configuration change is made. The default backup directory is /etc/vx/cbr/bk. The location of the backup directory can be configured by using the vxconfigbackup -l backup_directory_path command. SEE ALSO
vxconfigbackup(1M), vxconfigrestore(1M) VxVM 5.0.31.1 24 Mar 2008 vxconfigbackupd(1M)
All times are GMT -4. The time now is 04:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy