Mettbrot

hi mettbrot, please see the OP FAQ section, this should answer your questions, the last update to sickrage was only a day or so ago, so a quick force update should get you to the latest release Hey thanks for the reply. I regularly check the docker page with the update button and install them as they appear. After the latest docker update (and another one using "force update") sickrage still tells me I am on a version from Nov 2014 and 1871 commits behind. thank you for your help.

Hey binhex, is there a way to update sickrage from right within the app? When I check for updates and then "update now" nothing happens. Is a docker update necessary for this? I just recently switched sabnzbd and sickrage over to docker and I am absolutely loving it. Thanks for this

Haha, you got me right there! Also: wtf happened here, left for 1 day and a gazillion new posts?! Cant help but notice the correlation with the first "today" announcement post..

Make sure your server is connected to the ethernet and your computer, too. After booting up, the web interface of the server should be available if you just type http://tower in the adressbar of your web browser (on your computer). You can additionally check your router if it is set to give IP adresses automatically (DHCP) or alternatively set your own ip configuration on the flashdrive in /config/network.cfg like this: # Generated settings: USE_DHCP="no" IPADDR="192.168.178.39" NETMASK="255.255.255.0" GATEWAY="192.168.178.1" DHCP_KEEPRESOLV="no" DNS_SERVER1="192.168.178.1" I hope this helps.. You are not giving much info on what you tried so this is about it edit: If you have a screen and keyboard connected to the server you can log into the commandline by typing 'root' after it booted and see the ip of the device by typing 'ifconfig'.

I would start with version 6. It has been very stable and I suppose it is near its release (we never know though ^^) When you choose ReiserFS for you data drives file system I suppose you can move back and forth between version 6 and 5 BUT: -You will loose your addon configuration if you do so -You will miss out on all the nice features of version 6 such as virtualization/Docker which is great for plugins -and newer filesystems. If I were you I would go with version 6 and setup my data drives using XFS Install a docker for your Plex and you are good to go

can you simply advise teamspeak to create (and use) the db inside the config directory. If something happens this resides on the cache share and is safe.

