On Tuesday 17 August 2010 01:05 PM, Robert Nichols wrote:
>> I have contacted Western Digital, but I am yet to hear from them. In the
>> > mean time I want to minimize what ever problems I have since I have to
>> > run my machine with this drive until they confirm my RMA.
>> >
>> > I came across
On 08/17/2010 10:37 AM, Suvayu Ali wrote:
> Hi,
>
> On Sunday 15 August 2010 08:27 PM, JD wrote:
That should be possible. Any errors should be a good reason to send the
drives back.
James McKenzie
>> Of course. Be sure to zero out the drive if it contains
>> sensitiv
Hi,
On Sunday 15 August 2010 08:27 PM, JD wrote:
>> > That should be possible. Any errors should be a good reason to send the
>> > drives back.
>> >
>> > James McKenzie
>> >
> Of course. Be sure to zero out the drive if it contains
> sensitive data or private intellectual property before
> sen
On Mon, Aug 16, 2010 at 6:49 PM, Wolfgang S. Rupprecht
wrote:
> Does the hdparm secure erase work on most motherboards? It seems that
> most of newer boards have a bios that disables the secure erase at bios
> boot time. Only my oldest mobo allows me to use the security erase. I
> find that I h
"Bryn M. Reeves" writes:
> At a bare minimum you should use the drive's built-in secure erase
> feature (either using hdparm's (experimental) support or using the
> vendor's proprietary tools).
Does the hdparm secure erase work on most motherboards? It seems that
most of newer boards have a bio
On 08/16/2010 04:27 AM, JD wrote:
> Of course. Be sure to zero out the drive if it contains
> sensitive data or private intellectual property before
> sending it for replacement.
>
> dd if=/dev/zero of=/dev/sdx bs=256M
Just to be clear this is not at all sufficient if you really, truly care
about
On 08/15/2010 08:14 PM, James McKenzie wrote:
> JD wrote:
>>On 08/15/2010 06:44 PM, Suvayu Ali wrote:
>>
>>> On Sunday 15 August 2010 10:17 AM, James McKenzie wrote:
>>>
Got a good backup of this drive? Looks like it needs to be retested, in
a different machine and if it fails, rep
JD wrote:
> On 08/15/2010 06:44 PM, Suvayu Ali wrote:
>
>> On Sunday 15 August 2010 10:17 AM, James McKenzie wrote:
>>
>>> Got a good backup of this drive? Looks like it needs to be retested, in
>>> a different machine and if it fails, replaced.
>>>
>>> I had a drive that exhibited the s
On 08/15/2010 06:44 PM, Suvayu Ali wrote:
> On Sunday 15 August 2010 10:17 AM, James McKenzie wrote:
>> Got a good backup of this drive? Looks like it needs to be retested, in
>> a different machine and if it fails, replaced.
>>
>> I had a drive that exhibited the same behavior and eventually, i
Robert Nichols wrote:
> On 08/15/2010 12:05 PM, Suvayu Ali wrote:
>
>>> SMART Attributes Data Structure revision number: 16
>>> Vendor Specific SMART Attributes with Thresholds:
>>> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
>>> WHEN_FAILED RAW_VALUE
>>>1 Raw
On 08/15/2010 06:44 PM, Suvayu Ali wrote:
> On Sunday 15 August 2010 10:17 AM, James McKenzie wrote:
>> Got a good backup of this drive? Looks like it needs to be retested, in
>> a different machine and if it fails, replaced.
>>
>> I had a drive that exhibited the same behavior and eventually, i
Hi Robert,
On Sunday 15 August 2010 06:46 PM, Robert Nichols wrote:
> Your problem is the 172 sectors pending reallocation. Those are sectors
> that are currently unreadable and will be reallocated to spare sectors
> the next time they are written. The problem is that the drive has no
> way to k
On 08/15/2010 12:05 PM, Suvayu Ali wrote:
>> SMART Attributes Data Structure revision number: 16
>> Vendor Specific SMART Attributes with Thresholds:
>> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
>> WHEN_FAILED RAW_VALUE
>>1 Raw_Read_Error_Rate 0x002f 199
On Sunday 15 August 2010 10:17 AM, James McKenzie wrote:
> Got a good backup of this drive? Looks like it needs to be retested, in
> a different machine and if it fails, replaced.
>
> I had a drive that exhibited the same behavior and eventually, it failed.
>
I downloaded the bootable iso of the
Suvayu Ali wrote:
> Hi everyone,
>
> Some background:
> Recently my RAM went bad, and I realised it too late. Towards the last
> few of days my desktop had crashed more than once. Yesterday I received
> the replacement RAMs from RMA. On installing them and turning on my
> machine I noticed error
Hi everyone,
Some background:
Recently my RAM went bad, and I realised it too late. Towards the last
few of days my desktop had crashed more than once. Yesterday I received
the replacement RAMs from RMA. On installing them and turning on my
machine I noticed errors like these,
Device: /dev/sdb
16 matches
Mail list logo
