gerard6110

Approx. since 6-9 months (after one of the unRAID OS stable upgrades), one of my Linux based VM's on my unRAID basic system is not booting anymore - meaning it boots, but does not complete and thus rendering it useless. Other Linux and windows based VMs all running fine. I've tried all kinds of things except for starting from scratch (as I don't want to loose data, VMs, dockers). Starting VM from safe mode (no plugins): to no avail Creating a new one with the exact same settings (as before): to no avail Creating a new one with the exact same settings (as before) in safe mode: to no avail Creating a new one with the exact same settings on my other unraid pro system: no problem at all; even copying the basic vdisk1.img virtual disk to the pro server and using that - again no problem at all. What I feel is very strange is that the VM-xml files on basic and pro are quite different; despite the same starting settings?! Point is that I want to run the VM on my basic system, as it is setup to use as little as possible energy (for 24/7), whereas the other media-server is too power hungry (and thus only running when required). I'm almost certain any of the files is corrupt. But which? bzimage and bzroot have already been replaced - to no avail therefore. It would be very very nice to get this one running again ...

First of all thanks for the new version. The setup wizard and the help information are a major improvement compared to tobbens tvheadend docker I was using with KODI to my full satisfaction. However, as we are advised to switch to this version (same as for oscam), this week I tried it. After the wizard my channels were not numbered however. Is this correct behavious or did this have to do that during the wizard is not asking for a card reader and which was therefore not yet configured correctly for communication with tvheadend? At least it would be nice that the card reader option (CA) is also incorporated into the wizard. Oscam is working fine, although while selecting the exact same config path as I had with tobbens docker I had to manually copy the config information into the new config files, as the path was changed. Another folder 'oscam' was created inside the config folder. Why? Then with oscam running succesfully (after the initial hickup), I tried switching to LS TVheadend. I backed up my tvheadend folder, installed the new docker pointing to the same folders and was up and running in no time. So far so good. However, and I have not read through all the pages here before, because I would imagine it would have been solved long time ago if it was picked up, I am throwing in my issue here just like that. There is a communication error between kodi and this new tv headend concerning instant recording. Instant recording and stopping directly from within tvheadend is fine. However not from within KODI. Starting instanct recording is fine. Instant stopping indeed stops the recording, however: - the indicator remains on recording - there's no on screen message that the recoding is stopped - in tvheadend appears a red exclamation mark like a failed recording, which is not correct as it stopping was a purposely manual action and thus it should present in tvheadend the green ok indicator if a correct finished recording. - trying to instant record that show again results in a 'PVR backend error. Check the log for more information about this message. OK'; which log? The new version also failed to record autocreated shows. This morning I installed the LS tvheadend again completely from scratch with empty config folder, during which I noticed the wizard - very very good, except for above comments - but still the same issue. Not sure if recording autocreated shows would fail too, but with this - I would say basic - instant recording issue there's no reason for me to check other things. Hope this can be solved quickly; until then I will stick with my proven tobben docker.

Hi, this is also happening now with a XPEnology VM on my Elite Server. It was working fine until 6.2.3. But after going to 6.2.4 the VM does not start anymore. Windows 10 VM, Windows 7 VM and Ubuntu VM all starting fine.

OK, moved Users menu to the Settings menu. All buttons now staying on the header. However, spacing between header menus differs from menu to menu: Wide: Dashboard, Shares, Settings, Plugins, Docker, Apps, Stats and Tools Narrow: Main, VMs

Dynamix WebGui On certain tabs the status bar at the bottom is not desiplayed correctly, where it is dropped out of view. This has been the case at least as of 6.1.9. This happens on the Tabs: Main and VMs. In itself not so important, except when stopping the array, it is impossible to follow what is going on, as part of the logging messages are invisible. Would be nice if this could be fixed.

System Buttons On my Elite TV Server its display behaviour is fine, however on my Stacker Media Server its behavious is odd, meaning that the buttons are located below the main menu bar, with a white background on certain Tab(-Subtabs). Both using Windows explorer and both with Tabbed Views. This happens on the Tab(-Subtab): Dashboard, Shares-User Shares, Settings, Plugins-Installed Plugins, Apps-Installed Apps, Stats-Disk Stats and Tools. It not a real problem; just annoying (to the nice layouts).

s3_sleep Thanks to Dynamix for (updating) the plugin - with the 2016.09.24 update at least the powerdown script is being executed, so shutdown works again. However, even before this update (but since moving to Unraid 6.2 stable) it was / is not detecting the HDD's spinning. Even immediately after spinning up all drives, it says the all monitored drives are spun down. The system checks all drives, except for the cache SSD's. As you know the minimum time before spinning down is 15 minutes. So after spinning up it should at least take 15 minutes for them to spin down. Log: Sep 25 12:13:34 Stacker s3_sleep: ---------------------------------------------- Sep 25 12:13:34 Stacker s3_sleep: killing s3_sleep process 18257 Sep 25 12:13:34 Stacker s3_sleep: ---------------------------------------------- Sep 25 12:13:34 Stacker s3_sleep: command-args=-C 2 -a -c -m 15 -e eth0 -N 0 -D 2 Sep 25 12:13:34 Stacker s3_sleep: action mode=shutdown Sep 25 12:13:34 Stacker s3_sleep: check disks status=yes Sep 25 12:13:34 Stacker s3_sleep: check network activity=no Sep 25 12:13:34 Stacker s3_sleep: check active devices=no Sep 25 12:13:34 Stacker s3_sleep: check local login=no Sep 25 12:13:34 Stacker s3_sleep: check remote login=no Sep 25 12:13:34 Stacker s3_sleep: version=3.0.4 Sep 25 12:13:34 Stacker s3_sleep: ---------------------------------------------- Sep 25 12:13:34 Stacker s3_sleep: included disks=sdb sde sdf sdg sdh sdi sdj sdk sdl sdm Sep 25 12:13:34 Stacker s3_sleep: excluded disks=sda sdc sdd Sep 25 12:13:34 Stacker s3_sleep: ---------------------------------------------- Sep 25 12:13:34 Stacker s3_sleep: s3_sleep process ID 18509 started, To terminate it, type: s3_sleep -q Sep 25 12:13:34 Stacker s3_sleep: All monitored HDDs are spun down Sep 25 12:13:34 Stacker s3_sleep: Extra delay period running: 15 minute(s) Sep 25 12:13:46 Stacker emhttp: Spinning up all drives... Sep 25 12:13:46 Stacker emhttp: shcmd (370): /usr/sbin/hdparm -S0 /dev/sdc &> /dev/null Sep 25 12:13:46 Stacker kernel: mdcmd (56): spinup 0 Sep 25 12:13:46 Stacker kernel: mdcmd (57): spinup 1 Sep 25 12:13:46 Stacker kernel: mdcmd (58): spinup 2 Sep 25 12:13:46 Stacker kernel: mdcmd (59): spinup 3 Sep 25 12:13:46 Stacker kernel: mdcmd (60): spinup 4 Sep 25 12:13:46 Stacker kernel: mdcmd (61): spinup 5 Sep 25 12:13:46 Stacker kernel: mdcmd (62): spinup 6 Sep 25 12:13:46 Stacker kernel: mdcmd (63): spinup 7 Sep 25 12:13:46 Stacker kernel: mdcmd (64): spinup 8 Sep 25 12:13:46 Stacker kernel: mdcmd (65): spinup 9 Sep 25 12:13:46 Stacker emhttp: shcmd (371): /usr/sbin/hdparm -S0 /dev/sdd &> /dev/null Sep 25 12:14:34 Stacker s3_sleep: All monitored HDDs are spun down Sep 25 12:14:34 Stacker s3_sleep: Extra delay period running: 14 minute(s) Sep 25 12:15:35 Stacker s3_sleep: All monitored HDDs are spun down Sep 25 12:15:35 Stacker s3_sleep: Extra delay period running: 13 minute(s) Sep 25 12:16:35 Stacker s3_sleep: All monitored HDDs are spun down Sep 25 12:16:35 Stacker s3_sleep: Extra delay period running: 12 minute(s) Sep 25 12:17:35 Stacker s3_sleep: All monitored HDDs are spun down Sep 25 12:17:35 Stacker s3_sleep: Extra delay period running: 11 minute(s) Sep 25 12:18:35 Stacker s3_sleep: All monitored HDDs are spun down Sep 25 12:18:35 Stacker s3_sleep: Extra delay period running: 10 minute(s) Would you please have a look. Thanks.

Yessss! Thanks a lot myce.

s3_sleep Since the upgrade to 6.2 stable (few days ago) my media server is not shutting down anymore automatically. Manually shutting down and WOL'ing is fine. The log says, something like: ... All drives spundown. Shutting down system. System woken up. Resetting timers ... Repeat ... It seems to me the shutdown or powerdown script is not found / executed. Please help, as the server is normally off, except when consuming content from it: movies, series, music.

Hi in my case after upgrading to 6.2 it is not shutting down anymore. It seems the powerdown scripts is not found by s3_sleep.

No it has nothing to do with the CPU. The behaviour of not waking from sleep was already with 6.1.9, because of the SAS controller card not detected and thus the array not started. But I had no problem with it, because I just had s3_sleep have it shutdown, after which I could WOL it. But now - since the upgrade to 6.2 - it is not shutting down anymore automatically. Manually shutting down and WOL'ing is working fine. In my opinion the shutdown script or powerdown script is not called or found from s3_sleep.

Hi, As everything was working well with 6.1.9 I waited until the next stable Unraid version to upgrade to. Apart from some hickups, everything is running fine again, except S3_Sleep. It appears as if the shutdown script is not executed, because it says "Shutdown system now" and then nothing happens. See part of the log: Sep 22 21:22:26 Stacker s3_sleep: All monitored HDDs are spun down Sep 22 21:22:26 Stacker s3_sleep: Extra delay period running: 1 minute(s) Sep 22 21:23:26 Stacker s3_sleep: All monitored HDDs are spun down Sep 22 21:23:26 Stacker s3_sleep: Extra delay period running: 0 minute(s) Sep 22 21:23:26 Stacker s3_sleep: Check TCP/SSH/TTY/IP activity Sep 22 21:23:26 Stacker s3_sleep: Communication state is idle Sep 22 21:23:26 Stacker s3_sleep: Shutdown system now Sep 22 21:23:26 Stacker s3_sleep: System woken-up. Reset timers Sep 22 21:24:26 Stacker s3_sleep: All monitored HDDs are spun down Sep 22 21:24:26 Stacker s3_sleep: Extra delay period running: 1 minute(s) Sep 22 21:25:26 Stacker s3_sleep: All monitored HDDs are spun down Sep 22 21:25:26 Stacker s3_sleep: Extra delay period running: 0 minute(s) Sep 22 21:25:26 Stacker s3_sleep: Check TCP/SSH/TTY/IP activity Sep 22 21:25:26 Stacker s3_sleep: Communication state is idle Sep 22 21:25:26 Stacker s3_sleep: Shutdown system now Sep 22 21:25:26 Stacker s3_sleep: System woken-up. Reset timers Sep 22 21:26:26 Stacker s3_sleep: All monitored HDDs are spun down Sep 22 21:26:26 Stacker s3_sleep: Extra delay period running: 1 minute(s) Sep 22 21:27:27 Stacker s3_sleep: All monitored HDDs are spun down Sep 22 21:27:27 Stacker s3_sleep: Extra delay period running: 0 minute(s) Sep 22 21:27:27 Stacker s3_sleep: Check TCP/SSH/TTY/IP activity Sep 22 21:27:27 Stacker s3_sleep: Communication state is idle Sep 22 21:27:27 Stacker s3_sleep: Shutdown system now Sep 22 21:27:27 Stacker s3_sleep: System woken-up. Reset timers Please help to resolve, because this is really just a media server, only woken up to watch something after which it should shutdown automatically. Note: pushing the sleep button, the system indeed goes to sleep (but due to some incompatibilities it will not wake up from sleep). Fortunately, shutdown did the job perfectly.

I'm not seeing this issue. Try clearing the browser cache and possibly a different browser to see if it continues. Indeed not seeing this issue with Google Chrome, but I prefer to keep on using IE 11+ for everything (old habits). BTW all tabs under Main have this issue; both in windowed mode as in full screen mode.

Hi, Maybe it's just my setup, but after installing this plugin, the main / array operation tab is somewhat corrupted at the bottom. The bottom line is a little bit of the page and when stopping / restarting the array, the progress tekst is not displayed fully. I know it's just esthetics, but just a little bit annoying and probably a very simple things to fix. Thanks.

OK, good to know. However, apparently I was too quick: Now I cannot connect TV Headend (using CA word) to the reader, which was the whole purpose of the exercise. Nothing changed to oscam.conf and oscam.user, still connection refused. What IP to use for oscam: tried 0.0.0.0, 127.0.0.1, localhost and the IP of the box itself. Port and key as defined in oscam.conf User and pwd as defined in oscam.user No go.

OK, working now, but still not with smartreader protocol and also not with mouse protocol, but with smargo protocol and device /dev/ttyUSB0; so I would say: partly solved. Hope you can make the container suitable for smartreader protocol too (I would gladly try it out), because as I understood when (other) usbdevices get connected in different order it may not work anymore, which should not be the case with smartreader protocol. Correct me if I'm wrong. Thanks for helping (so far).

I hope so. At least nothing is listed under oscam readers and log errors still the same. Reader config (from oscam.server file - working under Ubuntu) [reader] label = SRv2 description = Argolis SmartReader2 plus protocol = smartreader device = SRV2;Serial:A......4 caid = 0604 boxkey = 1122334455667788 rsakey = 3C8.........76A detect = cd mhz = 600 cardmhz = 600 ident = 0604:000000 group = 1 emmcache = 1,3,2,0 blockemm-unknown = 1 blockemm-g = 1 dropbadcws = 1

So after switching from ubuntu to unraid: # dmesg | tail tun: © 1999-2004 Max Krasnyansky <[email protected]> kvm: Nested Virtualization enabled kvm: Nested Paging enabled Ebtables v2.0 registered device virbr0-nic entered promiscuous mode virbr0: port 1(virbr0-nic) entered listening state virbr0: port 1(virbr0-nic) entered listening state virbr0: port 1(virbr0-nic) entered disabled state docker0: port 1(veth35e41c4) entered forwarding state docker0: port 2(veth02d5f3b) entered forwarding state # ls -la /dev/ttyUSB* crw-rw---- 1 root dialout 188, 0 Nov 5 22:06 /dev/ttyUSB0 After removing and re-inserting the card reader: # dmesg | tail virbr0: port 1(virbr0-nic) entered disabled state docker0: port 1(veth35e41c4) entered forwarding state docker0: port 2(veth02d5f3b) entered forwarding state usb 1-2: USB disconnect, device number 3 ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 ftdi_sio 1-2:1.0: device disconnected usb 1-2: new full-speed USB device number 4 using xhci_hcd ftdi_sio 1-2:1.0: FTDI USB Serial Device converter detected usb 1-2: Detected FT232BM usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0 # ls -la /dev/ttyUSB* crw-rw---- 1 root dialout 188, 0 Nov 5 22:07 /dev/ttyUSB0 Re-starting OSCAM, still Libusb init error : -99 Cannot open device: While parameter --device=/dev/ttyUSB0:/dev/ttyUSB0 is part of the Docker.

OK, herewith dmesg | tail again (immediately after disconnecting and connecting): # dmesg | tail virbr0: port 1(virbr0-nic) entered disabled state docker0: port 1(veth1f5b4f4) entered forwarding state docker0: port 2(vethe6157dc) entered forwarding state usb 1-2: USB disconnect, device number 3 ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 ftdi_sio 1-2:1.0: device disconnected usb 1-2: new full-speed USB device number 4 using xhci_hcd ftdi_sio 1-2:1.0: FTDI USB Serial Device converter detected usb 1-2: Detected FT232BM usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0 Hoping making sense now ...

@saarg: thanks for helping; no problem trying things (basically Ubuntu and unRaid are running on the same box; just during boot to decide which one I want to use). # dmesg|tail (before disconnecting or removing things) tun: © 1999-2004 Max Krasnyansky <[email protected]> kvm: Nested Virtualization enabled kvm: Nested Paging enabled Ebtables v2.0 registered device virbr0-nic entered promiscuous mode virbr0: port 1(virbr0-nic) entered listening state virbr0: port 1(virbr0-nic) entered listening state virbr0: port 1(virbr0-nic) entered disabled state docker0: port 1(veth2f67798) entered forwarding state docker0: port 2(vethdb62bbf) entered forwarding state # dmesg|tail (2x, after disconnecting or removing things) device virbr0-nic entered promiscuous mode virbr0: port 1(virbr0-nic) entered listening state virbr0: port 1(virbr0-nic) entered listening state virbr0: port 1(virbr0-nic) entered disabled state docker0: port 1(veth2f67798) entered forwarding state docker0: port 2(vethdb62bbf) entered forwarding state usb 6-3: USB disconnect, device number 2 usb 1-2: USB disconnect, device number 3 ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 ftdi_sio 1-2:1.0: device disconnected Notes: Line usb 6-3 came up after disconnecting my Bleckberry Lines usb 1-2 to ftdi_sio 1-2 came up after removing the card reader I have OSCAM, SABnzbd and TVHeadend4-stable running as containers. KVM enabled, but no guest OS running. # dmesg|tail (after connecting blackberry, inserting cardreader and rebooting) tun: © 1999-2004 Max Krasnyansky <[email protected]> kvm: Nested Virtualization enabled kvm: Nested Paging enabled Ebtables v2.0 registered device virbr0-nic entered promiscuous mode virbr0: port 1(virbr0-nic) entered listening state virbr0: port 1(virbr0-nic) entered listening state virbr0: port 1(virbr0-nic) entered disabled state docker0: port 1(vethc2cf933) entered forwarding state docker0: port 2(veth70b087e) entered forwarding state

# lsmod | grep serial usbserial 19129 1 ftdi_sio When changing the comport (using Ubuntu), I suppose I must also change the protocol(s). Which one? smartreader protocol for the reader (in oscam.server file), newcamd protocol (in oscam.conf file) or both and thus which (minimal) settings changes? Sorry for the questions, but although I have OSCAM running under Ubuntu I'm actually a complete noob of what is happening in there (still to study, but on the other hand, it is running ... and where does one stop to understand). Knowing how much effort it took to get it up and running the first time (and thus the reason for my own little tutorials with all relevant steps and settings!) I would like to know all upfront before making the switch.

OK, tried a couple of things: - modprobe - install libusb in unraid (host) (if that was correct; don't know how to do in container) => same error. With oscam container it is impossible to check readers, because lsusb not installed. I would prefer to keep using the smartreader protocol, because of automatic card updates (I understood this is not the case with mouse protocol). FYI on the Smartreader2Tool (after installation - ubuntu instructions available). Check smartreader settings: cd smartreader ./smartreader2tool Output: ? smartreader2+ version v1.1; settings for *** Smartcard ? MODE fixed ? FREQ 6,00 Mhz ? T_MODE t = 1 ? EGT 0 ? NAME ABCDEFGH To change the device name / serial (exactly 8 characters): ./smartreader2tool -n ABCDEFGH To change other settings: ./smartreader2tool -help Output: ? Smartreader2+ settings tool v1.0 ? Usage: ./smartreader2tool -… -… -… ? -d <comport> (default comport = "/dev/ttyUSB0") ? -m <0 = autoswitch / 1 = fixed Mhz> mode ? -n <name> (max 8 characters) ? -N remove custom device name ? In fixed mode you can also apply: ? -x <frequency in khz> ? -t <val> t = val ? -e <val> egt = val

Argolis Smargo Smartreader V2 plus (USB smartcard reader) with smartreader protocol for the reader (in oscam.server) and newcamd protocol (in oscam.conf). http://www.argolis.com/ Under Ubuntu one has to: - Prepare it for oscam and the respective smartcard (but that's a one-time step only; so already done) Note: in there, there's a step to make the smartreader (temporary) visible through ttyUSB0 via: modprobe usbserial vendor=0x0403 product=0x6001 (should I put this in the unraid go-script?) - Compile and install libusb when using USB Readers (yes/no already in unraid?) - Actually install oscam (checkout oscam from trunk, prepare the build, compile, install oscam, make executable and run at boot), but I take it this is all done in the container.

# ls -la /dev/ttyUSB* Output: /bin/ls: cannot access /dev/ttyUSB*: No such file or directory

Hi, I have OSCAM and TVHeadend working in Ubuntu Server 14.04 ie. the hardware is fine, but I want to switch to UNRAID (primarily because of HDDs-usage). So, running unraid 6.1.3 (trial) and Container OSCAM-test, but getting error Reader Device Error. The live log says: (reader) SRv2 [smartreader] Libusb init error : -99 (reader) SRv2 [smartreader] Cannot open device: "ID;Serial:**" Added the extra parameters: --device=/dev/ttyUSB0:/dev/ttyUSB0, but then the container does not start; error: Error response from daemon: Cannot start container 71...d3: error gathering device information while adding custom device "/dev/ttyUSB0": lstat /dev/ttyUSB0: no such file or directory. Adding the extra parameters: --device=/dev/ttyUSB1:/dev/ttyUSB1 or --device=/dev/ttyUSB2:/dev/ttyUSB2 did not help either. # lsusb (on unraid host): Bus 006 Device 002: ID 0fca:8004 Research In Motion, Ltd. Blackberry Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler G4 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Please help. Thanks.