geoffschultz
New Member
- Messages
- 3
- Location
- Marlborough
I have a 2 TB eSATA drive that contains my backups. This drive has been working well for years and isn't accumulating errors. It was a basic disk until I deleted a partition that I wasn't using any more and expanded the size of the backup partition. That worked fine until yesterday when I was no longer able to access either of the partitions on the drive. Here's the output of the disk manager relating to this drive:
When I use Windows Explorer to access either of the volumes on the drive, I get a message "Z:\ is not accessible". When I click on Computer, I see both of the volumes on the disk, but there is no information regarding disk space used/available. If I right click on the drive and go Properties/Tools/Error Check, I get a message "The disk check cannot be performed because windows can not access the disk."
However, if I go into Disk Manage, right click on the partition and go to Properties/Tools/Error Check, I can scan the drive! It completes showing that it found the following errors:
I then get a message that I need to reboot the computer to repair these errors, which I do. According to the event log, it repairs all of the errors, but I'm back at the same place that I was before and a scandisk of the volume shows the same errors.
Any ideas on how to fix this?
-- Geoff
When I use Windows Explorer to access either of the volumes on the drive, I get a message "Z:\ is not accessible". When I click on Computer, I see both of the volumes on the disk, but there is no information regarding disk space used/available. If I right click on the drive and go Properties/Tools/Error Check, I get a message "The disk check cannot be performed because windows can not access the disk."
However, if I go into Disk Manage, right click on the partition and go to Properties/Tools/Error Check, I can scan the drive! It completes showing that it found the following errors:
Chkdsk was executed in scan mode on a volume snapshot.
Checking file system on Z:
Volume label is Backup_Files.
Stage 1: Examining basic file system structure ...
Stage 2: Examining file name linkage ...
Stage 3: Examining security descriptors ...
Found corrupt security descriptor entry at offset 0x80000 in \$Secure <0,0x9>:$SDS
... queued for offline repair.
[repeated 50 times]
Windows has found problems that must be fixed offline.
Please run chkdsk /spotfix to fix the issues.
----------------------------------------------------------------------
CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Multiple object id files found. Ignoring extra object id files.
Multiple quota files found. Ignoring extra quota files.
Multiple reparse file found. Ignoring extra reparse files.
Multiple Usn Journal file found. Ignoring extra Usn Journal files.
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Repairing an index entry with id 256 in index $SII of file 9.
[repeated 50 times]
The security Id 0x100 of security descriptor entry at offset 0x100000
is a duplicate.
[repeated 50 times]
Repairing the security file record segment.
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
1890993151 KB total disk space.
1654698064 KB in 355988 files.
149256 KB in 13126 indexes.
0 KB in bad sectors.
499283 KB in use by the system.
65536 KB occupied by the log file.
235646548 KB available on disk.
4096 bytes in each allocation unit.
472748287 total allocation units on disk.
58911637 allocation units available on disk.
I then get a message that I need to reboot the computer to repair these errors, which I do. According to the event log, it repairs all of the errors, but I'm back at the same place that I was before and a scandisk of the volume shows the same errors.
Any ideas on how to fix this?
-- Geoff
My Computer
System One
-
- OS
- Windows 8
- System Manufacturer/Model
- Various - 3 systems
- Memory
- 9-16 GB