Chugalug

Members
  • Posts

    27
  • Joined

  • Last visited

Everything posted by Chugalug

  1. Been having some network issues on my server. All of my dockers were showing that the version was unknown etc and I could ping the server but would get packets dropped. Rebooted the server and it was better for a while, not it is starting again. I see this in the log which I find weird specially as the IP addresses it is showing are not on my network, my IP subnet is 10.10.20.1 etc, any help would be appreciated. Sep 6 08:02:15 Unraid avahi-daemon[9910]: Joining mDNS multicast group on interface vetha2baa46.IPv6 with address fe80::401a:ebff:fe30:e7d1. Sep 6 08:02:15 Unraid avahi-daemon[9910]: New relevant interface vetha2baa46.IPv6 for mDNS. Sep 6 08:02:15 Unraid avahi-daemon[9910]: Registering new address record for fe80::401a:ebff:fe30:e7d1 on vetha2baa46.*. Sep 6 08:02:28 Unraid kernel: veth62aff59: renamed from eth0 Sep 6 08:02:28 Unraid kernel: br-8ae76cee11aa: port 9(vethdb6932f) entered disabled state Sep 6 08:02:28 Unraid avahi-daemon[9910]: Interface vethdb6932f.IPv6 no longer relevant for mDNS. Sep 6 08:02:28 Unraid avahi-daemon[9910]: Leaving mDNS multicast group on interface vethdb6932f.IPv6 with address fe80::40bc:caff:fea8:811e. Sep 6 08:02:28 Unraid kernel: br-8ae76cee11aa: port 9(vethdb6932f) entered disabled state Sep 6 08:02:28 Unraid kernel: device vethdb6932f left promiscuous mode Sep 6 08:02:28 Unraid kernel: br-8ae76cee11aa: port 9(vethdb6932f) entered disabled state Sep 6 08:02:28 Unraid avahi-daemon[9910]: Withdrawing address record for fe80::40bc:caff:fea8:811e on vethdb6932f. Sep 6 08:02:28 Unraid kernel: br-8ae76cee11aa: port 9(vethe633046) entered blocking state Sep 6 08:02:28 Unraid kernel: br-8ae76cee11aa: port 9(vethe633046) entered disabled state Sep 6 08:02:28 Unraid kernel: device vethe633046 entered promiscuous mode Sep 6 08:02:28 Unraid kernel: IPv6: ADDRCONF(NETDEV_UP): vethe633046: link is not ready Sep 6 08:02:28 Unraid kernel: br-8ae76cee11aa: port 9(vethe633046) entered blocking state Sep 6 08:02:28 Unraid kernel: br-8ae76cee11aa: port 9(vethe633046) entered forwarding state Sep 6 08:02:28 Unraid kernel: eth0: renamed from vethbcca532 Sep 6 08:02:28 Unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe633046: link becomes ready Sep 6 08:02:30 Unraid avahi-daemon[9910]: Joining mDNS multicast group on interface vethe633046.IPv6 with address fe80::fc2a:2eff:febf:fc33. Sep 6 08:02:30 Unraid avahi-daemon[9910]: New relevant interface vethe633046.IPv6 for mDNS. Sep 6 08:02:30 Unraid avahi-daemon[9910]: Registering new address record for fe80::fc2a:2eff:febf:fc33 on vethe633046.*. Sep 6 08:23:49 Unraid dnsmasq-dhcp[12916]: DHCPREQUEST(virbr0) 192.168.122.178 52:54:00:d7:c3:5d Sep 6 08:23:49 Unraid dnsmasq-dhcp[12916]: DHCPACK(virbr0) 192.168.122.178 52:54:00:d7:c3:5d DESKTOP-DAUHJ0O Sep 6 08:51:15 Unraid dnsmasq-dhcp[12916]: DHCPREQUEST(virbr0) 192.168.122.178 52:54:00:d7:c3:5d Sep 6 08:51:15 Unraid dnsmasq-dhcp[12916]: DHCPACK(virbr0) 192.168.122.178 52:54:00:d7:c3:5d DESKTOP-DAUHJ0O Sep 6 09:18:43 Unraid dnsmasq-dhcp[12916]: DHCPREQUEST(virbr0) 192.168.122.178 52:54:00:d7:c3:5d Sep 6 09:18:43 Unraid dnsmasq-dhcp[12916]: DHCPACK(virbr0) 192.168.122.178 52:54:00:d7:c3:5d DESKTOP-DAUHJ0O Sep 6 09:46:49 Unraid dnsmasq-dhcp[12916]: DHCPREQUEST(virbr0) 192.168.122.178 52:54:00:d7:c3:5d Sep 6 09:46:49 Unraid dnsmasq-dhcp[12916]: DHCPACK(virbr0) 192.168.122.178 52:54:00:d7:c3:5d DESKTOP-DAUHJ0O Sep 6 09:59:18 Unraid emhttpd: shcmd (1511): /usr/local/sbin/mover &> /dev/null & Sep 6 10:13:45 Unraid dnsmasq-dhcp[12916]: DHCPREQUEST(virbr0) 192.168.122.178 52:54:00:d7:c3:5d Sep 6 10:13:45 Unraid dnsmasq-dhcp[12916]: DHCPACK(virbr0) 192.168.122.178 52:54:00:d7:c3:5d DESKTOP-DAUHJ0O Sep 6 10:41:30 Unraid dnsmasq-dhcp[12916]: DHCPREQUEST(virbr0) 192.168.122.178 52:54:00:d7:c3:5d Sep 6 10:41:30 Unraid dnsmasq-dhcp[12916]: DHCPACK(virbr0) 192.168.122.178 52:54:00:d7:c3:5d DESKTOP-DAUHJ0O Sep 6 11:09:20 Unraid dnsmasq-dhcp[12916]: DHCPREQUEST(virbr0) 192.168.122.178 52:54:00:d7:c3:5d Sep 6 11:09:20 Unraid dnsmasq-dhcp[12916]: DHCPACK(virbr0) 192.168.122.178 52:54:00:d7:c3:5d DESKTOP-DAUHJ0O
  2. I followed the Spaceinvaderone video guide on how to get everything up and running and I am getting the following error in the log when trying to start the rocketchat docker. The mongodb seems to start ok from what I can tell. Any ideas? } /app/bundle/programs/server/node_modules/fibers/future.js:280 throw(ex); ^ MongoParseError: Unescaped at-sign in authority section at parseConnectionString (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/uri_parser.js:589:21) at connect (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/operations/connect.js:272:3) at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/mongo_client.js:221:5 at maybePromise (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/utils.js:714:3) at MongoClient.connect (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/mongo_client.js:217:10) at Function.MongoClient.connect (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/mongo_client.js:427:22) at new MongoConnection (packages/mongo/mongo_driver.js:206:11) at new MongoInternals.RemoteCollectionDriver (packages/mongo/remote_collection_driver.js:4:16) at Object.<anonymous> (packages/mongo/remote_collection_driver.js:38:10) at Object.defaultRemoteCollectionDriver (packages/underscore.js:784:19) at new Collection (packages/mongo/collection.js:97:40) at new AccountsCommon (packages/accounts-base/accounts_common.js:23:18) at new AccountsServer (packages/accounts-base/accounts_server.js:23:5) at packages/accounts-base/server_main.js:7:12 at module (packages/accounts-base/server_main.js:19:1) at fileEvaluate (packages/modules-runtime.js:336:7) { name: 'MongoParseError', [Symbol(mongoErrorContextSymbol)]: {} }
  3. It appears I did have SSH open so I have closed it and those have stopped now. Thank you so much!!!!
  4. Hi Everyone I just looked in my logs and I am seeing a bunch of different IP addresses trying to gain access to my server, mainly from China looking up the IP addresses. What can I do about this, freaking out a little bit. Here is a small snippet of the log but there are a bunch of different ones trying to gain access. Thank you Apr 20 09:05:28 Tower sshd[1077]: Invalid user dnsmasq from 62.210.125.29 port 57258 Apr 20 09:05:28 Tower sshd[1077]: error: Could not get shadow information for NOUSER Apr 20 09:05:28 Tower sshd[1077]: Failed password for invalid user dnsmasq from 62.210.125.29 port 57258 ssh2 Apr 20 09:05:29 Tower sshd[1077]: Received disconnect from 62.210.125.29 port 57258:11: Bye Bye [preauth] Apr 20 09:05:29 Tower sshd[1077]: Disconnected from invalid user dnsmasq 62.210.125.29 port 57258 [preauth] Apr 20 09:05:36 Tower sshd[1269]: Failed password for root from 206.189.229.112 port 50756 ssh2 Apr 20 09:05:36 Tower sshd[1269]: Received disconnect from 206.189.229.112 port 50756:11: Bye Bye [preauth] Apr 20 09:05:36 Tower sshd[1269]: Disconnected from authenticating user root 206.189.229.112 port 50756 [preauth] Apr 20 09:05:49 Tower sshd[2154]: Failed password for root from 49.88.112.71 port 37939 ssh2 Apr 20 09:05:49 Tower sshd[2154]: Failed password for root from 49.88.112.71 port 37939 ssh2 Apr 20 09:05:50 Tower sshd[2154]: Failed password for root from 49.88.112.71 port 37939 ssh2 Apr 20 09:05:50 Tower sshd[2154]: Received disconnect from 49.88.112.71 port 37939:11: [preauth] Apr 20 09:05:50 Tower sshd[2154]: Disconnected from authenticating user root 49.88.112.71 port 37939 [preauth] Apr 20 09:06:32 Tower sshd[2767]: Invalid user rt from 159.138.65.33 port 38316 Apr 20 09:06:32 Tower sshd[2767]: error: Could not get shadow information for NOUSER Apr 20 09:06:32 Tower sshd[2767]: Failed password for invalid user rt from 159.138.65.33 port 38316 ssh2 Apr 20 09:06:33 Tower sshd[2767]: Received disconnect from 159.138.65.33 port 38316:11: Bye Bye [preauth] Apr 20 09:06:33 Tower sshd[2767]: Disconnected from invalid user rt 159.138.65.33 port 38316 [preauth] Apr 20 09:06:54 Tower sshd[3124]: Accepted none for adm from 62.112.11.88 port 49806 ssh2
  5. Sorry this is the start of the error I meant. Feb 21 19:19:36 Tower kernel: blk_update_request: I/O error, dev sdh, sector 1026147647 Feb 21 19:19:36 Tower kernel: XFS (sdh1): metadata I/O error: block 0x3d29c4ff ("xlog_iodone") error 5 numblks 64 Feb 21 19:19:36 Tower kernel: XFS (sdh1): xfs_do_force_shutdown(0x2) called from line 1200 of file fs/xfs/xfs_log.c. Return address = 0xffffffff812b37d1 Feb 21 19:19:36 Tower kernel: XFS (sdh1): Log I/O Error Detected. Shutting down filesystem Feb 21 19:19:36 Tower kernel: XFS (sdh1): Please umount the filesystem and rectify the problem(s) Feb 21 19:19:36 Tower kernel: sd 7:0:0:0: [sdh] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 21 19:19:36 Tower kernel: sd 7:0:0:0: [sdh] tag#7 CDB: opcode=0x2a 2a 00 01 ba 3c 98 00 00 10 00 Feb 21 19:19:36 Tower kernel: blk_update_request: I/O error, dev sdh, sector 28982424 Feb 21 19:19:36 Tower kernel: sdh: detected capacity change from 1050214588416 to 0 Feb 21 19:19:36 Tower kernel: Buffer I/O error on dev sdh1, logical block 3622795, lost async page write Feb 21 19:19:36 Tower kernel: Buffer I/O error on dev sdh1, logical block 3622796, lost async page write Feb 21 19:25:28 Tower kernel: blk_update_request: I/O error, dev loop0, sector 175584 Feb 21 19:25:28 Tower kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 1, flush 0, corrupt 0, gen 0 Feb 21 19:25:28 Tower kernel: blk_update_request: I/O error, dev loop0, sector 2272736 Feb 21 19:25:28 Tower kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 2, flush 0, corrupt 0, gen 0
  6. I tried to delete my docker and recreate it but still getting errors as well getting a bunch of other errors that are concerning, wondering if I am having motherboard issues. Its weird that there are errors relating to BTRFS when the cache was reformatted to XFS. The error below causes my cache drive to show no directories on it, shows normal on the main page but click on the directory and it shows nothing is on it. syslog-4.txt
  7. Ok thanks for the info, I'm going to delete my docker and try and create a new image and see. I will report back. Cheers
  8. Hello I upgraded to a new larger cache drive and it automatically got formatted to BTRFS, I figured I would give it a go and transferred all of my apps etc over to is. When writing data to the cache drive I was getting a lot of error messaged in the log pertaining to BTRFS errors so I figured I would switch to XFS. I transferred my data off, reformatted to XFS and transferred all of the data back, I am still getting BTRFS errors, things seem fine but I would like to figure out the root of this and if there is a fix for it. The errors are along the lines of this and I have no drives that are BTRFS in my system anymore: Feb 19 20:36:26 Tower kernel: BTRFS error (device loop1): bad fsid on block 20987904 Feb 19 20:36:26 Tower kernel: BTRFS error (device loop1): bad fsid on block 20987904 Feb 19 20:36:26 Tower kernel: BTRFS error (device loop1): failed to read chunk root Feb 19 20:36:26 Tower kernel: BTRFS error (device loop1): open_ctree failed Feb 19 20:36:26 Tower root: mount: wrong fs type, bad option, bad superblock on /dev/loop1, Feb 19 20:36:26 Tower root: missing codepage or helper program, or other error Feb 19 20:36:26 Tower root: Feb 19 20:36:26 Tower root: In some cases useful info is found in syslog - try Feb 19 20:36:26 Tower root: dmesg | tail or so. Feb 19 20:36:26 Tower root: mount error
  9. I got the plugins to run it looks like and the plugininstallfile.done is in there now and it showed the following at the end: Installing homebridge-LogitechHarmony Loaded plugin: homebridge-philipshue Registering platform 'homebridge-philipshue.PhilipsHue' --- Loaded plugin: homebridge-sonos Registering accessory 'homebridge-sonos.Sonos' --- Loaded plugin: homebridge-wink Registering platform 'homebridge-wink.Wink' But it still won't keep the docker running, when I refresh the page it shows the red stop button.
  10. Ok thank you. Did you just leave the ones you wanted to use in the config file? Like only the ones you're going to list in the plugin install file? And do I need to do anything else but have the config file and the plugin install file, is there a step I'm missing?
  11. I have put the config.json file and the pluginsInstallList file into a folder that was named /mnt/cache/appdata/homebridge which is the host path in the docker settings. A folder called persist is created and it changed the one file to pluginsInstallList.done, not sure if that sounds correct, not sure what else to try
  12. I can't seem to get this docker to start at all. I click the start button and it says started with the green play button, but I refresh the page and it says its stopped with the red stop button on it. The log on the docker page doesn't show anything, not sure what I am doing wrong here, anyone have any suggestions?
  13. Thanks Squid. I did what you said and it is rebuilding the disk now, I will report back to let you know how it all worked out. Cheers.
  14. I've tried the spin up and it doesn't do anything either. Not sure what way to go here with this, scared of losing data.
  15. Thank you for the reply. That is totally possible as I didn't notice until after a reboot so not sure if it was red or not before. Here is the smart report. smart_report.txt
  16. Hello I noticed a Grey Triangle on one of my Drives today, also noticing that there is no option at the bottom to do a Parity Check and on the dashboard under Parity Status it says Data is invalid. I don't even know where to start here, and I am not even sure what the Grey Triangle is for. Any help on where to go from here would be a big help. I just updated to Unraid 6 RC3 today. Thank you syslog.txt.zip
  17. Thank you for your input Martin. I seem to have gotten it to work at 6Gbps now and I have done so many things I am not 100% sure which one fixed it, at one point I got it to 3Gbps and then to 6. I have: - Changed it to a different pcie slot, it was in a x16 slot, I put it in the very first x1 slot at the top of the board, also changed the cable this got it to 3Gbps, started getting write errors so that cable may have been wonky - Changed cable again and then it went back to 1.5Gbps - Changed this new cable to a different port on the card and the hard drive is now at 6Gbps and everything seems to be running good, not that this hard drive will be able to pull down that much speed I know. So not sure if there are wonky ports on that card or if it is a factor between cables and ports, I don't know, I guess I will see when I add more drives in the future and can deal with it then, at least this drive is running smooth and at it's full potential. Thanks again Martin, Cheers,
  18. Sorry the motherboard is a Gigabyte z87x-d3h and the Unraid version is 5.0.5. Thank you.
  19. Hello I recently got the Syba SI-PEX40064 and I have 1 4TB WD Red drive running on it. It appears to be running at 1.5Gbps so not at SATA III speeds. Is there any way to fix this? I Have attached my syslog, a few things from it that I noticed. Mar 2 02:37:27 Tower kernel: i801_smbus 0000:00:1f.3: enabling device (0001 -> 0003) Mar 2 02:37:27 Tower kernel: ACPI Warning: 0x0000f040-0x0000f05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20130117/utaddress-251) (Minor Issues) Mar 2 02:37:27 Tower kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver (System) Mar 2 02:37:27 Tower kernel: ata10: link is slow to respond, please be patient (ready=0) (Drive related) Mar 2 02:37:27 Tower kernel: ata10: softreset failed (device not ready) (Minor Issues) Mar 2 02:37:27 Tower kernel: ata10: failed to reset engine (errno=-5) (Minor Issues) Mar 2 02:37:27 Tower kernel: ata10: softreset failed (1st FIS failed) (Minor Issues) Mar 2 02:37:27 Tower kernel: ata10: failed to reset engine (errno=-5) (Minor Issues) Mar 2 02:37:27 Tower kernel: ata10: softreset failed (1st FIS failed) (Minor Issues) Mar 2 02:37:27 Tower kernel: ata10: limiting SATA link speed to 1.5 Gbps (Drive related) Mar 2 02:37:27 Tower kernel: ata10: SATA link up 1.5 Gbps (SStatus 113 SControl 310) (Drive related) Mar 2 02:37:27 Tower kernel: ata10.00: ATA-9: WDC WD40EFRX-68WT0N0, WD-WCC4E0052800, 80.00A80, max UDMA/133 (Drive related) Mar 2 02:37:27 Tower kernel: ata10.00: 7814037168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA (Drive related) Mar 2 02:37:27 Tower kernel: ata10.00: configured for UDMA/133 (Drive related) And then when I run a dmesg|grep SATA|grep link from telnet I get: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) ata8: SATA link down (SStatus 0 SControl 300) ata7: SATA link down (SStatus 0 SControl 300) ata9: SATA link down (SStatus 0 SControl 300) ata10: limiting SATA link speed to 1.5 Gbps ata10: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Thank You syslog-2014-03-02.txt.zip
  20. Thank you for the tips Dale, after many hours of reading and looking through the file structure, trying many different things I have solved my issue. I did all that you suggested, and yes that one disk is in trouble, it wasn't part of the Array it was just connected to run some tests on it. I also ran the Reiserfsck on all of the disks and all came back clean. I ran the new permissions from the settings to see if maybe it was a permission issue but the issue persisted. So after reading how mnt/usr0 is the mnt that mover uses to pass files through to the array I saw an apps folder in there, where my apps folder from the cache drive is set to cache only. I tried to create a new directory in there as a test in Midnight Commander and I got the same Error 28 from my logs. I decided to delete this apps folder and try and run the mover script again, everything worked perfectly now.
  21. My mover is working, it moves the files fine to the correct location but then it starts throwing up errors until it fills my tmpfs 100%. So every morning I wake up and the logs are full like this. I just tested it manually and it did it now too. I have attached a syslog. The mover script starts at 18:35:48 Thank you. syslog-2014-02-05-1.txt.zip
  22. No my cables aren't tied together, they are touching in areas but it's hard to overcome that. And it's not the power supply, I got a new 850watt today and it's still throwing up errors on those two drives. Thinking I will need to RMA them again and see, if it happens again with two more drives then I am at a loss, I will need to switch away from the blacks I guess. Thanks for the suggestions so far, if anyone else thinks of anything else please let me know. Cheers,
  23. Thanks for looking. I have the corsair tx-650 power supply http://www.newegg.ca/Product/Product.aspx?Item=N82E16817139020 I did buy it refurbished so not sure if that has anything to do with it, I know I probably shouldn't have done that since the PSU is one of the most important components. I didn't think it could be that cause all other disks seem to run fine off the same cable and power cable. I have the following running off of it 1 x 4TB WD Red Parity Drive 1 x 120gb Kingston SSD Cache Drive 2 x 4TB Seagate 4000DM000 1 x 1TB Samsung HD103 All of those are running good and then I have tried these two WD Black 4TB's, one in place of the 1TB samsung and the other in the last port on my motherboard. I have checked all the cable connections and made sure that they are secure and have tried different SATA cables. I let the parity sync run through last night and it finished with 1510 errors on that one disk, it said there was no parity sync errors. Running a parity check right now and it's about 40% through, there has been 9520 writes on this disk and 9510 errors, in the log I am getting those same read error, sector= as in the last log. Just running an extended self SMART test right now to see what it shows. Maybe I should be trying another PSU though I don't know.
  24. Also ran a smart report on it and have attached it here. Thanks Again. smart_report.txt
  25. sorry, Here you go, I just stopped everything it was doing and ran one, only one of the Black drives is connected right now. Thank you. syslog.zip