Bad magic number in super-block while trying to open /dev/sda2

hello,
So I've a linux partition, and then I wanted to install a Windows copy. I've only 1 HDD with differents partition into it:
sda5 (swap)
sda6 /user
sda7/var
sda8 / (which contain the boot and root of course)
sda3 /home
sda2 NTFS (windows xp)
So, as I had linux installed before windows, I had to make my sda2 NTFS (87) under my cfdisk. Then, I went to install windows, everything worked fine, windows booted with his boot system, but I had to restore grub with my archlinux live cd:
grub> find /boot/grub/stage1
grub>root (hd0,7)
grub>setup (hd0)
everything worked successfully, my grub loaded till while booting archlinux I got this error:
couldn't find ext2 superblock, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sda2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
What I tried is to run the e2fsck -b 8193 /dev/sda2 but right after that, I thought about it, this isn't linux partition so of course, the superblock isn't the same as they are ntfs type from widnows?
I've read on some forum but unfortunately didn't solve my problem, if anyone has any suggestion before I format the NTFS partition, I'd really appreciate it.
best regards, maz

what I think it happened, is that after installing windows your partitions numbers got twisted a bit. What you have to do is to edit /etc/fstab, and check out your linux and swap partitions mounting entries, I believe you just have to change the number of /dev/sda[number] coresponding to your linux partition in fstab
If you can't solve it, post the output of
fdisk -l
and
cat /etc/fstab
Last edited by I'mGeorge (2011-07-21 20:53:31)

Similar Messages

E2fsck: Bad magic number in super-block

e2fsck: Bad magic number in super-block while trying to open /dev/hda1
Yup, a very tricky one this is. I did the following:
[root@(none)~]#e2fsck /dev/hda1
e2fsck 1.40.2 (12-jul-2007)
/dev/hda1: clean, 310310/4702208 files, 8118002/9396009 blocks
What can I do to fix the super-block? I unable to boot up my system right now, and I can't afford to format my disk.
I have systemrescuedisk with the TestDisk application at hand(if needed?).

B wrote:There is a backup superblock every 8192 blocks if i'm correct. So the next one is at 8193. Try telling e2fsck to use that to fix your partition.
I've tried that, with no luck I'm afraid. So I've gotten more serious and.
With Testdisk I managed to indentify these superblocks.
[Superblocks] where * means it has been e2fsck'ed
0, blocksize=4096*
32768, blocksize=4096*
98304, blocksize=4096*
163840, blocksize=4096*
229376, blocksize=4096*
294912, blocksize=4096*
819200, blocksize=4096*
884736, blocksize=4096*
1605632, blocksize=4096*
2654208, blocksize=4096*
umount /dev/hda1
e2fsck -b 32768 /dev/hda1
/dev/hda1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
<4 minutes later>
I get the question:
Free inodes count wrong for group #1 (ie. 32254, counted=231)
Fix<y>? y
This question got repeated #286 times, where I answered the same (y) each time.
/dev/hda1: ********* FILE SYSTEM WAS MODIFIED ************
/dev/hda1: ********* REBOOT LINUX **************
/dev/hda1: 310310/4702208 files (1.5% non-contiguous), 8118002/9396009 blocks
So i rebooted... but still the same error occurs during kernel boot. So now I figured I had
to do the same with 98304 and so forth. YUP! I was right, this superblock was dirty too.
e2fsck -b 98304 /dev/hda1
answer yes to all. Reboot, and repeat with 162840. Until your kernel manages to mount
your disk cleanly and hopefully boot up.
Sadly when I e2fsck -b 98304 /dev/hda1 yet again just to check, it still claims to be dirty.
Now I'm kinda back to where I started.
I will look further into if testdisk can provide some automagic solution to my problem.
Pointers is apprecieted!

Bad Magic Number error trying to deploy WAR file from Netweaver Studio

We hae an application that runs fine as a WAR in both Tomcat and Weblogic and we are trying to deploy it on Netweaver. I tried both to use the External deployment archives and the Workspace Deployable Archives. In both cases, the deployment fails with error:
Bad magic number, found 0x80CCF1C3, expected 0xCAFEBABE.
I know the server is working because I can deploy a very simple test application with no errors. The server is a new installation of 7.1.
Any help on how to get past this error or how to troubleshoot further is appreciated.

