iTunes

update: I feel like the problems arose when 'initializing' the database. Once it has been setup I haven't had the issue anymore... So kinda solved?

While sadly, it wasn't the cause of my problem I have uninstalled NerdTools. Thank you for pointing that out. If anyone else has any idea, please reach out.

Hi all, so recently I've moved all of my docker volumes to use NFS shares (and thus connecting to my unraid server). This all worked fine for months, however today I decided to move another docker compose stack and all of a sudden I keep getting (what I think) are NFS crashes? I have increased the NFS thread count and the Global Share Number of fuse File Descriptors already.... Does anyone have any idea? I have attached 2 diagnostics files, from 2 different occasions. Thank you! EDIT: might be worth mentioning that the stack includes mariaDB, which when I'm restarting/editing/whatever MariaDB it seems to 'crash' (I.E. the shares disappear) a lot tower-diagnostics-20250217-1532.zip tower-diagnostics-20250217-1321.zip

So, just to be sure... I manually move the files from the cache/Library share to the plex share and 'correct' the settings afterwards?

This returns this: drwxrwxrwx 1 nobody users 38 May 10 17:19 Library/ Would it just be a visual bug and would the Library share actually reside on the plex disk? If so, would it be safe to just switch the 'Primary storage' to plex instead of 'cache' like it says right now? (ls -l /mnt/cache doesn't return Library..)

So my Plex config is at '/mnt/plex/' but I also have a user share at /mnt/user/Library called Library which says it's location is plex' (the plex cache pool SSD) when looking through the unraid webgui... So I am fairly sure it's on the plex pool... Could it be a symlink or something?

Hello all, so, I have had my unraid server for years now and am still very happy with it. Now one thing that's been bugging me lately is this one 'mystery' share I had called 'Library'... it seems to house a Plex appdata/config, that actually is being updated (like has new logs, folders are edited every day, etc.), which I find very strange seen as my Plex config is mounted at '/mnt/plex/'.... When I open the share it says it is stored on the Array, yet when I go into the webGUI's 'explorer' it lists that it resides on the 'plex cache drive' (which is mounted like a cache drive, so not part of the array)... Could anyone help me debug? Thank you in advance! tower-diagnostics-20240814-1657.zip

Hi guys, couple of months ago I opened a thread for the same issue, it was fixed then by connecting the SSD straight to the mobo using SATA instead of using my hot swap bays (backplane). The issue hadn't occured for months, but now all of a sudden, with no changes made it's back... As far as I can tell SMART is only displaying 'old age errors' and no (pre-)failed ones, so the disk should be fine, I think? Other than the drive label changing to 'sdb' nothing has changed... I have attached both diagnostics from 'before' (aka when plex starts throwing the error but the drive appears to be connected normally in the unraid gui. As well as after an array start & stop when the drive shows up as unmountable. (Only a full system reboot fixes this afaik) Thank you all in advance! diag_after_array_restart.zip plex_ssd_SMART.zip diag_before_array_restart.zip

Just an update: hasn't occured since I connected it straight to the mobo SATA. Is there anything I can derive from the errors occuring when connected through the backplane?

Forgot to mention it's connected via backplane, I'll switch it around to straight to the onboard SATA. Wouldn't it affect the other SSD as well though (unless it's that specific slot that's giving problems)...

Hi guys, so recently my plex SSD which I've assigned as a pool device started getting random 'disconnects' (the drive is still connected but gives I/O errors.) resulting in my plex docker crashing. Whenever this happens all I have to do is reboot the array and everything will be up and running again... SMART reports no issues and to be honest I have no idea what to make out of the syslog messages... The drive in question is labeled sdq, it's the only kingston in the system... Maybe this could be useful, the error plex reports in the docker log: libc++abi: terminating with uncaught exception of type boost::filesystem::filesystem_error: boost::filesystem::create_directories: I/O error [system:5]: "/config/Library/Application Support/Plex Media Server/Cache", "/config/Library/Application Support/Plex Media Server/Cache" tower-diagnostics-20231113-1049.zip

Hi, so I'm using Plex on a seperate cache SSD (setup as a pool) everything been's working great but since a few weeks I've been getting errors... The docker keeps running, but nothing is working. Also the logs are filled with this: Starting Plex Media Server. . . (you can ignore the libusb_init error) libc++abi: terminating with uncaught exception of type boost::filesystem::filesystem_error: boost::filesystem::create_directories: I/O error [system:5]: "/config/Library/Application Support/Plex Media Server/Cache", "/config/Library/Application Support/Plex Media Server/Cache" This error just keeps spamming over and over again. The only fix I have found so far is to stop the array and re-start it as just restarting the docker results in an error. At first glance it seems like the entire Plex SSD becomes inaccessible. I have attached the diagnostics from before restarting the array. Thanks guys! tower-diagnostics-20231012-0735.zip

I suppose you will need to 're-config' all folders and such (when migrating from the old plugin)?

Oh for the SSD as well... So what's the next thing to troubleshoot now? Try putting it somewhere else on the backplane, switching power cords, etc.?

Yes I know, HDD 3 and some others have been giving some errors as of lately although SMART displays no errors for them I just thought they were at the end of their life as those were my first drives I bought used a couple of years ago... Plan on replacing them anyways... If problems for disk 3 keep happening after replacing I will come back to this. Though I really want to get the plex SSD sorted...