Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 6 subscribers
  • Views 2587 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Drobo S Problem Sophos related?

rbpeirce

Does anybody know if out-of-the-box Sophos Home Edition attaches itself to files on attached disk drives?

I have been having a problem.  I can't log on when my Drobo S is attached.  This has been going on for months and I have gone down many dead-ends.  The latest one is that running 'lsof +d /volumes/B1' on my MBP shows UserEvent is accessing the Applications folder on pretty much every attached partition.  When I manually break that connection I can log off and log on but the connection is recreated.

Today I discovered I could tell Sopos to exclude these partitions in its automatic startup configuration.  Upon rebooting and logging in, lsof produced no output.  I can only conclude that Sophos was responsible for this but I would like to confirm it.

I also found, at least so far, that I can log off and back on without disconnecting the Drobo S.  I will want to test this for several days but the UserEvent seems to be causing the problem and Sophos seems to be responsible for that.

Who knows anything about this?

:1010454


This thread was automatically locked due to age.
Parents
  • 0

    There was a Sophos update in early August.  Early August was also when my Drobo S began to act up.  My first thought was something was wrong with the Drobo but after all sorts of checks it came up clean.  Next I discovered that Sophos treats all attached drives as local, so I blocked the Drobo.  The problem was reduced but not eliminated.  Finally I totally removed Sophos from the computer and the problem went away.

    I believe the first release of Sophos I ran may have been 7.3.  At any rate, it has been a while and I never had any problems until August.

    I also have Sophos running on my wife's laptop but I use a different add-on drive on that and have had no problem.  I tried connecting the Drobo to my wife's computer and got the same problem as on mine so I removed Sophos from her computer as well.

    Here is the thing.  The latest release of Sophos appears to work okay with some attached drives but not all.  In particular, the Drobo S seems to have problems.  I say seems to because this problem has been kind of random, possibly related to the prvious message.  I will have to run this way for several days before I am sure the problem has really gone away.

    :1010492
Reply
  • 0

    There was a Sophos update in early August.  Early August was also when my Drobo S began to act up.  My first thought was something was wrong with the Drobo but after all sorts of checks it came up clean.  Next I discovered that Sophos treats all attached drives as local, so I blocked the Drobo.  The problem was reduced but not eliminated.  Finally I totally removed Sophos from the computer and the problem went away.

    I believe the first release of Sophos I ran may have been 7.3.  At any rate, it has been a while and I never had any problems until August.

    I also have Sophos running on my wife's laptop but I use a different add-on drive on that and have had no problem.  I tried connecting the Drobo to my wife's computer and got the same problem as on mine so I removed Sophos from her computer as well.

    Here is the thing.  The latest release of Sophos appears to work okay with some attached drives but not all.  In particular, the Drobo S seems to have problems.  I say seems to because this problem has been kind of random, possibly related to the prvious message.  I will have to run this way for several days before I am sure the problem has really gone away.

    :1010492
Children
No Data