Pi Bullseye Update Failed :(

I just tried to do the update of the NextCloudPi docker container running on my Pi3 under HypriotOS and it’s all gone wrong :frowning:

I stopped the container and removed it, pulled the new Bullseye image and did the usual commands to install it using the previous mounted data volume. If I look in the logs of the container I see the following:

Conf php7.3-fpm disabled.,
To activate the new configuration, you need to run:,
  service apache2 reload,
Enabling conf php7.4-fpm.,
To activate the new configuration, you need to run:,
  service apache2 reload,
Starting PHP-fpm,
Starting Apache,
Starting mariaDB,
2022-04-04 18:28:28 0 [Note] mysqld (mysqld 10.5.12-MariaDB-0+deb11u1) starting as process 143 ...,
2022-04-04 18:28:28 0 [Warning] The parameter innodb_file_format is deprecated and has no effect. It may be removed in future releases. See https://mariadb.com/kb/en/library/xtradbinnodb-file-format/,
2022-04-04 18:28:28 0 [Warning] The parameter innodb_buffer_pool_instances is deprecated and has no effect.,
2022-04-04 18:28:28 0 [Note] InnoDB: Uses event mutexes,
2022-04-04 18:28:28 0 [Note] InnoDB: Compressed tables use zlib 1.2.11,
2022-04-04 18:28:28 0 [Note] InnoDB: Number of pools: 1,
2022-04-04 18:28:28 0 [Note] InnoDB: Using generic crc32 instructions,
2022-04-04 18:28:28 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts),
2022-04-04 18:28:29 0 [Note] InnoDB: Using Linux native AIO,
2022-04-04 18:28:29 0 [Note] InnoDB: Initializing buffer pool, total size = 268435456, chunk size = 134217728,
2022-04-04 18:28:29 0 [Note] InnoDB: Completed initialization of buffer pool,
2022-04-04 18:28:29 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.3.34.,
2022-04-04 18:28:29 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error,
2022-04-04 18:28:29 0 [Note] InnoDB: Starting shutdown...,
2022-04-04 18:28:29 0 [ERROR] Plugin 'InnoDB' init function returned error.,
2022-04-04 18:28:29 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.,
2022-04-04 18:28:29 0 [Note] Plugin 'FEEDBACK' is disabled.,
2022-04-04 18:28:29 0 [ERROR] Unknown/unsupported storage engine: InnoDB,
2022-04-04 18:28:29 0 [ERROR] Aborting,
Starting PHP-fpm,
Starting Apache,
Starting mariaDB,
2022-04-04 18:41:01 0 [Note] mysqld (mysqld 10.5.12-MariaDB-0+deb11u1) starting as process 124 ...,
2022-04-04 18:41:01 0 [Warning] The parameter innodb_file_format is deprecated and has no effect. It may be removed in future releases. See https://mariadb.com/kb/en/library/xtradbinnodb-file-format/,
2022-04-04 18:41:01 0 [Warning] The parameter innodb_buffer_pool_instances is deprecated and has no effect.,
2022-04-04 18:41:01 0 [Note] InnoDB: Uses event mutexes,
2022-04-04 18:41:01 0 [Note] InnoDB: Compressed tables use zlib 1.2.11,
2022-04-04 18:41:01 0 [Note] InnoDB: Number of pools: 1,
2022-04-04 18:41:01 0 [Note] InnoDB: Using generic crc32 instructions,
2022-04-04 18:41:01 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts),
2022-04-04 18:41:01 0 [Note] InnoDB: Using Linux native AIO,
2022-04-04 18:41:01 0 [Note] InnoDB: Initializing buffer pool, total size = 268435456, chunk size = 134217728,
2022-04-04 18:41:01 0 [Note] InnoDB: Completed initialization of buffer pool,
2022-04-04 18:41:01 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.3.34.,
2022-04-04 18:41:01 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error,
2022-04-04 18:41:01 0 [Note] InnoDB: Starting shutdown...,
2022-04-04 18:41:01 0 [ERROR] Plugin 'InnoDB' init function returned error.,
2022-04-04 18:41:01 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.,
2022-04-04 18:41:01 0 [Note] Plugin 'FEEDBACK' is disabled.,
2022-04-04 18:41:01 0 [ERROR] Unknown/unsupported storage engine: InnoDB,
2022-04-04 18:41:01 0 [ERROR] Aborting,

Is there any way I can get things back again, or do I have to stop everything, move the volume folder to somewhere different and then start again and try to migrate the stored files and folders back in again?

I’m not sure what the crash that the log is talking about may be. This came up immediately when I tried to access after starting the new container, and the old container was running OK before and to my knowledge was as up to date as the internal updater allowed.

If I try to access the web interface I get this:

Internal Server Error

The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the server log.

Can it be recovered or is it a rebuild job? I’m no expert on docker, so guidance is needed please!

I don’t know, I think it should be recoverable by removing the old and pulling the new image

It looks like it’s run the upgrade from that log, which commands did you use?