Looks like it's complaining about a missing shared library. Check weblogic.xml for library-ref elements and make sure the domain you are deploying to has those libraries deployed.

OCFS2 bad magic number

Hello.
Do anybody know about what doing with this error:
mount /dev/sde /raid/4
mount.ocfs2: Bad magic number in inode while trying to determine heartbeat information
fsck.ocfs2 /dev/sde
fsck.ocfs2 1.6.4
fsck.ocfs2: Bad magic number in inode while initializing the DLM
sudo debugfs.ocfs2 /dev/sde
debugfs.ocfs2 1.6.4
debugfs: ls //
ls: Bad magic number in inode while checking directory at block 66
debugfs: stats
Revision: 0.90
Mount Count: 0   Max Mount Count: 20
State: 0   Errors: 0
Check Interval: 0   Last Check: Sat Oct 18 06:30:52 2014
Creator OS: 0
Feature Compat: 3 backup-super strict-journal-super
Feature Incompat: 592 sparse inline-data xattr
Tunefs Incomplete: 0
Feature RO compat: 1 unwritten
Root Blknum: 65   System Dir Blknum: 66
First Cluster Group Blknum: 32
Block Size Bits: 12   Cluster Size Bits: 17
Max Node Slots: 16
Extended Attributes Inline Size: 256
Label: mediadisk4
UUID: 1126B3D209AA4BE088260B2A590AB995
Hash: 2997730071 (0xb2adbb17)
DX Seed[0]: 0x00000000
DX Seed[1]: 0x00000000
DX Seed[2]: 0x00000000
Cluster stack: classic o2cb
Inode: 2   Mode: 00   Generation: 2716855348 (0xa1efec34)
FS Generation: 2716855348 (0xa1efec34)
CRC32: 00000000   ECC: 0000
Type: Unknown   Attr: 0x0   Flags: Valid System Superblock
Dynamic Features: (0x0)
User: 0 (root)   Group: 0 (root)   Size: 0
Links: 0   Clusters: 213645733
ctime: 0x50bf9210 -- Wed Dec 5 22:27:28 2012
atime: 0x0 -- Thu Jan 1 03:00:00 1970
mtime: 0x50bf9210 -- Wed Dec 5 22:27:28 2012
dtime: 0x0 -- Thu Jan 1 03:00:00 1970
ctime_nsec: 0x00000000 -- 0
atime_nsec: 0x00000000 -- 0
mtime_nsec: 0x00000000 -- 0
Refcount Block: 0
Last Extblk: 0   Orphan Slot: 0
Sub Alloc Slot: Global   Sub Alloc Bit: 65535
Thanks for any help.

This looks to be filesystem corruption. The reason the fsck's don't find anything is they are really _not_ doing any checking. In the filesystem is an unmounted-cleanly flag. This flag is set when the umount(1) is done. If the system were to crash with the filesystem still mounted, this unmounted-cleanly flag would not be set, so the system would consider the filesystem to need checking: no unmounted-cleanly flag, fsck has work to do; unmounted-cleanly flag set means fsck does nothing.
Be sure the filesystem is unmounted all around the cluster before attempting to repair the filesystem.
So do this:
    # fsck.ocfs2 -f /path/to/device/partition
The "-f" switch forces fsck.ocfs2 to ignore the state of the "unounted-cleanly" flag and actually perform its tests.
Does this repair the problem?

OCFSV2 : mount.ocfs2: Bad magic number in inode

Hi everyone,
DUe to high load I/O, i can't mount my ocfsV2 partition :
mount.ocfs2: Bad magic number in inode while trying to determine heartbeat information
marge:~# fsck.ocfs2 /dev/sdc1
fsck.ocfs2: Bad magic number in inode while initializing the DLM
The disk is an iscsi device, there are no block damaged.
I try to modify the signature with bvi but the result is the same.
The disk containt image file created with dd (Virtual machine).
Do you have a software or a workaround to recover my vm's ?
Or i must consider to format my parttion ?
Thank you

