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."