On Sep 20, 2008, at 11:21 PM, Tannis Baker wrote:
I don't have any Windows stuff on the machine.
It need not be on that machine, anywhere on your network, and
specifically Windows Vista or Windows 2008 Server.
So, I backed up my HD and then, before looking into how to zero it ( a
new one on me!), I tried reconfiguring the ethernet speed setting to
10baseT/UTP half-duplex.
Ok great, it works well at the lowest possible speed. Check what your
router supports, chances are it is 100 Mbs. If so, try moving the
iMac's link speed to 100 Mbs Full Duplex and see if it works. If not,
try 10 Mbs Full Duplex.
There is a good chance the router will support its max speed, it is
likely just getting confused with the auto negotiation of the speed.
Now I shall zero away and see if that fixes the HD problem. The
interesting thing here is that Disk Utility likes any bootable copy I
make onto an external drive - it is only the new internal that is
showing
the volume probs.
If the drive has bad sectors on it, then it will develop drive
corruption problems very quickly. The Zero format will mark the bad
sectors as non-usable. The only issue is, those are SUPPOSED to be
marked by the manufacturer (all drives will have bad sectors right
from manufacturing, so they are tested and mapped before shipping).
So if you have bad ones on a brand new drive, hopefully it is just
the drive maker has crappy quality control and isn't testing them (is
this a Western Digital or Maxtor drive?) but it could be a sign of a
defective drive as well. (Its a shame that Seagate bought Maxtor, I'd
like to say it will bring up the quality of Maxtor, but that never
happens, instead I'm sure it will bring down the quality of Seagate).
Also, regarding liking a copy but not the original, that is because
the corruption is happening in the drive tables, which are specific
to the format on the drive. Those don't copy over to a new drive. So
you are cloning data off a bad drive, on to a good drive, and leaving
the bad stuff behind. Thus Disk Util reports the copy as good, but
the original as bad.
The danger here is, the bad may not be properly readable, so it is
possible to copy the files over and have the copy be corrupt because
it couldn't be properly read off the bad drive. However, the copy may
still test as good, because the drive believes it to be so, it
doesn't know that the data stream it was given to write out was a bad
stream. So when the data is checked, the drive reports that the data
it was given is the data that was written, so it must be good, even
though the data it has is not the correct data based on the original.
Hopefully that made sense.
-chris
<www.mythtech.net>
___________________________________________________________________________
To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to
<[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
