fespinoza831

It hasn't reoccurred, any issues leaving Syslog Server enabled?.

I had already ran those commands in the comment but had not rebooted. I have enabled the Syslog Server.

Hello this morning I was unable to access the UI, I had to manually shut down the server. So the diag is from after the reboot but I did get the messeges below via email. At 4:40am I received this msg /etc/cron.daily/fix.common.problems.sh: line 2: 2598178 Bus error /usr/local/emhttp/plugins/fix.common.problems/scripts/scan.php 2> /dev/null warning: Potentially dangerous mode on unraid-api: 0666 error: Ignoring unraid-api because it is writable by group or others. error: found error in file unraid-api, skipping warning: Potentially dangerous mode on unraid-api.patch: 0666 error: Ignoring unraid-api.patch because it is writable by group or others. error: found error in file unraid-api.patch, skipping /etc/cron.daily/tailscale-daily: line 3: 2598220 Bus error /usr/local/emhttp/plugins/tailscale/daily.php > /dev/null 2>&1 /etc/cron.daily/user.script.start.daily.sh: line 2: 2598240 Bus error /usr/local/emhttp/plugins/user.scripts/startSchedule.php daily At 4:47am I received this msg /etc/cron.hourly/user.script.start.hourly.sh: line 2: 2605358 Bus error /usr/local/emhttp/plugins/user.scripts/startSchedule.php hourly At 5:47am I received this msg /etc/cron.hourly/user.script.start.hourly.sh: line 2: 2666712 Bus error /usr/local/emhttp/plugins/user.scripts/startSchedule.php hourly plexserver-diagnostics-20250220-0614.zip

Hello, I just update to 7.0.0 yesterday and today my mover isn't running, cache drive was 94% full this morning and I had to manually move the files because the mover would not run plexserver-diagnostics-20250218-0623.zip

keep getting this when trying to check disk 10 fatal error -- Input/output error

Any way to determine if its power cable or data cables? and any recommendations on cables? seems my issues are always related to cables.

Hello, I removed the failing disk but started getting errors again when trying to rebuild parity drive. tried running XFS repair on the drive but it gets suck on Format log to cycle 18.plexserver-diagnostics-20250121-1045.zip

Weird I didn't see any error on disk 7 when 9 was disabled. I do recall seeing them a few days ago but I stopped the server and scanned the drive for for errors then repaired.

Here is the diag plexserver-diagnostics-20250117-0917.zip

the disk rebuild for disk 9 keeps failing, it says it has errors. and it pauses.

i got a disabled disk morning before work plexserver-diagnostics-20250117-0645.zip

Hello today I had a disabled drive. I attempted to remove and re add but rebuild would fail. it started getting errors on multiple drives. so I should shown check all cables and even replaced a few but continue to get error with two drives. Ended up trying a new config removing the two drives but now I still get errors on another drive and when I try to repair i get the following Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval -1 fatal error -- Input/output error plexserver-diagnostics-20240806-1806.zip

The same drive has been disabled 3 times in a week. Always the same drive but it passes smart checks with no errors. Disk 7 plexserver-diagnostics-20240602-2106.zip

Thanks, verified all connections and was able to rebuild the drive. I have previously purchase server different cables for my hard drives. but have seen issues with all. are there any reliable cables that can be recommended.

Hello had a drive get disabled and after try to rebuild data it pauses and starts a read check. the read check completed. started the rebuild again but its did the same thing. plexserver-diagnostics-20240428-2026.zip

So I disabled the syslog and it hasnt shutdown anymore..

its the same diag log or is it another log

sorry I hadn't replied sooner but noticed that syslog was still enabled when I pulled that previous log. or is there a different log that you need.

I suspect my server is loosing power, just not sure how to confirm. I wake up to the server up an running fine but it will be doing a parity check. its happened a few times this week. I do have it plugged into a UPS and has a gold nzxt 750 PSU. but any suggestions on how to confirm or test my PSU. on a side note I notice a separate issue at the same time. Nvidia GPU wont be recognized but it will say that there's a new driver for me to install and that a reboot is needed and GPU wont work until I restart again. I have since change to CPU transcoding for the meantime. plexserver-diagnostics-20240314-0728.zip

It will be fine then i get notified that there's a new driver update and the gpu will disappear. but no hardware changes or anything

Hello I keep getting this error every few days. "NVIDIA-SMI has failed because it couldnt communicate with the NVIDIA driver". After rebooting it says Unable to determine the device handle for GPU0000:01:00.0: Unknown Error plexserver-diagnostics-20240310-0610.zip

Thank everyone I have delete the additional .cfg files

updated to 6.12.6 and mover is now running. Thank you. I would like to clean up the shares like you said but not sure if I'm understanding the issue here which share is not on storage media?

I enabled the mover logging, uninstalled the mover tuning plugin, checked to make sure cache pool options are correct, manually triggered the move and nothing, plexserver-diagnostics-20240116-2026.zip

Had so many other issues not sure when this started but files are no longer being moved even is I trigger it manually. plexserver-diagnostics-20240115-2022.zip