Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)
I can't explain what is going on but this is driving me crazy. A
couple of weeks ago I used XP's (XP SP2) Disk Management to reformat a
180GB WD IDE drive as a single NTFS partition with 64K clusters (as
recommended for use with video recordings). All appeared fine after I
copied backed up data back onto the drive. However after powering
off/on, XP sees the drive as empty with no operating system (status is
seen as "Healthy"). Partition Magic and other disc utilities see the
drive as having no problems at all but XP is what counts. When I
attempt to access that drive in XP, the error message "An error
occurred reading folder. The file or directory is corrupted and
unreadable." OK, that would be expected I guess if XP doesn't see a
file system. I had used this drive for 1.5 years with no problems
before I changed cluster size.
I tried to reformat a couple of times (still 64K clusters) and the
same problem would occur after powering off/on. Before giving up, I
tried the drive in another computer running XP and this time the drive
couldn't even be formatted. So I have RMAed that drive and am awaiting
a replacement.
However here is where things get interesting. I just installed a new
Seagate 120GB SATA drive. Again I formatted it using Disk Management
with 64K clusters (full format). I copied some data onto it and it
seemed fine. But after I had powered off/on a few times, once again XP
sees the drive as 100% empty with no file system. Again, Partition
Magic doesn't see any problem with the drive. HOW CAN THIS BE
HAPPENING? This is an entirely new drive, using SATA instead of ATA on
an entirely different controller! The only thing in common is that
both were formatted with 64K clusters. Is there any known problem with
64K clusters that would cause XP to not recognize the NTFS file
system???
I don't yet know if my new drive is also dead but I'm becoming
downright paranoid. Any help here is greatly appreciated.
I can't explain what is going on but this is driving me crazy. A
couple of weeks ago I used XP's (XP SP2) Disk Management to reformat a
180GB WD IDE drive as a single NTFS partition with 64K clusters (as
recommended for use with video recordings). All appeared fine after I
copied backed up data back onto the drive. However after powering
off/on, XP sees the drive as empty with no operating system (status is
seen as "Healthy"). Partition Magic and other disc utilities see the
drive as having no problems at all but XP is what counts. When I
attempt to access that drive in XP, the error message "An error
occurred reading folder. The file or directory is corrupted and
unreadable." OK, that would be expected I guess if XP doesn't see a
file system. I had used this drive for 1.5 years with no problems
before I changed cluster size.
I tried to reformat a couple of times (still 64K clusters) and the
same problem would occur after powering off/on. Before giving up, I
tried the drive in another computer running XP and this time the drive
couldn't even be formatted. So I have RMAed that drive and am awaiting
a replacement.
However here is where things get interesting. I just installed a new
Seagate 120GB SATA drive. Again I formatted it using Disk Management
with 64K clusters (full format). I copied some data onto it and it
seemed fine. But after I had powered off/on a few times, once again XP
sees the drive as 100% empty with no file system. Again, Partition
Magic doesn't see any problem with the drive. HOW CAN THIS BE
HAPPENING? This is an entirely new drive, using SATA instead of ATA on
an entirely different controller! The only thing in common is that
both were formatted with 64K clusters. Is there any known problem with
64K clusters that would cause XP to not recognize the NTFS file
system???
I don't yet know if my new drive is also dead but I'm becoming
downright paranoid. Any help here is greatly appreciated.
Facebook
Twitter
Instagram