From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1GVjIc-00055R-8s for garchives@archives.gentoo.org; Fri, 06 Oct 2006 06:35:10 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k966Y0UE015556; Fri, 6 Oct 2006 06:34:00 GMT Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k966TeN3029450 for ; Fri, 6 Oct 2006 06:29:41 GMT Received: by nf-out-0910.google.com with SMTP id p46so1367695nfa for ; Thu, 05 Oct 2006 23:29:40 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=LUZFhy65JJj8PSeS7AmOQBrGGSpoDCib/vt+90kRfeTFypeUBLcM5fBCgcB6aMBmA8uGrOlnWvKQ0/ghJ0saJtwklz44uNu6iZU0G5YsSHu2LuHBg7MO+XsrMWqOOnc+b2o//V9+Z0+nlvQSFJDYz7X0uX/5U8EH17Xs/jdGRWk= Received: by 10.78.202.19 with SMTP id z19mr1235528huf; Thu, 05 Oct 2006 23:29:40 -0700 (PDT) Received: by 10.78.166.20 with HTTP; Thu, 5 Oct 2006 23:29:40 -0700 (PDT) Message-ID: <5e213dd40610052329m7f707624w8da75d2e8d4bdd40@mail.gmail.com> Date: Fri, 6 Oct 2006 08:29:40 +0200 From: "Gregory SACRE" To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] [OT] Problem with disk: cannot mount as ext3 but yes as ext2 ??? Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Archives-Salt: b329de3b-4cfb-431e-95f7-0cfed82b2442 X-Archives-Hash: f341d1192445e938b7358a17c5abdb87 Hello, I had a hard disk attached on an old RedHat PC formatted and mounted as ext3 filesystem. I removed the hard disk from the PC and plugged it in my Gentoo box. I tried to mount it as ext3 file system and got this error: -------------------------------------------------------------------------------- | # mount -t ext3 /dev/hdd1 /jukebox | mount: wrong fs type, bad option, bad superblock on /dev/hdd1, | missing codepage or other error | In some cases useful info is found in syslog - try | dmesg | tail or so -------------------------------------------------------------------------------- I then tried to see the partition type with fdisk: -------------------------------------------------------------------------------- | Command (m for help): p | | Disk /dev/hdd: 81.9 GB, 81964302336 bytes | 16 heads, 63 sectors/track, 158816 cylinders | Units = cylinders of 1008 * 512 = 516096 bytes | | Device Boot Start End Blocks Id System | /dev/hdd1 1 158816 80043232+ 83 Linux -------------------------------------------------------------------------------- My next step was to try to repair it with fsck.ext3: -------------------------------------------------------------------------------- | fsck.ext3 -p /dev/hdd | fsck.ext3: Bad magic number in super-block while trying to open /dev/hdd | /dev/hdd: | 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 -------------------------------------------------------------------------------- I tried what was written with e2fsck: -------------------------------------------------------------------------------- | e2fsck -b 8193 /dev/hdd | e2fsck 1.39 (29-May-2006) | e2fsck: Bad magic number in super-block while trying to open /dev/hdd | | 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 -------------------------------------------------------------------------------- After googling for a while, and not really finding an answer, I tried to mount it as readonly, and because of a typo, I mounted it as ext2... and it worked!!! I tried then to mount it normally, not anymore as read-only with ext2 format... and it worked!!! So my first question is: how come? I'm sure the filetype is ext3 as it can be seen in my old fstab: -------------------------------------------------------------------------------- | [...] | /dev/hdb5 swap swap defaults 0 0 | #/dev/hdc1 /jukebox ext3 defaults 1 1 --> this is the one ;-) | [...] -------------------------------------------------------------------------------- I thought maybe I could try to repair it with the normal fsck: -------------------------------------------------------------------------------- | fsck /dev/hdd1 | fsck 1.39 (29-May-2006) | e2fsck 1.39 (29-May-2006) | /dev/hdd1: Attempt to read block from filesystem resulted in short read while reading block 525 | | /dev/hdd1: Attempt to read block from filesystem resulted in short read reading journal superblock | | fsck.ext3: Attempt to read block from filesystem resulted in short read while checking ext3 journal for /dev/hdd1 -------------------------------------------------------------------------------- Is there anything wrong with my hardware? Is it a super-block problem? Is there a way to solve it? Thank you in advance! Greg -- gentoo-user@gentoo.org mailing list