Swixxy

I just did a fresh install with the dev branch and within a couple of minutes everything was installed and it was fired up. Here's what I see in my log: First install detected, cloning repository Using the dev branch Branch dev set up to track remote branch dev from origin. npm-container: updating npm dependencies -- git-rev-sync... Sep 23 14:09:46 cc54b1595e56 syslog-ng[123]: syslog-ng starting up; version='3.5.3' [[[[[ /config/plexrequests-meteor ]]]]] => Started proxy. => Meteor 1.2.0.1: React and Angular support, ECMAScript 2015, new faster build system, and improvements to the Cordova integration for mobile apps. This release is being downloaded in the background. Update your app to Meteor 1.2.0.1 by running 'meteor update'. => Started MongoDB. => Started your app. => App running at: http://localhost:3000/ [34mI20150923-14:10:02.876(-4) (percolate_synced-cron.js:85) [39mSyncedCron: Scheduled "Update CP download status" next run @Wed Sep 23 2015 18:00:00 GMT-0400 (EDT) See in the log where it says "Started your app" under "Started MongoDB". Do you not get that message? Could you perhaps be trying to use a port that is already being used by something else? Yeah i dont seem to get that message. Or the 'app running at'. However i do get the cronjobs all firing off successfully. I've tried reinstalling to a different location - And that works fine, so it seems that somethngs gone wrong with the DB thats stopping it from launching. Any ideas on what i can do? PITA having to set it all up again so trying to avoid that if possible

I've tried all the different branches incase that was causing the issue - Is it the fact meteor seems to have an update? Not sure what to do at this point. The log seems fine. After starting the mongodb, it will take another 10-20 second to start the app (may be longer but that's how long it takes for me). Did you wait long enough? Does it give an error later? Meteor update should not have an effect. I tested it again and it will download the update in the background and then it will keep saying the update is ready to be applied. You can leave it as is and it is harmless. Unfortunately, the update is not compatible with plexrequests at the moment so just leave it as is. In my case (I tried the master branch) it works just fine once the app loads. I also installed from scratch and again it worked fine. I'll try other branches later to see if they cause any issues. Hmm.. I have left it running for days, and it still doesn't work. Afterwards it just says the cron.hourly logs so it all seems to 'think' its running fine. Is there a log file somewhere i could check besides the one found in the docker page of unraid? Looking through the apps files i don't see one

Is there an issue with the plexRequests docker recently? Last few days it doesn't seem to work at all. Tried re-installing it several times. Log seems to do this I've tried all the different branches incase that was causing the issue - Is it the fact meteor seems to have an update? Not sure what to do at this point.

I can't seem to get the files to get onto my cache drive. I've set the folder /MCMA2_Linux_x86_64 to my cache drive, but nothing goes inside it. What can i do to make these persist stopping and starting?

I've had no luck with it and just had to give up using sensors on my motherboard

