Not sure if you guys can help on this since it is not necessarily (that I know of) an unraid issue.

 

But one, when I reboot I always get a stupid popup saying cannot reconnect mapped drives (simple double clicking them in Explorer makes them work again..I've tried some fixes online that worked but then stopped)

 

Secondly...sometimes my mapped drives randomly lose connection..this morning when I woke up they were all unmapped.  Not sure if this happens when unraid spins the drives down or something?  Though last night ithappened during actions when SAB was repairing a file.

 

Any help appreciated.

 

I am in Windows 7 64 bit Enterprise.

 

Edit:/

Just realized that my unraid was NOT in use last night..that was my local machine..so is it simply (on the second issue) that the drives are all spinning down or going to sleep mode then windows losing the mapping...and if so..any way to workaround it?

if so..any way to workaround it?

Two ways I can think of...

 

1. set the spin down time to "never" on the unRAID server.

2. don't use windows. reformat and install Ubuntu.

 

(The first might be easier than the second, but the second probably also eliminates any potential for MS-Windows viruses as well  )

Whether or not the drives spin down shouldn't make any difference.  Is your UnRAID server set to go to sleep?  The S3 sleep state would result in a lost connection -- and THAT would explain why the mappings are lost.    Same thing is true if your PC is set to use sleep mode.

 

I have a similar system. I use a Win7 HTPC to access my unraid box (never sleeps, does spin down drives) through mapped drives (so in the future I can remap drives or switch to NFS). My HTPC does go to sleep, without issues when it resumes (I dont think i get the popup, but then again XBMC is running...). The only time I run into this problem is after a reboot or shutdown. When it initially logs in, it fails to connect to the mapped drive. I think its because its one of the first items to execute on bootup and its timing out before my wifi connection is fully established, but then again, its only a theory (I can't connect through ethernet since its in the other room).

I think its because its one of the first items to execute on bootup and its timing out before my wifi connection is fully established, but then again, its only a theory (I can't connect through ethernet since its in the other room).

 

Agree.  This definitely sounds like a "race condition" => i.e. one thing is finishing before another thing it depends on has finished.

Windows loves to cleanup broken shortcuts, google windows delete broken shortcut to find the solution. You can also set windows to always wait for network connection and it should ease your problem.

 

Not sure why this affects some users and not others, my friend has the exact same pc as me and he had the same problem, I've never experienced it though.

... my friend has the exact same pc as me and he had the same problem, I've never experienced it though.

 

Does your friend use sleep mode and you don't?

Is one of the systems set for S1 and the other S3 sleep mode in the BIOS?

Are the sleep options set differently vis-à-vis powering down the NIC?  (in either the BIOS or on any Windows clients)

... etc.

 

... and of course all these all interact between the various PC's involved in the mappings.

 

I suspect if you "played detective" on these, you'd find one or more of the above was the reason for the different behavior.