RodWorks

I don't know if it actually rebooted, happened at 1 am so, I wasn't watching. Just see a parity is running since then. Was just curious if the logs showed anything.

Been running 7.0 for a month or so without issue, however, in the last 48 hours I've had 2 crash instances where a parity check starts randomly. System seems to run fine otherwise, I can't make out anything from the logs. Thanks for any input. unraid-syslog-20250225-1738.zip unraid-diagnostics-20250225-1247.zip

File? Not sure what you're referring to. It's nothing that I put there intentionally. Just posted looking for some help as FCP suggested.

Your flash drive has possible corruption on /boot/config/unraid_notify.cfg. Post your diagnostics in the forum for more assistance. Checking to see if this is legit corruption....Thanks for the help. unraid-diagnostics-20240404-1024.zip

Copy that, thank you for your time and advice. Everything is up and running again!

root@Unraid:~# btrfs dev stats /mnt/cache [/dev/sdd1].write_io_errs 0 [/dev/sdd1].read_io_errs 0 [/dev/sdd1].flush_io_errs 0 [/dev/sdd1].corruption_errs 0 [/dev/sdd1].generation_errs 0 [/dev/sde1].write_io_errs 6575101 [/dev/sde1].read_io_errs 13546 [/dev/sde1].flush_io_errs 121230 [/dev/sde1].corruption_errs 0 [/dev/sde1].generation_errs 0 so is this a pool cache failing? Or just do the delete and recreate and check after that?

Good morning, getting this error which has kept my docker from loading. Appreciate any help. unraid-diagnostics-20230823-1024.zip

Thank you, sir!

Recently upgraded both cache drives and restored app data and all seemed to be working fine until a recent restart. After boot the array didn't automatically mount and was looking for the old cache drives. I selected the new ones, but it says emulated/disabled for both new drives. unraid-diagnostics-20230114-0505.zip

Anyone have a link to the prior version until this one gets worked out? Checked the docker hub and there's no archive. Edit: Moved to the Selfhosters Shinobi container. No issues any more.

I deleted the storage drive manually again and set it to delete after 2 days just to see if it would start deleting again. Appears that it isn't still. Also, restarted Maria DB and made sure it's connected in the logs. What's interesting is the Shinobi UI shows a different storage capacity than the drive itself shows. The Shinobi capacity is consistent with 2 days of recordings at 250 gb, while the drive is actually at 1.72 tb and growing consistent with the time since I wiped it last. Edit: Just checked the files on the drive and they go back to 4/19 even though my settings say to delete after 2 days. However, I can't access them in the Shinobi UI even though they're visible files on the drive.

Ever since I updated the container 2 months ago, Shinobi has been running out of space and not deleting old files. I thought I had something messed up so I deleted all the recordings and double checked the settings to delete after 30 days. Now it's run over again and locked up at max storage. Only thing I changed was updating the container. Not sure what's going on. Anyone else with the issue?

Thanks, appreciate the feedback.

I see there's an update on the docker container, just making sure there's no issues before updating? What are the changes?

This is what's getting written to the log repeatedly. ,"message":"/appinfo/app.php is deprecated, use \\OCP\\AppFramework\\Bootstrap\\IBootstrap on the application class instead."

Ok, prefer is not an option.. I'll see if I can sort the errors out, otherwise it's gotta go.

Ok, I guess that makes sense. What's a solution to this issue? Why doesn't Nextcloud write logs to the appdata share?

Not on my Nextcloud data share, keeps one of my drives and parity spun up 24/7 even though mover only runs at 0200. Nextcloud.log updates every minute. If I stop the container the drives spin down normally.

I just want to understand how Nextcloud can write directly to a share that is set to write to a cache drive first....

I realize this, but only when the mover runs correct? There's a nextcloud.log inside the data folder that's being written to constantly which seems to be the issue. The finder screenshot is what's inside the data share of Nextcloud. You can see the .log file there along with appdata files.

Can someone explain why this container is all the sudden constantly writing log files to my array data share /mnt/user/Nextcloud/ even though the share is set to "yes" use cache pool? I have the container configured to use /mnt/user/appdata/nextcloud for everything config related, but I'm finding all kinds of appdata/config related files on the data share. This has just started in the past few months (keeps my disk 9 and parity always spun up).

Update: System booted and ran perfect with each CPU running solo in socket 0. After that I put a CPU back in socket 1 (reversed the order now) and the system is running fine again. I do still have 32 gb (4 x 8gb) pulled from the system. Hoping one is the problem. Still lost. unraid-diagnostics-20201007-1005.zip

Had the first issue about a month ago, when I randomly found Unraid crashed, upon restart I got this error. I recreated my USB drive and it booted up normally and worked fine until yesterday. Now, I'm getting the crashes and errors more often, but was able to get unraid to boot in Web GUI mode. I'm also seeing this error on boot sometimes. I removed half of my 64 GB of ram to try and isolate a bad ram module. However, I'm still seeing the errors booting with either half of the ram removed. Also, on the last boot, the system booted up running on only one processor and half the ram. So, any ideas on where to start troubleshooting this issue? unraid-diagnostics-20201006-2253.zip

I'm having an issue with all my camera feeds constantly dying and reconnecting. This Reddit post talks about this issue. Has anyone fixed this issue with the space invader container?

Where do I send the bug report?