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 1GX48Z-0002Hw-Gd for garchives@archives.gentoo.org; Mon, 09 Oct 2006 23:02:19 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k99N18Y1024445; Mon, 9 Oct 2006 23:01:08 GMT Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k99MuGr5000043 for ; Mon, 9 Oct 2006 22:56:17 GMT Received: by nf-out-0910.google.com with SMTP id x30so97036nfb for ; Mon, 09 Oct 2006 15:56:16 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Pq9ZCo3zwEYWRFjSXN4LUU6uWhUNFx7BMhtzvpeIjFxOlALZwHgatATet4/kluaDRTxp+HgQ3c3JhD7xpuMlg+MTAWDzIBi1D3y6eFppK/lF74TtYaSyjFKgBXXs/ZiUYqmSkK5dSbKukdRQa0IFJVonplSYiDnYX9VKIBt3zYg= Received: by 10.82.129.5 with SMTP id b5mr716403bud; Mon, 09 Oct 2006 15:56:16 -0700 (PDT) Received: by 10.82.126.14 with HTTP; Mon, 9 Oct 2006 15:56:16 -0700 (PDT) Message-ID: <7573e9640610091556p6dbd859fy1a8ba318f1f0b441@mail.gmail.com> Date: Mon, 9 Oct 2006 15:56:16 -0700 From: "Richard Fish" Sender: richard.j.fish@gmail.com To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] [OT] Problem with disk: cannot mount as ext3 but can as ext2 In-Reply-To: <20061008090333.GA7536@Phoebe.thesee.dyndns.org> 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 References: <20061008090333.GA7536@Phoebe.thesee.dyndns.org> X-Google-Sender-Auth: 9973f18486300c4d X-Archives-Salt: 79d19db7-0499-4810-bd95-034d8bf47131 X-Archives-Hash: 8b36382ceb6c4a360263d3ae88fab2c9 On 10/8/06, gregory.sacre@gmail.com wrote: > | In some cases useful info is found in syslog - try > | dmesg | tail or so This was good advice.... > | # fsck.ext3 -p /dev/hdd > | fsck.ext3: Bad magic number in super-block while trying to open /dev/hdd > | /dev/hdd: Should have used /dev/hdd1 here.... > | # e2fsck -b 8193 /dev/hdd > | e2fsck 1.39 (29-May-2006) > | e2fsck: Bad magic number in super-block while trying to open /dev/hdd ...and here... > 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? Possibly a disk error on the blocks that would normally be reserved for the ext3 journal... > | /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 ...which is sort of what this message says. > Is there anything wrong with my hardware? Is it a super-block problem? > Is there a way to solve it? First, check the dmesg output after running "fsck.ext3 /dev/hdd1". That may show read errors on the disk, and if so, I'm guessing those blocks are now bad. You can also use smartctl (emerge smartmontools) to query the SMART information from the drive, or to run a SMART self-test of the disk. I believe you can also convert the filesystem to ext2, with "tune2fs -O ^has_journal /dev/hdd1". This should allow you to run fsck.ext2 on the filesystem, to check it for other consistency errors. -Richard -- gentoo-user@gentoo.org mailing list