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 ) id 1Mp8J3-0007Qr-Nq for garchives@archives.gentoo.org; Sat, 19 Sep 2009 22:21:25 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AE402E08BF; Sat, 19 Sep 2009 22:21:24 +0000 (UTC) Received: from mail-yw0-f196.google.com (mail-yw0-f196.google.com [209.85.211.196]) by pigeon.gentoo.org (Postfix) with ESMTP id 805D6E08BF for ; Sat, 19 Sep 2009 22:21:24 +0000 (UTC) Received: by ywh34 with SMTP id 34so2630885ywh.10 for ; Sat, 19 Sep 2009 15:21:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=yMjuFsD05Bc2kCjkudeV+ctxRo/gcl2+X8A5sRMO6ZA=; b=JLiep52h8N85fbVi7GaNQu+hwOFuRl0e6GcLTZv9PRqB7O3Voh+PMYXQSXjyrIMYU/ D5hQobx8nBH8EHtsOiNc6fxQqfWVa/mpyrhVgMM/R08LTl4DRBujNT3BuWIxd19xluRk ALtIwdL8EExDGZaDsPrehwKu3HnvdIDkM4PQI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=um1JPXMeADEl5q+DaxHhfCcoeAY0Ou2FT1a4G/Q9zYLvrkcxQrsMVMdmDmSUCqxQa2 pdmwCXxTYYAR4+FIKBne1C0VLmHe2G56M0vTlDenamAMSjbfhP3OFWGKMYxzPJ1mTzLa aed+uQ4U91KrMHCbvIcxM8BJvL4KrNmdipfA0= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.150.239.15 with SMTP id m15mr5721594ybh.109.1253398884226; Sat, 19 Sep 2009 15:21:24 -0700 (PDT) Date: Sat, 19 Sep 2009 15:21:24 -0700 Message-ID: <5bdc1c8b0909191521j72388919w35e54b577b55ae60@mail.gmail.com> Subject: [gentoo-user] USB drive dead? (Commands to check?) From: Mark Knecht To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 1e3e6ff8-4109-47a9-8af7-9a4d24d42a3d X-Archives-Hash: 02a6f36e966c5f36c1fb0beb751eb451 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 = cylinders of 16065 * 512 = 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 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 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 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 MacMini ~ #