public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: USB drive dead? (Commands to check?)
Date: Sat, 19 Sep 2009 15:38:41 -0700	[thread overview]
Message-ID: <5bdc1c8b0909191538h2ebf7697s742f2ee90bb9752a@mail.gmail.com> (raw)
In-Reply-To: <5bdc1c8b0909191521j72388919w35e54b577b55ae60@mail.gmail.com>

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 = 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 <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 ~ #
>

A little more info:

Buffer I/O error on device sda, logical block 12
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current]
sd 0:0:0:0: [sda] ASC=0x4b ASCQ=0x0
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=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current]
sd 0:0:0:0: [sda] ASC=0x4b ASCQ=0x0
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=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current]
sd 0:0:0:0: [sda] ASC=0x4b ASCQ=0x0
end_request: I/O error, dev sda, sector 96

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 ~ #


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=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current]
sd 0:0:0:0: [sda] ASC=0x4b ASCQ=0x0
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 ~ #


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.

Thanks,
Mark



  reply	other threads:[~2009-09-19 22:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-19 22:21 [gentoo-user] USB drive dead? (Commands to check?) Mark Knecht
2009-09-19 22:38 ` Mark Knecht [this message]
2009-09-19 22:59   ` [gentoo-user] " Volker Armin Hemmann
2009-09-19 23:05     ` Mark Knecht
2009-09-19 23:12   ` walt
2009-09-19 23:32     ` Volker Armin Hemmann
2009-09-19 23:40     ` Mark Knecht
2009-09-19 23:48       ` Volker Armin Hemmann
2009-09-20  0:01         ` Mark Knecht
2009-09-20 10:24           ` Stroller
2009-09-20 18:41             ` Mark Knecht
2009-09-21  8:21               ` Neil Bothwick
2009-09-21 21:38                 ` Mark Knecht
2009-09-21 19:07 ` [gentoo-user] " Paul Hartman
2009-09-21 21:39   ` Mark Knecht
2009-09-22 20:20     ` Mark Knecht
2009-09-24 19:02       ` Mick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5bdc1c8b0909191538h2ebf7697s742f2ee90bb9752a@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox