Jump to content

Tabraxis

Members
  • Content Count

    29
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Tabraxis

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. Ok, noted. Any idea as to why the ownership has changed from the update?
  2. Hey All, Have 2 weird issues: 1) Has anyone else's Plex switched ownership from the last update? For some reason my Plex is signed in as my user email instead of the Plexpass email? All the administration are now under my home user (same as the signed in email account) and I cant find a way to swap it back. My friends outside my network have lost access too. 2) Docker seems to be running on host instead of bridged. When I change it to bridged, I cannot access the docker? I surmise its the same cause Tautulli cannot access it. Anyone have any thoughts?
  3. Ok, i've fixed it. I copied the original Unraid USB to a pc. Then on another usb, formatted it using the Unraid tool loading 6.7.2 on it. Then posted it in the server to verify it would boot cleanly it did. It showed my HDD's in there order, but would not start as the pro key was assigned to the original USB. I then shut it down, copied the OS portion (leaving the config folder alone) of the new USB onto the original USB, the posted it back up (but not before modifying the GUI boot in syslinux). Fingers crossed, it all looks good atm. Hope this helps anyone else who might have this issue in the future.
  4. Hello All, So, here's how it starts. So i finally decided to update my main server to 6.7.2 from 6.6.6. I have a 2nd server and its running 6.7.2 and its been working fine (its more or less a test/backup unit), but regardless, its been working without issues. So i stopped my dockers, clicked the update and went through the motions of updating. It all seems to be ok, several minutes later i checked the server and it came up to the gui splash screen on the physical unit and i was able to login via my main pc. Great, no worries right? Well not so much, my plex was not working. After going through the settings several time i found that i needed to update the Nvida driver for hardware transcending add-on. So i removed the extra paths in the docker and was able to get plex working again. It nearly gave me a heart attack, thinking of recreating the folders/users with all the movies/tv shows on plex again. So i should have stopped there... but i'm an idiot and decided to continue on... its only a driver update right? whats the harm, right? So clicked on the 6.7.2 Nvidia driver waited for it to say "restart system" then proceeded to reboot. After 15 minutes, i finally went to check on it and found that it had an error. So i restarted it again manually, and the OS prompt left it alone and it came back with this "End trace" (SS attached). Not understanding fully what it meant, i restarted it again and this time selected "GUI /w no plugins". it finally landed on the "Kernel panic" (ss attached). I crossed my fingers and restarted it one last time, but and selected " no GUI or plugins" and still got the same "Kernel panic". Am i fubar'd? or is there a way to recover this? Thanks for any assistance you can provide.
  5. Sorry, I don't often send diagnostics out, so I tend to be selective on where the go. I've made the change to Prefer, and will be doing a restart next. Is it too much to assume that the cached appdata that my dockers are having issues with will go back to before the FCP mishap? Or is there anything else you can recommend I can do?
  6. I just sent you a PM with the diagnostics data.
  7. I came back today to find my log file usage at 100% and it filled with the attached two text files. I can provide the full list if its more helpful? example.txt example2.txt
  8. Hello, I did something stupid. I was going through my settings and have CA Fix install for quite a while now (fixing little issues here and there) and I clicked on something with out reading it fully first. I clicked on something that read to the effect of fixing an issue with my cache drive and now all of my Tautulli history is missing, my Nextcloud wont work and i'm missing a ton of Plex server movie & TV images. Does anyone have a clue what happened to my cache settings and how i can revert this mistake, or know where the data when so i can try pointing it to this location? I checked the actual cache drives and they are still there and have data on it, but i'm at a loss as to why abruptly with this one click its all F'd up? Thanks, Tabraxis.
  9. Glad it wasn't a difficult fix! Many Thanks and keep up the great work 😎
  10. Yes it is! Yikes, freaking me out Guess they had an issue and its fixed?
  11. Hello Binhex, Ok, so super weird. I deleted the supervisord.log ( .log1 through .log5) that i had, waited then restarted as steps said to. I already had DEBUG on ( for whatever reason) then waited for the logs to fill up. After it did i quickly checked for piece of mind, and it works again?! Iv'e got something downloading now, seems to check out. I guess your mere request alone snapped it into shape! Thanks ps. would you still want the .log file in case it helps the anyone else?
  12. Hello All, I was wondering what's happen to my docker. I came back this afternoon and found that nothing was downloading, so i restarted the docker and now I cant get access to the portal page? So I went to the logs, but I'm not able to find out what the issue actually is? Can anyone help me sort out why it just stopped suddenly? It just keeps repeating the above. Thanks, Brax.
  13. Hello Johnnie, Thank you for your time and suggestions. So after the extended self-test for cache drive 4, if it proves to be bad i'll replace it, will this affect my docker settings? ie, will i have to reconfigure each docker from fresh, or will the drop down with the saved configuration file still be available? Lastly, if i remove the two SSD drives and just use the HDD drives (or add another 1-2 of the same spec), will i have any issues where there is data on the SSD's that the system will be looking for. Or would a parity check resolve this maybe?
  14. Hello Johnnie, Please see attached diagnostics file. Thanks, gibson-diagnostics-20170319-0957.zip
  15. Hello All, So i woke up this morning and when to sign in to one of my VM's (to check some stats) and it was taking a long while, so i figure i'd login though the VNC directly. After logging into my site (and to my horror) all my dockers were not shown. I went directly to the docker page and found that nothing was there... literally nothing, no offline dockers, no add or remove, just a blank page. I've done a reboot on the server and still nothing, i've gone to the docker page and disabled docker, then enabled it, nothing. i've also disabled it, deleted the storage location (via the webpage), then enabled it again, still nothing. Has this happened to anyone before? if so, is there something else i can try. I just found this in my logs, but i don't know what it means (other than BTBFS has/had an error of some kind). Could anyone explain further, or have a fix suggestion? Mar 19 09:23:19 Gibson kernel: BTRFS info (device sdc1): read error corrected: ino 1 off 71995260928 (dev /dev/sdd1 sector 39913536) Mar 19 09:23:19 Gibson kernel: BTRFS info (device sdc1): read error corrected: ino 1 off 71995265024 (dev /dev/sdd1 sector 39913544) Mar 19 09:23:19 Gibson kernel: BTRFS info (device sdc1): read error corrected: ino 1 off 71995269120 (dev /dev/sdd1 sector 39913552) Mar 19 09:23:19 Gibson kernel: BTRFS info (device sdc1): read error corrected: ino 1 off 71995273216 (dev /dev/sdd1 sector 39913560) Mar 19 09:23:19 Gibson kernel: BTRFS error (device sdc1): parent transid verify failed on 71995277312 wanted 1364297 found 1351260 Mar 19 09:23:19 Gibson kernel: BTRFS info (device sdc1): read error corrected: ino 1 off 71995277312 (dev /dev/sdd1 sector 39913568) Mar 19 09:23:19 Gibson kernel: BTRFS info (device sdc1): read error corrected: ino 1 off 71995281408 (dev /dev/sdd1 sector 39913576) Mar 19 09:23:19 Gibson kernel: BTRFS info (device sdc1): read error corrected: ino 1 off 71995285504 (dev /dev/sdd1 sector 39913584) Mar 19 09:23:19 Gibson kernel: BTRFS info (device sdc1): read error corrected: ino 1 off 71995289600 (dev /dev/sdd1 sector 39913592) Mar 19 09:23:19 Gibson kernel: BTRFS error (device sdc1): parent transid verify failed on 71995310080 wanted 1364297 found 1342776 Mar 19 09:23:19 Gibson kernel: BTRFS info (device sdc1): read error corrected: ino 1 off 71995310080 (dev /dev/sdd1 sector 39913632) Mar 19 09:23:19 Gibson kernel: BTRFS info (device sdc1): read error corrected: ino 1 off 71995314176 (dev /dev/sdd1 sector 39913640) Mar 19 09:23:19 Gibson kernel: BTRFS error (device sdc1): parent transid verify failed on 73533718528 wanted 1381390 found 1346780 Mar 19 09:23:20 Gibson kernel: BTRFS error (device sdc1): parent transid verify failed on 73933422592 wanted 1381253 found 1357623 Mar 19 09:23:20 Gibson kernel: BTRFS error (device sdc1): parent transid verify failed on 73783640064 wanted 1367864 found 1357608 Mar 19 09:23:20 Gibson kernel: BTRFS error (device sdc1): parent transid verify failed on 73329033216 wanted 1380278 found 1357795 Mar 19 09:23:20 Gibson kernel: BTRFS error (device sdc1): parent transid verify failed on 73385132032 wanted 1380850 found 1357801 Mar 19 09:23:20 Gibson kernel: BTRFS error (device sdc1): parent transid verify failed on 73393733632 wanted 1380850 found 1357802