Can't Access CIFS Share After Reboot

[jsmiller1919]

Running FreeNas version 9.1.1 on an HP Micro Server with 4 disks. I rebooted the server and now I can't access the CIFS share from Windows 10 or Windows 2008 R2 server. The volume status says healthy in console. I inherited this box and don't have any experience with FreeNas. Any help would be appreciated. Thanks!

 

[dlavigne]

You'll need to provide a lot more information (as per the forum rules): system specs, build version (from System -> Information), operating system version of connecting client, and any error messages.

 

[jsmiller1919]

When I click on Change permissions it shows Unix. Should that be Windows? Would it have switched on it's own when it rebooted? Can I simply change that to Windows without issue?

 

[anodos]

When I click on Change permissions it shows Unix. Should that be Windows? Would it have switched on it's own when it rebooted? Can I simply change that to Windows without issue?

Post a debug file or PM it to me.

 

[Andrew T Schnable]

Running FreeNas version 9.1.1 on an HP Micro Server with 4 disks. I rebooted the server and now I can't access the CIFS share from Windows 10 or Windows 2008 R2 server. The volume status says healthy in console. I inherited this box and don't have any experience with FreeNas. Any help would be appreciated. Thanks!

Try to access the share using IP address rather than name; e.g., \\192.168.1.88\ instead of \\freenas\ ... Does that work?

What error are you seeing on windows when you try to access the share?

 

[Ericloewe]

Post a debug file or PM it to me.

Does 9.1 even have debug files? Fake edit: apparently it does.

 

[jsmiller1919]

Attached debug

 

[jsmiller1919]

Try to access the share using IP address rather than name; e.g., \\192.168.1.88\ instead of \\freenas\ ... Does that work?

What error are you seeing on windows when you try to access the share?

Tried using IP with no luck. Getting "Windows cannot access \\xxxxxx\cifs1".

 

[jsmiller1919]

This is showing on the screen. See attached.

 

[jsmiller1919]

A little more detail that I should have added in the original post. I was in the web interface using Chrome and when I was just checking things out I couldn't view the disks or volumes. I thought, well, I hadn't rebooted this thing in over a year so I rebooted. My share wasn't coming back online and I couldn't ping the server so I went to see what was going on and saw a bunch of errors on the screen just like above. I powered the server off and back on again and it seemed to boot ok. I could now log back into the interface but couldn't see my drives. I read somewhere that it could be a chrome thing so I tried Firefox and sure enough I could see the disks and volume. I could access my CIFS share just fine before the reboot. Not sure what is going on. I appreciate the help!

 

[anodos]

It's possible that your boot media got corrupted. Perhaps FreeNAS was running from memory and when you rebooted it went Kaput. Try booting from a fresh install on a different USB flash drive and importing your pool. By the way, your pool is 97% full. Bad things happen when you get to 100%. You might want to put some thought into how to proceed going forwards.

This might be a good time to upgrade to a newer version of freenas. The smb.conf in the old version is just bad (lots of voodoo). Not sure what were we thinking there.

If it were my box, my priorities would be:
1) verify that the pool is in good working order (most likely the case)
2) verify that hard drives are in good working order (can't tell in the old debug file)
3) free up space
4) upgrade to modern FreeNAS
5) redo config.

 

[jsmiller1919]

Yes, the disk did fill up. Caught me off guard. Am I able to just do an upgrade to correct the issue? I am not familiar with this at all. Are there any KB articles that can help me build that USB flash drive and import my pool? I may get rid of that box all together so my main goal right now is to just get the data off of there as soon as possible. Thanks for your help!

 

[nojohnny101]

I may get rid of that box all together so my main goal right now is to just get the data off of there as soon as possible. Thanks for your help!

Well in that case, offload the data anyway you can (shares, rsync, etc.) and then export the volume (mark it for destroy) then setup a new one.

Am I able to just do an upgrade to correct the issue?

Upgrading won't solve your issue of being dangerously close to full (recommendation is not to go above 80% capacity for a pool). I would solve that problem first before moving forward.

 

[jsmiller1919]

My volume looks like it is online but Windows can't access the share. When I go into Change permissions it is set to Unix. Can I just set it to Windows without causing problems to see if I can access the share? Is there another way to try and access the share? Keep in mind that I am only a Windows guy.

 

[anodos]

My volume looks like it is online but Windows can't access the share. When I go into Change permissions it is set to Unix. Can I just set it to Windows without causing problems to see if I can access the share? Is there another way to try and access the share? Keep in mind that I am only a Windows guy.

Enable "SSH", check the box "Login as Root with password" under "Services" -> "SSH". Download the application "winscp", then use your webui password to authenticate an "SFTP" session with the server and download your files.

 

[jsmiller1919]

Thank You for your help! I was able to get to the box via FTP. I am using FileZilla to copy off the files.