On 06/10/2010 05:20 PM, Gary Wright wrote:
> On Thu, Jun 10, 2010 at 4:06 PM, Axel Müller wrote:
>
>> I think it was about 1 1/2 year ago when there was a big fuss about some
>> Seagate drive models going bad because of a firmware bug. Seagate
>> provided a firmware update for these. If you haven
On Thu, Jun 10, 2010 at 4:06 PM, Axel Müller wrote:
> I think it was about 1 1/2 year ago when there was a big fuss about some
> Seagate drive models going bad because of a firmware bug. Seagate
> provided a firmware update for these. If you haven't allready done so,
> you might want to check the
Am Thu, 10 Jun 2010 11:06:36 -0500 schrieb David C. Rankin:
> Your experience sounds exactly like mine over the past year. I
> have had 4
> Seagate drives supposedly "go bad" after 13-14 months use (1-2 months
> after warranty runs out).
Hi.
I think it was about 1 1/2 year ago when there w
On 06/10/2010 05:06 PM, David C. Rankin wrote:
> Your experience sounds exactly like mine over the past year. I have had
> 4
> Seagate drives supposedly "go bad" after 13-14 months use (1-2 months after
> warranty runs out). The problem is always the same - smart says there is a
> badblock p
On 06/10/2010 08:46 AM, Mauro Santos wrote:
>>From my experience only, I find it quite hard to know when a disk is
> about to fail. Currently I am trying to figure out if an hard disk in a
> machine I manage is about to fail or not (3'5 drive), smart says it is,
> badblocks can't find anything wron
On 06/10/2010 02:00 AM, David C. Rankin wrote:
> I do like badblocks. It saved my bacon once before. Rather than doing
> the
> badblock recovery (since I have the data), what I think I'll do is search a
> bit
> more for the 'fdisk -l' info for the drive. If I find it, I'll try recreating
>
On 06/09/2010 03:44 PM, Mauro Santos wrote:
> On 06/09/2010 07:16 PM, David C. Rankin wrote:
>>
>> Before I add the drive to the heap of drives in my 'dead drive box' are
>> there
>> any other silver bullets I should try to try and resurrect the drive? (Data
>> isn't an issue, it's all backed
On 06/09/2010 03:14 PM, Sergey Manucharian wrote:
> Hi David,
>
> Excerpts from David C. Rankin's message of Wed, 09 Jun 2010 13:16 -0500:
>
>> Before I add the drive to the heap of drives in my 'dead
>> drive box' are there any other silver bullets I should try to try and
>> resurrect the d
On 06/09/2010 07:16 PM, David C. Rankin wrote:
>
> Before I add the drive to the heap of drives in my 'dead drive box' are
> there
> any other silver bullets I should try to try and resurrect the drive? (Data
> isn't an issue, it's all backed up :-)
>
> What say the gurus?
>
Try is
Hi David,
Excerpts from David C. Rankin's message of Wed, 09 Jun 2010 13:16 -0500:
> Before I add the drive to the heap of drives in my 'dead
> drive box' are there any other silver bullets I should try to try and
> resurrect the drive? (Data isn't an issue, it's all backed up :-)
I had si
On 06/09/2010 01:16 PM, David C. Rankin wrote:
> The situation:
>
> On reboot - grub 22 error
> boot arch install cd 2009-08, cannot mount drive
> partition table shows 1 partition /dev/hda1 (PATA drive) (should be 3)
> (I can't put my hands on the saved 'fdisk -l' data, it
Guys,
I have a disk on a arch box that has gone south. No prior warning, no
smart
errors, no nothing. Granted the drive is 5-6 years old, so a complete crater is
not out of the question.
The situation:
On reboot - grub 22 error
boot arch install cd 2009-08, cannot mount
12 matches
Mail list logo