I know , i wan't to switch to Linux forum but how to do that ? :-)
marge:~# modinfo ocfs2
filename: /lib/modules/2.6.26-2-xen-amd64/kernel/fs/ocfs2/ocfs2.ko
license: GPL
author: Oracle
version: 1.5.0
description: OCFS2 1.5.0
srcversion: C692B48692BFC8597E4D7A7
depends: jbd,ocfs2_stackglue,ocfs2_nodemanager
vermagic: 2.6.26-2-xen-amd64 SMP mod_unload modversions Xen
I created the filesystem with debian :
mkfs.ocfs2 /dev/sdc1
By default it create 4K cluster size. And it make 6 backup off superblock.
But recover superblock doesn"t work :
marge:~# fsck.ocfs2 -r 1 /dev/sdc1
[RECOVER_BACKUP_SUPERBLOCK] Recover superblock information from backup block#262144? <n> y
fsck.ocfs2: Bad magic number in inode while initializing the DLM
marge:~# debugfs.ocfs2 -R stats /dev/sdc1
     Revision: 0.90
     Mount Count: 0 Max Mount Count: 20
     State: 0 Errors: 0
     Check Interval: 0 Last Check: Thu May 7 16:26:37 2009
     Creator OS: 0
     Feature Compat: 1 BackupSuper
     Feature Incompat: 16 Sparse
     Tunefs Incomplete: 0 None
     Feature RO compat: 1 Unwritten
     Root Blknum: 5 System Dir Blknum: 6
     First Cluster Group Blknum: 3
     Block Size Bits: 12 Cluster Size Bits: 12
     Max Node Slots: 4
     Label:
     UUID: 3677066B5C7B424BB79FE30764552B57
     Cluster stack: classic o2cb
     Inode: 2 Mode: 00 Generation: 3020404948 (0xb407b8d4)
     FS Generation: 3020404948 (0xb407b8d4)
     Type: Unknown Attr: 0x0 Flags: Valid System Superblock
     User: 0 (root) Group: 0 (root) Size: 0
     Links: 0 Clusters: 52432135
     ctime: 0x4a02ef9d -- Thu May 7 16:26:37 2009
     atime: 0x0 -- Thu Jan 1 01:00:00 1970
     mtime: 0x4a02ef9d -- Thu May 7 16:26:37 2009
     dtime: 0x0 -- Thu Jan 1 01:00:00 1970
     ctime_nsec: 0x00000000 -- 0
     atime_nsec: 0x00000000 -- 0
     mtime_nsec: 0x00000000 -- 0
     Last Extblk: 0
     Sub Alloc Slot: Global Sub Alloc Bit: 65535
debugs say superblock is ok but unable to mount the partition :
mount.ocfs2: Bad magic number in inode while trying to determine heartbeat information

Mount.ocfs2 bad magic number in superblock

i get the following error: "mount.ocfs2: Bad magic number in superblock while opening device /dev/sdb1 .kindly help

Hi,
Did you already tried use the search of forum:
https://forums.oracle.com/forums/search.jspa?threadID=&q=Bad+magic+number+in+superblock+while+opening+device&objID=c509&dateRange=all&userID=&numResults=15
Re: mount command is not working for ocfs folder
If the search does not help you can continue on this thread.
Regards,
Levi Pereira

Bad magic number

I have an applet that i am trying to load in a JSP
<applet name="MyTestApplet" code="mypackage.MyTestApplet.class" >
</applet>
mypackage/MyTestApplet.class is under the approot/pages directory and the jsp is also in the same directory.
whenever the jsp is called and applet does not get inited and the error i see is a ClassFormatError: Bad magic number
Please help.. this is extremely urgent.
Thanks in advance for any input anyone may have.
The appserver i am using is SunONE

First the <applet tag is depreciated, you should use <object instead (w3c has depreciated applet for quite
some time now).
When I see the tag you don't use a jar package (archive is missing) so let's pretend the url to your page is
http://mysite/mypage.jsp
the mypage.jsp contains the applet so the url to the applet is:
http://mysite/mypackage/MyTestApplet.class
can you download the file using a browser?
you can do this by saving the following line in a html file and right click it then sava target
right click and save target as
After downloading is the file the same as the file on the web server?
The reason I ask this is because I got the bad magic number when a jar was loaded through a proxy.
The proxy did something with the jar file making it corrupt. I think your problem has something to do with
the way your web server is serving the applet or (proxy) something between the client and the server.

