SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-22 13:53:40 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Immich LXC fails to boot after first reboot - other LXCs built recently are fine #1710

New Issue
Closed
opened 2025-11-20 05:15:16 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 05:15:16 -05:00
Owner
Copy Link

Originally created by @Mithias-uk on GitHub (Aug 14, 2025).

✅ Have you read and understood the above guidelines?

Yes

📜 What is the name of the script you are using?

Immich

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

Decided to give Immich a go and whilst the script installs the LXC fine and it boots perfectly fine the first time round - subsequent boots after this fails consistently. I've not done anything special with the host, not with the script options (static IP only, stuff like that). Setup a different LXC just the other day and thats operating perfectly fine so appears to be something with Immich only. I've noted there another post about Immich LXC failing to start - don't know if linked?

Have done this twice now to make sure its not a fluke

🔄 Steps to reproduce the issue.

Run bash script as per usual, us advaanced options, static IP, no IPv6, network settings etc.
Start LXC, login first time and setup user
Attempt reboot of LXC for good measure
LXC fails to start

❌ Paste the full error output (if available).

Task output:-
run_buffer: 571 Script exited with status 25
lxc_init: 845 Failed to run lxc.hook.pre-start for container "117"
__lxc_start: 2034 Failed to initialize container "117"
TASK ERROR: startup for container '117' failed

Systemlog Output (might be wrong attempt but its broadly repeated each time):-
Aug 14 13:46:45 pve pvedaemon[1142]: root@pam starting task UPID:pve:0001DAD0:0003DB43:689DDAB5:vzstart:117:root@pam:
Aug 14 13:46:45 pve pvedaemon[121552]: starting CT 117: UPID:pve:0001DAD0:0003DB43:689DDAB5:vzstart:117:root@pam:
Aug 14 13:46:45 pve systemd[1]: Started pve-container@117.service - PVE LXC Container: 117.
Aug 14 13:46:46 pve kernel: EXT4-fs (dm-22): mounted filesystem 29c704e2-9aa9-4b16-9259-19b97236f03c r/w with ordered data mode. Quota mode: none.
Aug 14 13:46:46 pve pvedaemon[1143]: unable to get PID for CT 117 (not running?)
Aug 14 13:46:46 pve pvedaemon[121552]: startup for container '117' failed
Aug 14 13:46:46 pve pvedaemon[1142]: root@pam end task UPID:pve:0001DAD0:0003DB43:689DDAB5:vzstart:117:root@pam: startup for container '117' failed
Aug 14 13:46:47 pve kernel: EXT4-fs (dm-22): unmounting filesystem 29c704e2-9aa9-4b16-9259-19b97236f03c.
Aug 14 13:46:47 pve systemd[1]: pve-container@117.service: Main process exited, code=exited, status=1/FAILURE
Aug 14 13:46:47 pve systemd[1]: pve-container@117.service: Failed with result 'exit-code'.
Aug 14 13:46:47 pve systemd[1]: pve-container@117.service: Consumed 1.194s CPU time.
Aug 14 13:47:02 pve pvedaemon[1142]: root@pam starting task UPID:pve:0001DB76:0003E1F2:689DDAC6:vzstart:117:root@pam:
Aug 14 13:47:02 pve pvedaemon[121718]: starting CT 117: UPID:pve:0001DB76:0003E1F2:689DDAC6:vzstart:117:root@pam:
Aug 14 13:47:02 pve systemd[1]: Started pve-container@117.service - PVE LXC Container: 117.
Aug 14 13:47:03 pve kernel: EXT4-fs (dm-22): mounted filesystem 29c704e2-9aa9-4b16-9259-19b97236f03c r/w with ordered data mode. Quota mode: none.
Aug 14 13:47:03 pve pvedaemon[121718]: startup for container '117' failed
Aug 14 13:47:03 pve pvedaemon[1142]: root@pam end task UPID:pve:0001DB76:0003E1F2:689DDAC6:vzstart:117:root@pam: startup for container '117' failed
Aug 14 13:47:04 pve kernel: EXT4-fs (dm-22): unmounting filesystem 29c704e2-9aa9-4b16-9259-19b97236f03c.

