Greg F
-
Posts
15 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Greg F
-
-
Hi,
I built a second Unraid server (TowerW), which I store at my parents as an offsite backup. It was assembled last summer, and I use Syncback Free to synchronize my home Unraid server (TowerV) to a 16 TB My Cloud EX2 which I transfer back and forth when I go visit them. I use a Windows VM on each UnRaid server to run Syncback Free. Syncback has been doing a great job sync'ing my files, so I back-up the documents on the unraid server at my parents (TowerW), and they backup my home server (TowerV).
On my last two visits, the server at my parents has been failing the sync'ing. The message in the Windows VM running on the UnRaid server, to which I connect, with RDP, is that the network connection to the drive it's trying to sync has failed. I brought the server home with me, the last time, and have tried to run Syncback on my home Unraid Server Windows VM, and I'm still getting the message that the network connection to the array has failed. What I don't understand is how can the network connection to the array fail, when it's obviously still working because I can be signed onto the Unraid GUI over my network, or the Windows VM running on that server, which runs extremely stable and doesn't disconnect.
I tried to simply copy a directory over the network, not using Syncback, but it failed quickly. The very first file I tried to copy came up with Error 0x8007003B: An unexpected network error occurred. I think Syncback is related to my issues.
I ran the diagnostics, and have attached them for the Gurus here to review.
Thank you is advance,
Greg
-
I looked at the config for my Dockers. In my opinion everything looks ok. I couldn't see anything wrong with the plugins either. The ram is holding still at 8% utilization for the last day or so. I will run some tests, with the dockers running individually for a day or so, to see which docker starts using the ram. I should be able to narrow the problem down to the affected Docker.
Thank you for your input, I should be able to track it down from here.
-
Hi,
I ran Fix Common Problems today, and was expecting the usual no problems found, but was surprised to see "Out Of Memory errors detected on your server". I do have 32 GB of ECC ram, which has been in the server for just over four years, since I built it.
I've attached the diagnostics log in the hope that one of the experts here can advise what's going on. The server has an up-time of only 19 days. It's previously gone almost a year between reboots without this issue. The only docker that's been running over and above unraid, during this time is the PlexMediaServer. No other plugins or dockers have run for any extended duration during the 19 days.
Thanks,
Greg
Unraid Server Components:
M/B: Supermicro - X10SL7-F
CPU: Intel® Xeon® CPU E3-1230L v3 @ 1.80GHz
HVM: Enabled
IOMMU: Enabled
Cache: 256 kB, 1024 kB, 8192 kB
Memory: 32 GB Single-bit ECC (max. installable capacity 32 GB)
-
Hi, I finally got around to updating the old BIOS on the Supermicro motherboard that runs my unraid. The BIOS update went smoothly, with the CMOS cleared, defaults loaded afterwards, followed by a reboot. I then went into the BIOS and chose the boot device, as I need to boot off the USB stick for unraid.
After several reboots, I've been unable to get the web GUI to be accessible. The local GUI seemed to be fine, but I generally never use it. Finally, after starting the server, logging into it to run the diagnostics, I've got a web GUI. I've attached the diagnostics which hopefully show what is causing these problems.
Thank you in advance for your help.
-
1 hour ago, Greg F said:
Since I've already blown away that USB stick, I'll try to upgrade the back-up stick to see if the issue re-occurs. I have copied the config conterts to it, so the outcome should be similar I expect.
Well, I was wrong. My Backup USB stick upgraded perfectly, without incident. Interestingly, when I swapped back the original USB stick, with I had re-imaged with the Unraid USB creator, I ended up with no GUI, but a Tower login was present at the server. I have created a diagnostics log. After a shutdown -r command completed, everything seems fine again. From when I swapped in the original USB stick (line 1), the server has not been moved, powered down except by the shutdown command, nor was the USB stick removed/replaced.
-
23 minutes ago, Frank1940 said:
If you have a Tower Login, login. At the command prompt, type diagnostics and that will write the file to your flash drive in the logs folder/directory.
Since I've already blown away that USB stick, I'll try to upgrade the back-up stick to see if the issue re-occurs. I have copied the config conterts to it, so the outcome should be similar I expect.
-
I'm sorry to rain on the parade, but I had an issue.
After what appeared to be a successful installation, I rebooted when prompted. Instead of the Unraid gui opening, I received an error that the site was unreachable. I logged into the IPMI interface on the server, and it showed Unraid was at the Tower Login, but no gui. I'll open a bug report, but I don't have a diagnostics log to share, and I have no idea if this is reproduce-able. I could attempt the same process with my backup USB stick to see what happens, but if it fails, I would need help to get a log file out of it. Sadly, my Linux skills are rather laughable.
The good news, is I was able to rectify the situation by reflashing my USB drive with 6.6.7 and recopying the config back onto it.
Original version of Unraid on the server was 6.6.6, and the data disks are encrypted.
Loosing internal Network connection?
in General Support
Posted
It would appear the issue is definitely Microsoft changing SMB on Windows 10. My previous attempt to manually copy files was between two mapped drives in a Windows VM, by using Windows Explorer. This time, I mapped the two drives in Nemo on Linux Mint Debian edition, and successfully copied 84GB between two folders.
I'll read the sticky thread for some helpful hints in resolving the issues.
Thank you for your expert help, I never would have thought of the SMB issue.