JVM issue with applet - Duplicate Key in Parameter Table - Bad Magic Number

Hey, I have Googled this one to death and have seen a few vague references to this problem, but nothing I can relate back as solution.
I wonder if I need to tell the customer to reinstall the OS and, ultimately, the JRE. I'm just looking for a little guidance on what any of you may think. Am I missing a setting or something?
The user is trying to download an applet with IE with 1.3.1_16 and Firefox 1.07 with the Java Embeded Plug-in.
Even though JRE 1.3.1_16, 1.4.2_09 and 1.5 are all installed and Firefox has the JEP also installed, Firefox still wants to use 1.3.1_16 as does IE. I'm guessing that the JEP didn't work.
They can't use Safari which does seem to be using 1.4.2_09 because their RSA ID won't authenticate through it.
On my machine, when I run with the same OS,browsers, and Java 2 plug-ins, I can successfully load the applet.
This is the error that the user gets in the java console is:
Duplicate key in parameter table: code using the htmlAttribute.
first: com.ibm.eNetwork.HOD.HostOnDemand
second: com.ibm.eNetwork.HOD.HostOnDemand.class
java.lang.ClassFormatError: com/ibm/eNetwork/HOD/HostOnDemand (Bad magic number) at java.lang.ClassLoader.defineClass0(NativeMethod)
at java.lang.ClassLoader.defineClass(ClassLoader.java:488)...
Would you reinstall the OS and Java? or look at another setting? or look at the JEP installation again?
Thank you.

Without reading the full post (sorry for that) my guess is that the applet needed to be fetched through a
proxy, the proxy corrupts the applet because it's signed (finjan is one that does that).
The reason why a proxy would do so is because the default settings of sun jre will ask the user the
"do you trust" question to the user which could result in the user loading an applet that is allowed to do
anything the programmer wants (4us, spyware, nasty stuff).
Try to do the following:
1. create a html file locally with the following content:
rightclick and save target as
2. open the page, right click the link and save the file
3. apen the file with an unzip programm (winzip) and check if the content has changed.
4. If the content has changed than the proxy might have done this, contact the system administrator
It might allso have been done by a firewall installed locally.

Bad Magic Number in Disk Label & DiskSuite

Envrionment:
E450
Solaris 8
DiskSuite 4.2.1
16 disks
Because of a power failure, after reboot one of the disks has bad magic number in its disk label. The slice was in a mirror. DiskSuite has hot spares and one of them took over the failed slice. I am trying to figure out how to get it back to where it was.
I think I should use 'format' to recover the disk label from the backup label. However, once the label is recovered, how do I make it stop using the hotspare and have the failed slice join back to the mirror?
Sorry if this is basic question, I am relatively new to Sun/Solaris and I just took over the E450.
Thanks,

Envrionment:
E450
Solaris 8
DiskSuite 4.2.1
16 disks
Because of a power failure, after reboot one of the
disks has bad magic number in its disk label. The
slice was in a mirror. DiskSuite has hot spares and
one of them took over the failed slice. I am trying to
figure out how to get it back to where it was.
I think I should use 'format' to recover the disk
label from the backup label. However, once the label
is recovered, how do I make it stop using the hotspare
and have the failed slice join back to the mirror?
Sorry if this is basic question, I am relatively new
to Sun/Solaris and I just took over the E450.
Thanks,Since the host spare took over then you're free to repair/replace the bad drive. In this case you could check the drive using format and partition to view the partitions. If the label is bad then I would suspect the drive is still good and a simple format>label and save command would repair the label. Then once this is done if all goes well then the system should rebuild the drive and the hot spare will not longer be used. The system should regonize the drive as a replacement and rebuild it then stop using the hot spare.
Michael

Java.lang.ClassFormatError: HTML (Bad magic number)

