darkside40

Since upgrading to unRaid 6.4.1 the S3 Sleep script, which i also upgraded does not work correctly anymore. The problem seems to be that the newer Version of the Script also checks the hdparm output on the disks, but unRaid is not always able to put disks correctly into standby or that hdparm is not able to recognize it correctly. So spin down disks are sometime shown as active/idle and the Script does not sleep the Server. I think we already had such au problem last year, resulting in reverting back to a previous Version of the script. Would it be possible to make the hdparm check optional?

Morning, i tried to hunt down an issue where one of my disk does not get spin down correctly by unraid. When i tried to see if any files are opened on the disk with the command lsof | grep /mnt/disk5 i only get this failure: lsof: no pwd entry for UID 122 Does anybody know what that means? I know that command worked without any problems on 6.3.5, now i am on 6.4.1 of unRaid.

For quite a while now i have a problem with my unRaid System and its sleep procedure. Sometimes the system goes to sleep and after a second it simply and i dont know why, because it seems to happen randomly. I have already checked /proc/acpi/wakeup and disabled everything but the Powerbutton and the NIC (because i need this for WOL). root@HTMS:~# cat /proc/acpi/wakeup Device S-state Status Sysfs node PS2K S3 *disabled PS2M S3 *disabled RP01 S4 *disabled pci:0000:00:1c.0 PXSX S4 *disabled RP02 S4 *disabled PXSX S4 *disabled RP03 S4 *disabled pci:0000:00:1c.2 PXSX S4 *enabled pci:0000:03:00.0 RP04 S4 *disabled pci:0000:00:1c.3 PXSX S4 *disabled pci:0000:04:00.0 RP05 S4 *disabled PXSX S4 *disabled RP06 S4 *disabled PXSX S4 *disabled RP07 S4 *disabled PXSX S4 *disabled RP08 S4 *disabled PXSX S4 *disabled GLAN S4 *disabled EHC1 S4 *disabled pci:0000:00:1d.0 EHC2 S4 *disabled pci:0000:00:1a.0 XHC S4 *disabled pci:0000:00:14.0 HDEF S4 *disabled pci:0000:00:1b.0 PEG0 S4 *disabled pci:0000:00:01.0 PEGP S4 *disabled pci:0000:01:00.0 PEG1 S4 *disabled PEG2 S4 *disabled PWRB S3 *enabled platform:PNP0C0C:00 But it still happens. Does anybody had such problems and could help me track them down?

Seaching on ebay.de i have directly found one seller which is located in Germany. http://www.ebay.de/itm/IBM-ServeRaid-M1015-SATA-SAS-HBA-Controller-RAID-6Gbps-PCIe-x8-wie-9220-8i-/131847466320?_trksid=p2385738.m2548.l4275

The ffmpeg Version in this docker does not support VAAPI Transcoding. So no Hardware Transcoding. I think that is an issue which has been working on. If you want you could try a docker by linuxserver.io which should support Transcoding. Dont know how stable that work: https://hub.docker.com/r/linuxserver/emby/

+1 for the VAAPI support. Any more info what is the specific problem with that? When i recall it right, the Plex Docker can already do hardware transcoding. Correct me if i am wrong.

Same here. Tried it a couple of minutes ago, but no change. The broken version still shows as up-to-date. Is there any cache that needs to be deleted?

Hi bonienl, would it be possible to revert back to the last version of the script, until the problem with the new version is solved?

No its one of my Array disk, btw now it is SDB. I also tried the Custom commands method which you described, unfortunately that locked up the WebGui. Is there any way to revert back?

Got the same problem like b0mb. Yesterday i have updated to the latest S3 Sleep Version. From that point on my unRaid does not go to sleep anymore. Started the S3 Sleep debug it shows that there is ongoing activity on SDD. In the main it shown spun down but with temps displayed. I have also tried executing /usr/local/sbin/mdcmd spindown but the problem remains. Anyway to revert back to the last version of S3 sleep?

Really thanks for that great tutorial. I am just about to convert all my disks from ReiserFS to XFS. Unfortunately it takes about 24hrs to copy over 4TB of data from one drive to another. Write speeds never really rocked on unRaid

