• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

NTFS better??

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Originally posted by: bsobel
The NTFS logging capabilities ensure that the file system itself can return itself to a safe state after failure (for example sudden loss of power). This does not in anyway guarantee that user data isn't destroyed or lost in the rollback...
Click to expand...

Agreed!

I've had better luck, over the years restoring NTFS drives than FAT drives, but I cannot think of one instance where it was 100%.

HDs seem to be much more resilient than flash drives, e.g. flash drives seem to be much less forgiving - and FAT seems to work best on flash drives, sooooo...

That's why I was thinking about giving FATxx a whirl on my doomed W2K Pro hard drive.

Curiosity killed the Fat, I suppose, but the same applies to NTFS and its 9-lives, IMHO - just a matter of degree... 😉
 
That's why I was thinking about giving FATxx a whirl on my doomed W2K Pro hard drive.
Click to expand...

Seriously, if your getting delayed write failures on the drive, copy the data off and put a few drill bits thru the case (thats how I clear drives after wiping them). Fat/NTFS isnt going to make a difference if the drive is bad (well technically NTFS Is better as you have the drives bad sector list as well as the NTFS bad sector list and it duplicates more of they key structures). That said, when I hear write failure I figure the $100 for a new drive is so much cheaper than the later aggrevation of fixing the system...
 
Originally posted by: bsobel
Seriously, if your getting delayed write failures on the drive, copy the data off and put a few drill bits thru the case...

(W)hen I hear write failure I figure the $100 for a new drive is so much cheaper than the later aggrevation of fixing the system...
Click to expand...

I don't know what puked the primary drive, this time.

Last time this happened was a year ago, almost to the day. I guess that's all these $100 HDs are good for nowadays.

Let me tell you what occurred...

Wife's machine with dual 80GB SATAs.

It was running s-l-o-w and I was about to reboot it, when I got the dreaded "delayed write failed" message.

At that point, W2K Pro locked up, with the 'drive activity' LED, on the front of the case, lit-up solid...

I performed several 'black-screen' on/off cold boot cycles with the 'drive activity' LED lit-up solid every time.

I disconnected/reconnected the SATA cables - powered up - activity LED went dark - and her machine posted again, but now with the obligatory & illusive 'Error Loading OS...' message.

And, that's the way it's been ever since - despite trying everything in my bag of tricks - rebuilt the MBR, MFT, REG, yada, yada, yada.

It'll boot from a floppy and/or CD, but not from the HD.

Maybe I'll swap the primary and secondary drives around. Then again...

I've had a new ABIT VT7 mobo sitting in the closet for 3 years. LoL! Maybe it's time to put it into service, and do a general refurb! 😀
 
Originally posted by: bsobel
That's why I was thinking about giving FATxx a whirl on my doomed W2K Pro hard drive.
Click to expand...

Seriously, if your getting delayed write failures on the drive, copy the data off and put a few drill bits thru the case (thats how I clear drives after wiping them).
Click to expand...

Recip saw with bimetal Wood & Nails blades is fun too. Just don't try cutting directly through the drive's motor. Eye protection definitely mandatory 😉

As for using FAT32 for the OS... horrors. There goes normal security as I know it 😕

 

Eureka!!! Finally figured it out...

After doing yet another fruitless diagnostic (both SATA drives were 100%) I discovered that the BIOS was borked.

Somehow the boot order got changed. And, I swear I haven't changed anything in months - really! Somehow it must have flipped out mid-session...

Once I got W2K to boot, I checked the system with Belarc Advisor, and found out several security updates needed to be reinstalled.

LoL! That was 2 weeks of pure torture!

Good 'ol NTFS! Saved me $100... 😀
 
Originally posted by: mechBgon
Recip saw with bimetal Wood & Nails blades is fun too. Just don't try cutting directly through the drive's motor. Eye protection definitely mandatory 😉
Click to expand...
Reminds me of a good horror movie I saw lately.

Just remember that we're talking NTFS here. Be sure to cut the drive into small pieces, or the data will be recoverable. 😛
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top