Error 823

I am attempting to add a windows login to be able to access a database. Whe
n
I try to do this I receive the following error.
Error 823: I/O Error (bad page id) detected during read at offset
0x00000000ae6000 in file e:\program files\microsoft sql
server\mssql\master.mdf
I also receive the following when I run dbcc checkdb on the master database
Server: Msg 8928, Level 16, State 6, Line 1
Object ID 0, index ID 0: Page (1:1331) could not be processed. See other
errors for details.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:1395). The PageId in the
page header = (0:0).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 2, index ID 255: Page (1:1332) could not be processed. See other
errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 6, index ID 0: Page (1:1395) could not be processed. See other
errors for details.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:1331) is pointed to by the next pointer of IAM page (0:0) object
ID 40 index ID 2 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 40, index ID 2 due to invalid
allocation (IAM) page(s).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:1331) in database ID 1 is allocated in the SGAM (1:3) and PFS (1:1),
but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED
0_PCT_FULL'.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 3407872, index ID 512, page ID (1:1331). The PageId
in the page header = (1:3126).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:1330) in database ID 1 is allocated in the SGAM (1:3) and PFS (1:1),
but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED
0_PCT_FULL'.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1111693545, index ID 0, page ID (1:1332). The PageId
in the page header = (0:0).
DBCC results for 'master'.
CHECKDB found 1 allocation errors and 1 consistency errors not associated
with any single object.
DBCC results for 'sysobjects'.
There are 1278 rows in 23 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 103 rows in 4 pages for object 'sysindexes'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'sysindexes' (object ID 2).
DBCC results for 'syscolumns'.
There are 4958 rows in 94 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 2232 rows in 1213 pages for object 'syscomments'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'syscomments' (object ID 6).
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 789 rows in 4 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 16 rows in 1 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 0 rows in 0 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 5445 rows in 31 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 0 rows in 0 pages for object 'sysreferences'.
DBCC results for 'sysfulltextcatalogs'.
There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
DBCC results for 'sysfulltextnotify'.
There are 0 rows in 0 pages for object 'sysfulltextnotify'.
DBCC results for 'sysdatabases'.
There are 14 rows in 1 pages for object 'sysdatabases'.
DBCC results for 'sysxlogins'.
There are 46 rows in 1 pages for object 'sysxlogins'.
DBCC results for 'sysdevices'.
There are 6 rows in 1 pages for object 'sysdevices'.
DBCC results for 'sysmessages'.
There are 3883 rows in 166 pages for object 'sysmessages'.
DBCC results for 'sysconfigures'.
There are 38 rows in 1 pages for object 'sysconfigures'.
DBCC results for 'sysservers'.
There are 3 rows in 1 pages for object 'sysservers'.
CHECKDB found 1 allocation errors and 1 consistency errors in table
'sysservers' (object ID 40).
DBCC results for 'syslanguages'.
There are 33 rows in 3 pages for object 'syslanguages'.
DBCC results for 'syscharsets'.
There are 114 rows in 33 pages for object 'syscharsets'.
DBCC results for 'sysaltfiles'.
There are 28 rows in 6 pages for object 'sysaltfiles'.
DBCC results for 'sysfilegroups'.
There are 1 rows in 1 pages for object 'sysfilegroups'.
CHECKDB found 1 allocation errors and 1 consistency errors in table '(Object
ID 3407872)' (object ID 3407872).
DBCC results for 'spt_monitor'.
There are 1 rows in 1 pages for object 'spt_monitor'.
DBCC results for 'spt_values'.
There are 730 rows in 7 pages for object 'spt_values'.
DBCC results for 'spt_fallback_db'.
There are 0 rows in 0 pages for object 'spt_fallback_db'.
DBCC results for 'spt_fallback_dev'.
There are 0 rows in 0 pages for object 'spt_fallback_dev'.
DBCC results for 'spt_fallback_usg'.
There are 0 rows in 0 pages for object 'spt_fallback_usg'.
CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object
ID 538976288)' (object ID 538976288).
DBCC results for 'spt_provider_types'.
There are 25 rows in 1 pages for object 'spt_provider_types'.
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object
ID 1111693545)' (object ID 1111693545).
DBCC results for 'spt_datatype_info_ext'.
There are 10 rows in 1 pages for object 'spt_datatype_info_ext'.
DBCC results for 'MSreplication_options'.
There are 2 rows in 1 pages for object 'MSreplication_options'.
DBCC results for 'spt_datatype_info'.
There are 36 rows in 1 pages for object 'spt_datatype_info'.
DBCC results for 'spt_server_info'.
There are 29 rows in 1 pages for object 'spt_server_info'.
CHECKDB found 4 allocation errors and 6 consistency errors in database
'master'.
repair_allow_data_loss is the minimum repair level for the errors found by
DBCC CHECKDB (master ).
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
How can I correct these errors?Before fixing it, you should check your hardware and look
for issues with your disk subsystem. Check the event logs on
the server and look for any other system errors that may
have occurred around the same time.
After fixing any hardware issues, then you would need to
restore the last known good backup of the master database.
-Sue
On Wed, 29 Mar 2006 10:08:01 -0800, rleamey
<rleamey@.discussions.microsoft.com> wrote:

