On 3/29/2011 8:22 PM, Steven Peck wrote: > 1. Nope. Your drive will most likely be in an interesting state.
Don't care too much about that drive .. just the Windows install (C: and D:). Nothing runs from X:, only writes to X:. And I will tell that program to not execute. > 2. As it was interupted it will most likly flag the drive with a 'dirty > bit'. Depending on the condition it 'may' let you skip the recommended > chkdsk once on the way up but I would not plan on it. How? Hit ESCAPE when the Windows splash screen comes up? > If you are desperate, there is a kb article on how to disable the 'dirty > bit' flag for chkdsk but it seriously is not a thing to do lightly. I've seen references ... > You may try downing the system, then have the SAN people pull that LUN > off the server. The server will be upset but most likely be ok. I think I can unpresent that drive to the server ... > Please > note that there is risk to this suggestion and from 'some guy' on the > internet. While we have on occasion had to do similiar here with a > Hitachi SAN, your experience may not be mine and I'd rather not be 'that > guy' on the Internet if something does go wrong. :) No, I'm the idiot, and besides - my boss makes the final call. In fact, I would ask him to unpresent the drive (after I power down the server). > > On Tue, Mar 29, 2011 at 5:12 PM, Mike Leone <oozerd...@gmail.com > <mailto:oozerd...@gmail.com>> wrote: > > I have a bit of an urgent problem. I have a Win2003 server, and I needed > to run CHKDSK on the X: drive (a SAN drive that we use to write disk > backups to). So it is NOT running CHKDSK the boot drive, or the drive > where programs are installed; the X: drive is just for disk backup (EMC > Networker). > > X: is, however, like 2 TB in size ... mostly empty, tho, as the backup > to disk has not been working. (mostly meaning maybe 200-300G, probably > less, used space). > > Chkdsk has been running for like 75 minutes, and I have no way of > estimating how much longer it will take. > > So my questions: > > 1. There's no way to interrupt it, except to power down. But will it > corrupt the machine? I don't really care if the X: drive is corrupt, as > long as it boots up and the Lotus Notes services run (none of which are > installed on X:, everything is to drive E:, a separate SAN drive). > > 2. If I do power it down, will it insist on running CHKDSK when it comes > up? I need to get the server back into production, and can't really wait > for CHKDSK to finish on that drive. > > Any help REALLY appreciated, thanks. > > (yes, I'm an idiot) > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > <mailto:listmana...@lyris.sunbeltsoftware.com> > with the body: unsubscribe ntsysadmin > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > <mailto:listmana...@lyris.sunbeltsoftware.com> > with the body: unsubscribe ntsysadmin > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
