Server-Storage Diagnostic Results

Ask a question

Sunday, October 28, 2007 6:31 PM

0

I added WHS Toolkit to my server. It provides some useful features, not the least among them is Server-Storage Diagnostic. I have run it on my server and I find what I have to conclude is a potentially serious problem and I have not been able to find a fix for it.

What follows is part of the analysis portion of the log file called Server-Storage Diagnostic Results:

Total Files:                          3927
Files in folders:                     46
Files in shares:                      3881
Files encrypted:                      0
Files cannot open:                    0
Files opened by other programs:       0
Missing shadow due to missing disk:   0
Files with both shadows missing:      0
Shadow ACL diff from Tombstone:       3767
Tombstone ACL doesn't match QSM:      0
OpenService failed. error=1060
The two lines highlighted in blue concern me. Can anyone help?
- Reply
- Quote

All Replies

Sunday, October 28, 2007 6:55 PM

Moderator

0

Shadow ACL diff from Tombstone: 3767

Perhaps the following bits information will help:

On W2K3 If you change permissions on a file after the shadow copy was made ACL for the shadow copy will be different from that of the current version of the file. When restoring from a shadow it will maintain current rights, although you do need to have sufficient rights on the file in the shadow copy to do a restore.

Another thing is that rights for original folders differ from those with the tombstones. Browse to a shared folder on your data drive (in D:\shares) and inspect rights. If you browse to the original location of the same folder on disk ( C:\fs\de\"driveletter"\shares) and then look at the rights you will probably notice a difference.
- Reply
- Quote

Sunday, October 28, 2007 9:53 PM

brubber wrote:

Shadow ACL diff from Tombstone: 3767

Perhaps the following bits information will help:

On W2K3 If you change permissions on a file after the shadow copy was made ACL for the shadow copy will be different from that of the current version of the file. When restoring from a shadow it will maintain current rights, although you do need to have sufficient rights on the file in the shadow copy to do a restore.

Another thing is that rights for original folders differ from those with the tombstones. Browse to a shared folder on your data drive (in D:\shares) and inspect rights. If you browse to the original location of the same folder on disk ( C:\fs\de\"driveletter"\shares) and then look at the rights you will probably notice a difference.

Thanks!

I tried:

http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=2306266&SiteID=50

and the number did not change at all.

There is a difference. All on C: in the DE folder inherit from parent. On the D in the shares folder none are inherited. I created a new share and it is the same.

Monday, October 29, 2007 5:22 PM

Moderator

Jeshimon,

Can you please try to reset the owner information and then permissions?

Reset owner information on tombstone and shadows:

1.Log into your home server as administrator.

2.Right click on the d:\shares\photoes folder, select properties, and security tab.

3.Click on the advanced button.

4.Click on the Owner Tab. Make sure administrator account is listed.

5.Select “replace owner on sub containers and objects” and apply.

6.Repeat this on D:\DE\shares\photos and on C:\FS\[some number or digit]\de\shares\photos

Now,

Reset security permissions on tombstone and shadows:

1.Right click on the d:\shares\photoes folder, select properties, and security tab.

2.Click on the advanced button.

3.Check the “replace permission entries on all child objects with entries shown here that apply to child objects”

4.Click apply.

5.Reboot.

thanks,

Mark

Monday, October 29, 2007 7:13 PM

Mark,

First let me thank you.

Mark Vayman wrote:

4.Click on the Owner Tab. Make sure administrator account is listed.

I assume we want to select the Administrator line and not the Administrators line.

6.Repeat this on D:\DE\shares\photos

d:\de\shares\Photos folder does not exist and the folders that are there reflect the time before the upgrade.

On the upside this did reduce the count to 3185. I'll do more folders in a while.

Again, thank you Mark.

Jim

Monday, October 29, 2007 9:41 PM

Mark Vayman wrote:

Jeshimon,

Can you please try to reset the owner information and then permissions?

Reset owner information on tombstone and shadows:

1.Log into your home server as administrator.

2.Right click on the d:\shares\photoes folder, select properties, and security tab.

3.Click on the advanced button.

4.Click on the Owner Tab. Make sure administrator account is listed.

5.Select “replace owner on sub containers and objects” and apply.

6.Repeat this on D:\DE\shares\photos and on C:\FS\[some number or digit]\de\shares\photos

Now,

Reset security permissions on tombstone and shadows:

1.Right click on the d:\shares\photoes folder, select properties, and security tab.

2.Click on the advanced button.

3.Check the “replace permission entries on all child objects with entries shown here that apply to child objects”

4.Click apply.

5.Reboot.

thanks,

Mark

Mark,

I went up a level and performed the steps, ie: d:\shares; C:\fs\5\de\shares; C:\fs\6\de\shares; C:\fs\L\de\shares, etc. Looks like it worked. Now there is one problem left.

Drive D:\, 120683474944 bytes used, 177902411776 bytes left

Total Space used by storage: 698663407616 bytes

Total Space left for storage: 351828127744 bytes

Spaced used by backup: 85075189460 bytes

Spaced used by shares: 188712259808 bytes

Total Files: 3932