hi mettbrot, i will have to take another look at this, as you can see from the OP, teamspeak is one of my docker images thats "working but isnt as tidy as i want", one of the issues to resolve is relocating the database to the config share, as the db is the main location for all the settings for teamspeak, or at least it contains some of the settings, and thus when you did the upgrade it reset your db, leave it with me and i will see what i can come up with. no worries. I know this was a problem with the regular plugin, too. It got fixed with a version which copied the database on array stop: <!-- event handler --> <FILE Name="/usr/local/emhttp/plugins/ts3server/event/unmounting_disks" Mode="0770"> <INLINE> <![CDATA[ #!/bin/bash source /boot/config/plugins/ts3server/ts3server.cfg /etc/rc.d/rc.ts3server stop cp -u $INSTALLDIR/teamspeak3-server_linux-x86/ts3server.sqlitedb $DBPATH/ts3server.sqlitedb ]]> </INLINE> </FILE> not that it helps but you get the principle I thought this is what the config directory setting in the docker was all about.

If the device is occupied virsh will spit out an error message, nothing more.

after I updated the teamspeak docker I lost all my server settings I have pointed the /config directory to a directory on the cache disk, i thought this would survive the update. Any way to fix this for the future?

Hey dmacias while I figured out why usb passthrough did not work properly for me I came up with a great addition to VM Manager: Attach devices to running vms (this is what I needed to do to solve my problem). If an usb device gets removed from the host (or even the guest system removes it) it is not recognized by the guest if it is pluged in again. You need to attach it once more doing: Source: http://rolandtapken.de/blog/2011-04/how-auto-hotplug-usb-devices-libvirt-vms-update-1 Maybe you can add a devices tab where one can attach devices to running vms..? I think this would be a great addition.

GREAT SUCCESS! It had nothing to do with the usb controller. It works just fine with the usb2 controller. dmesg | grep dvb [ 8.868551] dvb-usb: found a 'Technisat SkyStar USB HD (DVB-S/S2)' in cold state, will try to load a firmware [ 8.876178] dvb-usb: downloading firmware from file 'dvb-usb-SkyStar_USB_HD_FW_v17_63.HEX.fw' [ 9.133212] usbcore: registered new interface driver dvb_usb_technisat_usb2 [ 9.631803] usb 1-3: dvb_usb_v2: found a 'TerraTec Cinergy T Stick RC' in warm state [ 11.420752] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. [ 11.501970] usbcore: registered new interface driver dvb_usb_af9015 [ 14.882976] usb 1-3: dvb_usb_v2: found a 'TerraTec Cinergy T Stick RC' in warm state [ 15.152678] usb 1-3: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer [ 15.284279] usb 1-3: dvb_usb_v2: schedule remote query interval to 500 msecs [ 15.284282] usb 1-3: dvb_usb_v2: 'TerraTec Cinergy T Stick RC' successfully initialized and connected ______________________________________________________________________________________ [ 520.805251] dvb-usb: found a 'Technisat SkyStar USB HD (DVB-S/S2)' in warm state. [ 520.806203] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 520.810237] dvb-usb: MAC address: 00:08:c9:f0:3b:69 [ 521.196976] dvb-usb: schedule remote query interval to 100 msecs. [ 521.210881] dvb-usb: Technisat SkyStar USB HD (DVB-S/S2) successfully initialized and connected. The problem was this: When the device is loaded it is found in cold state (no firmware) as the dmesg states and loads the firmware. Now the device is disconnected in order to be reconnected and found in warm state. This did not work for my card as the device gets a new device ID from unraid and thus being not recognized by the vm: before vm boot (unraid): Bus 001 Device 002: ID 0ccd:0097 TerraTec Electronic GmbH Cinergy T RC MKII Bus 001 Device 003: ID 14f7:0500 TechniSat Digital GmbH DVB-PC TV Star HD after vm boot (unraid) Bus 001 Device 002: ID 0ccd:0097 TerraTec Electronic GmbH Cinergy T RC MKII Bus 001 Device 004: ID 14f7:0500 TechniSat Digital GmbH DVB-PC TV Star HD note that the first DVB device stays at the same id during vm boot. To reattach the (new) device to the vm i had to create a XML file just with the hostdev definitions and load it in unraid via: virsh attach-device Ubuntu14.10 /boot/config/technisat.xml This is where I added the line in the dmesg above. Now my questions are: [*]Is there a way for unraid to give the same device always the same device ID and not a new one everytime it (re)connects? [*]If not: Do you have any idea how I can automate the process of reattaching the device in unraid if the vm guest system (ubuntu) is booted? Thanks for your support so far, I am very happy now.

Hey! So I installed Ubuntu 14.10 and setup the usb2 controller combination (not the nec controller) before installtion. on the first boot I could read it was trying to find the firmware for the DVBS card which is a great success! It was showing up under lsusb, everzthing great! BUT: then I installed pending system updates and manually downloaded the firmware files for the 2 cards from linuxtv.org and put the under lib/firmware. Next boot, i fire up the terminal and check lsub: lsusb Bus 001 Device 005: ID 0ccd:0097 TerraTec Electronic GmbH Cinergy T RC MKII Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub I feel like its kidding me. dmesg | grep dvb shows dmesg | grep dvb [ 25.412306] usb 1-3: dvb_usb_v2: found a 'TerraTec Cinergy T Stick RC' in cold state [ 26.055630] usb 1-3: dvb_usb_v2: downloading firmware from file 'dvb-usb-af9015.fw' [ 26.196781] usb 1-3: dvb_usb_v2: found a 'TerraTec Cinergy T Stick RC' in warm state [ 26.588495] dvb-usb: found a 'Technisat SkyStar USB HD (DVB-S/S2)' in cold state, will try to load a firmware [ 26.736544] usb 1-3: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer [ 26.778634] dvb-usb: downloading firmware from file 'dvb-usb-SkyStar_USB_HD_FW_v17_63.HEX.fw' [ 27.008125] usbcore: registered new interface driver dvb_usb_technisat_usb2 [ 27.592502] usb 1-3: dvb_usb_v2: schedule remote query interval to 500 msecs [ 27.592507] usb 1-3: dvb_usb_v2: 'TerraTec Cinergy T Stick RC' successfully initialized and connected [ 27.592610] usbcore: registered new interface driver dvb_usb_af9015 [ 28.667443] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. [ 28.675159] usb 1-3: dvb_usb_v2: usb_bulk_msg() failed=-71 [ 28.675511] usb 1-3: dvb_usb_af9015: rc query failed=-71 [ 28.798572] usb 1-3: dvb_usb_v2: 'TerraTec Cinergy T Stick RC' successfully deinitialized and disconnected [ 29.729023] usb 1-3: dvb_usb_v2: found a 'TerraTec Cinergy T Stick RC' in warm state [ 30.230101] usb 1-3: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer [ 30.279388] usb 1-3: dvb_usb_v2: schedule remote query interval to 500 msecs [ 30.279391] usb 1-3: dvb_usb_v2: 'TerraTec Cinergy T Stick RC' successfully initialized and connected so it is showing up but not as dvb device.. (also not under tvheadend) Any ideas?

Thanks for the response. I thought it would work since somewhere it said that it supports all three usb 1/2/3 in one device. I thought one reason for the device not to show up could have been the dual controllers in the usb 1/2 setting before. Maybe later today I can try with the newest Ubuntu version and the usb 1/2 Controllers from the beginning...

Sorry if I wasn't clear enough. I removed <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> and added <controller type='usb' index='0' model='nec-xhci'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> When I then start the VM I have the output from above. I have Ubuntu 14.04 running. The DVB device is usb 2.0 this is all I need I am on unRaid 14.0b if that helps.

I had it removed. Is there a way inside ubuntu to rigger reinstallation of the hardware? (or re-recognation)?

Yea I read about this controller and that it should be able to support both usb 1 and usb 2 without the need of the multifunction dual controler thing (uhci + ehci) Here are the outputs: lspci 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) 00:02.0 VGA compatible controller: VMware SVGA II Adapter 00:03.0 Unclassified device [0002]: Red Hat, Inc Virtio filesystem 00:04.0 Ethernet controller: Red Hat, Inc Virtio network device 00:05.0 SCSI storage controller: Red Hat, Inc Virtio block device 00:06.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon lsusb unable to initialize libusb: -99 which I read is short for "no USB controllers detected"... maybe this will help: dmesg | grep -i hcd [ 1.406538] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.406602] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 1.406628] uhci_hcd: USB Universal Host Controller Interface driver Could the problem be that I installed ubuntu with the other controller in the xml? I think the create VM tab creates a controller without any spec, juts like <controller type='usb' index='0'>

