Psycho

Hey guys, I seem to be having issues adding a new series: Couldn't import episode /data/completed/Series/Season/Episode: Access to the path '/tv/Series' is denied. I added the series but it doesn't appear to have created the folder. Other automatic downloads are working fine and being imported.

The server is fine besides the warnings on the dashboard, rebooting would remove this?

I installed the My Servers plugin a while back. Then during some server troubleshooting it was disabled (renamed plugin file). Today I noticed that the plugin wasn't installed (didn't click at the time as to why it wasn't) and tried installing it. It failed and now I get these messages on my dashboard: Warning: include(/usr/local/emhttp/plugins/dynamix.my.servers/include/myservers2.php): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php on line 427 Warning: include(): Failed opening '/usr/local/emhttp/plugins/dynamix.my.servers/include/myservers2.php' for inclusion (include_path='.:/usr/local/emhttp') in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php on line 427 Tried reinstalling the plugin again and it just fails with no specific error message.

Yes I did

Well now for some reason it's back online. I don't have any idea what knocked the webGUI offline. I looked at the syslog of when it wasn't reachable and no pointers there. I'll chalk it up to some other root cause I guess.

Enabled it, rebooted and let it run for an hour. syslog

That was me (my own stupidity), the GUI itself was unreachable beforehand. I'll enable the syslog and let it run for a while and hope for some clues.

Well unfortunately it just did it again this morning, double checked to make sure the change was still there and it is. Woke up to find the dashboard unreachable... VMs and docker still running. I do have access to the local server now and the GUI works fine there. knight-diagnostics-20220730-0734.zip

Sure enough something to do with Dynamix ... SSD Trim or Dynamix.unraid

I just updated from 6.10.2 to 6.10.3 and now Unraid won't boot. It appears to remain stuck on 'Starting Samba'. Booted in safe mode with no issues. knight-diagnostics-20220617-1958.zip

NIC being blacklisted... didn't notice any actual issues prior to that and went from 6.10.0 to 6.10.2. Disabled VT-d for now and was debating on other methods. Would any errors while running 6.10.0 give me actual warning or would it only show up in the logs? I don't see anything out of the ordinary but haven't checked the logs. EDIT: Nevermind, found the post link within the post link... will check the logs to see if I spot anything

Well dang... my old HP Z800 is affected too. nic is BCM5764M

Hello, ever since booting my server back up after a clean shutdown I cannot access the server via the local IP or .local URLs. I can SSH into the server and the VMs and docker are running fine. The error I get in the browser is ERR_CONNECTION_REFUSED I cannot access the server via GUI OS (possible dead video card) to see if the GUI shows up on the server itself. Any help would be greatly appreciated.

I just want to double check, my parity disk started chirping today and got disabled after a reboot. If I look at my parity disk I get this error: ata5: softreset failed (1st FIS failed) I found topics on here that state it's a onboard SATA controller problem and not a disk problem. I ordered a new disk to be safe and tried running a smart test but it fails to complete.(Host Interrupt) knight-diagnostics-20210214-1115.zip

0 KB (size on disk 7.03 GB) I guess it's not that bad if I only lost 7GB worth of data.

Well gents, I owe you a couple of beers. It looks like it worked, but I have a lost+found folder and file. How do I go thru it? To be clear, the lost+found folder only contains 1 file with no extensions and numbers as its name.

Repair or format? If repair, how do I go about doing so?

here you go knight-diagnostics-20201116-1131.zip

No backups. Most of it is media files, maybe a few important files on there. Can I access the drive content if I connect the drive to another system?

Yes, finally succeeded. Just stuck with my disk 2 problem now.

Ok so this is what I am greeted with now before even running the check: And this is what I get when filesystem check:

Well I decided to try the check Disk 2 filesystem first and I didn't get any clear error messages. So I'm currently rebuilding Disk 1 and Disk 2 is still unmountable. I guess I'll deal with Disk 2 once the rebuild is done. I ran the check with the -nv tag. knight-diagnostics-20201115-2007.zip

No UPS (yet)... also getting a second parity drive. You learn something new every time!

here you go knight-diagnostics-20201115-1816.zip

Just my luck, with 1 hour to go on the Disk 1 rebuild with no errors, I get hit with another power outage. Now disk 2 says: Do I need to do the "Retain current configuration" step again? knight-diagnostics-20201115-1614.zip