jk2587

Members
  • Posts

    18
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

jk2587's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Hi @limetech I'd like to be able to use the usbip client inside a docker container, and for that I believe the vhci-hcd kernel module needs to exist on the host. Here is the message I received when trying to run modprobe vhci-hcd in a container (homeassistant): modprobe vhci-hcd modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.18.20-unRAID/modules.dep.bin' modprobe: FATAL: Module vhci-hcd not found in directory /lib/modules/4.18.20-unRAID And when trying to run it on the host: modprobe vhci-hcd modprobe: FATAL: Module vhci-hcd not found in directory /lib/modules/4.18.20-unRAID Thanks for your help! Joel
  2. Hi Squid - I'm seeing the same issue as bdydrp on a server that was just upgraded from 5.x to 6.1.7 that I'm helping a friend with. When I choose to add a docker from CA (any docker) I get the same basic screen as if I clicked "Add container" on the docker tab. After the initial start of unRAID 6.1.7 I enabled docker, then installed CA. Installing plugins works fine, but not dockers. I have not yet rebooted since starting unraid 6.1.7. I seem to recall seeing this on another server I set up but I had to reboot for other reasons and following that there was no issue. The URL(s) in the new "AddContainer" tab look like: http://192.168.1.10/AddContainer?xmlTemplate=default:/var/lib/docker/unraid/templates-community-apps/94.xml http://192.168.1.10/AddContainer?xmlTemplate=default:/var/lib/docker/unraid/templates-community-apps/124.xml I looked in the directory specified and it doesn't exist - see below: root@pinta:~# ls -l /var/lib/docker/unraid total 0 drwxrwxrwx 1 root root 100 Jan 24 20:45 community.applications.datastore/ root@pinta:~# When I check another server which is working, I see the /var/lib/docker/unraid/templates-community-apps directory which is full of XML files. Hope that helps track down the issue! Let me know if there's anything else I can grab to help out. Thanks Update: I manually created that directory then clicked "Update Applications" and it's working as expected.
  3. I'm interested in the other SGI chassis - will send a PM. Thanks!
  4. The link is working again - thanks! This will be very helpful...
  5. I realize this is an old post, but the original download link is broken, any chance of getting it put somewhere else? I'm working out some fan control stuff and this app would be a big help. Thanks!
  6. I extracted them from the previous package: SABnzbdDependencies-1.3-i486-unRAID.tgz which you can download from http://lime-technology.com/forum/index.php?topic=2903.msg30274#msg30274 I'm still far from proficient with the command line myself, so I just used winrar to place libtbb.so and libtbb.so.2 on my flash drive (via \\tower\flash), then copied them with the following commands: cd /boot cp libtbb.so* /usr/lib I didn't bother adding to the go script, I'll just wait for a new package and copy these manually if I need to.
  7. Thanks for the package Romir, just wanted to let you know that libtbb.so and libtbb.so.2 that par2 needs are missing from the new dependencies package. Until the package has been updated I've copied them manually to /usr/lib and par2 is working as expected. Thanks!
  8. beta 8 cleared up this issue for me, I didn't specifically test beta 11 but I don't remember having issues yesterday on beta 10.
  9. I am unable to access any shares over the network with this version, it asks for a password (I do have user security enabled). I am on Windows 7, I have a user in unraid defined with the same name and password as the Windows 7 user, but the password does not work. Reverting back to beta 8 and everything works as expected. Sorry I didn't grab a syslog, had people coming over and needed it back up and running, if necessary I'll get it later tonight.
  10. Use telnet... Unless you're on vista or windows 7 telnet is already part of windows. Just open a command prompt and type: telnet <ipaddress> obviously replacing <ipaddress> with the actual ip address of your server.
  11. nate1749, The rack you bought is not correct. It is intended mainly for networking gear and is only 18" deep, while the Norco case is 25.5" deep. You need a much deeper case, and I can't say for sure as I don't have mine racked but I think you might need the rails too.
  12. I'm guessing you're using Vista or Win7, which does not have the telnet client installed by default. You can install it from Control Panel > Programs > Turn Windows Features on or off.
  13. It looks like the problems are resolved. I ran reiserfsck on all the data drives and there were two that had issues: disk 1 and the cache drive. Before I even knew there was a problem with the build I had transferred some data from the cache drive to disk1, so it was not a surprise to me that both of them would need fixing. Other than that, it looks like everything is running smoothly. I'm currently running the preclear script on 2 1.5 TB drives, I can't believe how much faster it is than my old system! I'll attach another syslog here, I'd really appreciate if RobJ could take a quick look to make sure everything is ok. I think it is, but I'm far from an expert when it comes to reading the logs. Thanks again for all the help, it made the process very painless and greatly minimized my chance of data loss.
  14. So it turns out that the timings were incorrect, so I adjusted them. I still had errors, but was able to isolate them to one stick of ram. Anyways, I got new ram and am currently on the 4th pass of memtest and all is well so far. I'll let it run for a few more hours before booting unraid. I assume that I should run a parity check when I load up unraid, and see about which disk needs the fsck. Is there anything else I should be aware of? Thanks
  15. I had originally run 1 pass of the memtest before starting up unraid, which passed. I ran it again this morning and it was immediately full of errors. I guess that really goes to show the importance of running it overnight in the first place. Unfortunately I don't have time to make any changes right now, but when I get home from work tonight I've got some time to spend with it.