From: Denis Wegge <denis_wegge@pandora.be>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS unable to mount, recover data
Date: Wed, 12 Dec 2007 21:05:50 +0100 [thread overview]
Message-ID: <47603F1E.1090901@pandora.be> (raw)
In-Reply-To: <Pine.LNX.4.64.0712120825540.3691@p34.internal.lan>
It was a Western Digital 320GB SATAII 16MB, WD3200KS-00PFB0 (don't
remember the name of the model).
Justin Piszcz wrote:
> Just curious what brand/make/model was it that failed?
>
> On Wed, 12 Dec 2007, Denis Wegge wrote:
>
>> I tried putting it in the freezer, but that didn't help. Tests on
>> another computer also show that the hard drive cannot be accessed.
>>
>> It seems like the data on the disk is definitely lost. The disk,
>> however, has a 3 year warranty, so I'm going to return it.
>>
>> Thanks for your help.
>>
>> Denis
>>
>> Justin Piszcz wrote:
>>>
>>>
>>> On Wed, 5 Dec 2007, Denis Wegge wrote:
>>>
>>>> Hello
>>>>
>>>> I am having trouble with the XFS filesystem on a 320GB Western Digital
>>>> SATA harddisk. For no obvious reason the partition can no longer be
>>>> mounted. The following error occurs:
>>>>
>>>> knoppix@Knoppix:~$ sudo mount /dev/sda1 /mnt/sda1
>>>> mount: /dev/sda1: can't read superblock
>>>
>>> Looks like your disk is dying or dead from your logs. You can try
>>> putting it
>>> in a plastic airtight bag then put it in the freezer and try again but
>>> otherwise if that does not work, its time for the trash bin (after
>>> you try)
>>> a dd and overwrite the disk but with that many bad sectors it looks like
>>> it has really gone south.
>>>
>>> Insert new disk, restore from backup.
>>>
>>> Justin.
>>>
>>>
>>>
>>
>>
>
>
prev parent reply other threads:[~2007-12-12 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 12:17 XFS unable to mount, recover data Denis Wegge
2007-12-05 12:47 ` Justin Piszcz
2007-12-12 9:19 ` Denis Wegge
2007-12-12 13:26 ` Justin Piszcz
2007-12-12 20:05 ` Denis Wegge [this message]
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=47603F1E.1090901@pandora.be \
--to=denis_wegge@pandora.be \
--cc=jpiszcz@lucidpixels.com \
--cc=xfs@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.