TwistedCarnivore

unbalanced installs and runs fine after the upgrade. fix common problems does not show any issues after installing unbalanced. upgrade assistant still shows and error with unbalanced after the upgrade. Must be something in the upgrade assistant causing it to report that problem. Disclaimer: This script is NOT definitive. There may be other issues with your server that will affect compatibility. Current unRaid Version: 6.12.8 Upgrade unRaid Version: 6.12.8 NOTE: You are currently running the latest version of unRaid. Checking for plugin updates OK: All plugins up to date Checking for plugin compatibility Issue Found: unbalanced.plg is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues. OK: All plugins are compatible Checking for extra parameters on emhttp OK: emhttp command in /boot/config/go contains no extra parameters Checking for disabled disks OK: No disks are disabled Checking installed RAM OK: You have 4+ Gig of memory Checking flash drive OK: Flash drive is read/write Checking for valid NETBIOS name OK: NETBIOS server name is compliant. Checking for ancient version of dynamix.plg OK: Dynamix plugin not found Checking for VM MediaDir / DomainDir set to be /mnt OK: VM domain directory and ISO directory not set to be /mnt Checking for mover logging enabled OK: Mover logging not enabled Checking for reserved name being used as a user share OK: No user shares using reserved names were found Checking for extra.cfg OK: /boot/config/extra.cfg does not exist Issues have been found with your server that may hinder the OS upgrade. You should rectify those problems before upgrading

I ran the update assistant twice a little while ago and got the same results. Removed the plugin and update assistant ran clean. Updating unraid now and will try and add unbalanced when it finishes.

Getting ready to upgrade unraid from 6.12.6 to 6.12.8. I ran the update assistant and got this error concerning unbalanced Issue Found: unbalanced.plg is not known to Community Applications. Compatibility for this plugin CANNOT be determined and it may cause you issues. Is this going to cause problems on the upgrade?

Did that again. It shows upgrading in the log when the container starts, but still showing same 10 extra files in integrity check. I did run all the occ commands that he showed in the discord post, and that didn't help either. Guess I just have a persistent poltergeist. Probably just wait for the next version to roll out and see what happens then . using keys found in /config/keys Initializing nextcloud 27.0.0.8 (this can take a while) ... Upgrading nextcloud from 27.0.0.8 ... Setting permissions Nextcloud is already latest version Initializing finished

No joy. root@snafu:~# docker exec -it nextcloud occ integrity:check-core - EXTRA_FILE: - core/js/tests/specs/appsSpec.js: - expected: - current: cf1ff76b5129943a1ffd6ea068ce6e8bc277718b9d0c81dccce47d723e1f290be20f197b6543f17f3b2ac78d8d4986354db4103de2b5e31c76e00e248984605b - core/l10n/et_EE.js: - expected: - current: 55e09a16c917b20c1bba2d5458aab6d4eb4c9a80a0480c7ca309db67a522c83682264d12fcfe6eb54d4120d04b4b90249a03d268b3adf2e7046db8a6229ce586 - core/l10n/et_EE.json: - expected: - current: 675629231727e9b6bc16463489466626476ae9571c5179c78c881e599e3ea991cec4dd9931c3c53bd731f8e0c57312fd31c6503a0b633a579c6bc9a71b5ecb3e - dist/files_trashbin-files_trashbin.js: - expected: - current: 24e537aff151f18ae18af31152bcfd7de9c96f0f6fdcca4c1ad975ece80bb35a2ab7d51c257af6a9762728d7688c9ba37a5359a950eb1e9f401d4b9d875d92b2 - dist/files_trashbin-files_trashbin.js.LICENSE.txt: - expected: - current: 2e40e4786aa1f3a96022164e12a5868e0c6a482e89b3642e1d5eea6502725061e2077786c6cd118905e499b56b2fc58e4efc34d6810ff96a56c54bf990790975 - dist/files_trashbin-files_trashbin.js.map: - expected: - current: 65c2a7ddc654364d8884aaee8af4e506da87e54ae82f011989d6b96a625b0dbfba14be6d6af545fa074a23ccf2cc29043a411dc3ac1f80a24955c8a9faa28754 - lib/private/Files/ObjectStore/NoopScanner.php: - expected: - current: 62d6c5360faf2c7fca90eaafa0e92f85502794a42a5993e2fe032c58b4089947773e588ad80250def78f268499e0e1d9b6b05bc8237cc946469cd6f1fb0b590c - lib/private/Updater/ChangesResult.php: - expected: - current: d2e964099dfd4c6d49ae8fc2c6cbc7d230d4f5c19f80804d5d28df5d5c65786a37ea6f554deacecad679d39dbba0d6bd6e4edadca292238f45f18f080277dad0 - lib/public/WorkflowEngine/IEntityCompat.php: - expected: - current: ea1856748e5fcf8a901597871f1708bdf28db69d6fa8771c70f38212f028b2ff744b04019230721c64b484675982d495a2c96d1175453130b4563c6a61942213 - lib/public/WorkflowEngine/IOperationCompat.php: - expected: - current: 6c09c15e9d855343cc33a682b95a827546fa56c20cc6a249774f7b11f75486159ebfe740ffcba2c9fa9342ab115e7bf99b8c25f71bb490c5d844da251b9751ed Restarted nextcloud and rescanned, still show the extra files.

