HFS drive bad/missing superblock magic number

Should an HFS drive have a superblock and magic number or is that strictly a UFS thing? I get this error but my drive is Mac formatted.

Hi,
You can run "fsck" command by giving the alternate superblock. The alternate superblock should have given during the filesystem creation in the disk using the "newfs" command. If there is nothing you need to run the "newfs" command for the filesystem creation where you will loose your entire data.
Regards,
Dharani
SlashSupport Indi Pvt Ltd.
Hi,
I've umounted a SunBlade 100 ide ATA II disk , and put
into
a linux box who can only read ufs.
Then when i mounted a hd again in a SunBlade 100 i've
found
that appears the message "corrupt label ..."
The hardisk it won't be able to boot. Then i've
mounted as
secondary of another SunBlade100 and i've tried to
access
to data, but when i've mounted i can't it.
And i did the next:
fsck -F ufs /dev/rdsk/c0t2d0s2 :
** /dev/dsk/c0t2d0s0
BAD SUPERBLOK : MAGIC NUMBER WRONG
use an alternate super-block to supply needed
information
I've tried to to the next :
fsck -F ufs -o b=32 /dev/rdsk/c0t2d0s0
But it was fail ....
Anybody can help me ?
Thanks

Similar Messages

Reformat external hard drive - "bad superblock", "magic number wrong" error

