From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-user+bounces-100540-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1Mp8tZ-0005P5-5X
	for garchives@archives.gentoo.org; Sat, 19 Sep 2009 22:59:09 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 67D30E097A;
	Sat, 19 Sep 2009 22:59:07 +0000 (UTC)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156])
	by pigeon.gentoo.org (Postfix) with ESMTP id 131B8E097A
	for <gentoo-user@lists.gentoo.org>; Sat, 19 Sep 2009 22:59:06 +0000 (UTC)
Received: by fg-out-1718.google.com with SMTP id d23so691510fga.10
        for <gentoo-user@lists.gentoo.org>; Sat, 19 Sep 2009 15:59:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlemail.com; s=gamma;
        h=domainkey-signature:received:received:from:to:subject:date
         :user-agent:references:in-reply-to:mime-version:content-type
         :content-transfer-encoding:message-id;
        bh=3t5JCRkModGOWa/X3ETSzpr3u/evNam0cU0FTHTgdRE=;
        b=M5yTzCocOdZDYbKRC4yFwuSqQhrKy0LEul8x8AkCl9yamheKdqtkByiHDLeye11xJ8
         eIBiIokcwtIZ18VyFUocNg6O8/PuSv8e6yRHY5Vs4sJDuwpzf/gFZzu4JCopO7uqi+LB
         0eD/j5n4RLdE52mESlnP4zzpPiJJWtOXaPO6Y=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=from:to:subject:date:user-agent:references:in-reply-to:mime-version
         :content-type:content-transfer-encoding:message-id;
        b=Ak3wV7VfsgwJHJqxnyDefKT95fXWVKf4xh57zI6pbmn3EsNwiRuBwZjNTsP+eQW8VF
         EPP1iONaVHxKZ5dFrX3tUup0rv/2GXjL0/W3Tcx/fUfX2ubEpT8dUqCnYO+ovB6vUy0F
         hIaZ2V0wT2y1WvJzRF6O1p0SoS2pQap3rXZ+8=
Received: by 10.86.211.38 with SMTP id j38mr3168822fgg.26.1253401146325;
        Sat, 19 Sep 2009 15:59:06 -0700 (PDT)
Received: from energy.localnet (energy.heim10.tu-clausthal.de [139.174.197.94])
        by mx.google.com with ESMTPS id 12sm850451fgg.15.2009.09.19.15.59.05
        (version=TLSv1/SSLv3 cipher=RC4-MD5);
        Sat, 19 Sep 2009 15:59:05 -0700 (PDT)
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org,
 Mark Knecht <markknecht@gmail.com>
Subject: Re: [gentoo-user] Re: USB drive dead? (Commands to check?)
Date: Sun, 20 Sep 2009 00:59:01 +0200
User-Agent: KMail/1.12.1 (Linux/2.6.31r4; KDE/4.3.1; x86_64; ; )
References: <5bdc1c8b0909191521j72388919w35e54b577b55ae60@mail.gmail.com> <5bdc1c8b0909191538h2ebf7697s742f2ee90bb9752a@mail.gmail.com>
In-Reply-To: <5bdc1c8b0909191538h2ebf7697s742f2ee90bb9752a@mail.gmail.com>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <200909200059.01593.volkerarmin@googlemail.com>
X-Archives-Salt: 40147813-2b39-4fe6-8e56-d5f1f50021c3
X-Archives-Hash: ec97700dbd70e9f21a94f240dabca621

