Welcome to MSFN

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


avada

Can't safely remove esata HDD

4 posts in this topic

Hi!

This one always annoys the hell out of me sometimes windows just refuses to let me remove the esata HDD. Usually I have explorer.exe locking it. I use the Unlocker program the free it up. But even then I can't remove it. Unlocker shows nothing. Now for the umpteenth time googled the issue. And found the Handle program from sysinternals. I could view the handles on the drive but couldn't close them because I got an error that the handle is invalid. What can I do?

Currently these are the handles:


System pid: 4 type: File 18EC: L:\$Extend\$RmMetadata\$TxfLog\$TxfLogContainer00000000000000000002
System pid: 4 type: File 1A64: L:\$Extend\$RmMetadata\$Txf
System pid: 4 type: File 1F80: L:\$Extend\$RmMetadata\$TxfLog\$TxfLogContainer00000000000000000001
System pid: 4 type: File 1FF8: L:\$Extend\$RmMetadata\$TxfLog\$TxfLog.blf

The System process is locking the drive...

0

Share this post


Link to post
Share on other sites

Most likely, you aren't using the driver for the esata port: i had this problem with xp some driver when installed had "safely remove drive for all drive internal or not" and other didn't had it even for the external one.

And if you're already using the right driver then you might try to stop services to identify which one is locking your drive. See there for examples.

Edited by allen2
0

Share this post


Link to post
Share on other sites

Most likely, you aren't using the driver for the esata port: i had this problem with xp some driver when installed had "safely remove drive for all drive internal or not" and other didn't had it even for the external one.

And if you're already using the right driver then you might try to stop services to identify which one is locking your drive. See there for examples.

I'm quite sure I'm using the proper drivers, because I usually can remove the hard rive. But sometimes windows just wouldn't let me. Also it seems it never lets me when I have the HDD connected before I start the computer.

Unfortunately only the darn system processes have handles on the drive so there is no service to be identified.

0

Share this post


Link to post
Share on other sites

The system process is used by many others: for example when you access from the network to a file using a share, the handle on the file is owned by the system process but in fact it is the server service which allow it if you stop the server service the handle would disappear on this file.

So you should really try stopping superfecth, indexing etc ... service on by one to find the right one.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.