Ran the command and restarted the container. Still showing the extra files. Would manually deleting the files hurt anything?

docker exec -it nextcloud occ db:add-missing-indices Worked this morning.

Checked for updates, and none showing. Technical information ===================== The following list covers which files have failed the integrity check. Please read the previous linked documentation to learn more about the errors and how to fix them. Results ======= - core - EXTRA_FILE - core/js/tests/specs/appsSpec.js - core/l10n/et_EE.js - core/l10n/et_EE.json - dist/files_trashbin-files_trashbin.js - dist/files_trashbin-files_trashbin.js.LICENSE.txt - dist/files_trashbin-files_trashbin.js.map - lib/private/Files/ObjectStore/NoopScanner.php - lib/private/Updater/ChangesResult.php - lib/public/WorkflowEngine/IEntityCompat.php - lib/public/WorkflowEngine/IOperationCompat.php Raw output ========== Array ( [core] => Array ( [EXTRA_FILE] => Array ( [core/js/tests/specs/appsSpec.js] => Array ( [expected] => [current] => cf1ff76b5129943a1ffd6ea068ce6e8bc277718b9d0c81dccce47d723e1f290be20f197b6543f17f3b2ac78d8d4986354db4103de2b5e31c76e00e248984605b ) [core/l10n/et_EE.js] => Array ( [expected] => [current] => 55e09a16c917b20c1bba2d5458aab6d4eb4c9a80a0480c7ca309db67a522c83682264d12fcfe6eb54d4120d04b4b90249a03d268b3adf2e7046db8a6229ce586 ) [core/l10n/et_EE.json] => Array ( [expected] => [current] => 675629231727e9b6bc16463489466626476ae9571c5179c78c881e599e3ea991cec4dd9931c3c53bd731f8e0c57312fd31c6503a0b633a579c6bc9a71b5ecb3e ) [dist/files_trashbin-files_trashbin.js] => Array ( [expected] => [current] => 24e537aff151f18ae18af31152bcfd7de9c96f0f6fdcca4c1ad975ece80bb35a2ab7d51c257af6a9762728d7688c9ba37a5359a950eb1e9f401d4b9d875d92b2 ) [dist/files_trashbin-files_trashbin.js.LICENSE.txt] => Array ( [expected] => [current] => 2e40e4786aa1f3a96022164e12a5868e0c6a482e89b3642e1d5eea6502725061e2077786c6cd118905e499b56b2fc58e4efc34d6810ff96a56c54bf990790975 ) [dist/files_trashbin-files_trashbin.js.map] => Array ( [expected] => [current] => 65c2a7ddc654364d8884aaee8af4e506da87e54ae82f011989d6b96a625b0dbfba14be6d6af545fa074a23ccf2cc29043a411dc3ac1f80a24955c8a9faa28754 ) [lib/private/Files/ObjectStore/NoopScanner.php] => Array ( [expected] => [current] => 62d6c5360faf2c7fca90eaafa0e92f85502794a42a5993e2fe032c58b4089947773e588ad80250def78f268499e0e1d9b6b05bc8237cc946469cd6f1fb0b590c ) [lib/private/Updater/ChangesResult.php] => Array ( [expected] => [current] => d2e964099dfd4c6d49ae8fc2c6cbc7d230d4f5c19f80804d5d28df5d5c65786a37ea6f554deacecad679d39dbba0d6bd6e4edadca292238f45f18f080277dad0 ) [lib/public/WorkflowEngine/IEntityCompat.php] => Array ( [expected] => [current] => ea1856748e5fcf8a901597871f1708bdf28db69d6fa8771c70f38212f028b2ff744b04019230721c64b484675982d495a2c96d1175453130b4563c6a61942213 ) [lib/public/WorkflowEngine/IOperationCompat.php] => Array ( [expected] => [current] => 6c09c15e9d855343cc33a682b95a827546fa56c20cc6a249774f7b11f75486159ebfe740ffcba2c9fa9342ab115e7bf99b8c25f71bb490c5d844da251b9751ed ) ) ) ) Screen shot of nextcloud admin page https://prnt.sc/-NXFxBW_Bk0u error.log nextcloud.log ngnix error.log snafu.tarfu.xyz-diagnostics-20230705-1339.zip