Sweet, thanks in advance

Has someone an idea what else I can try?

Hey everyone, just finished the second preclear cycle on a new drive. Maybe you can take a quick look at the details #2 Feb 28 19:01:25 Server preclear_disk-diff[757]: SMART Attributes Data Structure revision number: 10 Feb 28 19:01:25 Server preclear_disk-diff[757]: Vendor Specific SMART Attributes with Thresholds: Feb 28 19:01:25 Server preclear_disk-diff[757]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Feb 28 19:01:25 Server preclear_disk-diff[757]: 1 Raw_Read_Error_Rate 0x000f 110 099 006 Pre-fail Always - 28073888 Feb 28 19:01:25 Server preclear_disk-diff[757]: 3 Spin_Up_Time 0x0003 097 097 000 Pre-fail Always - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 5 Feb 28 19:01:25 Server preclear_disk-diff[757]: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 7 Seek_Error_Rate 0x000f 060 060 030 Pre-fail Always - 1118246 Feb 28 19:01:25 Server preclear_disk-diff[757]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 43 Feb 28 19:01:25 Server preclear_disk-diff[757]: 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 5 Feb 28 19:01:25 Server preclear_disk-diff[757]: 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 189 High_Fly_Writes 0x003a 098 098 000 Old_age Always - 2 Feb 28 19:01:25 Server preclear_disk-diff[757]: 190 Airflow_Temperature_Cel 0x0022 064 063 045 Old_age Always - 36 (Min/Max 18/37) Feb 28 19:01:25 Server preclear_disk-diff[757]: 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 3 Feb 28 19:01:25 Server preclear_disk-diff[757]: 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 16 Feb 28 19:01:25 Server preclear_disk-diff[757]: 194 Temperature_Celsius 0x0022 036 040 000 Old_age Always - 36 (0 18 0 0 0) Feb 28 19:01:25 Server preclear_disk-diff[757]: 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 42h+40m+12.024s Feb 28 19:01:25 Server preclear_disk-diff[757]: 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 11721066432 Feb 28 19:01:25 Server preclear_disk-diff[757]: 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 24114452099 Feb 28 19:01:25 Server preclear_disk-diff[757]: Feb 28 19:01:25 Server preclear_disk-diff[757]: SMART Error Log Version: 1 Feb 28 19:01:25 Server preclear_disk-diff[757]: No Errors Logged It seems good to me but what do I know Thanks!

I had this exact problem yesturday with beta14. I had to powerdown via a attached keyboard. 1 docker (teamspeak), 4 plugins (sab, sick, sleep, cachedisk), 3,5 GB memory run 7 cycles of memtest

Ah, okay. Good to know. What about updating unrar to a recent version? Could this help with the "unusable rar file" issue?

On another thing: How are the dependencies installed? I cannot use unrar from a telnet session since v2. Is this intentional? I can see it sitting in /boot/packages though...

Hey Phaze! Could you update the unrar package in your dependency for sabnzbd? http://www.linuxfromscratch.org/blfs/view/svn/general/unrar.html Here is an explanation for the latest version. I get more and more "unusable rar files" in sabzbd, thats why Thanks Mettbrot

Any idea for this? Anything else I can try? When I change the usb controllers to: <controller type='usb' index='0' model='nec-xhci'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> i get a unable to onitialize libusb: -99 on lsusb on the Ubuntu guest.

awesome! I'll try it out!