hmmmm I don't have "fuse_remember="330" wonder if Tom added that and until you "SMB settings pressed apply"

Let me try it on mine.

OK, lets try this first, can you shutdown unRAID and remove the key and insert it into another device to access it?

if so rename share.cfg to something else, copy the share.cfg from the unRAID source, put the stick back into your unRAID server and boot it back up.

 

default share.cfg should contain only: (from the source)

 

# Share options
shareFlash=e
shareDisk=e
shareUser=-

 

Once you boot back up, paste in your post what the share.cfg contains and check your /config/shares directory as well and report back.

 

 

All shares are gone, share.cfg restarted exactly as above (clean) and the directory is also empty.

Well, i did the same as you  clicked apply in SMB settings, emhttp crashed, WebGUI no longer available (good stuff) shares are accessible.

Good thing there is no way to restart unRAID gratefully via commandline!

 

I check and see the date/timestamp changed on my share.cfg and it now contains "fuse_remember="330", so I will post this so see what Tom's say about when it was added and what's it do (nothing to do with your problem).

 

 

OK, lets try this first, can you shutdown unRAID and remove the key and insert it into another device to access it?

if so rename share.cfg to something else, copy the share.cfg from the unRAID source, put the stick back into your unRAID server and boot it back up.

 

default share.cfg should contain only: (from the source)

 

# Share options
shareFlash=e
shareDisk=e
shareUser=-

 

Once you boot back up, paste in your post what the share.cfg contains and check your /config/shares directory as well and report back.

 

 

All shares are gone, share.cfg restarted exactly as above (clean) and the directory is also empty.

Sorry are you saying you did all those steps above? and reboot and now you don't see shares in the WebGui?

 

Well, i did the same as you  clicked apply in SMB settings, emhttp crashed, WebGUI no longer available (good stuff) shares are accessible.

Good thing there is no way to restart unRAID gratefully via commandline!

 

I check and see the date/timestamp changed on my share.cfg and it now contains "fuse_remember="330", so I will post this so see what Tom's say about when it was added and what's it do (nothing to do with your problem).

 

Damn, i'am sorry!

 

Sorry are you saying you did all those steps above? and reboot and now you don't see shares in the WebGui?

Yes. But they appeared again after i went to SMB settings and activated it.

 

OK, good, my assumption is when you reboot unRAID now and start the array (maybe start/stop the array) , you should get the user share .cfg's created (hopefully) now.

Well, i did the same as you  clicked apply in SMB settings, emhttp crashed, WebGUI no longer available (good stuff) shares are accessible.

Good thing there is no way to restart unRAID gratefully via commandline!

 

I check and see the date/timestamp changed on my share.cfg and it now contains "fuse_remember="330", so I will post this so see what Tom's say about when it was added and what's it do (nothing to do with your problem).

 

Damn, i'am sorry!

 

Not your fault, I posted in the RC16c thread, we'll see what Tom says.

 

OK, good, my assumption is when you reboot unRAID now and start the array (maybe start/stop the array) , you should get the user share .cfg's created (hopefully) now.

 

Nope, no luck with the files appearing...

Go to one of the shares in share settings and just click apply (don't change anything) see if one is generated, if not, change a simple value (that won't hurt you) click apply and check for .cfg file again.

Yep, pressing apply made all the cfg files to appear!

Sweet, I got to run for now, run a few simple data tests. Good luck, check back later...

Thanks, but i don't think i am going to waste more of anyone time with this. Maybe it's a disk issue that SMART doesn't catches or something...

 

Thanks for your time and help though!

I don't believe SMART would not report on something, you're welcome to post your smart reports for review by the community.

See if you have an old syslog around somewhere with prior versions of unRAID to see what HIGHMEM states in them, would be interesting.

Lastly, stupid question, you did run "new permissions", would not hurt to run and let it complete again.

 

 

Good thing there is no way to restart unRAID gratefully via commandline!

 

 

Well there is actually (I just had an emhttp crash myself, so found this):

 

http://lime-technology.com/wiki/index.php/Console#To_cleanly_Stop_the_array_from_the_command_line

 

Just make sure you've got nothing open in /mnt/user and this will cleanly stop the array, then you can issue a reboot command.