This is happening on a SBS 2003 Premium Server (SP2 installed).

This has been an ongoing issue since a  Raid 1 Array / Controller (Promise 
TX2300) has been added to the system.  THe old RAID 1 array (Silicon Image) 
is still in the system, but the drive letters where changed to higher letters 
for the sake of having the ability to copy data from old to new.

THe server appears to function normally other than this problem.

The OS and data was restored to the new new raid array using Windows Backup.
The same original drive letters are still there, just now mapping to the 
volumes on the new raid array.  

Here is the errors in the backup09.log file:
rror: Could not access portions of directory System State\COM+ Class 
Registration Database.

I also see the following errors in the event viewer system log:

You may not have permission to open the file, or the directory may be 
missing or damaged.
Please contact the owner or administrator.

Error: Could not access portions of directory System State\Registry.
You may not have permission to open the file, or the directory may be 
missing or damaged.
Please contact the owner or administrator.

I also see the following errors in the event viewer System Log:
Event ID:  7   - he device, \Device\Harddisk0, has a bad block.
Event ID:  14 - The shadow copies of volume C: were aborted because of an IO 
failure on volume C:.


We have run Chkdsk on the C: Drive a few times and no damage is found or 
repaired.

I have also noticed that running a shadow copy on the C: drive also fails.

a list of the "vssadmin list writers"  produces the following:
Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {f23e5be4-0374-4596-bdb7-87e55686bc1c}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {2ccf0719-8d71-4b52-9e54-894853c9845d}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {9881a09f-da21-46ac-839e-f2185fcb3f23}
   State: [1] Stable
   Last error: No error

Writer name: 'TermServLicensing'
   Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}
   Writer Instance Id: {793738e7-ff3e-4393-b543-c280ab921b8c}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {7cfd193e-27bd-4064-8a1d-b9792975e89d}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {d70833b6-a951-4dbf-926a-bc0aef7e4d39}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {e133a0c2-b59a-4884-9df0-3328c5fb0ac1}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Removable Storage Manager'
   Writer Id: {5d3c3e01-0297-445b-aa81-a48d7151e235}
   Writer Instance Id: {28aebc5b-2d40-420a-8b18-9c662e281030}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {adca8b5b-f3d4-485b-a711-ee79b8c24db2}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {ae394f42-88c6-4570-b79e-6c4e48fd207d}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {9632f75f-dde8-4f19-acfe-e59614328e30}
   State: [1] Stable
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {8a11dde0-9213-4958-9345-4b787b85a60a}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'WINS Jet Writer'
   Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
   Writer Instance Id: {30ffb76e-a300-49e6-b4c5-32d280a153b1}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {c63e33d1-e7c6-4f79-bcea-08fda9940938}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {3f612001-0a41-4cbd-aac4-d43d09d75077}
   State: [1] Stable
   Last error: No error 



Any help would be appreciated.  

Thank YOU in advance.

Sounds like \Device\Harddisk0 is going bad.  Did you run chdsk /R ?

This may help:
http://www.techsupportforum.com/hardware-support/laptop-support/273870-solved-system-restore-backups-aborted-c-due-i-o-failure.html

-- 
Allan Williams




