TrendMend Posted June 16, 2020 Posted June 16, 2020 Hey there! Please forgive me if I incorrectly state something, as I am brand new to UNRAID. I have setup a basic system with 2 2tb drives (one for parity) just to get started, and I am having issues with SMB. This system is intended to be used only for windows and to store very important (on-site only) files, yet for some reason SMB just doesn't want to play well with everything. Anytime I tried to start a large file transfer in or out (either with a large amount of files, or a few 50gb+ files) SMB would just quit on me and not work until a reboot. The only way I was able to get the files on was by an FTP transfer, but that isn't optimal for the users of this device for everyday use. I've tried multiple solutions laid out by other folks to see if it was computer side, but came to the conclusion that it is in fact the UNRAID server. Right now I am at a loss, as I have a time constraint of about a week to complete this setup (it's for a family members' business) or I am going to have to rollback to the old system in place (just a single folder on a computer, not very safe in case of drive failure). I would attach a diagnostics file, but when SMB locks up, it won't let me download it. I've tried to ssh in and move it to a folder that I can access after reboot, but almost all files are 0kb, with no text inside (when SMB is working fine they are full of information). Thanks in advance for any input. P.S: I don't know if this is related, but for some reason it says there are too many devices connected (2 drives + 1 thumb drive), I've checked the logs and it does show those 3. It could be because I am still on trial (wanted to make sure this all works before paying), but I don't know. Quote
trurl Posted June 16, 2020 Posted June 16, 2020 That last part sounds like maybe your Flash has dropped. Boot from USB2 port. Diagnostics will tell us more about your configuration so get those before the problem if you can't get them during problem. Also thought I should mention that parity is not a substitute for backups. Quote
TrendMend Posted June 16, 2020 Author Posted June 16, 2020 (edited) 9 hours ago, trurl said: That last part sounds like maybe your Flash has dropped. Boot from USB2 port. Diagnostics will tell us more about your configuration so get those before the problem if you can't get them during problem. Also thought I should mention that parity is not a substitute for backups. Hey, Sorry I don't really understand the "flash dropped" thing, but it should be booting from usb2. I have attached diagnostics below, please feel free to take a look if you so desire. I understand that parity isn't a substitute for backups, the whole unraid thing was just designed for on-site storage whereas backups are kept off-site. The only reason to move it to unraid was to allow other members of the work-group access it, and while doing so provide a performance boost to the one computer that was playing both roles in the past. This is all only due to a sysadmin that decided it would be best to get rid of the servers for reasons unknown about 20 years ago, subsequently screwing almost every single thing up and then disappearing, leaving me to pick up the pieces to this day. Edited June 16, 2020 by TrendMend Quote
trurl Posted June 16, 2020 Posted June 16, 2020 10 minutes ago, TrendMend said: don't really understand the "flash dropped" thing USB3 ports are known to lose connection to the flash drive for some, so USB2 ports are recommended for the boot flash. The syslog in your diagnostics has a lot of things in it that seem related to your problem, but they aren't typical and I have looked at a lot of syslogs. Lots of people transferring files to/from Windows using SMB and I have never seen these in their syslogs. Is there something unusual about the way you are trying to transfer these files, the way your network is configured, etc? Take a look at your syslog and see if you can help explain what is happening. Quote
TrendMend Posted June 16, 2020 Author Posted June 16, 2020 (edited) 19 minutes ago, trurl said: USB3 ports are known to lose connection to the flash drive for some, so USB2 ports are recommended for the boot flash. The syslog in your diagnostics has a lot of things in it that seem related to your problem, but they aren't typical and I have looked at a lot of syslogs. Lots of people transferring files to/from Windows using SMB and I have never seen these in their syslogs. Is there something unusual about the way you are trying to transfer these files, the way your network is configured, etc? Take a look at your syslog and see if you can help explain what is happening. I'll take a look at it for you in a little bit here. It is just a standard unraid setup for smb where it is connected to 3 systems over a workgroup (regular name). The network was wired by me, it's cat 5e connected to an un-managed switch, along with the stupidest modem from the internet provider (one of those "colorvision" things, the model released like 6 months ago)That's really about it, there is like 4 shares though if that helps. I use FTP every little bit here, but not very recently. EDIT: Oh yeah and there is the nerdtools plugin, I was just using it for tmux. The problem was there before I had it installed though. EDITv2: I removed the diagnostics, as for some reason I don't think it anonymized it. There is some stuff I need to remove in it before re-attaching. Edited June 16, 2020 by TrendMend Quote
TrendMend Posted June 16, 2020 Author Posted June 16, 2020 28 minutes ago, trurl said: Take a look at your syslog and see if you can help explain what is happening. OH, duh... I have : log level = 3 logging = syslog in my smb configuration, as per request by another user on discord. That is probably why you are seeing so much smb related stuff. The problem is I can't get the diagnostics after smb stops working, it will just freeze up and ssh'ing in shows that the syslog has nothing. Quote
trurl Posted June 16, 2020 Posted June 16, 2020 18 minutes ago, TrendMend said: I removed the diagnostics, as for some reason I don't think it anonymized it. Diagnostics only looks for certain things to anonymize, and your syslog contained things it wasn't looking for. 4 minutes ago, TrendMend said: I have : log level = 3 logging = syslog in my smb configuration, as per request by another user on discord. That is probably why you are seeing so much smb related stuff. The problem is I can't get the diagnostics after smb stops working, it will just freeze up and ssh'ing in shows that the syslog has nothing. Get rid of that unless that other knowledgeable user on discord is going to help you with it. Quote
TrendMend Posted June 16, 2020 Author Posted June 16, 2020 19 minutes ago, trurl said: Get rid of that unless that other knowledgeable user on discord is going to help you with it. Thanks for the quick response, yeah they couldn't figure it out and I guess I forgot to remove it. I'll attach a new diagnostics file here once I let the server run for a few Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.