On Sonntag 20 September 2009, Mark Knecht wrote:
> On Sat, Sep 19, 2009 at 3:21 PM, Mark Knecht <markknecht@gmail.com> wrote:
> > Hi,
> >   I seem to have lost an external USB drive I've been using on my
> > MythTV backend server for video storage. What commands can I try to
> > get it to wake up or at least show me what's working and what isn't?
> > The drive shows under fdisk /dev/sda. I can see the large partition,
> > and it seems to be the right size, according to fdisk anyway, but I
> > cannot mount it using mount, and so far I cannot get e2fsck to do
> > anything. Both of these fail:
> >
> >
> > mount -t ext2 /dev/sda1 /video
> > mount -t ext3 /dev/sda1 /video
> >
> >   I have power cycled the drive and I've rebooted the MacMini. Nothing
> > changed.
> >
> > Thanks in advance,
> > Mark
> >
> > MacMini ~ # fdisk /dev/sda
> >
> > The number of cylinders for this disk is set to 19929.
> > There is nothing wrong with that, but this is larger than 1024,
> > and could in certain setups cause problems with:
> > 1) software that runs at boot time (e.g., old versions of LILO)
> > 2) booting and partitioning software from other OSs
> >   (e.g., DOS FDISK, OS/2 FDISK)
> >
> > Command (m for help): p
> >
> > Disk /dev/sda: 163.9 GB, 163928604672 bytes
> > 255 heads, 63 sectors/track, 19929 cylinders
> > Units =3D cylinders of 16065 * 512 =3D 8225280 bytes
> > Disk identifier: 0xa9b5c6b5
> >
> >   Device Boot      Start         End      Blocks   Id  System
> > /dev/sda1               1       19929   160079661   83  Linux
> >
> > Command (m for help):
> >
> >
> >
> > MacMini ~ # df
> > Filesystem           1K-blocks      Used Available Use% Mounted on
> > /dev/hda4             75890040  37169416  34865560  52% /
> > udev                     10240       156     10084   2% /dev
> > shm                     257396         0    257396   0% /dev/shm
> > MacMini ~ # fsck -t ext3 /dev/sda
> > fsck 1.41.3 (12-Oct-2008)
> > e2fsck 1.41.3 (12-Oct-2008)
> > fsck.ext3: Superblock invalid, trying backup blocks...
> > fsck.ext3: Bad magic number in super-block while trying to open /dev/sda
> >
> > 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>
> >
> > MacMini ~ # e2fsck -b 8193 /dev/sda
> > e2fsck 1.41.3 (12-Oct-2008)
> > e2fsck: Bad magic number in super-block while trying to open /dev/sda
> >
> > 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>
> >
> > MacMini ~ # fsck -t ext3 /dev/sda1
> > fsck 1.41.3 (12-Oct-2008)
> > e2fsck 1.41.3 (12-Oct-2008)
> > fsck.ext3: Attempt to read block from filesystem resulted in short
> > read while tr            ying to open /dev/sda1
> > Could this be a zero-length partition?
> > MacMini ~ # e2fsck -b 8193 /dev/sda1
> > e2fsck 1.41.3 (12-Oct-2008)
> > e2fsck: Bad magic number in super-block while trying to open /dev/sda1
> >
> > 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>
> >
> > MacMini ~ # e2fsck -b 8193 /dev/sda
> > e2fsck 1.41.3 (12-Oct-2008)
> > e2fsck: Bad magic number in super-block while trying to open /dev/sda
> >
> > 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>
> >
> > MacMini ~ #
>=20
> A little more info:
>=20
> Buffer I/O error on device sda, logical block 12
> sd 0:0:0:0: [sda] Result: hostbyte=3D0x00 driverbyte=3D0x08
> sd 0:0:0:0: [sda] Sense Key : 0x3 [current]
> sd 0:0:0:0: [sda] ASC=3D0x4b ASCQ=3D0x0
> end_request: I/O error, dev sda, sector 96
> Buffer I/O error on device sda, logical block 12
> sd 0:0:0:0: [sda] Result: hostbyte=3D0x00 driverbyte=3D0x08
> sd 0:0:0:0: [sda] Sense Key : 0x3 [current]
> sd 0:0:0:0: [sda] ASC=3D0x4b ASCQ=3D0x0
> end_request: I/O error, dev sda, sector 96
> Buffer I/O error on device sda, logical block 12
> sd 0:0:0:0: [sda] Result: hostbyte=3D0x00 driverbyte=3D0x08
> sd 0:0:0:0: [sda] Sense Key : 0x3 [current]
> sd 0:0:0:0: [sda] ASC=3D0x4b ASCQ=3D0x0
> end_request: I/O error, dev sda, sector 96
>=20
> MacMini ~ # fsck -t ext3 /dev/sda1
> fsck 1.41.3 (12-Oct-2008)
> e2fsck 1.41.3 (12-Oct-2008)
> fsck.ext3: Attempt to read block from filesystem resulted in short
> read while trying to open /dev/sda1
> Could this be a zero-length partition?
> MacMini ~ #
>=20
>=20
> end_request: I/O error, dev sda, sector 95
> __ratelimit: 58 callbacks suppressed
> Buffer I/O error on device sda1, logical block 16
> Buffer I/O error on device sda1, logical block 17
> Buffer I/O error on device sda1, logical block 18
> Buffer I/O error on device sda1, logical block 19
> Buffer I/O error on device sda1, logical block 20
> Buffer I/O error on device sda1, logical block 21
> Buffer I/O error on device sda1, logical block 22
> Buffer I/O error on device sda1, logical block 23
> Buffer I/O error on device sda1, logical block 24
> Buffer I/O error on device sda1, logical block 25
> sd 0:0:0:0: [sda] Result: hostbyte=3D0x00 driverbyte=3D0x08
> sd 0:0:0:0: [sda] Sense Key : 0x3 [current]
> sd 0:0:0:0: [sda] ASC=3D0x4b ASCQ=3D0x0
> end_request: I/O error, dev sda, sector 95
> __ratelimit: 86 callbacks suppressed
> Buffer I/O error on device sda1, logical block 16
> Buffer I/O error on device sda1, logical block 17
> Buffer I/O error on device sda1, logical block 18
> Buffer I/O error on device sda1, logical block 19
> Buffer I/O error on device sda1, logical block 20
> Buffer I/O error on device sda1, logical block 21
> Buffer I/O error on device sda1, logical block 22
> Buffer I/O error on device sda1, logical block 23
> Buffer I/O error on device sda1, logical block 24
> Buffer I/O error on device sda1, logical block 25
> MacMini ~ #
>=20
>=20
> I could try reinstalling the file system but I had a few backups on
> this drive for other systems. (non-critical, but possibly useful) I'd
> like to be sure I cannot recover them before I blow everything away.
>=20
> Thanks,
> Mark
>=20

you might be lucky and able to use smartctl on that device. Sadly most usb=
=20
converters don't support smart even when the drive does.

That could tell you some more, but a quick glance says:

your drive is hosed.=20
Block errors... ugh... maybe the heads had a bit of platter contact.

You can try using magicrescue - or even better photorec.

they won't repair your filesystems - but they might be able to get the data=
 off=20
you are after.

Gl=C3=BCck Auf
Volker