Files in folders: 46

Files in shares: 3886

Files encrypted: 0

Files cannot open: 0

Files opened by other programs: 0

Missing shadow due to missing disk: 0

Files with both shadows missing: 0

Shadow ACL diff from Tombstone: 0

Tombstone ACL doesn't match QSM: 0

OpenService failed. error=1060

Thanks,

Jim

Monday, October 29, 2007 9:53 PM

Moderator

Jeshimon,

On you home server, could you please see if the driver extender migrator is running by typing the following in a command line:

SC Query DriveExtenderMigrator

thanks,

Mark

Monday, October 29, 2007 10:02 PM

Mark,

Looks as if it is not running. At one point I remember trying to get it started, but the steps I used were from CTP (I think) . before RC1 at least.

C:\Documents and Settings\Administrator\Desktop>SC Query DriveExtenderMigrator
[SC] EnumQueryServicesStatus : OpenService FAILED 1060:

The specified service does not exist as an installed service.

C:\Documents and Settings\Administrator\Desktop>

I am open to suggestions.

Jim

Monday, October 29, 2007 10:14 PM

Moderator

Jim,

Can you please contact me through whsforum@microsoft.com

thanks,

Mark

Monday, October 29, 2007 11:22 PM

Moderator

Mark, just out of curiosity,

1. Does "Shadow ACL diff from Tombstone" always have to be 0 at any point in time on WHS?

2. Same for Tombstone ACL doesn't match QSM?

Tuesday, October 30, 2007 9:02 PM

Mark Vayman wrote:

Jim,

Can you please contact me through whsforum@microsoft.com

thanks,

Mark

Mark,

Well, you got it done, thanks for all the help. Wish this had been out a bit ago:

http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=2342456&SiteID=50

Jim

Tuesday, October 30, 2007 10:17 PM

Moderator

Jim / Mark,

Can you perhaps explain how the problem was solved and what (may have) caused it?

The technical brief on demigrator service is very descriptive, however does not really provide any information that was not already known nor does it provide any handles for troubleshooting or recovering from errors.

Tuesday, October 30, 2007 10:31 PM

Moderator

My Shadow ACL diff from Tombstone is showing 9. Is that OK or should it be at 0?

The rest of the log shows the following:

Drive D:\, 1255632896 bytes used, 297330253824 bytes left

Total Space used by storage: 938710011904 bytes

Total Space left for storage: 514537930752 bytes

Spaced used by backup: 377982510660 bytes

Spaced used by shares: 3361816440 bytes

Total Files: 183

Files in folders: 148

Files in shares: 35

Files encrypted: 0

Files cannot open: 0

Files opened by other programs: 0

Missing shadow due to missing disk: 0

Files with both shadows missing: 0

Shadow ACL diff from Tombstone: 9

Tombstone ACL doesn't match QSM: 0

DEMigrator service restore state to 4 pending...

DEMigrator service is restored.

Tuesday, October 30, 2007 11:34 PM

In my case Windows Home Server Drive Extender did not get installed and registerd correctly. It did not show in sevices.msc at all let alone as running.

Hope this helps.

Tuesday, October 30, 2007 11:42 PM

Moderator

Ok, thanks. No need to get into details then since this probably one in a million prob.

Wednesday, October 31, 2007 12:45 AM

Yeah, it seems I'm one of the lucky people that gets those.

Wednesday, October 31, 2007 7:51 AM

As we all seem to be comparing diagnostics

Total Files:                          2069
Files in folders:                     70
Files in shares:                      1999
Files encrypted:                      0
Files cannot open:                    1
Files opened by other programs:       1
Missing shadow due to missing disk:   0
Files with both shadows missing:      70
Shadow ACL diff from Tombstone:       0
Tombstone ACL doesn't match QSM:      0
DEMigrator service restore state to 4 pending...
DEMigrator service restore state to 4 pending...
DEMigrator service restore state to 4 pending...
DEMigrator service is restored.

Is this normal or something I should be worried about?

Thursday, November 15, 2007 10:51 AM

Mark, re your post above on resetting security permissions - a thank you from me too.

Shadow ACL diff from Tombstone: 50587 - tells you something about the size of my music library!

All fixed now.

Bill

Monday, December 31, 2007 6:34 PM

Mark Vayman wrote:

Jeshimon,

Can you please try to reset the owner information and then permissions?

Reset owner information on tombstone and shadows:

1.Log into your home server as administrator.

2.Right click on the d:\shares\photoes folder, select properties, and security tab.

3.Click on the advanced button.

4.Click on the Owner Tab. Make sure administrator account is listed.

5.Select “replace owner on sub containers and objects” and apply.

6.Repeat this on D:\DE\shares\photos and on C:\FS\[some number or digit]\de\shares\photos

Now,

Reset security permissions on tombstone and shadows:

1.Right click on the d:\shares\photoes folder, select properties, and security tab.

2.Click on the advanced button.

3.Check the “replace permission entries on all child objects with entries shown here that apply to child objects”

4.Click apply.

5.Reboot.

thanks,

Mark

Worked for me too, thx

Dawg.