Installed the upgrade last night, not showing any upgrades available, restarted and still showing the extra files. Not too worried about it, will check again when the next upgrade comes out.

It did upgrade and runs fine. Security check shows code integrity issue. Technical information ===================== The following list covers which files have failed the integrity check. Please read the previous linked documentation to learn more about the errors and how to fix them. Results ======= - core - EXTRA_FILE - core/js/tests/specs/appsSpec.js - core/l10n/et_EE.js - core/l10n/et_EE.json - dist/files_trashbin-files_trashbin.js - dist/files_trashbin-files_trashbin.js.LICENSE.txt - dist/files_trashbin-files_trashbin.js.map - lib/private/Files/ObjectStore/NoopScanner.php - lib/private/Updater/ChangesResult.php - lib/public/WorkflowEngine/IEntityCompat.php - lib/public/WorkflowEngine/IOperationCompat.php Looks like files that don't need to be there any more.

I normally upgrade from cl as my connection sucks and the web interface normally times out in the middle of the upgrade. I tried to upgrade nextcloud from cl and got this error. root@snafu:~# docker exec -it nextcloud updater.phar OCI runtime exec failed: exec failed: unable to start container process: exec: "updater.phar": executable file not found in $PATH: unknown Any suggestions?

Works great on 6.11.5 Instructions for moving dashboard back to the left side works fine. 👍

The pi doesn't run docker currently. Is there a non docker install for this.

What would you use on a pi running pihole to sync with a docker instance on unraid running pihole synch as master. Unraid docker as master pi running pihole as slave

I have an issue with scrutiny causing read errors on spundown drives. If scrutiny tries to do a smart read on a drive that is spundown, unraid shows a read error. If it goes on long enough unraid will eventually deactivate the drive. After a drive is deactivated unraid starts seeing phantom drives and the drive mappings get totally screwed up. The phantom drives seems to be a known issue with scrutiny. Turning off spindown and the problem goes away. Somewhere the drives aren't getting the message to spin up prior to scrutiny trying to do a smart read. I think the problem is in scrutiny but hopefully this will help someone else having the same problem.