i was just given a brand new 300GB USB hard drive, however, as it came NTFS-formatted, immediately after plugging it in for the first time, i fired up Disk Utility, and attempted to format it with UFS.
The problem arose when the progress bar just sat there for an hour at a constant 5%. Assuming the program had stalled (it hadn't...though it would have sat there indefinitely), i quit Disk Utility, opened it back up, and again attempted to format the drive--only this time, almost immediately the program output:
BAD SUPER BLOCK: MAGIC NUMBER WRONG
LOOK FOR ALTERNATE SUPERBLOCKS? yes
SEARCH FOR ALTERNATE SUPER-BLOCK FAILED. YOU MUST USE THE
-b OPTION TO FSCK TO SPECIFY THE LOCATION OF AN ALTERNATE
SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(8).
i opened up Terminal and tried manually to find an alternate superblock, to no avail.
fsck -b32 /dev/disk2s3
i've been unable to find any solutions to this issue online, but i'd really like to use my drive i've heard that this problem has to do with hardware that's about to fail, however, this is a brand new drive, and i'm quite certain the error is as a result of the aborted reformat operation.
Does anyone know how to remedy this? Thanks in advance.

Hello TheRedWino, and a warm welcome to the forums!
Hmmm, what kind of Case/Chipset does it have?
Have you tried erasing it with Zeros one Pass?
"Disk Utility
1. Insert the Mac OS X Install disc that came with your computer, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
3. Click the Erase tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume, then choose MacOS Extended Journalled, select the Partition tab.
6. Click Erase & look for Security Options. choose Zero 1 pass."
Formatting & Partitioning a Hard Drive in OS X - Tiger and Leopard...
http://www.kenstone.net/fcphomepage/partitioningtiger.html

Fsck: "Bad super block: magic number wrong"

One of my 750 Gig FireWire drives behaves peculiarly, all the files stopped opening on it. Disk Utility doesn't see anything wrong, DiskWarrior 4 didn't fix the HD's behavior, DataRescue II was willing to rescue files... but 750 Gigs' worth? Who has that big of a spare HD.
So I booted in Safe mode and ran the following fsck command from Terminal:
/sbin/fsck -f /dev/disk3s3
I received the following answer:
"BAD SUPER BLOCK: MAGIC NUMBER WRONG
LOOK FOR ALTERNATE SUPERBLOCKS? no"
My UNIX knowledge pretty much ended at this. I surmise from the answer that I won the UNIX "corrupted directory" jackpot. Does anyone know what commands I should enter to look for alternate superblocks or perform some other remedial action here? Thank you in advance

George,
When you formatted the drive, did you re-partition it and format it with HFS+? It seems partitioned by another OS, which allows HFS+ volumes. Did you use a boot loader, so you could boot two OSs from the disk? I'll just offer some more things sighted, not insights.
This is looking like a common problem, though; so I could use some help with ownership & permissions from someone. It would seem that Tiger & Leopard both mount NTFS partitions read only, but NTFS-3g's permission system is similar enough to Unix's that it can be mounted read/write.
MacFUSE appears to do things with 'FUSE', a mystical object at first glance, one whose permissions can be converted to either HFS+, ext2, or usf. The ownership & permissions appear to change with where the external drive is mounted on the boot disk's file tree. I assume you know all about these things.
Is using them together a good idea? In any case, they both allow a file system to be mounted read/write, and modify the Mac OS itself. Here's an interesting remark from the MacFUSE FAQ:
+Q 3.2. After installing MacFUSE, I can't mount any disk images, optical discs, etc. What's going on?+
+A: It's likely that you installed a broken ntfs-3g package you found on the Internet. The package might be interfering with the disk image/disc mounting process. Try removing the /System/Library/Filesystems/ntfs-3g.fs/ directory.+
Also, Leopard's update 10.5.1 has the sentence:
+Addresses formatting issues with certain drives used with Time Machine (specifically, single-partition MBR drives greater than 512 GB in size as well as NTFS drives of any size and partition scheme).+
You can check the volume's ownereship & permissions with a Ctrl-click 'Info Menu' on the mounted volume's icon. Does all look OK?
Wish I knew more, but perhaps these observations will give you some ideas. Best of luck.
Bruce

BAD SUPER BLOCK: MAGIC NUMBER WRONG

My Mac mini started playing up a couple of weeks ago, I thought it was the attached firewire drives, but it looks like a problem on the hard disk. I've been trying to fix this and I need help!
- I tried to restore leopard - only to find my leopard install disc is corrupt. I tried to make a copy with toast, but that failed, a couple of times
- So I've tried to use disk utility. I try to repair the volume. It gets to 'Checking Catalog file'. Then it gives the messages:
Invalid Key length
Volume check failed
Eror: Filesystem verify or repair failed.
- Then, booting from another leopard disk (for another machine, so I can't install from it), I've been running fsck. It says it can't the superblock, when I make suggestions I get the above message 'Bad super block': magic number wrong'. Any idea where there might be another valid copy of the superblock?
So, I'm a bit stuck. It's really annoying that the leopard disk that I bought doesn't copy and doesn't install.
Any suggestions gratefully received!

How to Make a Non-Commercial DVD copy of MAC OS X Leopard
Making a DVD Image 
Step1. Insert the retail Mac OS X Install DVD into your drive. 
Step 2. Launch Disk Utility (Applications > Utilities). 
Step 3. In Disk Utility, you will notice a white pane on the left hand side. In the pane, select the Mac OS X Install DVD by clicking on it once. 
Step 4. Click New Image on the Disk Utility toolbar. 
Step 5. A dialog box will appear. Give the new image a name. I used 'Mac OS X Install DVD'. Select the destination where you wish to save it. Leave Image Format at Compressed (default) and Encryption at None (default). 
Step 6. Click Save to begin creating the image. 
Step 7. Once your image has been created DO NOT mount it. Leave the image alone and proceed to the next section.
  Burning the Image
 Step 1. Launch Disk Utility (Applications > Utilities). 
Step 2. Click Burn on the Disk Utility toolbar (upper left). 
Step 3. Navigate to where you saved the DVD image created in the previous section. Click on the image file, then click the Burn button. Do not drag and drop the image file into Disk Utility during this step. 
Step4. Insert a DVD when prompted and proceed to Burn it. (use good quality media) Using these exact steps I was successfully able to create a personal backup copy of Mac OS X Leopard. I hope this tutorial helps.

New install on new drive - Corrupt label - wrong magic number

Hi,
I put a new 120GB Seagate drive in my Sun Blade 100, and installed Solaris 9 9/05. But, every time I boot, I see a WARNING msg:
WARNING: .... (dad0)
corrupt label - wrong magic number
I installed from the 1st software CD, as I've done many times before, but this is the 1st time I've done an installation on a new, non-Sun hard drive, so from what I can tell, I need to do something additional to prevent having this warning, but I can't figure out what.
I've tried "boot cdrom -s" and then format -> partition, and I can see that the swap and backup slices had started in cylinder 0. From what I've read, that's a problem, so I changed swap to start in cylinder 1.
Here's what format->part->print looks like now:
partition> pri
Volume: abc
Current partition table (original):
Total disk cylinders available: 57459 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 root wm 2008 - 52437 98.11GB (50430/0/0) 205754400
1 swap wu 1 - 2010 3.91GB (2010/0/0) 8200800
2 backup wm 0 - 57458 111.79GB (57459/0/0) 234432720
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 home wm 52438 - 57457 9.77GB (5020/0/0) 20481600
And, here's "prtvtoc /dev/rdsk/c0t0d0s0:
# prtvtoc /dev/rdsk/c0t0d0s0
* /dev/rdsk/c0t0d0s0 (volume "abc") partition map
* Dimensions:
* 512 bytes/sector
* 255 sectors/track
* 16 tracks/cylinder
* 4080 sectors/cylinder
* 57461 cylinders
* 57459 accessible cylinders
* Flags:
* 1: unmountable
* 10: read-only
* Unallocated space:
* First Sector Last
* Sector Count Sector
* 0 4080 4079
* 8204880 18446744073709539376 8192639
* 234428640 4080 234432719
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory
0 2 00 8192640 205754400 213947039 /
1 3 01 4080 8200800 8204879
2 5 00 0 234432720 234432719
7 8 00 213947040 20481600 234428639 /export/home
Can anyone tell me what I need to do to eliminate the problem?
Also, I don't mind doing a complete new installation, but I'd like to know what I SHOULD have done during the installation to avoid this problem.
Thanks,
Jim

Hi,
I think that I fixed the swap ending cylinder, but I'm still getting the same warning when I boot the system. Here's the new format->partition->print:
partition> print
Volume: abc
Current partition table (original):
Total disk cylinders available: 57459 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 root wm 2008 - 52437 98.11GB (50430/0/0) 205754400
1 swap wu 1 - 2007 3.90GB (2007/0/0) 8188560
2 backup wm 0 - 57458 111.79GB (57459/0/0) 234432720
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 home wm 52438 - 57457 9.77GB (5020/0/0) 20481600
What else can I do to try to eliminate this warning?
Thanks,
Jim

BAD SUPER BLOCK: MAGIC NUMBER WRONG LOOK FOR ALTERNATE SUPERBLOCKS?

Im running a multi drive enclosure via FW400 and one of the drives is a 750Gb partitioned into two partitions, roughly half and half.
Ive done a bit of research on this "error" but am wondering if others have had trouble with larger drives in external enclosures.
Im running a fsck -fy /dev/disk3s3 type command from terminal on the unmounted partition which is giving me trouble - but this "error" keep popping up and Terminal offers no insight into when it might end, or what its actually doing.

The article seems to state that both commands will work but they seem to work differently depending on ???
In SUM fsck will detect the filesystem. If the filesystem is HFS, it will then turn the job over to fsck_hfs. If the filesystem is UFS then it will run fsck. SUM is a barebones operating system that is quite different then OS X fully loaded- only the root filesystem is mounted, read only. In this instance it is safe to operate on the filesystem. In fully loaded OS X, volumes must be unmounted to repair them. This will prevent any processes from trying to write to the drive. The article itself is a bit old and could use updating:
% diskutil verifyVolume /dev/disk1s9
Started verify/repair volume (filesystem) on disk disk1s9 andromeda
Checking Journaled HFS Plus volume
Detected a case-sensitive catalog
Checking Extents Overflow file
Checking Catalog file
Checking multi-linked files
Checking Catalog hierarchy
Checking Extended Attributes file
Checking volume bitmap
Checking volume information
The volume andromeda appears to be OK
[ + 0%..10%..20%..30%..40%..50%..60%..70%..80%..90%..100% ]
Finished verify/repair volume (filesystem) on disk disk1s9 andromeda
As you can see diskutil will work fine on a non-startup volume- at least on my 10.5.6 system. I would stay away from fsck_hfs unless you wanted to rebuild the catalog. You might find the /var/log/fsck_hfs.log interesting.

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

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 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)

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.

Sun Ultra 25 - Bad magic number in disk label

I have a Sun Ultra 25 SPARC that is booting fine to it's 80GB SATA drive. Solaris 10, OpenBoot 4.22.19.
Here's what I did:
I installed a 2TB Western Digital SATA drive into the HDD1 slot.
I formatted the disk in the HDD1 slot via the format command, labeled the disk, and divided it into partitions.
I then used newfs to build the ufs on all partitions.
I mirrored the disk in HDD0 to the disk in HDD1 using ufsdump for all partitions. The data is accessible and looks ok.
After this was done I did an installboot to /dev/rdsk/c1t1d0s0 (the / partition of the HDD1 slot).
I then did a fsck on every partition to verify that they are okay.
I then took the hard drive in HDD1 and put it in the HDD0 slot, now wanting to boot off that disk.
At the reboot:
Bad magic number in disk label
Can't open disk label package
If I do a probe-scsi:
MPT Version 1.05, Firmware Version 1.08.03.00
Target 0
Unit 0 Disk ATA WDC WD20EADS-00R0A01 3907029168 Bocks, 2000 GB SATA device PhyNum 0
As far as I can tell disk0 is the correct devalias which is:
/pci@1e,600000/pci@0/pci@9/pci@0/scsi@1/disk@0,0
I just don't understand how the fsck is okay, but the boot give bad magic number in disk label?
The 80GB drive in HDD slot 0 works fine with the boot disk0 command, all I'm doing is swapping a larger disk with the same data for the smaller disk.

if it is like any other Sun product, it needs to go through the format command and get a volname.... it is just a label, but it needs to be done.
haroldkarl

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.

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?

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

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

HFS drive bad/missing superblock magic number

Similar Messages

Maybe you are looking for