Bob G. wrote:
> This is happening on a SBS 2003 Premium Server (SP2 installed).
>
> This has been an ongoing issue since a  Raid 1 Array / Controller
> (Promise TX2300) has been added to the system.  THe old RAID 1 array
> (Silicon Image) is still in the system, but the drive letters where
> changed to higher letters for the sake of having the ability to copy
> data from old to new.
>
> THe server appears to function normally other than this problem.
>
> The OS and data was restored to the new new raid array using Windows
> Backup. The same original drive letters are still there, just now
> mapping to the volumes on the new raid array.
>
> Here is the errors in the backup09.log file:
> rror: Could not access portions of directory System State\COM+ Class
> Registration Database.
>
> I also see the following errors in the event viewer system log:
>
> You may not have permission to open the file, or the directory may be
> missing or damaged.
> Please contact the owner or administrator.
>
> Error: Could not access portions of directory System State\Registry.
> You may not have permission to open the file, or the directory may be
> missing or damaged.
> Please contact the owner or administrator.
>
> I also see the following errors in the event viewer System Log:
> Event ID:  7   - he device, \Device\Harddisk0, has a bad block.
> Event ID:  14 - The shadow copies of volume C: were aborted because
> of an IO failure on volume C:.
>
>
> We have run Chkdsk on the C: Drive a few times and no damage is found
> or repaired.
>
> I have also noticed that running a shadow copy on the C: drive also
> fails.
>
> a list of the "vssadmin list writers"  produces the following:
> Writer name: 'SqlServerWriter'
>   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
>   Writer Instance Id: {f23e5be4-0374-4596-bdb7-87e55686bc1c}
>   State: [5] Waiting for completion
>   Last error: No error
>
> Writer name: 'System Writer'
>   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
>   Writer Instance Id: {2ccf0719-8d71-4b52-9e54-894853c9845d}
>   State: [5] Waiting for completion
>   Last error: No error
>
> Writer name: 'MSDEWriter'
>   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
>   Writer Instance Id: {9881a09f-da21-46ac-839e-f2185fcb3f23}
>   State: [1] Stable
>   Last error: No error
>
> Writer name: 'TermServLicensing'
>   Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}
>   Writer Instance Id: {793738e7-ff3e-4393-b543-c280ab921b8c}
>   State: [5] Waiting for completion
>   Last error: No error
>
> Writer name: 'Dhcp Jet Writer'
>   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
>   Writer Instance Id: {7cfd193e-27bd-4064-8a1d-b9792975e89d}
>   State: [5] Waiting for completion
>   Last error: No error
>
> Writer name: 'Event Log Writer'
>   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
>   Writer Instance Id: {d70833b6-a951-4dbf-926a-bc0aef7e4d39}
>   State: [1] Stable
>   Last error: No error
>
> Writer name: 'IIS Metabase Writer'
>   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
>   Writer Instance Id: {e133a0c2-b59a-4884-9df0-3328c5fb0ac1}
>   State: [5] Waiting for completion
>   Last error: No error
>
> Writer name: 'Removable Storage Manager'
>   Writer Id: {5d3c3e01-0297-445b-aa81-a48d7151e235}
>   Writer Instance Id: {28aebc5b-2d40-420a-8b18-9c662e281030}
>   State: [5] Waiting for completion
>   Last error: No error
>
> Writer name: 'COM+ REGDB Writer'
>   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
>   Writer Instance Id: {adca8b5b-f3d4-485b-a711-ee79b8c24db2}
>   State: [1] Stable
>   Last error: No error
>
> Writer name: 'BITS Writer'
>   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
>   Writer Instance Id: {ae394f42-88c6-4570-b79e-6c4e48fd207d}
>   State: [5] Waiting for completion
>   Last error: No error
>
> Writer name: 'Registry Writer'
>   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
>   Writer Instance Id: {9632f75f-dde8-4f19-acfe-e59614328e30}
>   State: [1] Stable
>   Last error: No error
>
> Writer name: 'FRS Writer'
>   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
>   Writer Instance Id: {8a11dde0-9213-4958-9345-4b787b85a60a}
>   State: [5] Waiting for completion
>   Last error: No error
>
> Writer name: 'WINS Jet Writer'
>   Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
>   Writer Instance Id: {30ffb76e-a300-49e6-b4c5-32d280a153b1}
>   State: [5] Waiting for completion
>   Last error: No error
>
> Writer name: 'WMI Writer'
>   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
>   Writer Instance Id: {c63e33d1-e7c6-4f79-bcea-08fda9940938}
>   State: [5] Waiting for completion
>   Last error: No error
>
> Writer name: 'NTDS'
>   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
>   Writer Instance Id: {3f612001-0a41-4cbd-aac4-d43d09d75077}
>   State: [1] Stable
>   Last error: No error
>
>
>
> Any help would be appreciated.
>
> Thank YOU in advance.