Jump to content

principis

Members
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About principis

  • Rank
    Member

Recent Profile Visitors

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

  1. I guess you haven't assigned a cache disk? That means that the cache is just written to ram. You could assign the extra disk as cache disk and that would solve the problem.
  2. In the previous thread I said it seemed to be fixed by changing to /mnt/disk1 well it's not. I'm still on 6.7.2, please let me know if there's an rc3 and I'll help test. Maybe downgrade the kernel?
  3. Sorry I am in the middle of exams and didn't get an email... The issue is completely solved for me. Just moved plex db from /mnt/user to /mnt/disk1. I'm sorry but I won't do any testing. I have way too much work to do and it's really annoying. I posted diagnostics on the different thread.
  4. My appdata was on /mnt/user/appdata. I experienced corruption (Plex sqlite db) after upgrading to 6.7.0. After a reinstall of Plex, it corrupted after a few hours. I downgraded back to 6.6.7 which solved the issue. After reading and commenting on the previous thread, I changed my appdata to /mnt/disk1/appdata, upgraded to 6.7.0 and reinstalled Plex. I have not experienced corruption since. I have no time to test but maybe this information aids in solving this. unraid-diagnostics-20190626-0903.zip
  5. As I said before I experienced corruption on /mnt/share when I upgraded to 6.7.0. I have changed to /mnt/disk1 with a clean install of Plex and it seems to be fixed... I'm not sure because I don't know how to test it and don't have time to test but Plex seems to be working fine. (Although it segfaulted yesterday after an update...)
  6. I have no plugins which could mess with it (I think). Only the folder caching plugin, which is disabled for appdata, and the turbowrite plugin. Plex is working for ~12 hours now. (on /mnt/disk1/appdata). So I think that the issue for me is only the /mnt/user.
  7. Upgraded to 6.7.0 again and moved my dockers to /mnt/disk1. Will see if any corruption occurs.
  8. Yes probably. I'm not blaming unraid, I just think they should "fix" (for unraid) it by downgrading the broken dependency if possible or put a warning in the release notes or something. I don't have the time to find the exact problem. If you do not have a cache drive this is a terrible idea... I was told to put it on /mnt/user so I did. I still find it strange that it causes problems.
  9. I do not have a cache disk so no. And it worked fine for years so no I haven't tested it. Shouldn't this be fixed instead of a workaround? I may test it with /mnt/diskX when I have time.
  10. Same issue... After upgrade to 6.7.0 plex db suddenly corrupted. Reinstalled plex completely, same issue after a day. Downgrading to 6.6.7 fixed it. (Appdata is on /mnt/user) I thought something had to be broken with the filesystem (XFS) but checked and it was fine. But parity check found ~300 errors. Never had this before. There is something really broken with 6.7.0 and I am not going to upgrade again.
  11. When trying to create a 8 GB swap file it stuck on 6.4 GB so I manually made one with fallocate and mkswap. I don't really understand why the plugin doesn't use that method... You shouldn't really notice much of a performance hit. And afaik it's not possible on linux and I think it's really difficult to implement exclusions. Memory is assigned in pages. Most of the time blocks of 4 KB (or 2 MB or 1GB). The linux kernel handles swapping and it tries to swap out pages which are least recently used. For example when a program starts it may load a lot of code in memory just for initialization but after that it won't be used so this code which is allocated in pages can be swapped out to free up memory. So yes, all memory is swapped out. (If I'm correct, it may be that Linux handles it differently, I'm only a CS student not an expert ;) ).
  12. Hi, After upgrading to 6.6.2, upload is very slow, around 300KB/s instead of my normal 4.7 MB/s. Downgrading to 6.6.1 fixes the problem. It's also very unstable, what I mean by this is when I start a download from a different location to my server with wget, it take a long time to start and the download speed itself is very unstable. So I downgraded to 6.6.1 and it worked fine for a bit but after sleeping and testing it again just now, it's again really slow. I'm downloading with wget on the command line and only get 70 KB/s... And no it's not my network everything works fine. I'll try to downgrade to 6.5.3 unraid-diagnostics-20181020-0308.zip UPDATE: When downloading unRAID 6.5.3 on 6.6.1 it started really slow ~30KB/s so I opened a new shell and ping -f 192.168.1.1 and suddenly the speed went up to ~20MB/s when I stopped the ping flood, it went down to ~30KB/s... Any ideas? UPDATE 2: it may have something to do with my ISP but it doesn't explain all problems...
  13. So I reinstalled unraid completely without restoring a backup so a completely clean install and it happened again. Apr 3 18:17:38 Tower kernel: Plex Media Scan[1244]: segfault at 7f7aafef8d89 ip 00007f7a6d5b742c sp 00007f7a67ffd6a0 error 4 in libjemalloc.so.1[7f7a6d51c000+133000] Apr 3 18:35:00 Tower kernel: Plex Media Scan[6826]: segfault at 7fb6d0562480 ip 00007fb4566fdb08 sp 00007fb450ffdb30 error 6 in libjemalloc.so.1[7fb4566c9000+133000] Apr 3 18:38:30 Tower kernel: Plex Media Scan[7895]: segfault at 0 ip (null) sp 00007f5cc2bfe8d8 error 14 in Plex Media Scanner[400000+42e000] Apr 3 18:38:30 Tower kernel: Plex Media Scan[7893]: segfault at 7f5d0aaf8d89 ip 00007f5cc815d42c sp 00007fffe148c1e0 error 4 in libjemalloc.so.1[7f5cc80c2000+133000] Apr 3 18:39:54 Tower kernel: Plex Media Scan[8387]: segfault at 7fc4a62f8d89 ip 00007fc463a7042c sp 00007fc45e3fd700 error 4 in libjemalloc.so.1[7fc4639d5000+133000] Apr 3 18:41:08 Tower kernel: Plex Media Scan[8768]: segfault at 7f95cb6f8d89 ip 00007f9588edc42c sp 00007f95837fd640 error 4 in libjemalloc.so.1[7f9588e41000+133000] Apr 3 19:28:17 Tower kernel: Plex Media Scan[23091]: segfault at 0 ip (null) sp 00007fb3673fe8d8 error 14 in Plex Media Scanner[400000+42e000] I'll try to find out what happens when the error occures but I don't know how... unraid-diagnostics-20170405-1240.zip
  14. @RobJ I just wanted to tell you what happend, maybe you know if it's fixed or not. So after I found out that there were some error with dimm 4, I pulled it out, vacuumed the slot and cleaned the ram stick with 94% alcohol. (I forgot the 99%). After that, I ran memtest86 for 15 hours or more. (4 passes) and it didn't find any errors. I also changed the driver settings and it was on 'native' but I changed it to AHCI (keep in mind it's an IBM server from 2008) The ram is 4 sticks of 2 GB ECC DDR2, some samsung memory I bought second hand (it came out an old HP server). Should I reinstall Plex? Or should I reinstall whole unRAID?
  15. Thank you very much for your answer. Everytime there's a upgrade for Plex I have a lot of problems with it... When I click upgrade it hangs and won't finish upgrading and it won't start, ... It's very annoying. (I think I upgraded this month.) is it possible that something is corrupted and that that causes the segfaults? Shall I try to reinstall the plugin? (I don't know what a segfault is and how bad it is.) Edit: Never mind... It's a ram error. Just checked the BIOS event and it reports seeing A LOT of single bit errors on dimm 4.