🖼️ Additional context (optional).

No response

Originally created by @Mithias-uk on GitHub (Aug 14, 2025). ### ✅ Have you read and understood the above guidelines? Yes ### 📜 What is the name of the script you are using? Immich ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Decided to give Immich a go and whilst the script installs the LXC fine and it boots perfectly fine the first time round - subsequent boots after this fails consistently. I've not done anything special with the host, not with the script options (static IP only, stuff like that). Setup a different LXC just the other day and thats operating perfectly fine so appears to be something with Immich only. I've noted there another post about Immich LXC failing to start - don't know if linked? Have done this twice now to make sure its not a fluke ### 🔄 Steps to reproduce the issue. Run bash script as per usual, us advaanced options, static IP, no IPv6, network settings etc. Start LXC, login first time and setup user Attempt reboot of LXC for good measure LXC fails to start ### ❌ Paste the full error output (if available). Task output:- run_buffer: 571 Script exited with status 25 lxc_init: 845 Failed to run lxc.hook.pre-start for container "117" __lxc_start: 2034 Failed to initialize container "117" TASK ERROR: startup for container '117' failed Systemlog Output (might be wrong attempt but its broadly repeated each time):- Aug 14 13:46:45 pve pvedaemon[1142]: <root@pam> starting task UPID:pve:0001DAD0:0003DB43:689DDAB5:vzstart:117:root@pam: Aug 14 13:46:45 pve pvedaemon[121552]: starting CT 117: UPID:pve:0001DAD0:0003DB43:689DDAB5:vzstart:117:root@pam: Aug 14 13:46:45 pve systemd[1]: Started pve-container@117.service - PVE LXC Container: 117. Aug 14 13:46:46 pve kernel: EXT4-fs (dm-22): mounted filesystem 29c704e2-9aa9-4b16-9259-19b97236f03c r/w with ordered data mode. Quota mode: none. Aug 14 13:46:46 pve pvedaemon[1143]: unable to get PID for CT 117 (not running?) Aug 14 13:46:46 pve pvedaemon[121552]: startup for container '117' failed Aug 14 13:46:46 pve pvedaemon[1142]: <root@pam> end task UPID:pve:0001DAD0:0003DB43:689DDAB5:vzstart:117:root@pam: startup for container '117' failed Aug 14 13:46:47 pve kernel: EXT4-fs (dm-22): unmounting filesystem 29c704e2-9aa9-4b16-9259-19b97236f03c. Aug 14 13:46:47 pve systemd[1]: pve-container@117.service: Main process exited, code=exited, status=1/FAILURE Aug 14 13:46:47 pve systemd[1]: pve-container@117.service: Failed with result 'exit-code'. Aug 14 13:46:47 pve systemd[1]: pve-container@117.service: Consumed 1.194s CPU time. Aug 14 13:47:02 pve pvedaemon[1142]: <root@pam> starting task UPID:pve:0001DB76:0003E1F2:689DDAC6:vzstart:117:root@pam: Aug 14 13:47:02 pve pvedaemon[121718]: starting CT 117: UPID:pve:0001DB76:0003E1F2:689DDAC6:vzstart:117:root@pam: Aug 14 13:47:02 pve systemd[1]: Started pve-container@117.service - PVE LXC Container: 117. Aug 14 13:47:03 pve kernel: EXT4-fs (dm-22): mounted filesystem 29c704e2-9aa9-4b16-9259-19b97236f03c r/w with ordered data mode. Quota mode: none. Aug 14 13:47:03 pve pvedaemon[121718]: startup for container '117' failed Aug 14 13:47:03 pve pvedaemon[1142]: <root@pam> end task UPID:pve:0001DB76:0003E1F2:689DDAC6:vzstart:117:root@pam: startup for container '117' failed Aug 14 13:47:04 pve kernel: EXT4-fs (dm-22): unmounting filesystem 29c704e2-9aa9-4b16-9259-19b97236f03c. ### 🖼️ Additional context (optional). _No response_
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1710
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?