Mlatx

Wouldn't a disk error show up in a smart report?

Any ideas? It seems my syslog is getting filled up causing ram to filled up causing 100% cpu. I'm attaching another diagnostics upon waking up this morning. server-diagnostics-20220521-1045.zip

My CPU is pegged at 100%, and I don't know what is causing it. Here is the diagnostics report. Any ideas? server-diagnostics-20220520-1124.zip

server { listen 443 ssl; listen [::]:443 ssl; server_name your_subdomain*; include /config/nginx/ssl.conf; client_max_body_size 0; location /zm { include /config/nginx/proxy.conf; proxy_pass https://your_internal_ip:your_port/zm; } }

Has anyone gotten Baikal working through a reverse proxy like Swag? I can get the connection to work on the local network. However, it won't connect through Swag. That kind of defeats the purpose for me. Solved: I used the following for my proxy conf and named it baikal.subdomain.conf. I happened to use port 8008. I have my own domain running through cloudflare using swag. server { listen 443 ssl; listen [::]:443 ssl; server_name your_url.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; proxy_pass http://your_unraid_ip:8008; } }

Awesome. I was going to buy a new motherboard but found an 8 port card with the LSI chip. Thanks.

ok thanks

It's not a power issue. It probably is a controller issue. The last time I had this prior to unraid 6.9 it happened across all disks. Here is a post where a member described the issue being common for Ryzen boards, I need IOMMU, so what is my other option, a separate controller card?

So here I am again back in the same situation. This seems to happen every 6-8 weeks. Yesterday I had errors show up on the same parity disk and data disk. The parity has already been reconstructed, and the data disk is in progress. Here is the diagnostics report after the errors showed up. Is there anything here that is suspicious? server-diagnostics-20210727-0741.zip

That's a good idea to shut them down first. It takes less than a minute doing it manually. I extended the VM timeout, but figured that may be the case. Thanks.

Ok. Here are the diagnostics from when I shutdown according to the time they show. server-diagnostics-20210617-1840.zip

They are attached. Did I attach the wrong file?

I'm on version 6.9.2, and I seem to be getting unclean shutdowns all of the time. Parity starts upon reboot. Her are the diagnostics. Can anyone provide some input? server-diagnostics-20210617-2308.zip

Thanks Constructor. No I've rebuilt disks before. Thanks for helping out. If it happens again, I'll make sure to download diagnostics before restarting.

Yes, I rebooted from the webUI. Should I reboot a different way?

That error happened after the reboot. Here are the diagnostics. Fix common problems extended scan seems to freeze. server-diagnostics-20210606-1800.zip

Hi All, My parity and disk 1 are disabled for some reason. Parity check ran on 6/1 with zero errors. Fix common problems says check the main tab. The SMART shows no errors. The unraid log shows no errors. I've tried rebooting it, and it temporarily fixed the issue before going back to being disabled. I'd love some help on what I should do to test it. I'm running a Ryzen 2700 with ECC memory. I know Ryzens can have some issues as I have every once in a while where all disks report errors. But a reboot solves that. I'm running a fix common problems extended test. What else should I do?

Would it be beneficial to use another database say mariadb as I already have it for nextcloud? Or should I just stick with the mysql that is part of zoneminder?

Thanks. I have a backup of appdata where the database resides in the zoneminder install. I'll try to restore that and see what happens.

Ok thanks.

Last night I had to stop Zoneminder, and when I restarted it, it didn't come back up. I'm getting these errors in the log: Starting ZoneMinder: DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110. May 23 14:09:45 18d28a2717c6 zmpkg[1040]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/share/perl5/ZoneMinder/Database.pm line 110. Can't call method "prepare_cached" on an undefined value at /usr/share/perl5/ZoneMinder/Config.pm line 96. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder/Config.pm line 147. Compilation failed in require at /usr/share/perl5/ZoneMinder.pm line 33. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder.pm line 33. Compilation failed in require at /usr/bin/zmpkg.pl line 34. BEGIN failed--compilation aborted at /usr/bin/zmpkg.pl line 34. May 23 14:09:45 18d28a2717c6 zmpkg[1040]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) error val:] ZoneMinder failed to start *** /etc/my_init.d/40_firstrun.sh failed with status 255 *** Killing all processes... May 23 14:09:45 18d28a2717c6 syslog-ng[41]: syslog-ng shutting down; version='3.25.1' I've found a post with a DBI Connect error and was able to start zoneminder with the a custom variable and start mysqld in safe mode. Then it produced an error log with this error: InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. What can I do to correct this?

I have Nextcloud 3.03 running on Win10. I'm getting the 413 request entity too large error. I have the max client body size set to 100M on the various *.conf files. I'm running Unraid 6.9 beta 35. Those changes did nothing. I've uninstalled and reinstalled the client on Windows. Has anyone had this problem and fixed it on version 3?

Update: The parity rebuild completed successfully. The 3rd disk that gave an error during parity rebuild was fine once parity completed. The 2nd disk is being rebuilt. Hopefully the BIOS update helps and if not will upgrade to beta. Thanks for your help.

As the parity drive is being rebuilt, I get another read error on one of the disks making it 3 out of 5 disks getting read errors. Is it possible the sata controller is going bad? Also, this is happening as the parity is being rebuilt. Do I risk any damage here? I can see the progress in the lower corner, but my main tab is not showing the array and rebuild info.

So I upgraded the Bios, and upon booting no read errors were found. However, the 2 drives in question remain disabled. Spinning them back up does nothing. How do I re-enable them?