Yipee

Members
  • Posts

    39
  • Joined

  • Last visited

Everything posted by Yipee

  1. Not sure what changed but it appears to be fixed with the latest plex media server updates. Installing from apps successfully and nothing changed on my end.
  2. Thank you for your suggestion. I already tried that, deleted the appdata folder from my array. I went as far as preclear/reformatted my cache drive thinking it may be corrupted but still no luck. Same error. Not sure what else to try other than looking into reverting back to Unraid 6.3.5 maybe.
  3. So I reformatted my cache drive and tried again but still no luck. Keep seeing the same errors: Jan 24 23:44:54 Tower kernel: docker-containe[26183]: segfault at 30f010 ip 000000000030f010 sp 00007ffd01436a30 error 14 in docker-containerd-shim[400000+303000] Jan 24 23:47:08 Tower kernel: docker-containe[31462]: segfault at 30f010 ip 000000000030f010 sp 00007ffda4b61610 error 14 in docker-containerd-shim[400000+303000] Jan 24 23:47:43 Tower kernel: docker-containe[354]: segfault at 30f010 ip 000000000030f010 sp 00007ffda3cae760 error 14 in docker-containerd-shim[400000+303000]
  4. Squid, I haven't try to use the previous app because I was running the limetech built and I saw that's they no longer supported. Not sure if that would work either since it wouldn't start again right after I updated Unraid to 6.4.0. It was working fine on the previous version of Unraid 6.3.5, I think.
  5. I've tried other version too but still no luck. I also tried to install one other Apps but still get an error. Possibly an issue with my docker but I already deleted the docker including the img file and increase the image size to 40GB but it didn't make a difference. Can you look at my log from my previous post to see if you can spot anything? I would appreciate it.
  6. I deleted the deleted orphaned images, docker.img file, recreated the docker, reinstalled from Apps still same error. I've attached my diagnostic log. tower-diagnostics-20180124-0020.zip
  7. The thing is I had Plex working fine until I updated Unraid to 6.4.0. Then Plex wouldn't start so I tried to reinstall it, I even deleted the docker and recreated but still no luck.
  8. I just tried to install the linuxserver version of Plex from the Community Applications and got the same command error: Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="plex" --net="host" -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -e "VERSION"="latest" -v "/mnt/user/appdata/plex/config/":"/config":rw linuxserver/plex c1651ae7f2e9aaa716c7dafcb0b6df168abcd4fce8d851812cd78dfb7e886f1f /usr/bin/docker: Error response from daemon: open /var/run/docker/libcontainerd/containerd/c1651ae7f2e9aaa716c7dafcb0b6df168abcd4fce8d851812cd78dfb7e886f1f/init/shim-log.json: no such file or directory. The command failed.
  9. I'm trying to install the official one from plexinc and I posted in their forum too but no help yet. I'm actually installing it from the GUI under Apps section. I've tried with and without the token but got the same result.
  10. Hello All. I keep getting this error when I try to install Plex Media Server. Does anyone know what it means? root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="PlexMediaServer" --net="host" -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e "PLEX_CLAIM"="Insert Token from https://plex.tv/claim" -e "PLEX_UID"="99" -e "PLEX_GID"="100" -e "VERSION"="latest" -v "/mnt/user/appdata/PlexMediaServer/transcode/":"/transcode":rw -v "/mnt/user/appdata/PlexMediaServer/data/":"/data":rw -v "/mnt/user/appdata/PlexMediaServer/config/":"/config":rw plexinc/pms-docker:plexpass 611828f82e68b14fgdbc3511c23ab3ec97abdf1cf319f52a6ac000b94918d679 /usr/bin/docker: Error response from daemon: open /var/run/docker/libcontainerd/containerd/611828f82e68b14fgdbc3511c23ab3ec97abdf1cf319f52a6ac000b94918d679/init/shim-log.json: no such file or directory. The command failed.
  11. Johnnie.black, you are the man! Thank you. I got it working again. I suspect I my array still has some file corruptions. What's the best way to check this?
  12. Is downgrading to unRAID v6.2.4 from v6.3.2 a simple process? Can you point me in the right direction?
  13. Here's the log: Not available reiserfsck 3.6.25 ************************************************************* ** Do not run the program with --rebuild-tree unless ** ** something is broken and MAKE A BACKUP before using it. ** ** If you have bad sectors on a drive it is usually a bad ** ** idea to continue using it. Then you probably should get ** ** a working hard drive, copy the file system from the bad ** ** drive to the good one -- dd_rescue is a good tool for ** ** that -- and only then run this program. ** ************************************************************* Will rebuild the filesystem (/dev/md5) tree Will put log info to 'stdout' Replaying journal: Replaying journal: Done. Reiserfs journal '/dev/md5' in blocks [18..8211]: 0 transactions replayed ########### reiserfsck --rebuild-tree started at Mon Feb 27 10:08:58 2017 ########### Pass 0: Loading on-disk bitmap .. ok, 201797007 blocks marked used Zero bit found in on-disk bitmap after the last valid bit. Fixed. ####### Pass 0 ####### init_source_bitmap: Bitmap 6082 (of 32768 bits) is wrong - mark all blocks [199294976 - 199327744] as used init_source_bitmap: Bitmap 6083 (of 32768 bits) is wrong - mark all blocks [199327744 - 199360512] as used init_source_bitmap: Bitmap 6084 (of 32768 bits) is wrong - mark all blocks [199360512 - 199393280] as used init_source_bitmap: Bitmap 6085 (of 32768 bits) is wrong - mark all blocks [199393280 - 199426048] as used init_source_bitmap: Bitmap 6086 (of 32768 bits) is wrong - mark all blocks [199426048 - 199458816] as used init_source_bitmap: Bitmap 6087 (of 32768 bits) is wrong - mark all blocks [199458816 - 199491584] as used init_source_bitmap: Bitmap 6088 (of 32768 bits) is wrong - mark all blocks [199491584 - 199524352] as used . . . . . init_source_bitmap: Bitmap 11153 (of 32768 bits) is wrong - mark all blocks [365461504 - 365494272] as used init_source_bitmap: Bitmap 11154 (of 32768 bits) is wrong - mark all blocks [365494272 - 365527040] as used init_source_bitmap: Bitmap 11155 (of 32768 bits) is wrong - mark all blocks [365527040 - 365559808] as used init_source_bitmap: Bitmap 11156 (of 32768 bits) is wrong - mark all blocks [365559808 - 365592576] as used init_source_bitmap: Bitmap 11157 (of 32768 bits) is wrong - mark all blocks [365592576 - 365625344] as used init_source_bitmap: Bitmap 11158 (of 32768 bits) is wrong - mark all blocks [365625344 - 365658112] as used init_source_bitmap: Bitmap 11159 (of 32768 bits) is wrong - mark all blocks [365658112 - 365690880] as used init_source_bitmap: Bitmap 11160 (of 32768 bits) is wrong - mark all blocks [365690880 - 365723648] as used init_source_bitmap: Bitmap 11161 (of 32768 bits) is wrong - mark Skipping 19389 blocks (super block, journal, bitmaps) 366265249 blocks will be read 0%....20%....40%....60%...
  14. Ran check files system on disk5 then with rebuild tree option two times but both seem to be stuck at the same spot and didn't finished. My array maybe corrupted that's why it didn't rebuild disk5 correctly. What should be my approach? Thanks for the help. tower-diagnostics-20170226-1313.zip
  15. Hi Guys, I precleared disk5 then rebuild the array, parity show valid and finding 0 errors but now my disk5 is unmountable. I had some file corruption on disk6 before which I already corrected with file system check so not sure if that cause any issue. Attached is the log file. Any help and suggestions would be appreciated. tower-diagnostics-20170224-1921.zip
  16. It was just me not following instructions correctly. I didn't realize that you need to flash the Dell firmware first before going to the next step. I thought that step was only for people that wanted the Dell firmware so I jumped right to flashing the P20 firmware. Maybe adding a note that flashing the Dell firmware is required before proceeding to next step for people like myself Thank you very much for the instructions though. I got the card up and running great so far.
  17. Never mind. I didn't realized I had to flash the Dell firmware first then P7 and P20 in order like the instructions provided by Fireball3. Thank you all. I appreciate all your instructions.
  18. I followed Bungy's suggestion to remove memory stick leaving just 1 and that seems to fix the "not enough available extended error" message. However I'm still running into other error when flashing and writing the SAS address.
  19. Hi guys. I followed Fireball3's guide to and flash my H310 but so far couldn't pass step 2 and 3. I keep getting not enough available extended memory error when I try to save existing SBR. I proceeded to step 3 to clear controller ROM and get the same error. Any help would be appreciated.
  20. Thanks John. Not sure why it dropped offline. I rebuild disk 8 once before because of the exact same problem.
  21. I just rebooted and drive 4 came up but drive 8 doesn't appear to be online. These are new drives. I'm not sure what to make of it. Log file attached. tower-diagnostics-20170130-1440.zip
  22. Hello, I just replaced 2 HDs with brand new Seagates ST33000650NS and both were precleared successfully and without errors but after I copied some data and invoke the mover, one of them dropped offline and both showing tons of errors. Log attached. Can someone help decipher what is going on? TIA. tower-diagnostics-20170130-0111.zip
  23. Thanks for the advice. My cache drive never dropped of according to the main page. It shows normal operation, device is active, even when I ran the first diagnostic so I don't know what's going on.