VSS errors following installation of Small Business Server
I've just installed SBS on a new machine and now consistently receive the following errors in the log report:
Source Event ID Last Occurrence Total Occurrences
VSS 7001 27/06/2006 12:20 2 *
VssAdmin: Unable to create a shadow copy: The shadow copy provider had an error. Please see the system and application event logs for more information. Command-line: 'C:\WINDOWS\system32\vssad
Source Event ID Last Occurrence Total Occurrences
VSS 12298 27/06/2006 12:20 2 *
Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume \\?\Volume{ab9378fe-019c-1
Source Event ID Last Occurrence Total Occurrences
VSS 12310 27/06/2006 12:20 2 *
Volume Shadow Copy Service error: The shadow copy could not be committed - operation timed out. Error context: DeviceIoControl(\\?\Volume
Reading around the subject it seems that this is *something* to do with backup. I've not configured any backup on the server as yet.
Any ideas on what's causing this and (more importantly) how to eliminate the errors from the log will be much appreciated.
Source Event ID Last Occurrence Total Occurrences
VSS 7001 27/06/2006 12:20 2 *
VssAdmin: Unable to create a shadow copy: The shadow copy provider had an error. Please see the system and application event logs for more information. Command-line: 'C:\WINDOWS\system32\vssad
Source Event ID Last Occurrence Total Occurrences
VSS 12298 27/06/2006 12:20 2 *
Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume \\?\Volume{ab9378fe-019c-1
Source Event ID Last Occurrence Total Occurrences
VSS 12310 27/06/2006 12:20 2 *
Volume Shadow Copy Service error: The shadow copy could not be committed - operation timed out. Error context: DeviceIoControl(\\?\Volume
Reading around the subject it seems that this is *something* to do with backup. I've not configured any backup on the server as yet.
Any ideas on what's causing this and (more importantly) how to eliminate the errors from the log will be much appreciated.
ASKER
It's a completely new installation on brand new hardware (the idea was there should be no "legacy" issues).
Graham
Graham
Are these the only errors you are getting in the Event log? What is your hard drive configuration? Actually, what is the entire hardware configuration?
Jeff
TechSoEasy
Jeff
TechSoEasy
ASKER
I get 8 critical errors per day... the three that I pasted in account for 6 of those and the following accounts for 2:
Source Event ID Last Occurrence Total Occurrences
VolSnap 8 29/06/2006 12:20 2 *
The flush and hold writes operation on volume C: timed out while waiting for a release writes command.
Immediately following this there is an informational message saying:
The Volume Shadow Copy service entered the stopped state.
There are two hard drives, looking at the hardware config this is probably where the issue lies. Disk (0) is the system disk (C:) and contains a basic 80Gb NTFS partition on which SBS is installed. Disk (1) is "another" disk and whilst it has a partition defined for it, any attempt to format the disk results in an IO timeout (which sort of ties in with the other errors although those are being reported for C:).
Source Event ID Last Occurrence Total Occurrences
VolSnap 8 29/06/2006 12:20 2 *
The flush and hold writes operation on volume C: timed out while waiting for a release writes command.
Immediately following this there is an informational message saying:
The Volume Shadow Copy service entered the stopped state.
There are two hard drives, looking at the hardware config this is probably where the issue lies. Disk (0) is the system disk (C:) and contains a basic 80Gb NTFS partition on which SBS is installed. Disk (1) is "another" disk and whilst it has a partition defined for it, any attempt to format the disk results in an IO timeout (which sort of ties in with the other errors although those are being reported for C:).
Is this a machine designed to be a server? Or is it a PC trying to be a server?
Are you installing this to be a production machine or just testing? Please provide more details... because the first recommendation I would have would be to fully reinstall... however, if you don't have adequate hardware to begin with, then that would be a waste of time.
Jeff
TechSoEasy
Are you installing this to be a production machine or just testing? Please provide more details... because the first recommendation I would have would be to fully reinstall... however, if you don't have adequate hardware to begin with, then that would be a waste of time.
Jeff
TechSoEasy
ASKER
No it's a server:
Rackqueen 411 - Basic
Entry level AMD Unit Built And Tested.
Fits In Cabinets 600-900 Deep
Specification
Queenserver RM 411 4U Rackmount Cases With 300 Watt Psu
AMD - AMD SEMPRON 2600+ HT SKT-754 RET Cpu And Dynatron 1u Cooler
Black CD Rom and Black Floppy Drive
Asus Mainboard Mainboard With Onboard Video/Sound/Lan Model K8-VM MX
80 GB Hard Drive
512MB Ram
plus an extra 80Gb drive...
As a server it's not stretched at all... as this extract from the daily report might suggest ;-)
Performance Counters Today Last Month Rate of Growth
Memory in use 441 MB No data
Free disk space (C:) 73,282 MB No data
Busy disk time (0 C:) 1 % No data
Busy disk time (1) 0 % No data
CPU Use (0) 0 % No data
I'm concerned by the fact that it's trying to do things with disk (1) but can't... so I've removed the partition to see if this has an effect on the errors in the logs. Of course this might take a 24 run test to verify.
Rackqueen 411 - Basic
Entry level AMD Unit Built And Tested.
Fits In Cabinets 600-900 Deep
Specification
Queenserver RM 411 4U Rackmount Cases With 300 Watt Psu
AMD - AMD SEMPRON 2600+ HT SKT-754 RET Cpu And Dynatron 1u Cooler
Black CD Rom and Black Floppy Drive
Asus Mainboard Mainboard With Onboard Video/Sound/Lan Model K8-VM MX
80 GB Hard Drive
512MB Ram
plus an extra 80Gb drive...
As a server it's not stretched at all... as this extract from the daily report might suggest ;-)
Performance Counters Today Last Month Rate of Growth
Memory in use 441 MB No data
Free disk space (C:) 73,282 MB No data
Busy disk time (0 C:) 1 % No data
Busy disk time (1) 0 % No data
CPU Use (0) 0 % No data
I'm concerned by the fact that it's trying to do things with disk (1) but can't... so I've removed the partition to see if this has an effect on the errors in the logs. Of course this might take a 24 run test to verify.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Well I deleted the partition (amounts to the same thing) and the errors have disappeared so I guess the disk isn't set up properly.
Thanks.
Thanks.
Jeff
TechSoEasy