Hi all, i've been having this problem for a while (Ever since moving cases and adding another controller card to my mobo) Every so often my parity disk will fail to write and get disabled by unraid. Sometimes when i boot up all the drives connected to a card will all error, sometimes it will last for an hour or so, then they slowly start to error. Now i've got it down to a few days, however eventually it seems a drive (Usually parity as obviously its most used) will error. I've attatched the bit of the syslog below. The drive when active has 0 health problems and runs fine. However i keep reseating the card into the port however im running out of ideas as to why the card seems to temporarily lose connection. The cards are an aoc-sas2lp-mv8 and aoc-saslp-mv8. I believe it is the newer sas2 card that keeps giving way, although i have had the other card do the same thing, but this is normally noticeable on bootup, so its apparent instantly when there is an issue. All the hard drives are in a backplane, ive tried moving the drives around and dont think the backplane has anything to do with it, am almost convinced its the card just temporarily 'losing connection' What type of things should i check for? Mar 24 10:21:31 jbox kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Mar 24 10:21:31 jbox kernel: sas: ata7: end_device-1:0: cmd error handler Mar 24 10:21:31 jbox kernel: sas: ata7: end_device-1:0: dev error handler Mar 24 10:21:31 jbox kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 24 10:21:31 jbox kernel: ata7.00: failed command: READ DMA EXT Mar 24 10:21:31 jbox kernel: ata7.00: cmd 25/00:00:b8:0a:d7/00:02:cc:01:00/e0 tag 19 dma 262144 in Mar 24 10:21:31 jbox kernel: res 51/40:00:c8:0a:d7/00:02:cc:01:00/e0 Emask 0x9 (media error) Mar 24 10:21:31 jbox kernel: ata7.00: status: { DRDY ERR } Mar 24 10:21:31 jbox kernel: ata7.00: error: { UNC } Mar 24 10:21:31 jbox kernel: sas: ata8: end_device-1:1: dev error handler Mar 24 10:21:31 jbox kernel: sas: ata9: end_device-1:2: dev error handler Mar 24 10:21:31 jbox kernel: sas: ata10: end_device-1:3: dev error handler Mar 24 10:21:31 jbox kernel: sas: ata11: end_device-1:4: dev error handler Mar 24 10:21:31 jbox kernel: sas: ata12: end_device-1:5: dev error handler Mar 24 10:21:31 jbox kernel: sas: ata13: end_device-1:6: dev error handler Mar 24 10:21:31 jbox kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x1) Mar 24 10:21:31 jbox kernel: ata7.00: revalidation failed (errno=-5) Mar 24 10:21:31 jbox kernel: ata7: hard resetting link Mar 24 10:21:31 jbox kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x1) Mar 24 10:21:31 jbox kernel: ata7.00: revalidation failed (errno=-5) Mar 24 10:21:36 jbox kernel: ata7: hard resetting link Mar 24 10:21:37 jbox kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x1) Mar 24 10:21:37 jbox kernel: ata7.00: revalidation failed (errno=-5) Mar 24 10:21:37 jbox kernel: ata7.00: disabled Mar 24 10:21:37 jbox kernel: sd 1:0:0:0: [sdc] Mar 24 10:21:37 jbox kernel: Result: hostbyte=0x00 driverbyte=0x08 Mar 24 10:21:37 jbox kernel: sd 1:0:0:0: [sdc] Mar 24 10:21:37 jbox kernel: Sense Key : 0x3 [current] [descriptor] Mar 24 10:21:37 jbox kernel: Descriptor sense data with sense descriptors (in hex): Mar 24 10:21:37 jbox kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 01 Mar 24 10:21:37 jbox kernel: cc d7 0a c8 Mar 24 10:21:37 jbox kernel: sd 1:0:0:0: [sdc] Mar 24 10:21:37 jbox kernel: ASC=0x11 ASCQ=0x4 Mar 24 10:21:37 jbox kernel: sd 1:0:0:0: [sdc] CDB: Mar 24 10:21:37 jbox kernel: cdb[0]=0x88: 88 00 00 00 00 01 cc d7 0a b8 00 00 02 00 00 00 Mar 24 10:21:37 jbox kernel: blk_update_request: I/O error, dev sdc, sector 7731612360 Mar 24 10:21:37 jbox kernel: ata7: EH complete Mar 24 10:21:37 jbox kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Mar 24 10:21:37 jbox kernel: md: disk0 read error, sector=7731612296 Mar 24 10:21:37 jbox kernel: md: disk0 read error, sector=7731612304 Mar 24 10:21:37 jbox kernel: md: disk0 read error, sector=7731612312 Mar 24 10:21:37 jbox kernel: md: disk0 read error, sector=7731612320 log.zip

So the fan script for me detects 4 PWM controllers, and i have 5 PWM fan ports. CPU Fan on Fan1, backplane on ports 2~4. However no matter what i do with the PWM controller, or with the PWM fan setting (No matter which pwm controller is selected ,it always detects /sys/devices/platform/w83627ehf.2576/fan1_input) it just sets all of the fans to slow down (Inluding my CPU fan!). What am i doing wrong?

Working for me on v6b14, thank you very much.

This link sadly goes to a 404 not found when you try to download the file. Can you throw it up on github if possible

I also need this. Could someone perhaps host it on a google drive somewhere or any other free upload service.

So i decided to totally rewire my case. I have a non modular PSU so there are quite a few redundant cables hanging around near the PSU. I noticed one of the cables had snuck under a corner of the motherboard. So i rewired and cable tied all my cables and tidied it all up so there is zero chance of any cables falling onto anything. I then resat the mobo into the mount holes to ensure it was fully installed. Since i did all of this my IPMI interface now shows the fan speeds as correct !!! And also i haven't had any beeping as of yet. (Every other thing i tried the beeping returned within a few hours - been about 8 hours so far with no errors) Now i seem to have a problem of none of my sensors being loaded into unraid (sensors command shows No sensors found!), but i uninstalled two plugins (Dynamix fan control and system temp so i suspect this is why as the sensors probably arent loaded) however i can deal with that. So as of now my full 'fix' was 1) all 4Pin fans 2) all Fans connected directly to mobo (3 fans are daisy chained - working fine) 3) IPMI upgrade to latest firmware & reset 4) Rewire all power/data cables so non are anywhere near the mobo except where they directly connect (And then only the head is near. They all go straight down) 5) Turned off IPMI power entirely whilst rewiring to let IPMI sensors reset UPDATE Okay, so i was loading up my sensors and now as soon as i loaded the sensors in for the fans, within a few minutes suddenly i have a failed Fan 5 and now my IPMI sensor is showing the RPM as 6k for my fans (completely wrong!) I suspect that its actually unraid messing with the sensors now - So stopping unraid from loading them should stop it from working (So no System Temp/ Fan auto control plugins for dynamix, or any other sensor using plugin) It ran perfectly well, and kept the sensor data in IPMI correct for the whole time until the sensors were loaded using modprobe w83627ehf So now i suspect that it is actually this causing the issue, and the only reason it was 'fixed' was by me removing the plugins and restarting unraid (Meaning the sensors were unloaded, and then not reloaded on startup like normal)