hi,
i have quite a strange problem:
when my applet tries to parse an XML file with SAX (no DTD-validation) i got the following error:
java.lang.ClassFormatError: <HTML> (Bad magic number)
Well i had some problems before with the ClassFormatError but they were because some class-files were corrupt. They were easy to fix because the defecitve class-file was written next to java.lang.ClassFormatError. This time i got the <HTML> expression next to the error. what does this mean?
thnx in advance!
marc

Bad magic Number. means the first 4 bytes did not equals CAFEBABE (0xCAFEBABE) But why do you see <HTML> after that is beyound me. Can you locate which class is foul and replace it?

T6340 cannot boot disk - Bad magic number in disk label

Hi,
I have a shiny new T6340 that I am just setting up.
When I get through the CMM to the SP and onto the EEPROM,
I then try to start the boot process:
{0} ok boot disk1
Sun Blade T6340 Server Module, No Keyboard
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.30.4, 130848 MB memory available, Serial #76313344.
Ethernet address 0:14:4f:8c:73:0, Host ID: 848c7300.
Boot device: /pci@500/pci@0/pci@9/@0/disk@1 File and args:
Bad magic number in disk label
Can't open disk label package
ERROR: boot-read fail
Evaluating:
Can't open boot device
{0} ok show-disks
a) /pci@500/pci@0/pci@9/LSILogic,sas@0/disk
b) /pci@500/pci@0/pci@2/pci@0/usb@0,2/storage@5/disk
c) /pci@500/pci@0/pci@2/pci@0/usb@0,2/storage@1/disk
q) NO SELECTION
Enter Selection, q to quit: q
{0} ok boot /pci@500/pci@0/pci@9/LSILogic,sas@0/disk
Boot device: /pci@500/pci@0/pci@9/LSILogic,sas@0/disk File and args:
Bad magic number in disk label
Can't open disk label package
ERROR: boot-read fail
Can't open boot device
{0} ok This is a brand new B6000 system and has not been booted before.
Please tell me what I need to do to enable the disks, so I can do the next bit!
rachel

@rachel,
In your original post you showed a screen capture of what you tried.
First you typed "boot disk1". ( Why disk1? Why not disk0?)
When that didn't seem to work, you displayed the disks recognized by the system at OpenBoot.
The first of those disks was a device path of
/pci@500/pci@0/pci@9/LSILogic,sas@0/disk{code}
and so you attempted to boot from that but omitted whatever slice might be the boot slice of a factory preinstalled OS. For example...
{code:java}
boot /pci@500/pci@0/pci@9/LSILogic,sas@0/disk@0,0{code}
(just guessing at what could be that bootable slice).
What happens if you simply type "*boot*" when you are at OBP?

Java.lang.ClassFormatException : Bad Magic number Excpetion

