mad taurus

Try creating a linux live USB drive and booting to Linux to test the network hardware first. If it works there, then perhaps it is the Unraid instance. You could back up the flash contents, then do a new build onto the flash drive and restore the config.

-Yes, I have disabled the onboard as I am using the pci-e TP link card. I had thought perhaps the onboard was the issue but it appears to not be. -Yes, this server was originally on 5.x.x but I have since upgraded and done clean installs, while maintaining the settings -It's a windows 8 VM, so it's mostly just for downloading, shouldn't be using too much CPU but chrome can have a tendency to run amok at times. -Disk 5 was precleared before adding to the mix. I was having this issue before I put this drive in to replace a smart failing drive. -I'll configure NTP properly. Thanks! -I'll configure the Jumbo frames, I never touched this setting so it's odd that it is set so high. -192.168.1.208 is my kodi box, I have it doing nightly synchronizations to my media to keep the library updated. Thanks for any help. I configured a Windows 7 VM, taking my Windows 8.1 VM down, and the whole system was online this morning so that's a positive (12+ hrs). I normally completely lose network connectivity overnight, or during the day, it's really at random and at random times. One thing is that the unraid box completely loses network connectivity. At the console, I can't ping even the gateway, or any other devices on my network. Once I do the network cable unplug/replug, it works again. Odd... Thanks!

Anyone with any thoughts? I could try perhaps using a different Windows VM OS? I see some have had issues with Windows VM's, though I have been running this Windows 8.1 OS for over a year now and this issue just started in the past couple months. I could try a Windows 7 OS instead to see if that resolves the issue.

Did you stop the array to see if you can access the settings? Can the VM's access the Internet with the current settings?

Can you ping it by the IP? If yes, how are you trying to connect to the server? If no, are you able to connect a monitor to it and see if it's booting up properly?

You can move data over now if you want. Pre-clearing a drive just reduces the downtime for your server as it cannot add the drive to the array until it is precleared. Depending on the size, that can take hours, even days. Your best bet is to use the Screen app, so you can preclear it while the server is up. Once it's done, you shut the array down, add the drive, and it takes only minutes instead of hours/days.

Hi, My system specs: Intel Pentium G3258 16GB (4x4GB) DDR3 1600 at stock settings Corsair CX400w (30A on +12v) Hitachi 5k4000 4TB (Parity) WD Green EZRX 3TB (data) Seagate ST3000DM001 (data) WD Green EARS 2TB (2) (data) WD Green EZRX 4GB (data) WD Black 500GB (cache) Verbatim 2GB flash drive running Unraid 6.1.9 (had issues with 6.2.4, rolled back, was having same issues before 6.1.9l) This setup has been running fine for over 18 months, and I clean the system out every 2-3 months. Hard drives are cooled by 2 x 120mm fans. CPU is cooled by a Coolermaster Evo 212+. The issue I have been having for probably around 2 months is that I will randomly lose network connectivity to the system. -I cannot ping the Unraid IP, it has a static IP assigned -I cannot ping or reach the Windows VM it is running. Windows VM has a static IP assigned -I cannot ssh or telnet to the Unraid IP -I cannot connect to the http web UI The things I have tried: -connecting using a different LAN cable -connecting to a different port on the switch -connecting directly to the router -installing a different network card (TP-Link Gigabit PCI-e) There are 2 ways to resolve the issue temporarily -reboot the UnRAID server -unplug and replug the LAN cable. This doesn't matter if it happens at the switch, router, or at the PC. Disconnecting the LAN cable at any of these locations and plugging back in will provide network connectivity again. I haven't made any changes to my network. My other wired devices (android TV boxes, Linksys router acting as another access point, smart TV) do not lose connectivity. I've attached my diagnostic from when it failed this morning, I don't know at what point it did this. I hope there are some ideas. Let me know if more information is needed. nas-diagnostics-20161207-0200.zip

On your flash drive, what do you see in your /config folder? There should be stuff in cfg files that you can look into to see the info.

Check to see if you have the folder Private in /etc/samba. Mine was missing when I moved up to 6.2.x and I went back to 6.1.9 as a fresh install with the /config folder copied back onto the USB key. SMB is now working where it wasn't before. I haven't moved to 6.2.x again since 6.1.9 is working for now.

Is there any hints when it states this at the console login screen after it boots? "Default via 192.168.1.1 dev br0 linkdown" "192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.56 linkdown" I'm not sure what that really means. When I go into the Settings -> Network Settings, I get this on the console "Device eth1 does not exist" I'm not sure where it is getting eth1 from?

I'll try a few things. The clients I access with SMB are: 1-Windows 10 Pro workstation 1-Windows 8.1 Pro workstation 1-Windows 7 Pro workstation 2-Android phones (Samsung running Android 6.0, Xiaomi running 7.1, all done through Solid Explorer) NFS is accessed by with no issues: 1-media box running Kodi 16.1 1-media box through SPMC 16 running android 5.1.1

I have removed the credentials from Credential Manager. No luck with blank credentials for accessing the shares. Starting to wonder if I should just restore a previous flash drive backup, though I haven't been great at doing backups and I think the last full flash drive backup I have is 6.0b15. Which I would be happy with since everything worked. Is it as simple as just copying the files onto the existing flash drive? I haven't had to do any such thing yet since the system just ran perfectly until this weekend.

1. They are on the same workgroup. 2. I set that about 30 minutes ago. I imagine it will take some time for it to replicate. Update: Unraid box is now the local master, verified by nbtstat -a and also using the local master plugin. Still unable to see any shares from NAS. Have some of the SMB shares set as Public with no security. Still not able to connect

Hi, I do not have SMB access from Windows 8.1/10 to my unraid box. I can use FTP, NFS, SSH, and the http interface without any issues. I did not make any changes to shares that I can understand would cause this problem. I have attached the diagnostics from Tools -> Diagnostics, I hope there is something there that can give some hints. When I try to access the unraid SMB shares, I get prompted for credentials. I enter them in 3 times, then I get the error message "The specified name is no longer valid" I've tried disabling SMB v2 and v3 as per the MS article without success. I've removed the saved information in Credential Manager I was on 6.19 when this happened, upgraded to 6.2.1 and then 6.2.2 with the same problems. I don't run any dockers, and the only plugin I have installed is the Dynamix local master. Thanks for any help/ideas on what to do. **Resolved** Reloaded 6.1.9 onto the USB key, then copied my config folder from previous setup onto USB drive. Everything appears to be working now, the only thing to hash out are permissions but at least SMB is now working again. I had to add my VM back in again, no big deal there. What i did notice is that on my non-working install, the folder etc\samba\private was missing. I have this folder now so perhaps this was an issue. Thanks to everyone that helped! nas-diagnostics-20161101-1311.zip

I have the exact same issue. My server was working fine on 6.1.9, then it started acting up the past week where it would just go inaccessible at some point (http, SSH, SMB share or NFS share access), and I would have to do a hard reboot since it runs headless. I thought this was a good time to upgrade so went to 6.2.1 and then I lost access via SMB. I can access using http, SSH, or NFS but not SMB. Upgraded to 6.2.2 and same thing. I have tried from Windows 7, Windows 8.1, Windows 10, and from Android. It doesn't accept any of my user credentials (have changed the password to several different accounts). FTP access works as well so I do know everything appears to be running. Have tried samba start through SSH with no luck. Not really sure what I should do at this point.