I did a full IPMI reset. Still no change. I've also changed out the fans to all PWM fans now - still problems. Incidentally i'm having problems with the reported speeds of my fans too. a 'sensors' command returns root@jbox:/# sensors coretemp-isa-0000 Adapter: ISA adapter CPU Temp: +36.0 C (high = +89.0 C, crit = +105.0 C) Core 2: +35.0 C (high = +89.0 C, crit = +105.0 C) jc42-i2c-0-19 Adapter: SMBus I801 adapter at 0400 temp1: +28.0 C (low = +0.0 C) ALARM (HIGH, CRIT) (high = +0.0 C, hyst = +0.0 C) (crit = +0.0 C, hyst = +0.0 C) jc42-i2c-0-1a Adapter: SMBus I801 adapter at 0400 temp1: +27.0 C (low = +0.0 C) ALARM (HIGH, CRIT) (high = +0.0 C, hyst = +0.0 C) (crit = +0.0 C, hyst = +0.0 C) jc42-i2c-0-1b Adapter: SMBus I801 adapter at 0400 temp1: +29.4 C (low = +0.0 C) ALARM (HIGH, CRIT) (high = +0.0 C, hyst = +0.0 C) (crit = +0.0 C, hyst = +0.0 C) w83627dhg-isa-0a10 Adapter: ISA adapter Vcore: +1.08 V (min = +0.60 V, max = +1.49 V) in1: +1.82 V (min = +1.62 V, max = +1.99 V) AVCC: +3.28 V (min = +2.96 V, max = +3.63 V) +3.3V: +3.28 V (min = +2.96 V, max = +3.63 V) in4: +1.53 V (min = +0.00 V, max = +1.65 V) in5: +1.26 V (min = +1.13 V, max = +1.38 V) in6: +1.46 V (min = +1.42 V, max = +0.00 V) ALARM 3VSB: +3.28 V (min = +2.96 V, max = +1.25 V) ALARM Vbat: +3.12 V (min = +2.96 V, max = +3.63 V) Array Fan: 694 RPM (min = 712 RPM, div = ALARM fan2: 493 RPM (min = 12053 RPM, div = 16) ALARM fan4: 680 RPM (min = 0 RPM, div = ALARM fan5: 685 RPM (min = 712 RPM, div = ALARM temp1: +30.0 C (high = +60.0 C, hyst = +55.0 C) sensor = thermistor MB Temp: +29.0 C (high = +95.0 C, hyst = +92.0 C) sensor = CPU diode temp3: +28.5 C (high = +86.0 C, hyst = +75.0 C) sensor = CPU diode cpu0_vid: +1.513 V intrusion0: OK My CPU fan & backplane fans are daisy chained into fan1 port. Then my backplane fans are in fan2 fan3 and fan4. These are all 3000RPM fans at max speed, yet all showing totally wrong results in the sensors command (And wrong fan ports). The IPMI interface shows them in the correct ports, although is also showing very low RPMs (all showing 585RPM). Could this be a driver error perhaps? I know i never had this problem on older versions of unraid with this MOBO. Although i cant say ive ever really looked at the sensors command before either since everything seemed fine

Auto Fan script is also not working for me. Shows PWM Controller as none, detect buttons do nothing. I have an X8SIL-F supermicro motherboard. ls -la `dirname $(find /sys/devices -iname "fan*_input")` dirname.txt ls -la `dirname $(find /sys/devices -iname "pwm[0-9]")` dirnamepwm.txt Have attached output of the above commands dirname.txt dirnamepwm.txt

Thank you for the reply! I had some 3pin fans inside the new case which were connected to Ports 2 & 3. With the rest being 4pin. I've disconnected them briefly (the 3 pin fans) to see if the problem persists. However Fan 4 has already gone through the same errors - so it seems like the problem is persisting even with only 4Pin PWM fans 1 2015/03/16 17:57:20 FAN 4 Fan Lower Non-Critical - Going Low - Asserted 2 2015/03/16 17:57:20 FAN 4 Fan Lower Critical - Going Low - Asserted 3 2015/03/16 17:57:20 FAN 4 Fan Lower Non-Recoverable - Going Low - Asserted I dont believe anything else has changed

Hi all, I have a problem that i suspect is my board however i'm not sure what to do about it. Every so often my server will detect a fan as being 0 RPMs. It seems to get all of them. The fans never noticeably stop working, and two of the ports (4 & 5) aren't plugged in - Yet even these two suddenly get detected as 0 RPM (And then stay forever at 0RPM as they arent plugged into anything) - this is via the IPMI web interface This happened after i moved from an old case into a new case, so i suspect i could have possibly done something whilst moving them. The server also makes a random 'warning siren' sound every so often, which i suspect is it thinking the fan is failing and then going off. This sound happens for anywhere from 2 to 20 seconds. Is there anything i can do? Thank you for any help - The siren noise waking my SO up at 1am from the other room occasionally isn't boding well