Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory Bad Super Block: Magic Number Wrong Post 29116 by matthewbane on Monday 30th of September 2002 12:48:01 PM
Old 09-30-2002
Bad Super Block: Magic Number Wrong

I had a power outage a day ago and when the power came back on my FreeBSD 4.6 webserver had problems. It said it was unable to mount /var and made me start in single user mode and said to run fsck MANUALY. So i did and this is now what i get.

www# fsck /dev/ad0s1e
** /dev/ad0s1e
BAD SUPER BLOCK: MAGIC NUMBER WRONG
/dev/ad0s1e: INCOMPLETE LABEL: type 4.2BSD fsize 16384, frag 0, cpg 64, size 39102273

So i did some research and found a few places that told we me to fix the Super Block with the alternative super block. So i ran this.

www# newfs -N /dev/ad0s1e
Warning: Block size and bytes per inode restrict cylinders per group to 385.
Warning: 2240 sector(s) in last cylinder unallocated
/dev/ad0s1e: 39102272 sectors in 9547 cylinders of 1 tracks, 4096 sectors
19092.9MB in 25 cyl groups (385 c/g, 770.00MB/g, 12288 i/g)
super-block backups (for fsck -b #) at:
32, 1576992, 3153952, 4730912, 6307872, 7884832, 9461792, 11038752, 12615712, 14192672, 15769632, 17346592, 18923552, 20500512, 22077472, 23654432, 25231392, 26808352, 28385312,
29962272, 31539232, 33116192, 34693152, 36270112, 37847072

Once I found the alternative blocks I tried this.

www# fsck -b 34693152 /dev/ad0s1e
Alternate super block location: 34693152
** /dev/ad0s1e
BAD SUPER BLOCK: MAGIC NUMBER WRONG

Running FreeBSD 4.6 on PIII 450
The System has 2 drives
Root is at /dev/da0 a 4.3 GB SCSI drive
And I am missing my /var that was on a 20GB IDE drive /dev/ad0

So I still can not fix or mount the /dev/ad0s1e drive. How do I fix BAD SUPER BLOCK: MAGIC NUMBER WRONG and mount the drive?
how can I fix INCOMPLETE LABEL? Is the drive file system toast? or can I recover the files?
Is there a way to recover the drive data and move it to the good drive?
Thank you for any help.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Bad magic number in super-block

I am running mandrake 8.2 and when booting I get the message: e2fschk: Bad magic number in super-block while trying to open /dev/hda8. The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and really contains a valid an ext2 filesystem (and... (1 Reply)
Discussion started by: Jay
1 Replies

2. 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

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. HP-UX

BAD SUPER BLOCK - Run fsck with alternate super block number

Error received when I tried to restore a blank disk with an 'auto recovery' DDS tape via HP-UX recovery system 2.0 onto a 1Gb SCSI. I assumed it would do the setup, wrong. Could someone tell me the procedure to initial disk for recovering files using cpio. The system is a HP-UX 9.04 version on a... (1 Reply)
Discussion started by: admin wanabee
1 Replies

5. Solaris

solaris error BAD SUPER BLOCK

I want mount a disk. I have this error. I'm trying to correct with the superblock but i have the same error. Look my procedure. bash-2.03# fsck -F ufs /dev/rdsk/c0t1d0s0 Alternate super block location: 9423392. ** /dev/rdsk/c0t1d0s0 BAD SUPER BLOCK: MAGIC NUMBER WRONG USE AN ALTERNATE... (1 Reply)
Discussion started by: simquest
1 Replies

6. Solaris

wrong magic number

/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

7. Filesystems, Disks and Memory

Bad super block: Magic number wrong

Whenever i run, # fsck -F ufs /dev/dsk/c0t0d0s7 The following error prompt out:- ** /dev/dsk/c0t0d0s7 BAD SUPER BLOCK: MAGIC NUMBER WRONG USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; eg. fsck -o b=# where # is the alternate super block. SEE fsck_ufs(1M). ... (3 Replies)
Discussion started by: beginningDBA
3 Replies

8. 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

9. Filesystems, Disks and Memory

Can't repair super block, bad magic number

Hello all, I have a hard drive that I can't repair. The drive is WD15EARS - Filesystem ext4 ( not 100% sure ) It's used in a Synology DS110j NAS. I try to run fsck -p /dev/sdb on the HD and I get this: Bad magic number in super-block while trying to open /dev/sdb /dev/sdb: The superblock... (4 Replies)
Discussion started by: dallasw1983
4 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
HD(4)							     Linux Programmer's Manual							     HD(4)

NAME
hd - MFM/IDE hard disk devices DESCRIPTION
The hd* devices are block devices to access MFM/IDE hard disk drives in raw mode. The master drive on the primary IDE controller (major device number 3) is hda; the slave drive is hdb. The master drive of the second controller (major device number 22) is hdc and the slave hdd. General IDE block device names have the form hdX, or hdXP, where X is a letter denoting the physical drive, and P is a number denoting the partition on that physical drive. The first form, hdX, is used to address the whole drive. Partition numbers are assigned in the order the partitions are discovered, and only nonempty, nonextended partitions get a number. However, partition numbers 1-4 are given to the four partitions described in the MBR (the "primary" partitions), regardless of whether they are unused or extended. Thus, the first logi- cal partition will be hdX5. Both DOS-type partitioning and BSD-disklabel partitioning are supported. You can have at most 63 partitions on an IDE disk. For example, /dev/hda refers to all of the first IDE drive in the system; and /dev/hdb3 refers to the third DOS "primary" partition on the second one. They are typically created by: mknod -m 660 /dev/hda b 3 0 mknod -m 660 /dev/hda1 b 3 1 mknod -m 660 /dev/hda2 b 3 2 ... mknod -m 660 /dev/hda8 b 3 8 mknod -m 660 /dev/hdb b 3 64 mknod -m 660 /dev/hdb1 b 3 65 mknod -m 660 /dev/hdb2 b 3 66 ... mknod -m 660 /dev/hdb8 b 3 72 chown root:disk /dev/hd* FILES
/dev/hd* SEE ALSO
chown(1), mknod(1), sd(4), mount(8) COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 1992-12-17 HD(4)
All times are GMT -4. The time now is 08:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy