Your next option would be to reboot it to recovery console and then run the chkdsk
-----Original Message----- From: Salvatore Palmisano [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 10, 2002 4:46 PM To: NT 2000 Discussions Subject: RE: Bad Block Event Log It doesn't tell me it'll do it at next reboot. All it says is 'cannot open volume for direct access.' But then again, this is all from terminal services...i hooked a keyboard and monitor to it, but didn't restart it yet in fear of it not coming back up. It wont recognize the keyboard until I reboot, though. Any way to reinitialize the keyboard without a restart? .salvatore http://sienar.org/ http://palmisanonet.com/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Roger Seielstad Sent: Tuesday, December 10, 2002 6:49 AM To: NT 2000 Discussions Subject: RE: Bad Block Event Log You're probably going to want to run chkdsk x: /r, which will give you that error - but also says that it will schedule itself for the next reboot. ------------------------------------------------------ Roger D. Seielstad - MCSE Sr. Systems Administrator Inovis - Formerly Harbinger and Extricity Atlanta, GA ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to %%email.unsub%% *****This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you have received this email in error please notify [EMAIL PROTECTED] Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Stainsafe Inc. or any of its subsidiaries or affiliates. The company accepts no liability for any damage caused by any virus transmitted by this email.***** ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
