bigdave

Members
  • Posts

    39
  • Joined

  • Last visited

Everything posted by bigdave

  1. Done. New diag attached. unraid-diagnostics-20240122-1711.zip
  2. Will the data on those be safe or should I back them up first?
  3. I've read all the other posts I can find on how to replace a failing cache pool drive but they don't seem to work for me. What I have tried is, run balance, shut down array, replace bad drive with a new drive, start array, I get an error that I can't start the array and that the Cache pool BTRFS missing device(s) even if I try to specify the new drive, it says too many missing and can't start the array. I have two drives and they are in RAID1 at least in the GUI. What am I missing on how to replace a cache pool drive? I have both drives in now so if needed I could make it a 3 drive pool. Thanks, bigdave
  4. Can this same process be used to downgrade firmware? I need to go to 16 to get TRIM support back.
  5. Changed it to Yes, same happens. Installing MariaDB/MySQL system tables in '/config/mysql' ... 2019-01-02 10:53:35 22395577351048 [ERROR] InnoDB: preallocating 12582912 bytes for file ./ibdata1 failed with error 95 2019-01-02 10:53:35 22395577351048 [ERROR] InnoDB: Could not set the file size of './ibdata1'. Probably out of disk space 2019-01-02 10:53:35 22395577351048 [ERROR] InnoDB: Database creation was aborted with error Generic error. You may need to delete the ibdata 1 file before trying to start up again. 2019-01-02 10:53:36 22395577351048 [ERROR] Plugin 'InnoDB' init function returned error. 2019-01-02 10:53:36 22395577351048 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2019-01-02 10:53:36 22395577351048 [ERROR] Unknown/unsupported storage engine: InnoDB 2019-01-02 10:53:36 22395577351048 [ERROR] Aborting
  6. root@unraid:/mnt/user/appdata/NginxProxyManager/log# more init_db.log Installing MariaDB/MySQL system tables in '/config/mysql' ... 2019-01-01 17:43:17 22792248212360 [ERROR] InnoDB: preallocating 12582912 bytes for file ./ibdata1 failed with error 95 2019-01-01 17:43:17 22792248212360 [ERROR] InnoDB: Could not set the file size of './ibdata1'. Probably out of disk space 2019-01-01 17:43:17 22792248212360 [ERROR] InnoDB: Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before tr ying to start up again. 2019-01-01 17:43:17 22792248212360 [ERROR] Plugin 'InnoDB' init function returned error. 2019-01-01 17:43:17 22792248212360 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2019-01-01 17:43:17 22792248212360 [ERROR] Unknown/unsupported storage engine: InnoDB 2019-01-01 17:43:18 22792248212360 [ERROR] Aborting Installation of system tables failed! Examine the logs in /config/mysql for more information. The problem could be conflicting information in an external my.cnf files. You can ignore these by doing: shell> /usr/bin/mysql_install_db --defaults-file=~/.my.cnf You can also try to start the mysqld daemon with: shell> /usr/bin/mysqld --skip-grant-tables --general-log & and use the command line tool /usr/bin/mysql to connect to the mysql database and look at the grant tables: shell> /usr/bin/mysql -u root mysql mysql> show tables; Try 'mysqld --help' if you have problems with paths. Using --general-log gives you a log in /config/mysql that may be helpful. The latest information about mysql_install_db is available at https://mariadb.com/kb/en/installing-system-tables-mysql_install_db You can find the latest source at https://downloads.mariadb.org and the maria-discuss email list at https://launchpad.net/~maria-discuss Please check all of the above before submitting a bug report at http://mariadb.org/jira /mnt/user/appdata is large enough for this.
  7. Yes and yes. Just tried deleting and reinstalling with the same result.
  8. I see this error in the init_db.log /mnt/user/appdata/NginxProxyManager/log# more init_db.log Installing MariaDB/MySQL system tables in '/config/mysql' ... 2018-12-27 14:32:02 22714951916424 [ERROR] InnoDB: preallocating 12582912 bytes for file ./ibdata1 failed with error 95 2018-12-27 14:32:02 22714951916424 [ERROR] InnoDB: Could not set the file size of './ibdata1'. Probably out of disk space 2018-12-27 14:32:02 22714951916424 [ERROR] InnoDB: Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again. 2018-12-27 14:32:03 22714951916424 [ERROR] Plugin 'InnoDB' init function returned error. 2018-12-27 14:32:03 22714951916424 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2018-12-27 14:32:03 22714951916424 [ERROR] Unknown/unsupported storage engine: InnoDB 2018-12-27 14:32:03 22714951916424 [ERROR] Aborting
  9. Went from 6.4.0 to 6.5.2 - no issues. Everything works, love the console menu choice on dockers!
  10. I'm having this same issue, logged into the docker to confirm it has access. Weird thing is some work fine and some don't (most don't) then I have to manually move them.
  11. Since the PhazE plugin has not been updated for the new dependancies it will not install them. Your best be going forward would be to switch to the docker.
  12. Need fixes for Sab 2.0 RC's as they will be final soon, SABYenc needs to be included now. Thanks!
  13. This is a plex issue they're not using the csrf_token variable on the form post for that page which is producing this error. I'll see if I can get them to fix or I'll just deal. Like I said plex works fine. I've had plex in a docker before and I just didn't see the point. Mods can close.
  14. You can /etc/rc.d/rc.plexmediaserver stop. My backup scripts still work fine. It's just this issue with the gui. It's not a big deal I'd just like to get it fixed.
  15. Plex works fine in 6.3 you just need to start it manually /etc/rc.d/rc.plexmediaserver start after updating the paths in /boot/config/plugins/plexmediaserver/settings.ini
  16. Phaze plugin changes the Library directory which I don't want to do, he removes application support directory, I don't want to risk any plex library issues. I don't see the point of docker other than to isolate dependency issues it still has access to the same resources and seems to just complicate things with having to map media drives so the paths match the existing library. At this point I just need to know if this a unraid issue or a plex issue. Like I said, Plex still makes this txz available and it still works fine just the UI is broken.
  17. Not really a fan of the docker, this is the plex official txz they still have available to download for unraid on their main site. This worked prior to 6.3.x and still works just the settings page has this issue. https://downloads.plex.tv/plex-media-server/1.4.2.3400-ab906953b/PlexMediaServer-1.4.2.3400-ab906953b-x64-UnRAID.txz I'm also not the only having this issue: https://forums.plex.tv/discussion/259334/cant-launch-plex-on-unraid-cant-seem-to-figure-out-error
  18. I'm not sure if this is a plex issue or a dynamics issue. I've opened a plex forum post as well: https://forums.plex.tv/discussion/259331/error-after-upgrade-to-6-3-x/p1?new=1 Warning: syntax error, unexpected END_OF_LINE, expecting '=' in /boot/config/plugins/plexmediaserver/settings.ini on line 2 in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(382) : eval()'d code on line I have to manually update /boot/config/plugins/plexmediaserver/settings.ini to get it to start. Then it works fine.
  19. This worked for my Install failed: Failed integrity test/404 issue. Thanks!
  20. I had this issue too. For some reason I had cron= in my crontab I just commented it out and no more error.
  21. No, plugins are horrible. I am using your unmenu package on 5.0 beta 13.