LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 10-18-2007, 08:20 PM   #1
R00T.OSIRIS
Member
 
Registered: Dec 2006
Location: -84.706059324915, -62.4843750666430
Distribution: Gentoo, FreeBSD, OpenSuSe
Posts: 51

Rep: Reputation: 15
Bad magic number in superblock, again!


Alright, so I installed gentoo 2007.0 on a new pc I built, and everything seemed to be working good for a week. Rebooted several times, then one time I did, I got the error, bad superblock on my /tmp part sda8. I couldn't find anyway around it, and I wanted to resize all my partitions anyways so I decided to wipe out the partition table and all partitions then redo it all (with fdisk from the minimal cd).
Finally got everything built again, had rebooted twice, everything seemed fine. I do it a third time, and now it's saying every logical partition on my extended partiton's superblock is bad. (My primary / first three boot and work fine)

Code:
localhost grub # mount /dev/sda6 -t ext3 /home
mount: wrong fs type, bad option, bad superblock on /dev/sda6,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so
(same error for sda6-9 (sda5 is swap, which swapon will not mount))

Code:
localhost grub # dmesg | tail
sd 6:0:0:3: [sdg] Attached SCSI removable disk
sd 6:0:0:3: Attached scsi generic sg7 type 0
usb-storage: device scan complete
Unable to find swap-space signature
Unable to find swap-space signature
VFS: Can't find ext3 filesystem on dev sda6.
EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as ext2
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev sda6.
VFS: Can't find ext3 filesystem on dev sda6.
Code:
localhost grub # fsck.ext3 /dev/sda6
e2fsck 1.39 (29-May-2006)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext3: Bad magic number in super-block while trying to open /dev/sda6

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>
(same for sda6-9)

I tried running with the -b 8193, but produced the exact same error. Not sure if that's where my alternative superblocks are stored or not. Figured my blocksize was 4096 I tried -b 32768 with the exact same output as above.


Code:
localhost grub # fdisk -l /dev/sda

Disk /dev/sda: 150.0 GB, 150039945216 bytes
255 heads, 63 sectors/track, 18241 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1           7       56196   83  Linux
/dev/sda2               8        1664    13309852+  83  Linux
/dev/sda3            1665        2441     6241252+  83  Linux
/dev/sda4            2442       18241   126913500    5  Extended
/dev/sda5            2442        2564      987966   83  Linux
/dev/sda6            2565        3781     9775521   83  Linux
/dev/sda7            3782        4998     9775521   83  Linux
/dev/sda8            4999        5607     4891761   83  Linux
/dev/sda9            5608       18241   101482573+  83  Linux
Oh and I tried all of this on a knoppix live cd as well, with the same results.

I'm not really sure where to go from here, any advice would be greatly appreciated! Is this indicating a Hard Drive with bad blocks? or a software issue? Thanks!

Alright so I checked for bad blocks using badblocks -n on all the partitions. It didn't find any. The only things I did in between the last two reboots was, emerge -uD --newuse world, revdep-rebuild, (had to remerge emul-linux-x86-xlibs) and ran dispatch-conf.
This is on an amd64, 2.6.22-gentoo-r8, the hdd is a raptor 150, m2n32sli motherboard.

Last edited by R00T.OSIRIS; 10-18-2007 at 09:53 PM.
 
Old 10-19-2007, 06:59 PM   #2
comprookie2000
Gentoo Developer
 
Registered: Feb 2004
Location: Fort Lauderdale FL.
Distribution: Gentoo
Posts: 3,291
Blog Entries: 5

Rep: Reputation: 58
post /etc/fstab
may help;
http://forums.gentoo.org/viewtopic-t...t3+blocks.html

Last edited by comprookie2000; 10-19-2007 at 07:04 PM.
 
Old 10-19-2007, 08:18 PM   #3
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 19,970

Rep: Reputation: 3633Reputation: 3633Reputation: 3633Reputation: 3633Reputation: 3633Reputation: 3633Reputation: 3633Reputation: 3633Reputation: 3633Reputation: 3633Reputation: 3633
Gotta be hardware. Check cables (power and interface), seating, kinks whatever.

See if you can swap the disk into another interface - or even box to eliminate controller chip as a suspect.
Or go get another disk - they're cheap, and you'll use it sometime even if ultimately there's nothing wrong with your current disk ...

No power interuptions ???.
 
Old 10-19-2007, 11:54 PM   #4
R00T.OSIRIS
Member
 
Registered: Dec 2006
Location: -84.706059324915, -62.4843750666430
Distribution: Gentoo, FreeBSD, OpenSuSe
Posts: 51

Original Poster
Rep: Reputation: 15
Code:
/dev/sda1               /boot           ext2            noauto,noatime  1 2
/dev/sda3               /               ext3            noatime         0 1
/dev/sda2               /usr            ext3            noatime         0 1
/dev/sda5               none            swap            sw              0 0
/dev/sda6               /home           ext3            noatime         0 1
/dev/sda7               /tmp            ext3            noatime         0 1
/dev/sda8               /storage        ext3            noatime         0 1
/dev/cdrom              /mnt/cdrom      audo            noauto,ro       0 0

#/dev/fd0               /mnt/floppy     auto            noauto          0 0

shm                     /dev/shm        tmpfs           nodev,nosuid,noexec     0 0
Thanks for the replies!

I checked out that link but didn't didn't get much. I couldn't do anything with the partitions with fsck dumpe2fs debugfs as they all would report superblock errors, and trying to use the backup SB yeilded the same errors.

I don't believe it's hardware anymore, it's controlled on the software level. Every block on the drive was good. If the logic board was bad on the HDD it would seem I'd have a lot more corruption then JUST my superblockS. That and it's easily fixed by redoing the partition.
Cable is good. No power interuptions, on a custom UPS and my PS is a corsair 620w, so it's pretty stable.

I don't know. If I have some time I'd like to weed out what's causing it. I'm still kind of leaning towards something in the update I did.

Last edited by R00T.OSIRIS; 10-20-2007 at 12:06 AM.
 
Old 10-26-2007, 09:49 PM   #5
BIGCAM
LQ Newbie
 
Registered: Oct 2007
Posts: 3

Rep: Reputation: 0
R00T.OSIRIS don't know if you have fixed that error.
I just overcame the nearly same error but only restricts and exactly to this error you got
Code:
localhost grub # fsck.ext3 /dev/sda6
e2fsck 1.39 (29-May-2006)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext3: Bad magic number in super-block while trying to open /dev/sda6

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>
I think the error you got is very close to mine, it is not an hard error but it is relatively harder error. It is some sorts of error happens in the low-level format of a HDD partition.

I did a lot trails which were all failed before I headed to PartitionMagic.
Believe or not this piece of software did a lot more work than cfdisk and fdisk even e2fsck. It took my little book over 10minutes to sort things out. And the particular partition was fixed after reboot.

You can give it a go, All I did was use a boot disk which has PartitionMagic installed, to boot the laptop and run it. It automatically fixed several errors. I got that disk long time ago. Im sure there's ways to build it into an blank disc.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
"Bad magic number in superblock" for a windows partition Prio Linux - Newbie 1 12-14-2006 09:12 AM
harddrive won't mount: bad magic number in superblock sohmc Linux - Software 2 01-18-2006 07:35 AM
ext2, ext3 bad magic number in superblock shuuhen Linux - General 1 12-13-2005 01:29 AM
bad magic number in superblock crazynachos Linux - Games 1 04-15-2004 01:43 PM
bad magic number in superblock crazynachos Linux - Newbie 1 04-14-2004 02:09 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 01:38 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration