From: Lesa H. on
I have a customer that has some System log entries of ntfs Event ID 55 as
follows:

The file system structure on the disk is corrupt and unusable. Please run
the chkdsk utility on the volume \Device\HarddiskVolume2

I have been unable to find how to translate the \Device\HarddiskVolume2 to a
drive letter. Is there a way to do this?

Thanks in advance,

Lesa H.



From: David on
What is your Computer Mangement-Disk Management showing about your disk
configuration?

David Olsen
www.powerbits.com.au


"Lesa H." <itsplesa(a)news.postalias> wrote in message
news:OLIS1dAAJHA.3396(a)TK2MSFTNGP03.phx.gbl...
>I have a customer that has some System log entries of ntfs Event ID 55 as
> follows:
>
> The file system structure on the disk is corrupt and unusable. Please run
> the chkdsk utility on the volume \Device\HarddiskVolume2
>
> I have been unable to find how to translate the \Device\HarddiskVolume2 to
> a
> drive letter. Is there a way to do this?
>
> Thanks in advance,
>
> Lesa H.
>
>
>


From: Miles Li [MSFT] on
Hello Lesa,

Thank you for posting here.

According to your description, I understand the issue is that:

On a workstation of the SBS domain, Event ID 55 is recorded that indicates
the "The file system structure on the disk is corrupt and unusable".

If I have misunderstood the problem, please don't hesitate to let me know.

Typically, \Device\HarddiskVolume2 indicates the second partition on a
basic disk. You can verify the drive letter in the Computer
Management--->Disk Management. The second volume of that disk is the
HarddiskVolume2 (from left to right).

To determine the each driver's physical device name, you can use
Sysinternals WinObj:

WinObj v2.15
http://technet.microsoft.com/en-us/sysinternals/bb896657.aspx

1. Expand the node \--->GLOBAL??
2. In the right panel, you can verify the physical device name of each
drive letter such as C:, D:

About the Event ID 55, please run CHKDSK command on the disk that contains
the corrupted file. There is a known issue that Event ID 55 will be
recoreded while saving a file that has a DBCS file name Windows Server
2003. Please make sure that the latest service pack is installed on the
system.

There is a known issue that some Antivirus software may cause this issue,
you may perform the clean boot on the client that has this issue to narrow
down the issue.

a) Type msconfig in the command prompt and press Enter
b) Click Services tab and select Hide All Microsoft Services and
Disable All third party Services.
c) Click Startup tab and Disable All startup items
d) Click OK and choose Restart
e) After reboot, check whether the Event ID 55 persists.

For your reference:

885871 You may receive an error message when you revise and
then save a file that has a DBCS file name in Windows Server 2003 or in
Windows 2000
http://support.microsoft.com/kb/885871

If the issue persists, please help to collect the following information:
=====================

1. Does this issue happen on SBS or workstation? Please let me know the
version of the OS.

2. If the event log is recorded on a SBS server, could you please collect
the MPS report on the SBS 2003 server and send to me at
v-mileli(a)microsoft.com <mailto:v-mileli(a)microsoft.com>?

Microsoft Product Support's Reporting Tools (MPSRPT_DirSvc.EXE)
http://www.microsoft.com/downloads/details.aspx?FamilyID=CEBF3C7C-7CA5-408F-
88B7-F9C79B7306C0&displaylang=en

I hope these steps will give you some help. If you have any questions or
concerns, please do not hesitate to let me know.


Best regards,

Miles Li

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

From: Lesa H. on
Thanks David and Miles,

I found out using the WinObj program that the problem drive is the C: drive
on the SBS server. I believe they recently had an issue with one of the
drives in the RAID array. This error may have appeared when the drive was
replaced during the time they were bringing the server back up. I'll talk to
the customer today and find out when exactly they did the replacement. I
have sent the logs to Miles.

I'll get back to this post after I talk to the customer.

Lesa
"Miles Li [MSFT]" <v-mileli(a)online.microsoft.com> wrote in message
news:nodT3sRAJHA.3988(a)TK2MSFTNGHUB02.phx.gbl...
> Hello Lesa,
>
> Thank you for posting here.
>
> According to your description, I understand the issue is that:
>
> On a workstation of the SBS domain, Event ID 55 is recorded that indicates
> the "The file system structure on the disk is corrupt and unusable".
>
> If I have misunderstood the problem, please don't hesitate to let me know.
>
> Typically, \Device\HarddiskVolume2 indicates the second partition on a
> basic disk. You can verify the drive letter in the Computer
> Management--->Disk Management. The second volume of that disk is the
> HarddiskVolume2 (from left to right).
>
> To determine the each driver's physical device name, you can use
> Sysinternals WinObj:
>
> WinObj v2.15
> http://technet.microsoft.com/en-us/sysinternals/bb896657.aspx
>
> 1. Expand the node \--->GLOBAL??
> 2. In the right panel, you can verify the physical device name of each
> drive letter such as C:, D:
>
> About the Event ID 55, please run CHKDSK command on the disk that contains
> the corrupted file. There is a known issue that Event ID 55 will be
> recoreded while saving a file that has a DBCS file name Windows Server
> 2003. Please make sure that the latest service pack is installed on the
> system.
>
> There is a known issue that some Antivirus software may cause this issue,
> you may perform the clean boot on the client that has this issue to narrow
> down the issue.
>
> a) Type msconfig in the command prompt and press Enter
> b) Click Services tab and select Hide All Microsoft Services and
> Disable All third party Services.
> c) Click Startup tab and Disable All startup items
> d) Click OK and choose Restart
> e) After reboot, check whether the Event ID 55 persists.
>
> For your reference:
>
> 885871 You may receive an error message when you revise and
> then save a file that has a DBCS file name in Windows Server 2003 or in
> Windows 2000
> http://support.microsoft.com/kb/885871
>
> If the issue persists, please help to collect the following information:
> =====================
>
> 1. Does this issue happen on SBS or workstation? Please let me know the
> version of the OS.
>
> 2. If the event log is recorded on a SBS server, could you please collect
> the MPS report on the SBS 2003 server and send to me at
> v-mileli(a)microsoft.com <mailto:v-mileli(a)microsoft.com>?
>
> Microsoft Product Support's Reporting Tools (MPSRPT_DirSvc.EXE)
> http://www.microsoft.com/downloads/details.aspx?FamilyID=CEBF3C7C-7CA5-408F-
> 88B7-F9C79B7306C0&displaylang=en
>
> I hope these steps will give you some help. If you have any questions or
> concerns, please do not hesitate to let me know.
>
>
> Best regards,
>
> Miles Li
>
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> This newsgroup only focuses on SBS technical issues. If you have issues
> regarding other Microsoft products, you'd better post in the corresponding
> newsgroups so that they can be resolved in an efficient and timely manner.
> You can locate the newsgroup here:
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
> When opening a new thread via the web interface, we recommend you check
> the
> "Notify me of replies" box to receive e-mail notifications when there are
> any updates in your thread. When responding to posts via your newsreader,
> please "Reply to Group" so that others may learn and benefit from your
> issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we
> provide other information for your reference, we recommend you post
> different incidents in different threads to keep the thread clean. In
> doing
> so, it will ensure your issues are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>


From: Miles Li [MSFT] on

Hello Lesa,


Please take your time to collect information from the customer. If there is
any update, please do not hesitate to let me know.


Best regards,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.