principis
-
Posts
18 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by principis
-
-
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...)
-
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.
-
Upgraded to 6.7.0 again and moved my dockers to /mnt/disk1. Will see if any corruption occurs.
-
6 hours ago, saarg said:
The issue is not only with unraid, but with mergerfs also. If there is anyone that should fix it, it's sqlite. If they even see it a an issue.
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.
6 minutes ago, testdasi said:I actually thought there was already a post some years ago telling people to use /mnt/cache instead of /mnt/user for docker config because of various issues. It was long enough ago that I only change my config to /mnt/cache out of habit when dealing with dockers without knowing why.
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.
-
2 hours ago, saarg said:
So you did not try to use /mnt/cache or /mnt/diskX?
That is the only solution to not have this issue.
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.
-
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.
-
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...
On 11/20/2018 at 7:44 PM, DZMM said:Out of interest, does all memory get moved to SWAP e.g. even memory in use by VMs?
Is there a way to not swap VM memory, or only certain dockers where performance doesn't matter?
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 ;) ).
-
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...
-
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?
-
11 hours ago, RobJ said:
Not related, but you have IDE emulation turned on for your onboard SATA drives. When you next boot, go into the BIOS settings and look for the SATA mode, and change it to a native SATA mode, preferably AHCI if available, anything but IDE emulation mode. It should be slightly faster, and a little safer.
You had your first segfault on March 16 at 2:05am, then again March 24 at 2:03am, then on March 27 around 7:30pm, then the last on March 30 at 2:05am. All were associated with Plex Media Scanner. A couple of them mention libjemalloc, but I'm not sure that matters because after the first segfault, the program may not have been running correctly, and that was on March 16. When these are reported, you should reboot when next convenient. Don't keep running just because it feels like nothing's wrong.
The 2 main causes for segfaults are RAM faults and dependency issues, then well after those, program bugs. In this case, I think it's a dependency issue, and for that you'll need PhAzE to take a look, when he has time. These are rarely easy to figure out.
There is a clear association with the time, a little after 2am, so you might look into what happens around then.
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.
-
I have a segfault error
Is there any solution to this?
Mar 30 02:04:51 unRAID kernel: Plex Media Scan[11495]: segfault at 0 ip (null) sp 00007f6f0a7fe8d8 error 14 in Plex Media Scanner[400000+42e000] Mar 30 02:06:47 unRAID kernel: Plex Media Scan[12145]: segfault at 0 ip (null) sp 00007fdd157fe8d8 error 14 in Plex Media Scanner[400000+42e000] Mar 30 02:07:07 unRAID kernel: Plex Media Scan[12226]: segfault at 7f23cbb19d89 ip 00007f238917542c sp 00007f2383bfd640 error 4 in libjemalloc.so.1[7f23890da000+133000] -
8 hours ago, RobJ said:
Harro and principis, you have posted in a very old thread about a very old version, Plex in v5, which was 32 bit, very different from what you are running. At that time, they had never heard of Dockers or diagnostics or XFS. Please post again in the support thread for the particular Plex you have installed.
Sorry I thought it was from this year... I think I accidentaly clicked the wrong topic after I logged in.
-
I have the same error...
Mar 30 02:04:51 unRAID kernel: Plex Media Scan[11495]: segfault at 0 ip (null) sp 00007f6f0a7fe8d8 error 14 in Plex Media Scanner[400000+42e000] Mar 30 02:06:47 unRAID kernel: Plex Media Scan[12145]: segfault at 0 ip (null) sp 00007fdd157fe8d8 error 14 in Plex Media Scanner[400000+42e000] Mar 30 02:07:07 unRAID kernel: Plex Media Scan[12226]: segfault at 7f23cbb19d89 ip 00007f238917542c sp 00007f2383bfd640 error 4 in libjemalloc.so.1[7f23890da000+133000]
Downgraded back to 6.6.7 due to Sqlite corruption
in General Support
Posted
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.