Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.
Ntfs log error
I am getting the following error in my logs:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2.
I am not completely certain which volume the error is referring to. Here is the output from diskpart:
DISKPART> list disk
Disk ### Status Size Free Dyn Gpt
-------- ---------- ------- ------- --- ---
Disk 0 Online 931 GB 0 B
Disk 1 Online 932 GB 0 B
Disk 2 Online 932 GB 17 MB
Disk 3 Online 932 GB 0 B
DISKPART> list volume
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 E DVD-ROM 0 B No Media
Volume 1 C NTFS Partition 159 GB Healthy System
Volume 2 D NTFS Partition 771 GB Healthy
Volume 3 X BACKUP01 NTFS Partition 932 GB Healthy
Volume 4 SBS_Backup NTFS Partition 931 GB Healthy
Volume 5 F Monthly Arc NTFS Partition 932 GB Healthy
Physically Volumes C: and D: are partitions on the internal 3 drive RAID 5 array.
Drive X is an external USB drive which is used by the SBS backup exclusively
Drive E is an External USB used for flat file backup
Drive F is an External USB used for archive purposes.
The internal SBS backup has failed the last few days giving a drive related error but the diskpart output makes it look to me like the log entry is referring to the D: partion (where all our data is). We have not noted any problems accessing or writing to files on the server.
So my question is which drive/partition is the error referring to and how do I go about fixing it. Also what are the risks associated with running chkdsk on a RAID and are there precautions I should take. Thanks
This stuff scares the crap out of me.........
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2.
I am not completely certain which volume the error is referring to. Here is the output from diskpart:
DISKPART> list disk
Disk ### Status Size Free Dyn Gpt
-------- ---------- ------- ------- --- ---
Disk 0 Online 931 GB 0 B
Disk 1 Online 932 GB 0 B
Disk 2 Online 932 GB 17 MB
Disk 3 Online 932 GB 0 B
DISKPART> list volume
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 E DVD-ROM 0 B No Media
Volume 1 C NTFS Partition 159 GB Healthy System
Volume 2 D NTFS Partition 771 GB Healthy
Volume 3 X BACKUP01 NTFS Partition 932 GB Healthy
Volume 4 SBS_Backup NTFS Partition 931 GB Healthy
Volume 5 F Monthly Arc NTFS Partition 932 GB Healthy
Physically Volumes C: and D: are partitions on the internal 3 drive RAID 5 array.
Drive X is an external USB drive which is used by the SBS backup exclusively
Drive E is an External USB used for flat file backup
Drive F is an External USB used for archive purposes.
The internal SBS backup has failed the last few days giving a drive related error but the diskpart output makes it look to me like the log entry is referring to the D: partion (where all our data is). We have not noted any problems accessing or writing to files on the server.
So my question is which drive/partition is the error referring to and how do I go about fixing it. Also what are the risks associated with running chkdsk on a RAID and are there precautions I should take. Thanks
This stuff scares the crap out of me.........
Asked:
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trial
Please ***NOTE*** that some USB drives are actually two drives STRIPED in a RAID0. I would only run CHKDSK on a single drive.
Thanks for the chkdisk warning about RAID. I thought I remembered there being an issue. I am still at a loss as to which partition is at fault. I already used the Dell Admin utility to check the drives and they all show healthy. Also the mmc plugin shows all the drives as healthy.
Just for a little more info. I have a another thread going regarding a problem with VSS and Windows backup. I now think all of these problems may be related. I restarted the VSS service and then tried to run the SBS backup. I got this error (first time it has ever shown up)
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolumeShad
So now what? Is it possible that all these errors are coming from the dedicated USB drive which is used by SBS backup? This server is for an accounting firm. You can imagine what a disaster it would be for it to crash before April 15th! I am trying to head off a catastrophe.......
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolumeShad
So now what? Is it possible that all these errors are coming from the dedicated USB drive which is used by SBS backup? This server is for an accounting firm. You can imagine what a disaster it would be for it to crash before April 15th! I am trying to head off a catastrophe.......
Volume Shadow Copy creates a hidden space on either the C: or D: partitions (depending on how its set)
1. Right-click Local Disk C:\
2. Properties
3. Select the ShadowCopies folder
Your Backup software would create the same type of hidden volume.
Possibly this hidden location is corrupt, because the partition on which it resides is ALSO corrupt.
VSS needs drives -- drives are corrupt -- VSS is corrupted
1. Right-click Local Disk C:\
2. Properties
3. Select the ShadowCopies folder
Your Backup software would create the same type of hidden volume.
Possibly this hidden location is corrupt, because the partition on which it resides is ALSO corrupt.
VSS needs drives -- drives are corrupt -- VSS is corrupted
Shadow Copies is disabled for all drives when I look under properties. Also when I check the Dell Management console there is no indication of trouble with the drives. I am not sure at what level that check is made (SMART?) but they show up as healthy. So assuming the one of the drives is corrupt where do I go from here?
Also no one has been able to tell me for sure which partition \Device\HarddiskVolume2 is. Any takers?
Thanks for the help so far
Also no one has been able to tell me for sure which partition \Device\HarddiskVolume2 is. Any takers?
Thanks for the help so far
Another ***NOTE***
running chkdsk mentioned in the KB article will execute CHKDSK in read-only mode -- which should be safe.
running chkdsk mentioned in the KB article will execute CHKDSK in read-only mode -- which should be safe.
Problem is not yet solved but I am closing the question. I will be reposting in a different thread where I can add more info
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
In regards to CHKDSK....
I believe you would be fine in running a chkdsk on any and all of the USB drives.
Chkdsk is a Windows utility that uses simple algorithms to recover data from a corrupt disk. Chkdsk can be started by the user or automatically by Windows if it detects disk corruption at boot time. (Windows will ask for confirmation before starting chkdsk but will start it anyway if no response is received after a number of seconds.) Chkdsk is not RAID-aware. Its algorithms only work in the simplest cases. In general, it must be avoided.
If chkdsk attempts to repair one or more member disks, the RAID data patterns will be destroyed, usually beyond recovery.
Here's Microsoft's response...
http://support.microsoft.com/kb/246026