Hello guys,

 

I guess it's the wrong section, but I couldn't find a matching topic in the docker category.

 

After swapping some drives I realized, that the docker Postgres_immich doesn't start anymore and now I can't access Immich anymore. I'm not sure if it was already before or after swapping the drives and changing the filesystem from xfs to zfs.

 

 

Here is the log from the docker, I hope someone can help me.

 

2024-07-17 14:05:24.873 CEST [1] LOG:  starting PostgreSQL 16.1 (Debian 16.1-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2024-07-17 14:05:24.873 CEST [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2024-07-17 14:05:24.874 CEST [1] LOG:  listening on IPv6 address "::", port 5432
2024-07-17 14:05:24.875 CEST [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-07-17 14:05:24.885 CEST [28] LOG:  database system was shut down at 2024-06-21 23:23:57 CEST
2024-07-17 14:05:24.886 CEST [28] LOG:  unexpected pageaddr 0/E6DD8000 in WAL segment 000000010000000100000020, LSN 1/20DD8000, offset 14516224
2024-07-17 14:05:24.886 CEST [28] LOG:  invalid checkpoint record
2024-07-17 14:05:24.886 CEST [28] PANIC:  could not locate a valid checkpoint record
[2024-07-17T12:05:24Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91908".
[2024-07-17T12:05:24Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91907".
2024-07-17 14:05:24.887 CEST [1] LOG:  startup process (PID 28) was terminated by signal 6: Aborted
2024-07-17 14:05:24.887 CEST [1] LOG:  aborting startup due to startup process failure
2024-07-17 14:05:24.887 CEST [1] LOG:  database system is shut down
[2024-07-17T12:05:24Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91907/segments/f4972d6d-9ca8-4189-afb0-1cc169987b03".
[2024-07-17T12:05:24Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91907/segments/232e68f8-f503-485b-9dbb-db0a550c4b80".
[2024-07-17T12:05:24Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91907/segments/b19ec19c-74f5-4c92-9eac-a72b0dc855b4".
[2024-07-17T12:05:24Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91907/segments/7efe88b7-0578-468d-825b-ddd8b1b096a2".
[2024-07-17T12:05:24Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91907/segments/9c779f11-e0ee-4aa1-8727-af6fa2360d08".
[2024-07-17T12:05:24Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91907/segments/0d3d6bbb-fa1a-4ba7-a9e5-73e55290415b".
[2024-07-17T12:05:24Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91907/segments/02fd6343-22f1-45e4-80bf-3b00fc39fc08".
[2024-07-17T12:05:24Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91907/segments/4b3760db-5475-4acf-9b3f-61782e5043e4".
[2024-07-17T12:05:24Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91907/segments/43dbb354-9283-4381-b51e-00b4a778b310".
[2024-07-17T12:05:24Z INFO  service::utils::clean] Delete outdated directory "pg_vectors/indexes/91907/segments/1f148544-831d-4411-8eb7-9f7a46ffc416".
2024-07-17 14:05:39.498 CEST [1] LOG:  starting PostgreSQL 16.1 (Debian 16.1-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2024-07-17 14:05:39.498 CEST [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2024-07-17 14:05:39.498 CEST [1] LOG:  listening on IPv6 address "::", port 5432
2024-07-17 14:05:39.500 CEST [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-07-17 14:05:39.509 CEST [29] LOG:  database system was shut down at 2024-06-21 23:23:57 CEST
2024-07-17 14:05:39.510 CEST [29] LOG:  unexpected pageaddr 0/E6DD8000 in WAL segment 000000010000000100000020, LSN 1/20DD8000, offset 14516224
2024-07-17 14:05:39.510 CEST [29] LOG:  invalid checkpoint record
2024-07-17 14:05:39.510 CEST [29] PANIC:  could not locate a valid checkpoint record
2024-07-17 14:05:39.510 CEST [1] LOG:  startup process (PID 29) was terminated by signal 6: Aborted
2024-07-17 14:05:39.510 CEST [1] LOG:  aborting startup due to startup process failure
[2024-07-17T12:05:39Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91908".
[2024-07-17T12:05:39Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91907".
2024-07-17 14:05:39.511 CEST [1] LOG:  database system is shut down
[2024-07-17T12:05:39Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91908/segments/ecf20f0e-e42e-4dbf-b0de-9d72b89cf48c".
[2024-07-17T12:05:39Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91908/segments/f8da567e-6625-4836-b385-9f7eb83836c8".
[2024-07-17T12:05:39Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91908/segments/95def546-bb10-4505-9ba4-bdcff0453bf4".
[2024-07-17T12:05:39Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91908/segments/bd938a5e-cf34-4173-bb91-46ef3bbe9f96".
[2024-07-17T12:05:39Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91908/segments/7224de17-c5d1-41f6-bf41-0acb63b84905".
[2024-07-17T12:05:39Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/91908/segments/1b4f28ca-3df0-425f-863f-0e41dafe8228".

PostgreSQL Database directory appears to contain a database; Skipping initialization

 

 

i solved it by copying a backup manually, but I would be happy if someone could tell me what exact the problem was. 

Do you mind explaining how you "copied a backup manually"?

I read the page at https://v1.102.0.archive.immich.app/docs/administration/backup-and-restore/, but I am not sure I have a valid "backup". I typically have an overnight rsync script copying all the strategic shares, so I know my files/photos are there, but I never took the time or risk to have anything but the default settings, which means photos will be all over the place with crappy filenames if I don't manage to restore my previous content.

Would a copy of the previous files of the appdata/postgres docker config be enough?