Wednesday, January 23, 2008 4:24 AM

Jeshimon wrote:

Mark,

First let me thank you.

Mark Vayman wrote:

4.Click on the Owner Tab. Make sure administrator account is listed.

I assume we want to select the Administrator line and not the Administrators line.

6.Repeat this on D:\DE\shares\photos

d:\de\shares\Photos folder does not exist and the folders that are there reflect the time before the upgrade.

On the upside this did reduce the count to 3185. I'll do more folders in a while.

Again, thank you Mark.

Jim

Can someone confirm that we should really be setting ownership to the Administrator user account and not to the Administrators group? From the testing I did on my system, any time a new share is created the ownership is set to Administrators (the group) not Administrator (the user).

Wednesday, January 23, 2008 4:56 AM

Moderator

tfieldho wrote:

Jeshimon wrote:

Mark,

First let me thank you.

Mark Vayman wrote:

4.Click on the Owner Tab. Make sure administrator account is listed.

I assume we want to select the Administrator line and not the Administrators line.

6.Repeat this on D:\DE\shares\photos

d:\de\shares\Photos folder does not exist and the folders that are there reflect the time before the upgrade.

On the upside this did reduce the count to 3185. I'll do more folders in a while.

Again, thank you Mark.

Jim

When I had to reset mine, I did the group, but in all honesty, it shouldn't matter (since the user Administrator is in the Administrators group by default anyway).

Wednesday, January 23, 2008 5:01 AM

kariya21 wrote:

When I had to reset mine, I did the group, but in all honesty, it shouldn't matter (since the user Administrator is in the Administrators group by default anyway).

Thanks. makes sense.

Wednesday, January 23, 2008 1:13 PM

Moderator

kariya21 wrote:

When I had to reset mine, I did the group, but in all honesty, it shouldn't matter (since the user Administrator is in the Administrators group by default anyway).

The proper owner for tombstones is not the administrator account, it's the administrators group. There's only one member of the Administrators group by default, but I can conceive of a future version of WHS wanting to be able to grant administrative access to some other user.

Thursday, January 24, 2008 5:50 PM

Things are looking better. I've been able to clean up all of the ACL / Tombstone differences. The one remaining issue that I see is the 6 "Missing shadow due to missing disk". any suggestions on this? I did have a drive die and removed it using the console. It looks like something wasn't cleaned up properly? (for example, the summary line "Shadow ACL diff from Tombstone" corresponds to a log file error of "Tombstone-Shadow mismatch")

I'd search for the error in the log file itself but the errors in the log use different wording than the summary uses and I really don't have time to search visually through 3,348,148 lines of text to find six errors. Indifferent

Drive D:\,                    8407486464 bytes used, 270174519296 bytes left
Total Space used by storage: 4779454926848 bytes
Total Space left for storage: 781495885824 bytes
Spaced used by backup:        142350 bytes
Spaced used by shares:        1959556826273 bytes

Total Files:                          145592
Files in folders:                     11
Files in shares:                      145581
Files encrypted:                      0
Files cannot open:                    0
Files opened by other programs:       0
Missing shadow due to missing disk:   6
Files with both shadows missing:      0
Shadow ACL diff from Tombstone:       0
Tombstone ACL doesn't match QSM:      0

Sunday, January 27, 2008 1:09 AM

Moderator

tfieldho wrote:

You could try doing a search for the word "missing" and see if it finds the 6 shadows somewhere in the log.

Sunday, January 27, 2008 5:03 AM

good suggestion. I did a find /i "missing" and searched through the 967 lines. Didn't find anything other than file / pathnames.

I also did a cursory search with a few other terms to see if I could guess the error message - "be found", "not found" "is missing", "missing from", "cannot be", "can't find". Nothing turned up. This feels like a huge waste of my time since I haven't a clue what the actual error messages are going to be.

I'm concerned that even after clearing up all of the ACL differences several days ago, the demigrator process is still consuming a significant amount of CPU time (19.5 hours of cpu time since the last reboot 72 hours ago).

so again, if anyone knows what error message in the chkde log file corresponds to a "Missing shadow due to missing disk", speak up.

Thursday, February 28, 2008 11:59 PM

http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=2770040&SiteID=50

Saturday, March 01, 2008 10:41 PM

Jeshimon wrote:

In my case Windows Home Server Drive Extender did not get installed and registerd correctly. It did not show in sevices.msc at all let alone as running.

Hope this helps.

Jim,

How did you install it? That service isn't running on my server either.

I had observed many files in the shared files folders that when clicked would report the file wasn't there. I fixed that problem by changing file ownership and promissions (as directed above). When I did that some the files that were listed but not openable disappeared, others became openable. But the Drive Extender service is still missing.

Saturday, March 01, 2008 11:13 PM

Bruce,

I hope I have it here, hang on.

Jim

Saturday, March 01, 2008 11:20 PM

Send me a mail and I'll reply with what I've got.

Jim

Sunday, March 09, 2008 1:22 AM

Does this problem recur every time you have to repair install? I am just curios about what others have seen. If it does, have any of you code commandos automated the fix?