![]() |
|
|
Welcome to the { mindfrost82.com } forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
|
|||
|
systems reboots when chkdsk finds unreadable segment
I have installed XP on C drive and chkdsk has found an unreadable file record
segment on the F drive (a Raid array). After chkdsk reports the error, the system reboots. How do I fix this please? I have read that chkdsk /f can take days to run on large disks (eg 70GB). My F drive is 240GB. I have the number of the faulty record segment. TIA .... Greg PS I originally posted this in the General newsgroup which I think was a mistake. Sorry! |
|
|||
|
RE: systems reboots when chkdsk finds unreadable segment
PS I tried running chkdsk /r and same thing happened, ie it found and
reported the error then system re-booted. "gvm" wrote: > I have installed XP on C drive and chkdsk has found an unreadable file record > segment on the F drive (a Raid array). After chkdsk reports the error, the > system reboots. How do I fix this please? I have read that chkdsk /f can take > days to run on large disks (eg 70GB). My F drive is 240GB. I have the number > of the faulty record segment. TIA .... Greg > > PS I originally posted this in the General newsgroup which I think was a > mistake. Sorry! > |
|
|||
|
Re: systems reboots when chkdsk finds unreadable segment
Run Disk CleanUp first as this can remove a problematic file.
What does Event Viewer report regarding the problem? You can access Event Viewer by selecting Start, Control Panel, Administrative Tools, and Event Viewer. When researching the meaning of the error, information regarding Event ID, Source and Description are important. HOW TO: View and Manage Event Logs in Event Viewer in Windows XP http://support.microsoft.com/kb/308427/en-us Part of the Description of the error will include a link, which you should double click for further information. You can copy using copy and paste. Often the link will, however, say there is no further information. http://go.microsoft.com/fw.link/events.asp (Please note the hyperlink above is for illustration purposes only) A tip for posting copies of Error Reports! Run Event Viewer and double click on the error you want to copy. In the window, which appears is a button resembling two pages. Click the button and close Event Viewer.Now start your message (email) and do a paste into the body of the message. Make sure this is the first paste after exiting from Event Viewer. -- Hope this helps. Gerry ~~~~ FCA Stourport, England Enquire, plan and execute ~~~~~~~~~~~~~~~~~~~ gvm wrote: > PS I tried running chkdsk /r and same thing happened, ie it found and > reported the error then system re-booted. > > "gvm" wrote: > >> I have installed XP on C drive and chkdsk has found an unreadable >> file record segment on the F drive (a Raid array). After chkdsk >> reports the error, the system reboots. How do I fix this please? I >> have read that chkdsk /f can take days to run on large disks (eg >> 70GB). My F drive is 240GB. I have the number of the faulty record >> segment. TIA .... Greg >> >> PS I originally posted this in the General newsgroup which I think >> was a mistake. Sorry! |
|
|||
|
Re: systems reboots when chkdsk finds unreadable segment
Gerry, the system crashes and reboots once disk cleanup attempts to use the
bad block on the disk. There are two types of events in the log as follows: Event Type: Error Event Source: System Error Event Category: (102) Event ID: 1003 Date: 22/11/2007 Time: 7:42:13 AM User: N/A Computer: TECHMASTERY Description: Error code 000000d1, parameter1 000001fb, parameter2 00000005, parameter3 00000000, parameter4 f77a1b6f. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 53 79 73 74 65 6d 20 45 System E 0008: 72 72 6f 72 20 20 45 72 rror Er 0010: 72 6f 72 20 63 6f 64 65 ror code 0018: 20 30 30 30 30 30 30 64 000000d 0020: 31 20 20 50 61 72 61 6d 1 Param 0028: 65 74 65 72 73 20 30 30 eters 00 0030: 30 30 30 31 66 62 2c 20 0001fb, 0038: 30 30 30 30 30 30 30 35 00000005 0040: 2c 20 30 30 30 30 30 30 , 000000 0048: 30 30 2c 20 66 37 37 61 00, f77a 0050: 31 62 36 66 1b6f Event Type: Error Event Source: Disk Event Category: None Event ID: 7 Date: 21/11/2007 Time: 9:56:31 PM User: N/A Computer: TECHMASTERY Description: The device, \Device\Harddisk1\D, has a bad block. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 03 00 68 00 01 00 b6 00 ..h...¶. 0008: 00 00 00 00 07 00 04 c0 .......À 0010: 00 01 00 00 9c 00 00 c0 ....œ..À 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 ee 6f c4 14 00 00 00 .îoÄ.... 0028: 32 6b 00 00 00 00 00 00 2k...... 0030: ff ff ff ff 01 00 00 00 ÿÿÿÿ.... 0038: 40 00 00 c4 02 00 00 00 @..Ä.... 0040: ff 20 0a 12 4c 02 20 40 ÿ ..L. @ 0048: 00 10 00 00 0a 00 00 00 ........ 0050: 00 60 40 d5 48 87 3e 86 .`@ÕH‡>† 0058: 00 00 00 00 c0 09 39 86 ....À.9† 0060: 00 00 00 00 f7 37 62 0a ....÷7b. 0068: 28 00 0a 62 37 f7 00 00 (..b7÷.. 0070: 08 00 00 00 00 00 00 00 ........ 0078: f0 00 03 00 00 00 00 0b ð....... 0080: 00 00 00 00 00 00 00 00 ........ 0088: 00 00 00 00 00 00 00 00 ........ "Gerry" wrote: > Run Disk CleanUp first as this can remove a problematic file. > > What does Event Viewer report regarding the problem? > > You can access Event Viewer by selecting Start, Control Panel, > Administrative Tools, and Event Viewer. When researching the meaning > of the error, information regarding Event ID, Source and Description > are important. > > HOW TO: View and Manage Event Logs in Event Viewer in Windows XP > http://support.microsoft.com/kb/308427/en-us > > Part of the Description of the error will include a link, which you > should double click for further information. You can copy using copy > and paste. Often the link will, however, say there is no further > information. > http://go.microsoft.com/fw.link/events.asp > (Please note the hyperlink above is for illustration purposes only) > > A tip for posting copies of Error Reports! Run Event Viewer and double > click on the error you want to copy. In the window, which appears is a > button resembling two pages. Click the button and close Event > Viewer.Now start your message (email) and do a paste into the body of > the message. Make sure this is the first paste after exiting from > Event Viewer. > > > -- > > > > Hope this helps. > > Gerry > ~~~~ > FCA > Stourport, England > Enquire, plan and execute > ~~~~~~~~~~~~~~~~~~~ > gvm wrote: > > PS I tried running chkdsk /r and same thing happened, ie it found and > > reported the error then system re-booted. > > > > "gvm" wrote: > > > >> I have installed XP on C drive and chkdsk has found an unreadable > >> file record segment on the F drive (a Raid array). After chkdsk > >> reports the error, the system reboots. How do I fix this please? I > >> have read that chkdsk /f can take days to run on large disks (eg > >> 70GB). My F drive is 240GB. I have the number of the faulty record > >> segment. TIA .... Greg > >> > >> PS I originally posted this in the General newsgroup which I think > >> was a mistake. Sorry! > > > |
|
|||
|
Re: systems reboots when chkdsk finds unreadable segment
Try this suggestion:
Start, Run, type "cmd" without quotes, type "F:" without quotes, type chkdsk /f and hit Enter. http://www.ss64.com/nt/chkdsk.html -- Hope this helps. Gerry ~~~~ FCA Stourport, England Enquire, plan and execute ~~~~~~~~~~~~~~~~~~~ gvm wrote: > Gerry, the system crashes and reboots once disk cleanup attempts to > use the bad block on the disk. There are two types of events in the > log as follows: Event Type: Error > Event Source: System Error > Event Category: (102) > Event ID: 1003 > Date: 22/11/2007 > Time: 7:42:13 AM > User: N/A > Computer: TECHMASTERY > Description: > Error code 000000d1, parameter1 000001fb, parameter2 00000005, > parameter3 00000000, parameter4 f77a1b6f. > > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > Data: > 0000: 53 79 73 74 65 6d 20 45 System E > 0008: 72 72 6f 72 20 20 45 72 rror Er > 0010: 72 6f 72 20 63 6f 64 65 ror code > 0018: 20 30 30 30 30 30 30 64 000000d > 0020: 31 20 20 50 61 72 61 6d 1 Param > 0028: 65 74 65 72 73 20 30 30 eters 00 > 0030: 30 30 30 31 66 62 2c 20 0001fb, > 0038: 30 30 30 30 30 30 30 35 00000005 > 0040: 2c 20 30 30 30 30 30 30 , 000000 > 0048: 30 30 2c 20 66 37 37 61 00, f77a > 0050: 31 62 36 66 1b6f > > > Event Type: Error > Event Source: Disk > Event Category: None > Event ID: 7 > Date: 21/11/2007 > Time: 9:56:31 PM > User: N/A > Computer: TECHMASTERY > Description: > The device, \Device\Harddisk1\D, has a bad block. > > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > Data: > 0000: 03 00 68 00 01 00 b6 00 ..h...¶. > 0008: 00 00 00 00 07 00 04 c0 .......À > 0010: 00 01 00 00 9c 00 00 c0 ....œ..À > 0018: 00 00 00 00 00 00 00 00 ........ > 0020: 00 ee 6f c4 14 00 00 00 .îoÄ.... > 0028: 32 6b 00 00 00 00 00 00 2k...... > 0030: ff ff ff ff 01 00 00 00 ÿÿÿÿ.... > 0038: 40 00 00 c4 02 00 00 00 @..Ä.... > 0040: ff 20 0a 12 4c 02 20 40 ÿ ..L. @ > 0048: 00 10 00 00 0a 00 00 00 ........ > 0050: 00 60 40 d5 48 87 3e 86 .`@ÕH‡>† > 0058: 00 00 00 00 c0 09 39 86 ....À.9† > 0060: 00 00 00 00 f7 37 62 0a ....÷7b. > 0068: 28 00 0a 62 37 f7 00 00 (..b7÷.. > 0070: 08 00 00 00 00 00 00 00 ........ > 0078: f0 00 03 00 00 00 00 0b ð....... > 0080: 00 00 00 00 00 00 00 00 ........ > 0088: 00 00 00 00 00 00 00 00 ........ > > "Gerry" wrote: > >> Run Disk CleanUp first as this can remove a problematic file. >> >> What does Event Viewer report regarding the problem? >> >> You can access Event Viewer by selecting Start, Control Panel, >> Administrative Tools, and Event Viewer. When researching the meaning >> of the error, information regarding Event ID, Source and Description >> are important. >> >> HOW TO: View and Manage Event Logs in Event Viewer in Windows XP >> http://support.microsoft.com/kb/308427/en-us >> >> Part of the Description of the error will include a link, which you >> should double click for further information. You can copy using copy >> and paste. Often the link will, however, say there is no further >> information. >> http://go.microsoft.com/fw.link/events.asp >> (Please note the hyperlink above is for illustration purposes only) >> >> A tip for posting copies of Error Reports! Run Event Viewer and >> double click on the error you want to copy. In the window, which >> appears is a button resembling two pages. Click the button and close >> Event Viewer.Now start your message (email) and do a paste into the >> body of the message. Make sure this is the first paste after exiting >> from Event Viewer. >> >> >> -- >> >> >> >> Hope this helps. >> >> Gerry >> ~~~~ >> FCA >> Stourport, England >> Enquire, plan and execute >> ~~~~~~~~~~~~~~~~~~~ >> gvm wrote: >>> PS I tried running chkdsk /r and same thing happened, ie it found >>> and reported the error then system re-booted. >>> >>> "gvm" wrote: >>> >>>> I have installed XP on C drive and chkdsk has found an unreadable >>>> file record segment on the F drive (a Raid array). After chkdsk >>>> reports the error, the system reboots. How do I fix this please? I >>>> have read that chkdsk /f can take days to run on large disks (eg >>>> 70GB). My F drive is 240GB. I have the number of the faulty record >>>> segment. TIA .... Greg >>>> >>>> PS I originally posted this in the General newsgroup which I think >>>> was a mistake. Sorry! |
![]() |
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|