Leftie

Members
  • Posts

    17
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Leftie's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I suspect that you're on the right track with trying to update the VirtIO drivers, since looks very much like a KVM performance issue. The fact that you're running KVM on unRAID is kind of incidental, therefore I think you'll have more luck getting deeply technical help on a dedicated KVM forum. By the way, don't sweat it about the balloon device. That just allows the hypervisor to reclaim memory that's been allocated to your VM. If you're not overbooking your memory allocations (that is; assigning more memory in total to your VMs than you physically have), the balloon device doesn't really do much. I really wish I could help you more with this, but my experience with VMs on KVM is limited to some lightweight linux installations. Sounds like your setup is quite advanced.
  2. I've been trying to configure the CrashPlan Docker to replace my ISPs version of CrashPlanPro, but I'm beginning to suspect that this is not possible. I need to be able to set a different CrashPlan host to which the backup engine connects (i.e. my ISPs CrashPlanPro host), but this obviously cannot be done via the GUI. I'm afraid I haven't been able to find a config file setting for this either, but if any of you could enlighten me on this, it would be highly appreciated
  3. Had the same symptoms as mazma, i.e. no reachable Web GUI. Tried deleting the app-folder, but since that didn't help, I ended up having to delete the container and image before things started working again. So I had to reconfigure everything from scratch, but at least now it's up and running again
  4. I'm running with mostly Windows desktops, and am using unRAID for basically all of my file storage. "My Documents", "My Pictures" etc. are all tricked into using the unRAID SMB shares, via Windows "hard links". This trick doesn't fool the Windows file indexing service though, so I'm wondering what you guys use when you need to search for files (both names and content). As a workaround, I've tried "Everything" and "Agent Ransack", preferring the latter even though it doesn't have the option to build an index. I would like to see a built-in (or at least unRAID based) solution for this. Are there any Docker projects for file searching/indexing or is there perhaps some clever trick that I'm missing?
  5. The router reboot solved it! Thanks for all the helpful tips everyone
  6. As stated in this post, DNS entries are received from DHCP. DNS name resolution does not work on the server, even though it works fine for other devices on the same subnet (also using DHCP).
  7. I'm not 100% sure. It has just been running by itself for quite a while, and since the samba service worked like it should, I didn't think to do a complete check on it before trying out Simplefeatures. This output looks OK to me: root@Tower:~# /sbin/route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 10.0.0.138 0.0.0.0 UG 202 0 0 eth0 10.0.0.0 0.0.0.0 255.255.255.0 U 202 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
  8. The static IP address information can now be disregarded. The server is now up and running with a DHCP supplied IP address. There is - as you said - no technical reason why the gateway should be the lowest or highest address on the subnet, it is merely done by convention. The gateway address has to be specified either way. In this instance, 10.0.0.138 is the default address of a ZyXEL router. That being said, yes I have about 6 other devices on this network that can all communicate fine both with each other and with the Internet. E.g. the machine I'm sitting at now (Windows 7, btw): Ethernet adapter eth0: Connection-specific DNS Suffix . : lan Link-local IPv6 Address . . . . . : fe80::cc47:6223:41e9:4326%25 IPv4 Address. . . . . . . . . . . : 10.0.0.111 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 10.0.0.138
  9. Right. Plugins are out, and I've rebooted again. Still no luck with pinging. Name resolution fails now too, by the way. root@Tower:~# ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 2 Transceiver: internal Auto-negotiation: on MDI-X: off Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) Link detected: yes root@Tower:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:1e:67:23:4b:b3 inet addr:10.0.0.42 Bcast:10.0.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:241 errors:0 dropped:0 overruns:0 frame:0 TX packets:258 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:20642 (20.1 KiB) TX bytes:66255 (64.7 KiB) Interrupt:16 Memory:b1100000-b1120000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:560 (560.0 B) TX bytes:560 (560.0 B) [Edit:] I may be a bit myopic here, but I've gotten hung up on the fact that there's a delay before the telnet prompt comes up. I timed it, and it's exactly 30 seconds. Did a bit of googling on this, and it seems it could be related to DNS resolving not working as it should (the 30 second delay is the timeout from the reverse DNS lookup). I'm just not sure where to start troubleshooting this. Here's the content of /etc/resolv.conf: # Generated by dhcpcd from eth0 # /etc/resolv.conf.head can replace this line domain lan nameserver 193.213.112.4 nameserver 130.67.15.198 nameserver 10.0.0.138 # /etc/resolv.conf.tail can replace this line [/edit]
  10. Hi, and thanks for the quick reply. There's probably a time-zone difference, so my answers will be lagging a bit behind. Yeah, after browsing through the forum for a mention of similar problems, the one that seemed closest had apparently been solved by reverting to DHCP instead of static IP, so I just went in and did the edit manually before restarting the network. Anyway, tried replacing the network.cfg and rebooting now, and it apparently does not change anything regarding network connectivity. A fresh syslog is attached to this post. syslog.txt
  11. This is a compound issue, but I think the problem of pinging out from the server is at least a clue to the root cause, so I'm using that as the thread title. (For now, anyway.) Some background: I'm running version 5.0-rc8a. After trying (and failing) to install SimpleFeatures, I noticed that my other plugins (sabnzbd, sickbeard, headphones etc. (influencer versions)) were not functioning properly. I tried reinstalling them, but this failed too. Rebooting also took ages (I think it was waiting for each plugin-installation to time out). I've removed all the plugins except for dropbox, since this still works (strangely enough), but this doesn't seem to solve the more basic connection issues I'm having. Current status: I can ping the server fine from my other computers. The unRAID Web GUI works fine. The Samba service and shares work fine. The Dropbox plugin works fine and even updates files from the Internet telnet to the server works fine, but the logon prompt takes about a minute to show up DNS name resolution works Ping from the server does not work (not to any devices on the network, including the router) wget does not work (which I guess is why the influencer-plugins are having problems) Contents of network.cfg: # Generated settings: USE_DHCP="yes" IPADDR="10.0.0.42" NETMASK="255.255.255.0" GATEWAY="10.0.0.138" DHCP_KEEPRESOLV="no" DNS_SERVER1="193.213.112.4" DNS_SERVER2="130.67.15.198" DNS_SERVER3="" I know the various IP settings are redundant when USE_DCHP="yes", but that shouldn't matter, should it? I've attached the syslog in the post here, but the only errors I see there, are related to ACPI. I hope I've provided you with enough clues to help me figure out the root cause, or at least help me find more clues. syslog.txt
  12. Just wanted to add to this, since this can still happen in 5.0-rc8a. Sorry if I should have made a thread in the beta sub-forum instead. Copied a huge amount of data (approx 1.2 times the size of the cache disk) to the array and ended up with a completely full cache disk, after which the mover script would not actually do anything. All it left in the syslog was a message saying it had started, just like OP mentions. For the record; the "Min. free space" attribute for the cache drive was set to the default value of 2000000. Tried running the script with the following command: /bin/bash -x /usr/local/sbin/mover This showed that the script exited with code 0 after the first test: if [ ! -d /mnt/cache -o ! -d /mnt/user0 ]; then exit 0 Can't really say for sure whether or not I had a user0 share at the time, but what I tried to do (instead of simply rebooting) was stop the SMB service from the GUI. After this, the mover script worked like it should once again. Now, I don't know exactly what steps are executed with the stopping of the SMB service, so I don't know what actually resolved the issue. I just figured you guys would appreciate the extra info.
  13. Hi guys, fresh meat here. Thought I'd post the specs of my newly built unRAID server, since I'm planning on contributing to the hardware compatibility list. MotherboardIntel S3420GPV Memory4 x 4GB Kingston unbuffered ECC PC3 DIMMS (Actually 2 x 8GB kits: KVR1333D3E9SK2/8G) ProcessorIntel Core i3 540 Cache driveWestern Digital VelociRaptor 500 GB Parity driveSeagate Barracuda 3TB Data drives2 x Western Digital Caviar Green 500GB 2 x Western Digital Caviar Green 2TB (Soon) Got the machine up and running yesterday, and I've been busy shuffling data around on my disks in order to free up enough space to move them over to the server. Some of that data has been pushed over on the 500GB disks present in the server from day 1. Once the 2TB disks are actually in place, I'll check if it's necessary to clean up the system log before the last round of data-migration. Please disregard the extreme overkill on system memory. I'd ordered a single 8GB kit (which is rather extreme in it self, I know), but my supplier managed to send me two. Who am I to complain, eh? [Edit: BTW, I'm running 5.0-rc8a. If everything goes to heck, I'll survive ]
  14. It is not instantly critical, but it is something you need to monitor. If the number keeps increasing, you have what is called predictive failure of the disk. As long as you have more "backup" sectors on the drive, it will just flag the bad ones and keep chugging away as normal. How many you actually have, depends on the drive. Check here for details: http://kb.acronis.com/content/9136
  15. Good point. Another reason not to use the array while it's rebuilding then