[PLUG] Failed Go-Flex hard drive

[John Jason Jordan]

On Sun, 27 Jan 2013 22:23:43 -0800
Dale Snell <ddsnell at frontier.com> dijo:
 
>> I opened Palimpsest, which reported the Smart information as "Disk
>> has a few bad sectors." I unmounted it and ran "e2fsck -p /dev/sdb"
>> which reported "Bad magic number in superblock while trying to
>> open /dev/sdb: The superblock could not be read or does not describe
>> a correct ext2 filesystem." (It is ext4.) The error message further
>> suggested to run "e2fsck -b 8193 <device>." I have not tried this as
>> I have no idea what this will do. 

>The -b option to e2fsck tells it to use an alternate superblock,
>this one at location 8193.  When an ext2/3/4 filesystem is
>created, is builds several spare superblocks, just in case one
>goes bad.  This sounds like such a situation.  In fact, I would do
>
>    # e2fsck -b 8193 -fpDC 0 /dev/sdb

Tried it. Same error messages. :(

Might there be other spare superblocks I could ask it to use?

>You should check out the man pages for e2fsck(8), mkext2(8), and
>tune2fs(8).  You might find them a bit dense, but it's good
>information to know.  If you have questions, well, you know where
>to ask.  :-)

I did check out the man page for e2fsck, but most of it was over my
head. I have used tune2fs to find a UUID, but will check out its man
page and the man page for mkext2 as well.

Another question: When the error message says "a correct ext2
filesystem," is it using "ext2" as a generic term for "any ext
filesystem"? I ask because I know the filesystem is ext4, therefore the
error message confuses me. Like "of course it's not a valid ext2
filesystem, stupid computer! It's an ext4 filesystem!"

Thanks for the suggestions. :)