>I am attempting to add a windows login to be able to access a database. Wh
en
>I try to do this I receive the following error.
>Error 823: I/O Error (bad page id) detected during read at offset
>0x00000000ae6000 in file e:\program files\microsoft sql
>server\mssql\master.mdf
>I also receive the following when I run dbcc checkdb on the master database
>Server: Msg 8928, Level 16, State 6, Line 1
>Object ID 0, index ID 0: Page (1:1331) could not be processed. See other
>errors for details.
>Server: Msg 8909, Level 16, State 1, Line 1
>Table error: Object ID 0, index ID 0, page ID (1:1395). The PageId in the
>page header = (0:0).
>Server: Msg 8928, Level 16, State 1, Line 1
>Object ID 2, index ID 255: Page (1:1332) could not be processed. See other
>errors for details.
>Server: Msg 8928, Level 16, State 1, Line 1
>Object ID 6, index ID 0: Page (1:1395) could not be processed. See other
>errors for details.
>Server: Msg 2575, Level 16, State 1, Line 1
>IAM page (1:1331) is pointed to by the next pointer of IAM page (0:0) objec
t
>ID 40 index ID 2 but was not detected in the scan.
>Server: Msg 7965, Level 16, State 1, Line 1
>Table error: Could not check object ID 40, index ID 2 due to invalid
>allocation (IAM) page(s).
>Server: Msg 8906, Level 16, State 1, Line 1
>Page (1:1331) in database ID 1 is allocated in the SGAM (1:3) and PFS (1:1)
,
>but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED
>0_PCT_FULL'.
>Server: Msg 8909, Level 16, State 1, Line 1
>Table error: Object ID 3407872, index ID 512, page ID (1:1331). The PageId
>in the page header = (1:3126).
>Server: Msg 8906, Level 16, State 1, Line 1
>Page (1:1330) in database ID 1 is allocated in the SGAM (1:3) and PFS (1:1)
,
>but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED
>0_PCT_FULL'.
>Server: Msg 8909, Level 16, State 1, Line 1
>Table error: Object ID 1111693545, index ID 0, page ID (1:1332). The PageId
>in the page header = (0:0).
>DBCC results for 'master'.
>CHECKDB found 1 allocation errors and 1 consistency errors not associated
>with any single object.
>DBCC results for 'sysobjects'.
>There are 1278 rows in 23 pages for object 'sysobjects'.
>DBCC results for 'sysindexes'.
>There are 103 rows in 4 pages for object 'sysindexes'.
>CHECKDB found 0 allocation errors and 1 consistency errors in table
>'sysindexes' (object ID 2).
>DBCC results for 'syscolumns'.
>There are 4958 rows in 94 pages for object 'syscolumns'.
>DBCC results for 'systypes'.
>There are 26 rows in 1 pages for object 'systypes'.
>DBCC results for 'syscomments'.
>There are 2232 rows in 1213 pages for object 'syscomments'.
>CHECKDB found 0 allocation errors and 1 consistency errors in table
>'syscomments' (object ID 6).
>DBCC results for 'sysfiles1'.
>There are 2 rows in 1 pages for object 'sysfiles1'.
>DBCC results for 'syspermissions'.
>There are 789 rows in 4 pages for object 'syspermissions'.
>DBCC results for 'sysusers'.
>There are 16 rows in 1 pages for object 'sysusers'.
>DBCC results for 'sysproperties'.
>There are 0 rows in 0 pages for object 'sysproperties'.
>DBCC results for 'sysdepends'.
>There are 5445 rows in 31 pages for object 'sysdepends'.
>DBCC results for 'sysreferences'.
>There are 0 rows in 0 pages for object 'sysreferences'.
>DBCC results for 'sysfulltextcatalogs'.
>There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
>DBCC results for 'sysfulltextnotify'.
>There are 0 rows in 0 pages for object 'sysfulltextnotify'.
>DBCC results for 'sysdatabases'.
>There are 14 rows in 1 pages for object 'sysdatabases'.
>DBCC results for 'sysxlogins'.
>There are 46 rows in 1 pages for object 'sysxlogins'.
>DBCC results for 'sysdevices'.
>There are 6 rows in 1 pages for object 'sysdevices'.
>DBCC results for 'sysmessages'.
>There are 3883 rows in 166 pages for object 'sysmessages'.
>DBCC results for 'sysconfigures'.
>There are 38 rows in 1 pages for object 'sysconfigures'.
>DBCC results for 'sysservers'.
>There are 3 rows in 1 pages for object 'sysservers'.
>CHECKDB found 1 allocation errors and 1 consistency errors in table
>'sysservers' (object ID 40).
>DBCC results for 'syslanguages'.
>There are 33 rows in 3 pages for object 'syslanguages'.
>DBCC results for 'syscharsets'.
>There are 114 rows in 33 pages for object 'syscharsets'.
>DBCC results for 'sysaltfiles'.
>There are 28 rows in 6 pages for object 'sysaltfiles'.
>DBCC results for 'sysfilegroups'.
>There are 1 rows in 1 pages for object 'sysfilegroups'.
>CHECKDB found 1 allocation errors and 1 consistency errors in table '(Objec
t
>ID 3407872)' (object ID 3407872).
>DBCC results for 'spt_monitor'.
>There are 1 rows in 1 pages for object 'spt_monitor'.
>DBCC results for 'spt_values'.
>There are 730 rows in 7 pages for object 'spt_values'.
>DBCC results for 'spt_fallback_db'.
>There are 0 rows in 0 pages for object 'spt_fallback_db'.
>DBCC results for 'spt_fallback_dev'.
>There are 0 rows in 0 pages for object 'spt_fallback_dev'.
>DBCC results for 'spt_fallback_usg'.
>There are 0 rows in 0 pages for object 'spt_fallback_usg'.
>CHECKDB found 1 allocation errors and 0 consistency errors in table '(Objec
t
>ID 538976288)' (object ID 538976288).
>DBCC results for 'spt_provider_types'.
>There are 25 rows in 1 pages for object 'spt_provider_types'.
>CHECKDB found 0 allocation errors and 1 consistency errors in table '(Objec
t
>ID 1111693545)' (object ID 1111693545).
>DBCC results for 'spt_datatype_info_ext'.
>There are 10 rows in 1 pages for object 'spt_datatype_info_ext'.
>DBCC results for 'MSreplication_options'.
>There are 2 rows in 1 pages for object 'MSreplication_options'.
>DBCC results for 'spt_datatype_info'.
>There are 36 rows in 1 pages for object 'spt_datatype_info'.
>DBCC results for 'spt_server_info'.
>There are 29 rows in 1 pages for object 'spt_server_info'.
>CHECKDB found 4 allocation errors and 6 consistency errors in database
>'master'.
>repair_allow_data_loss is the minimum repair level for the errors found by
>DBCC CHECKDB (master ).
>DBCC execution completed. If DBCC printed error messages, contact your
>system administrator.
>How can I correct these errors?|||Would there be anyway to fix it if we did not have a good copy of the backup
?
"Sue Hoegemeier" wrote:

> Before fixing it, you should check your hardware and look
> for issues with your disk subsystem. Check the event logs on
> the server and look for any other system errors that may
> have occurred around the same time.
> After fixing any hardware issues, then you would need to
> restore the last known good backup of the master database.
> -Sue
> On Wed, 29 Mar 2006 10:08:01 -0800, rleamey
> <rleamey@.discussions.microsoft.com> wrote:
>
>|||Restoring is the best option. If that's not an option, you
can rebuild master using the rebuildm.exe
You can find more information on how to do this in the books
online topic: Rebuilding the master Database
-Sue
On Thu, 30 Mar 2006 05:09:02 -0800, rleamey
<rleamey@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Would there be anyway to fix it if we did not have a good copy of the backu
p?
>"Sue Hoegemeier" wrote:
>