Hi all
I am trying to hit an applet through an iplanet web connector.
The scenario is machine 1 is the web server (iplanet 4.1) . machine 2 is app
server (iplanet 6.0 sp2)
The web connector is configured for handling all the requests to machine2
that refer to the app server.
when i place my jar (containing the applet classes) on the app server and
then try to open it through a jsp on the app server itself , it
throws a
java.lang.ClassFormatError: com/niit/cliks/te/web/TestingEngine (Bad magic
number)
exception.
But if i try with the same jar file on the web server (the same as running
the app server( - i.e. machine 2 ) the jar works just fine.
can anybody put some light on the issue. I am in a very tight deadline
situation.
thanks and regards
raghav..
PS - the applet is not signed and i don't wish (and plan) to sign it.

Dear friend
But the same class file and jars are working (without any change in the jar) when i put them on the web server which is also on the same machine running the app server.
I may suspect my compiled files but i don't.
i have compiled them at least ten times from the moment i started getting the error.
any other guesses....
thanks for your consideration
regards..
raghav..

Solaris boot images fail with bad magic number

hi guys, have had Solaris on boxes for allmost 10 years. I have never installed sol10, and I have a problem
1. I download the zip file, then use winrar to unzip them..
2. burt the image with nero 7
when my SunBlade 1000 comes up I do the Stop-A, and from the Ok promt
I do boot cdrom
this fails with "bad magic number" I have redown loaded it and reburnt it with nero reinstalled
and also changed out the DVD on SunBlade
3 I found a copy of Solaris 8 and the I got back a 'bitch' where is Solaris 9 so, most likely the drive is OK
HELP
Cris Harrison

Hello Cris,
unfortunately I don't understand your last sentence !
I found a copy of Solaris 8 and the I got back a '*****' where is Solaris 9 so, most likely the drive is OK
If this was a Solaris 8 (7/01 or later) DVD that did successfully boot, your DVD drive firmware (assuming that this is the Sun Toshiba SD-M1401) is up-to-date. If the DVD drive has firmware 1007, an update to 1009 is required to boot from DVD. otherwise you won't be able to boot from DVD (boot from CD works and a DVD can be automounted/mounted).
Partial output of probe-scsi
Before update:
Unit 0 Removable Read Only device TOSHIBA DVD-ROM SD-M14011007
After update:
Unit 0 Removable Read Only device TOSHIBA DVD-ROM SD-M14011009
[*Patch 111649-04 - Toshiba DVD 1401 firmware update*|http://sunsolve.sun.com/search/advsearch.do?collection=PATCH&type=collections&queryKey5=111649&toDocument=yes]
when my SunBlade 1000 comes up I do the Stop-A, and from the Ok promt ...
Instead of trying to directly boot, disable auto-boot and retry after a clean power-on.
Break with Stop-A
setenv auto-boot? false
reset-all
boot cdrom
Michael

Catfish - RuntimeError: Bad magic number in .pyc file

I'm using catfish as a search tool, I installed it on a new system with findutils as the backend. When I run it I get "RuntimeError: Bad magic number in .pyc file"
I have no idea how to fix this. It runs fine on another system. I tried to reinstall it and did a full upgrade. I tried it with various backends and I still get this runtimeerror. Any ideas?

See if you can locate a leftover .pyc file with:
pacman -Qo $(find /usr/lib/python2.{5,6} -name *.pyc) | grep "No package owns"
Provide pacman manages all files on your root partition, it should be fine to delete what this finds.

Mount.ocfs2: Bad magic number in superblock on RAC Node2

Everytime I try to start ocfs2 or mount a filesystem on node2, I get the following error:
"mount.ocfs2: Bad magic number in superblock while opening device /dev/sdb1
uname -r : 2.6.9-78.0.1.ELsmp
[root@rac1 ~]# /etc/init.d/o2cb status
Module "configfs": Loaded
Filesystem "configfs": Mounted
Module "ocfs2_nodemanager": Loaded
Module "ocfs2_dlm": Loaded
Module "ocfs2_dlmfs": Loaded
Filesystem "ocfs2_dlmfs": Mounted
Checking O2CB cluster ocfs2: Online
Heartbeat dead threshold: 61
Network idle timeout: 30000
Network keepalive delay: 2000
Network reconnect delay: 2000
Checking O2CB heartbeat: Not active
Same filesystem is visible on node1. Any help is much appreciated

Hi Yuvaraj,
I am facing the same situation and the only difference is that I am abe to see ocfs2 mount point on rac1 node and in rac2 node, it is not viewable.
If you could send how to fix this issue, it will be very gr8ful and would appreciate your timely help.
My id : [email protected]
Rac2 Node
[root@rac2 tmp]# /etc/init.d/o2cb status
Module "configfs": Loaded
Filesystem "configfs": Mounted
Module "ocfs2_nodemanager": Loaded
Module "ocfs2_dlm": Loaded
Module "ocfs2_dlmfs": Loaded
Filesystem "ocfs2_dlmfs": Mounted
Checking O2CB cluster ocfs2: Online
Heartbeat dead threshold: 61
Network idle timeout: 30000
Network keepalive delay: 2000
Network reconnect delay: 2000
Checking O2CB heartbeat: Not active
Rac1 Node
[root@rac2 tmp]# /sbin/mounted.ocfs2 -d
Device FS UUID Label
[root@rac2 tmp]# /sbin/mounted.ocfs2 -f
Device FS Nodes
Rac1 Node

Bad magic number in super-block while trying to open /dev/sda2

Similar Messages

Maybe you are looking for