gcalaway

Members
  • Posts

    12
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

gcalaway's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. I am not sure if there is a better way but I just figured this out if you or @master_of_pants have not yet. Or for anyone else... - Log in to your admin account and access the 'System Settings' page - The first section says 'Invite Links' with a button underneath - Click the button for 'Show Links' - Click the '+' next to the words 'Invite Links List' - If you know the username you want to add you can type it in, or select only the user group, link expiration date, and space. - From the list view, simply right click on the word 'link' next to the user you just created and send that link in an email or text message, etc.
  2. So happy to have found this thread. This either just started for me, or just became something I realized. ****** Got everything moved over and writes seems lower for now
  3. Makes sense, Was just a little surprised since it is just a fork of sonarr and the sonarr was working. Rolled back to "binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04", lost download files from ui, but thats not a big deal. Everything working again! Excited to be able to use v2 soon!
  4. Interesting glitches after updating. It seems Radarr will not authenticate my password for my Deluge, but if manually searching and downloading files are still sent to Deluge. Sonarr works just fine. Could be something I am doing wrong but seems strange to happen immediately after updating to V2
  5. More strange things I don't understand: Dec 1 16:57:58 Helios php-fpm[9258]: [WARNING] [pool www] child 14422 exited on signal 7 (SIGBUS) after 217.012773 seconds from start Dec 1 16:57:58 Helios nginx: 2017/12/01 16:57:58 [error] 9280#9280: *13310 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.1.65, server: , request: "POST /webGui/include/DeviceList.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.88", referrer: "http://192.168.1.88/Main"
  6. Thanks for the information @John_M, I guess its possible I had two cables fail, just surprising to me. I have been keeping an eye on my logs, upades: Dec 1 14:25:56 Helios rc.diskinfo[9637]: SIGHUP received, forcing refresh of disks info. Dec 1 14:25:58 Helios rc.diskinfo[9637]: SIGHUP received, forcing refresh of disks info.
  7. System- CPU: Ryzen 1700x, MOBO: ASUS X370 Pro, unRAID version: 6.4.0_rc14
  8. Just got a couple of more easystores for a server and got one installed and preclearing, the other i just shucked and installed, decided I wanted it in a different bay, moved it, and it did not mount. I didn't think anything of it and so I moved it back to the original spot thinking I would just preclear it and replace a faulty cable/test the current connection. Then the drive did not mount in the original bay. I checked the logs and saw the following, when I removed the drive again the errors stopped. (the server and all dockers are still running, checked fix common problems and nothing and I will not have another drive to test with until later today. Just want to make sure my other data is not in danger) Dec 1 11:48:28 Helios kernel: ata5: limiting SATA link speed to 1.5 Gbps Dec 1 11:48:28 Helios kernel: ata5: hard resetting link Dec 1 11:48:29 Helios kernel: ata5: SATA link down (SStatus 0 SControl 310) Dec 1 11:48:29 Helios kernel: ata5: EH complete Dec 1 11:48:29 Helios kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe frozen Dec 1 11:48:29 Helios kernel: ata5: irq_stat 0x00400040, connection status changed Dec 1 11:48:29 Helios kernel: ata5: SError: { PHYRdyChg CommWake DevExch } Dec 1 11:48:29 Helios kernel: ata5: limiting SATA link speed to 1.5 Gbps Dec 1 11:48:29 Helios kernel: ata5: hard resetting link Dec 1 11:48:30 Helios kernel: ata5: SATA link down (SStatus 0 SControl 310) Dec 1 11:48:30 Helios kernel: ata5: EH complete Dec 1 11:48:30 Helios kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen Dec 1 11:48:30 Helios kernel: ata5: irq_stat 0x00000040, connection status changed Dec 1 11:48:30 Helios kernel: ata5: SError: { CommWake DevExch } Dec 1 11:48:30 Helios kernel: ata5: limiting SATA link speed to 1.5 Gbps Dec 1 11:48:30 Helios kernel: ata5: hard resetting link Dec 1 11:48:32 Helios kernel: ata5: SATA link down (SStatus 0 SControl 310) Dec 1 11:48:32 Helios kernel: ata5: EH complete Dec 1 11:48:32 Helios kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe frozen Dec 1 11:48:32 Helios kernel: ata5: irq_stat 0x00400040, connection status changed Dec 1 11:48:32 Helios kernel: ata5: SError: { PHYRdyChg CommWake DevExch } Dec 1 11:48:32 Helios kernel: ata5: limiting SATA link speed to 1.5 Gbps Dec 1 11:48:32 Helios kernel: ata5: hard resetting link Dec 1 11:48:33 Helios kernel: ata5: SATA link down (SStatus 0 SControl 310) Dec 1 11:48:33 Helios kernel: ata5: EH complete Dec 1 11:48:34 Helios kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0x6 frozen Dec 1 11:48:34 Helios kernel: ata5: irq_stat 0x08000000, interface fatal error Dec 1 11:48:34 Helios kernel: ata5: hard resetting link Dec 1 11:48:35 Helios kernel: ata5: SATA link down (SStatus 0 SControl 310) Dec 1 11:48:35 Helios kernel: ata5: EH complete
  9. @dkerlee let me know how it goes, I have had no more crashes since adding the code personally, however I have seen a few log errors saying the Directory is not empty for the mnt/cache/appdata/Transcode/Sessions/plex. Other than that and a few updates to clear other errors (updating the Unassigned devices, and preclear) all has been going alright for 2 days 2 hours and 41 min...... fingers still crossed
  10. I was happy about hitting the 12 hour mark for the first time on this update but this makes me nervous again. any idea what happened?
  11. Thanks @johnnie.black for the link, had not found that. I have added the line to my Syslinux Configuration and we will see how it goes!
  12. Just joined to post about this: I have been using unraid for the last couple of months and did a build based around a Ryzen 1700x and an Asus X370 pro mobo. I have not been using any virtualization at all since I have hard there has been a lot of stability issues with that. Up until updating to the rc10b build I have been running a very stable system on the rc9b release and when I saw there were ryzen fixes on the new update I jumped on it two days ago.... Since updating to rc10b my system has needed a hard reset twice and does not stay up and running for more than 12 hours at a time at most. I went through this thread and either didn't see anyone else really experiencing the same things as me. is there a way to roll back to the previous build or is there something I can do to add a bit of stability to this? I am excited to use VMs but I don't mind rolling back and waiting if I cant keep my system stable for even one full day .... or maybe I am just too new to unraid an missing something! Thanks in advance for the help, and if there is anything I can provide log wise please let me know!