Maybe somebody has the same problem. Since some days i cant sync my folder because Syncthing is complaining: "home disk has insufficient free space". But this cannot be. The folder resides on my cachedrive with 600GB of free space.

Deleted the docker.img was the fastest solution.

Facing the same problem here. Just upgraded from 6.1.9 to 6.2.4. Docker always stays at Stopped. My Docker Image is just 10GB. Here is what syslog says: Dec 21 15:05:01 HTMS emhttp: shcmd (1837): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/cache/docker.img' /var/lib/docker 10 |& logger Dec 21 15:05:01 HTMS kernel: BTRFS info (device loop0): disk space caching is enabled Dec 21 15:05:01 HTMS kernel: BTRFS: has skinny extents Dec 21 15:05:01 HTMS root: Resize '/var/lib/docker' of 'max' Dec 21 15:05:01 HTMS kernel: BTRFS info (device loop0): new size for /dev/loop0 is 10737418240 Dec 21 15:05:01 HTMS emhttp: shcmd (1839): /etc/rc.d/rc.docker start |& logger Dec 21 15:05:01 HTMS root: starting docker ... Dec 21 15:05:02 HTMS emhttp: shcmd (1841): umount /var/lib/docker |& logger How can i get my Dockers back?

Hopefully not so long. I am still running OE 5.0.8 on my two NUC's.

If i recall it right Sparklyballs already has a IPv6 Version of the unRaid Kernel compiled by itself. Thin i read about it in the Daapd Container discussion. Maybe he could tell if he encountered any problems so far etc.

Does nobody have an idea?

Hi there, i have a problem with the automatic disk spin down in unRaid. Sometimes one of my disks which is attached to my Adaptec 1430SA Raid adapter does not get spun down correctly. I can see this when i take a look at the web interface. The disk is shown as spun down but the temperature is reported. When i look at the output of hdparm -C of the disk it is shown as active/idle not as standby. Strange thing is that if i "spin up" the disk from the Web Interface and then use the Web Interface to spin it down it always works. The disk is than reported as "standby" by hdparm. How can this be. Does the Webif and the automatic spindown use different commands to spin down the disks or where to search for the failure. I just switch from an Asmedia 2 Port controller card to the 1430SA, both showed the same behaviour. The problem for me is that with this failure the S3 Sleep command does not work correctly. Any help would really be appricated.

Do yourself a favour and use the Community Applications Plugins: http://lime-technology.com/forum/index.php?topic=40262.0 Makes unRaid Docker Life a breeze, instead of messing around with template repos.

You find the forked-daapd.conf inside the config folder. If it is empty the path in the docker config might be wrong or it is a permission problem. For example when you created the folder via terminal as user root and user nobody which runs the docker cant wright to that folder. Also the UID and GID looks messed up in the log. You should start from scratch and add the Container using Community Applications Plugin.

Do i need Windows etc. for the FW Update if needen? I have just seen some Exe File on the Website.

It is especially annoying for people like me if unRaid has no IPv6 connectivity. My ISP is running DSLite, i have no real IPv4 Adress anymore but only a Carrier Grade NAT. What i have on the other hand is a real IPv6 Adress. Life could be really easy for me but because unRaid has no IPv6 i need to run another 6Tunnel at home to translate from IPv6 to IPv4 for my unRaid if i connnect from outside. I would really appreciate and IPv6 branch, or a config setting or whatever to get IPv6 running on unRaid. I understand the fear of the Limetech team, but IPv6 is coming definately.

Okay got myself a Adaptec 1430SA which should arrive in a couple of days. Is this card plug and play, which i have read in the first post here or do i have to disable the card bios etc. like it ist described in the Wiki?

Okay found the reason, i had to set the User Interface Level to Advanced, the menu wont come up when you choose Basic or Advance.

Hi saarg, i just installed the TVHeadend unstable docker and found out that the CA's Tab is missing (which was there in the 4.0.5 Version i had) where i could configure the connection to my Oscam Server. Any idea why that is the case?