On Mar 23, 4:10 pm, Dan dantear...@gmail.com wrote:
At 3:04 PM -0400 3/23/2009, insightinmind wrote:
The answer then seemed to be yes ... zeroing a partition would cause
the controller to map out any bad sectors.
Not seems - is. Yes. The controller ALWAYS maps out bad blocks
whenever
At 9:17 AM -0700 3/25/2009, Al Poulin wrote:
If I may summarize the discussion about bad sectors.
Bad sectors (blocks) get mapped out on the fly during normal
read/write operations.
Bad sectors (blocks) get mapped out within a volume/partition when
you zero the volume/partition in Disk
On Mar 25, 12:51 pm, Dan dantear...@gmail.com wrote:
At 9:17 AM -0700 3/25/2009, Al Poulin wrote:
Bad sectors (blocks) get mapped out on the fly during normal
read/write operations.
Correct.
So, unlike the advice of 5 -10 years ago, we no longer need to map out
bad blocks in an entire
At 10:47 AM -0700 3/25/2009, Al Poulin wrote:
On Mar 25, 12:51 pm, Dan dantear...@gmail.com wrote:
At 9:17 AM -0700 3/25/2009, Al Poulin wrote:
Bad sectors (blocks) get mapped out on the fly during normal
read/write operations.
Correct.
So, unlike the advice of 5 -10 years ago
Drives
On Mar 22, 2009, at 10:58 PM, tortoise wrote:
I'd like the thank the originator of this tip.
I had a few drives reporting bad spots (in the full SMART report which
you get only when you download the source and build it; and also when
I tried to secure erase I got write errors *sometimes*
Greetings ( + )!( + )
Checking with Western Digital and Seagate, they have an application
that runs on a WINTEL PCEE that will do the low-level format which
will mark, i.e. remove the bad sectors from the drive but fortunately
I haven't own a WinTel (DOS) computer for more than 30 years.
Cheers
At 8:54 AM -0400 3/23/2009, insightinmind wrote:
I believe the bad sectors are mapped out, even when zeroing the
partitions ... as someone said, the controller doesn't function
around partition boundaries (my paraphrasing). Still not sure of the
answer here.
Not sure what controller doesn't
I'd like the thank the originator of this tip.
I had a few drives reporting bad spots (in the full SMART report which
you get only when you download the source and build it; and also when
I tried to secure erase I got write errors *sometimes* w/ hangs, noted
in apple console logs)
Yes, erasing
On Mar 20, 2009, at 5:39 PM, insightinmind wrote:
On Mar 20, 2009, at 8:15 PM, Charles Davis wrote:
Please note, I'm talking about the 'Write Zeros' operation, NOT just
'Erasing' ---[ Which is just Zeroing out the directory data, not
elimination the 'bit patterns' on the platter
What about SMART (S.M.A.R.T.) status and functionality? Shouldn't the
drive's built-in SMART routines map out bad blocks? If they do, will the
Surface Scan still try to read those blocks?
BTW, is Tech Tools Deluxe really TechTool Pro, or is it a different program
I haven't encoountered yet?
On Mar 20, 2009, at 6:36 AM, Aaron wrote:
What about SMART (S.M.A.R.T.) status and functionality?
Shouldn't the drive's built-in SMART routines map out bad blocks?
If they do, will the Surface Scan still try to read those blocks?
AFAIK, original S.M.A.R.T. Status didn't do any disk
On Mar 20, 2009, at 7:12 PM, Charles Davis wrote:
On Mar 20, 2009, at 11:57 AM, Dan wrote:
That's re-initializing a drive. You cannot reformat modern drives.
The process of zeroing it -- writing zeros to each sector on the
drive causes the hardware's bad block replacement mechanism to
On Mar 20, 2009, at 8:06 PM, insightinmind wrote:
On Mar 20, 2009, at 7:12 PM, Charles Davis wrote:
On Mar 20, 2009, at 11:57 AM, Dan wrote:
That's re-initializing a drive. You cannot reformat modern drives.
The process of zeroing it -- writing zeros to each sector on the
drive
On Mar 20, 2009, at 8:15 PM, Charles Davis wrote:
Please note, I'm talking about the 'Write Zeros' operation, NOT just
'Erasing' ---[ Which is just Zeroing out the directory data, not
elimination the 'bit patterns' on the platter surface.]
Same meaning here ... sometimes called Secure Erase
At 7:12 PM -0400 3/20/2009, Charles Davis wrote:
The process of zeroing it -- writing zeros to each sector on the
drive causes the hardware's bad block replacement mechanism to
trigger as needed.
What isn't being said here, is whether the 'bad block' mechanism is
operational when
At 8:11 PM -0400 3/20/2009, Charles Davis wrote:
I've always assumed partitions were being treated like a separate
volume, and was being re-mapped.
That's the way I'd like it to be, which means that the 'Bad Blocks'
routines probably only work when Zeroing the complete Hard Disk.
No.
The
Greetings ( + )!( + )
What you describe is exatly the same that I was having.
Used Tech Tools Deluxe Surface Scan on my 320Gb drive (took about 12
Hrs.) and the report was Failed - Bad Blocks so I've laid that disk
to rest RIP and have ordered a new drive.
If you have Tech Tools Deluxe run the
Hi All - thanks for your advice.
I think it's definitely a corrupted system problem. Tried to do an
Archive and Install and the problem got worse, to the point where Disk
First Aid has gone from saying there is nothing wrong with the disk,
to saying it cannot be repaired! Yuck!
From the OS X
As I said, I need help!
I have a 1 Ghz Dual Processor Quick Silver with 1.5 GB ram, running OS
10.4.11
I had two harddrives installed. My main drive is 150 GB but shows up
as being 120 gb. The other harddrive was about 80 GB.
Anyway... I turned the computer on today and heard a persistant
You may need to change the jumper setting and/or cable position on
your boot drive. The easiest way to see if this is the problem is to
put the old dead drive back in place, just as it was before. Your Mac
should boot normally and you will be able to use Disk Utility to check
the disk and
On Mar 17, 6:39 am, Janine Cheung hbbst...@gmail.com wrote:
As I said, I need help!
I have a 1 Ghz Dual Processor Quick Silver with 1.5 GB ram,
running OS
10.4.11
I have a QS 2002 Dual 1GHz ... nice machine.
I believe your HD settings are CS or Cable Select. Make sure you
didn't
First things First Remove, or at least disconnect the second HD
- leave out of the mix until you get the first HD working. [That
way THOSE files will be safe from further damage, and probably
recoverable later.] [Treat that HDs problems as a separate problem.]
On Mar 17, 2009, at
On Mar 17, 2009, at 6:39 AM, Janine Cheung wrote:
As I said, I need help!
I have a 1 Ghz Dual Processor Quick Silver with 1.5 GB ram,
running OS
10.4.11
I had two harddrives installed. My main drive is 150 GB but shows up
as being 120 gb.
You must have a pre-2002 Quicksilver if
On Tue, Mar 17, 2009 at 6:39 AM, Janine Cheung hbbst...@gmail.com wrote:
Then I rebooted using the main drive, and that's when it gets stuck
(as detailed above)
My files are still on the boot drive, but how can I get the harddrive
to mount?
snip!
Any other suggestions?
You might try an Archive and Install, I had this happen on my G4
iBook, but that was due to a bad DVD drive, that didn't install all
the system files... Sounds like a similar problem. (System files
corrupted) (Archive and install keeps all your files safe.)
To get your files off, you could
On Mar 17, 2009, at 5:39 AM, Janine Cheung wrote:
My files are still on the boot drive, but how can I get the harddrive
to mount?
I don't have an up-to-date version of Disk Warrior. if I got the
appropriate version and ran it, building a new volume directory for
the disk, would that
26 matches
Mail list logo
