02-26-2015
I'm afraid you overwrote critical system data during your failed resizing attempt.
Unless you know exactly what was your partition table and label like before the change, your best bet is probably to reinstall the OS then restore your data from backup.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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. Shell Programming and Scripting
In one of our internal scripts (unix.run), I have noticed that the following shebang.
#!/bin/sh -
for i in test1 test2 test3 ; do
.
.
.
Any idea what the - in the magic number stands for ?
And what impact does it have on the script ?
Continuing on the same script, I have the... (3 Replies)
Discussion started by: vino
3 Replies
3. Filesystems, Disks and Memory
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. Filesystems, Disks and Memory
LVM partition(8e type) begins with a magic number(0x4D48) - HM,
At this sector, I get the name of volume group plus two three more structures, which I am unable to decipher. So, if anyone can let me know the details of these structures.
In my case, I had made two logical volumes in my LVM... (2 Replies)
Discussion started by: ghimanshu
2 Replies
5. Solaris
/pci@if,0/pci@1,1/ide@3/dad@0,0 corrupt label wrong magic number
can u plz suggustion me (6 Replies)
Discussion started by: tirupathi
6 Replies
6. UNIX for Dummies Questions & Answers
Hello,
When I boot up my ancient SUNOS 5 system. it stops at the OK prompt and complains about a bad magic number. I have told that I need run fsck but I cannot seem to do so from the OK prompt. How can I get into a diagnostic mode so I can run fsck?
Thanks, (1 Reply)
Discussion started by: mojoman
1 Replies
7. AIX
Hello everybody:
I have a trouble running an application which connects to an Oracle server, I got this message:
Dependent module /opt/oracle/product/10.2/lib/libclntsh.so could not be loaded.
The module has an invalid magic number.
Running ldd MyApp doesn't report missing symbols, I've... (1 Reply)
Discussion started by: edgarvm
1 Replies
8. Solaris
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
9. Solaris
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
10. Solaris
This is first time post...found this forum when looking for possible solution to fix my sun pc. Just one day can't boot it already showing the following:
Boot device: disk File args:
Bad magic number in disk label
Can't open disk label package
Evaluating: boot
Can't open boot device... (40 Replies)
Discussion started by: SHuKoSuGi
40 Replies
LEARN ABOUT NETBSD
mbrlabel
MBRLABEL(8) BSD System Manager's Manual MBRLABEL(8)
NAME
mbrlabel -- update disk label from MBR label(s)
SYNOPSIS
mbrlabel [-fqrw] [-s sector] device
DESCRIPTION
mbrlabel is used to update a NetBSD disk label from the Master Boot Record (MBR) label(s) found on disks that were previously used on
DOS/Windows systems (or other MBR using systems).
mbrlabel scans the MBR contained in the very first block of the disk (or the block specified through the -s flag), then walks through every
extended partition found and generates additional partition entries for the disk from the MBRs found in those extended partitions.
Each MBR partition which does not have an equivalent partition in the disk label (equivalent in having the same size and offset) is added to
the first free partition slot in the disk label. A free partition slot is defined as one with an fstype of 'unused' and a size of zero
('0'). If there are not enough free slots in the disk label, a warning will be issued.
The raw partition (typically partition c, but d on i386 and some other platforms) is left alone during this process.
By default, the proposed changed disk label will be displayed and no disk label update will occur.
Available options:
-f Force an update, even if there has been no change.
-q Performs operations in a quiet fashion.
-r In conjunction with -w, also update the on-disk label.
-s sector Specifies the logical sector number that has to be read from the disk in order to find the MBR. Useful if the disk has remapping
drivers on it and the MBR is located in a non-standard place. Defaults to 0.
-w Update the in-core label if it has been changed. See also -r.
SEE ALSO
disklabel(8), dkctl(8), fdisk(8), mbr(8)
HISTORY
The mbrlabel command appeared in NetBSD 1.4.
BSD
April 5, 2010 BSD