Sponsored Content
Operating Systems Solaris Bad magic number in disk label. Post 302949241 by hicksd8 on Wednesday 8th of July 2015 11:45:57 AM
Old 07-08-2015
You didn't answer my post#36. Did the analyse error out in a few seconds or did it run for a long time? I'm trying to ascertain whether sectors on your drive can be read or not.
 

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
mpartition(1)						      General Commands Manual						     mpartition(1)

Name
       mpartition - partition an MSDOS hard disk

Note of warning
       This  manpage  has been automatically generated from mtools's texinfo documentation, and may not be entirely accurate or complete.  See the
       end of this man page for details.

Description
       The mpartition command is used to create MS-DOS filesystems as partitions.  This is intended to be used on non-Linux systems, i.e.  systems
       where fdisk and easy access to Scsi devices are not available.  This command only works on drives whose partition variable is set.

       mpartition  -p drive mpartition -r drive mpartition -I [-B bootSector] drive mpartition -a drive mpartition -d drive mpartition -c [-s sec-
       tors] [-h heads] [-t cylinders] [-v [-T type] [-b begin] [-l length] [-f]

       Mpartition supports the following operations:

       p      Prints a command line to recreate the partition for the drive.  Nothing is printed if the partition for the drive is not defined, or
	      an inconsistency has been detected.  If verbose (-v) is also set, prints the current partition table.

       r      Removes the partition described by drive.

       I      Initializes the partition table, and removes all partitions.

       c      Creates the partition described by drive.

       a      "Activates" the partition, i.e. makes it bootable.  Only one partition can be bootable at a time.

       d      "Desactivates" the partition, i.e. makes it unbootable.

       If no operation is given, the current settings are printed.

       For partition creations, the following options are available:

       s sectors
	      The number of sectors per track of the partition (which is also the number of sectors per track for the whole drive).

       h heads
	      The  number of heads of the partition (which is also the number of heads for the whole drive).  By default, the geometry information
	      (number of sectors and heads) is figured out from neighbouring partition table entries, or guessed from the size.

       t cylinders
	      The number of cylinders of the partition (not the number of cylinders of the whole drive.

       b begin
	      The starting offset of the partition, expressed in sectors. If begin is not given, mpartition lets the partition begin at the  start
	      of the disk (partition number 1), or immediately after the end of the previous partition.

       l length
	      The  size  (length) of the partition, expressed in sectors.  If end is not given, mpartition figures out the size from the number of
	      sectors, heads and cylinders.  If these are not given either, it gives the partition the biggest	possible  size,  considering  disk
	      size and start of the next partition.

       The following option is available for all operation which modify the partition table:

       f      Usually,	before	writing  back  any  changes to the partition, mpartition performs certain consistenct checks, such as checking for
	      overlaps and proper alignment of the partitions.	If any of these checks fails, the partition table is not changes.  The	-f  allows
	      you to override these safeguards.

       The following options are available for all operations:

       v      Together with -p prints the partition table as it is now (no change operation), or as it is after it is modified.

       vv     If the verbosity flag is given twice, mpartition will print out a hexdump of the partition table when reading it from and writing it
	      to the device.

       The following option is available for partition table initialization:

       B bootSector
	      Reads the template master boot record from file bootSector.

See Also
       Mtools' texinfo doc

Viewing the texi doc
       This manpage has been automatically generated from mtools's texinfo documentation. However, this process is only  approximative,  and  some
       items, such as crossreferences, footnotes and indices are lost in this translation process.  Indeed, these items have no appropriate repre-
       sentation in the manpage format.  Moreover, not all information has been translated into the manpage version.  Thus I strongly  advise  you
       to use the original texinfo doc.  See the end of this manpage for instructions how to view the texinfo doc.

       *      To generate a printable copy from the texinfo doc, run the following commands:

		     ./configure; make dvi; dvips mtools.dvi

       *      To generate a html copy,	run:

		     ./configure; make html

	      A premade html can be found at: `http://mtools.linux.lu' and also at: `http://www.tux.org/pub/knaff/mtools'

       *      To generate an info copy (browsable using emacs' info mode), run:

		     ./configure; make info

       The  texinfo  doc looks most pretty when printed or as html.  Indeed, in the info version certain examples are difficult to read due to the
       quoting conventions used in info.

mtools-3.9.8							      02Jun01							     mpartition(1)
All times are GMT -4. The time now is 08:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy