mattalat

Members
  • Posts

    34
  • Joined

  • Last visited

Everything posted by mattalat

  1. I tried time machine like a year ago and couldn't get it to work - excited to see if this allows it to function again!
  2. I attempted to update the plugin, and it showed a line or two in the update window before stalling for several minutes so I closed the window. Now there's a bar at the top of the screen saying "Attention - operation continues in background [00023828]" and the plugin status says "pending". It's been this way for 15 minutes now. Should I click the "bomb" icon to kill the process? Or keep waiting longer? Thanks.
  3. Totally agree - even the "Unraid Installation" instructions on the developer's website doesn't say anything about installing and setting up a database. Seems that the documentation is lacking.
  4. Not sure if this is the right place to ask - but has anyone successfully used this plugin to schedule shutdown of Ubiquiti devices (UDM, UNVR) upon power loss? I already have a UPS with Unraid shutdown enabled, but I saw a post from Squid from years ago suggesting that this plugin could then be used to shutdown other devices via SSH command. Would use the array stop as a trigger to send the command. Thanks!
  5. I think this may be what is causing my errors from above. Is there a recommended CA store app for the database?
  6. Sorry just to clarify - the app won’t work unless I install a separate DB app?
  7. I'm also having the same issue as sleepercells and some others above regarding the container being unable to start after a new install. Any ideas? Logs below: [2023-12-06 04:04:14] production.ERROR: SQLSTATE[HY000] [2002] No such file or directory (Connection: mysql, SQL: select * from information_schema.tables where table_schema = speedtest_tracker and table_name = migrations and table_type = 'BASE TABLE') {"exception":"[object] (Illuminate\\Database\\QueryException(code: 2002): SQLSTATE[HY000] [2002] No such file or directory (Connection: mysql, SQL: select * from information_schema.tables where table_schema = speedtest_tracker and table_name = migrations and table_type = 'BASE TABLE') at /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php:822) [stacktrace] #0 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(976): Illuminate\\Database\\Connection->runQueryCallback() #1 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(955): Illuminate\\Database\\Connection->tryAgainIfCausedByLostConnection() #2 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(778): Illuminate\\Database\\Connection->handleQueryException() #3 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(407): Illuminate\\Database\\Connection->run() #4 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(394): Illuminate\\Database\\Connection->select() #5 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Schema/MySqlBuilder.php(43): Illuminate\\Database\\Connection->selectFromWriteConnection() #6 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/DatabaseMigrationRepository.php(184): Illuminate\\Database\\Schema\\MySqlBuilder->hasTable() #7 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(700): Illuminate\\Database\\Migrations\\DatabaseMigrationRepository->repositoryExists() #8 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(140): Illuminate\\Database\\Migrations\\Migrator->repositoryExists() #9 /var/www/html/vendor/laravel/framework/src/Illuminate/Support/helpers.php(248): Illuminate\\Database\\Console\\Migrations\\MigrateCommand->Illuminate\\Database\\Console\\Migrations\\{closure}() #10 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(140): retry() #11 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(116): Illuminate\\Database\\Console\\Migrations\\MigrateCommand->repositoryExists() #12 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(84): Illuminate\\Database\\Console\\Migrations\\MigrateCommand->prepareDatabase() #13 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(633): Illuminate\\Database\\Console\\Migrations\\MigrateCommand->Illuminate\\Database\\Console\\Migrations\\{closure}() #14 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(83): Illuminate\\Database\\Migrations\\Migrator->usingConnection() #15 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(36): Illuminate\\Database\\Console\\Migrations\\MigrateCommand->handle() #16 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Util.php(41): Illuminate\\Container\\BoundMethod::Illuminate\\Container\\{closure}() #17 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(93): Illuminate\\Container\\Util::unwrapIfClosure() #18 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(35): Illuminate\\Container\\BoundMethod::callBoundMethod() #19 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php(662): Illuminate\\Container\\BoundMethod::call() #20 /var/www/html/vendor/laravel/framework/src/Illuminate/Console/Command.php(211): Illuminate\\Container\\Container->call() #21 /var/www/html/vendor/symfony/console/Command/Command.php(326): Illuminate\\Console\\Command->execute() #22 /var/www/html/vendor/laravel/framework/src/Illuminate/Console/Command.php(180): Symfony\\Component\\Console\\Command\\Command->run() #23 /var/www/html/vendor/symfony/console/Application.php(1081): Illuminate\\Console\\Command->run() #24 /var/www/html/vendor/symfony/console/Application.php(320): Symfony\\Component\\Console\\Application->doRunCommand() #25 /var/www/html/vendor/symfony/console/Application.php(174): Symfony\\Component\\Console\\Application->doRun() #26 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(201): Symfony\\Component\\Console\\Application->run() #27 /var/www/html/artisan(35): Illuminate\\Foundation\\Console\\Kernel->handle() #28 {main} [previous exception] [object] (PDOException(code: 2002): SQLSTATE[HY000] [2002] No such file or directory at /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php:65) [stacktrace] #0 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php(65): PDO->__construct() #1 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php(83): Illuminate\\Database\\Connectors\\Connector->createPdoConnection() #2 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php(48): Illuminate\\Database\\Connectors\\Connector->tryAgainIfCausedByLostConnection() #3 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/MySqlConnector.php(24): Illuminate\\Database\\Connectors\\Connector->createConnection() #4 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/ConnectionFactory.php(184): Illuminate\\Database\\Connectors\\MySqlConnector->connect() #5 [internal function]: Illuminate\\Database\\Connectors\\ConnectionFactory->Illuminate\\Database\\Connectors\\{closure}() #6 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(1319): call_user_func() #7 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(521): Illuminate\\Database\\Connection->getPdo() #8 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(416): Illuminate\\Database\\Connection->getPdoForSelect() #9 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(809): Illuminate\\Database\\Connection->Illuminate\\Database\\{closure}() #10 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(976): Illuminate\\Database\\Connection->runQueryCallback() #11 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(955): Illuminate\\Database\\Connection->tryAgainIfCausedByLostConnection() #12 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(778): Illuminate\\Database\\Connection->handleQueryException() #13 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(407): Illuminate\\Database\\Connection->run() #14 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(394): Illuminate\\Database\\Connection->select() #15 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Schema/MySqlBuilder.php(43): Illuminate\\Database\\Connection->selectFromWriteConnection() #16 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/DatabaseMigrationRepository.php(184): Illuminate\\Database\\Schema\\MySqlBuilder->hasTable() #17 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(700): Illuminate\\Database\\Migrations\\DatabaseMigrationRepository->repositoryExists() #18 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(140): Illuminate\\Database\\Migrations\\Migrator->repositoryExists() #19 /var/www/html/vendor/laravel/framework/src/Illuminate/Support/helpers.php(248): Illuminate\\Database\\Console\\Migrations\\MigrateCommand->Illuminate\\Database\\Console\\Migrations\\{closure}() #20 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(140): retry() #21 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(116): Illuminate\\Database\\Console\\Migrations\\MigrateCommand->repositoryExists() #22 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(84): Illuminate\\Database\\Console\\Migrations\\MigrateCommand->prepareDatabase() #23 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(633): Illuminate\\Database\\Console\\Migrations\\MigrateCommand->Illuminate\\Database\\Console\\Migrations\\{closure}() #24 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(83): Illuminate\\Database\\Migrations\\Migrator->usingConnection() #25 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(36): Illuminate\\Database\\Console\\Migrations\\MigrateCommand->handle() #26 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Util.php(41): Illuminate\\Container\\BoundMethod::Illuminate\\Container\\{closure}() #27 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(93): Illuminate\\Container\\Util::unwrapIfClosure() #28 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(35): Illuminate\\Container\\BoundMethod::callBoundMethod() #29 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php(662): Illuminate\\Container\\BoundMethod::call() #30 /var/www/html/vendor/laravel/framework/src/Illuminate/Console/Command.php(211): Illuminate\\Container\\Container->call() #31 /var/www/html/vendor/symfony/console/Command/Command.php(326): Illuminate\\Console\\Command->execute() #32 /var/www/html/vendor/laravel/framework/src/Illuminate/Console/Command.php(180): Symfony\\Component\\Console\\Command\\Command->run() #33 /var/www/html/vendor/symfony/console/Application.php(1081): Illuminate\\Console\\Command->run() #34 /var/www/html/vendor/symfony/console/Application.php(320): Symfony\\Component\\Console\\Application->doRunCommand() #35 /var/www/html/vendor/symfony/console/Application.php(174): Symfony\\Component\\Console\\Application->doRun() #36 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(201): Symfony\\Component\\Console\\Application->run() #37 /var/www/html/artisan(35): Illuminate\\Foundation\\Console\\Kernel->handle() #38 {main} "} s6-rc: warning: unable to start service laravel-automations: command exited 1 /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. prog: fatal: stopping the container. In Connection.php line 822: SQLSTATE[HY000] [2002] No such file or directory (Connection: mysql, SQL: s elect * from information_schema.tables where table_schema = speedtest_track er and table_name = migrations and table_type = 'BASE TABLE') In Connector.php line 65: SQLSTATE[HY000] [2002] No such file or directory
  8. File editing does not work on 6.12.4. I'm not sure exactly when this broke, but now when I try to click on yaml files to edit it just shows a blank square.
  9. Regarding exclusive shares - I currently have my appdata folder set to cache-only and mount my docker configs to /mnt/cache/appdata (rather than /mnt/user/appdata) to bypass FUSE. It sounds like going forward I don't need to do this? Is it fine to leave my current settings or should I switch to /mnt/user/appdata?
  10. Any update when an 6.12 RC compatible version will be available on the community apps page?
  11. Just chiming in same issue with update all button. It used to just occasionally do one of the images again, one time, and then stop, but the most recent time it went through all the images that had been updated maybe 3 or 4 times before stopping. No errors in Docker filesystem with scrub.
  12. Long term, everything will be SSD. Maybe not now, maybe not in 5 years, but 10+? Spinning platters are on their way out, much like ICE cars. To survive, unraid needs to pivot into a parity method that works with SSDs (probably easy), but also - focus on unraid's other huge strength: Easy GUI management of a home server! I was drawn to unraid not for it's unique parity abilities, but rather because of its straightforward management of docker containers and VMs, with a helpful and active community to provide support. The first step towards getting more people (noobs) like me into the ecosystem is to do away with the requirement to start an array to run docker containers. Sure you can plug in a dummy USB for a cache-only build, but why even make that a requirement? Make it easier for idiots like me to make this work without involving silly hardware hacks. Am I crazy?
  13. @JorgeBI've attached diagnostics to this after the fix. Can you please confirm that the df output looks OK? Sorry I'm a noob. wyse-diagnostics-20230404-2217.zip
  14. Ok update: I tried setting the share to Cache: Prefer and having mover send everything back to the cache drive, in the hopes of then sending all the data back to the array and seeing if unraid would then "see" the data on it. Unfortunately the mover error'd out after one file and the array drive was then seeing as unmountable due to a filesystem error. I did xfs_repair on the drive and now it's seeing everything as normal, all files visible on the array drive and utilization is correct. Do you think this is the sign of a bad drive or connector? What could have caused the file system error? Thanks.
  15. To do this - do I just turn off hardlinks in global drive settings? If I do that, when I turn it back on will hardlinks be in tact?
  16. More info: after rebooting the GUI seems to "remember" the newer 7 gb file I added, as used space remained 35 gb. I should have mentioned that I swapped SATA ports during the reboot that caused the issue. I switched it back and the problem persisted, so I didn't think it was relevant.
  17. This is apparently a known problem, however I can't find any bug reports about it. On an array drive (SATA drive, XFS file system) the "free space" and "used space" is dramatically wrong. I've attached screenshot of the main tab showing 27.9gb used, a screenshot of Dynamix File Manager showing the true used space (822 gb). The user shares calculation also shows the correct usage (screenshot attached as well. I've confirmed all files are there and accessible. I've attached diagnostics. Other, potentially helpful info: when I first installed the drive and ran the mover, everything appeared correct. Only after restarting did it display incorrectly. If I add new files to the array drive, unraid GUI seems to acknowledge their existence, ie. used space increased from 27.9 to 35 after adding a 7 gb file. It doesn't acknowledge the older files however. Edit: one other piece of info - I used the trash guides to utilize hardlinks for most of these files if that makes a difference. Thanks. wyse-diagnostics-20230401-2130.zip
  18. I was running a cache-only build, then yesterday added an array drive and had the mover transfer my media folder to it. It all went smoothly, and Unraid was reporting the correct disk utilization in the GUI. Today I rebooted the server after swapping out a cable, and now the GUI is reporting only 27.9 gb used when there is actually 822 gb used out of 4 tb. All the files are there and everything is working correctly. Dynamix File Manager also reports 822 gb used. See attached screenshots and diagnostics. Thanks! wyse-diagnostics-20230401-2130.zip
  19. Searched through all the comments and couldn't find an answer - also I apologize if this is a dumb question. What does the autotrim feature do? How is it different from scheduling trim?
  20. USB 3.0. Attached screenshot of UD settings page and diagnostics. wyse-diagnostics-20230318-2050.zip