SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Docmost LXC startup for container failed #584

New Issue
Closed
opened 2025-11-20 04:50:38 -05:00 by saavagebueno · 5 comments
saavagebueno commented 2025-11-20 04:50:38 -05:00
Owner
Copy Link

Originally created by @domoticauser on GitHub (Feb 22, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Docmost LXC

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

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/docmost.sh)"

📝 Provide a clear and concise description of the issue.

I have used the script, but i have an error

⠦ Creating LXC Container
Message from syslogd@pve at Feb 22 12:37:47 ...
kernel:[ 436.011843] EXT4-fs (dm-15): failed to convert unwritten extents to written extents -- potential data loss! (inode 134098, error -5)
✔️ LXC Container 102 was successfully created.
⠙run_buffer: 571 Script exited with status 32
lxc_init: 845 Failed to run lxc.hook.pre-start for container "102"
__lxc_start: 2034 Failed to initialize container "102"
startup for container '102' failed
⠹
[ERROR] in line 1115: exit code 0: while executing command pct start "$CTID"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

After the error, I restarted, removed the container, and tried again. The same problem occurred. Another container (Domoticz) isn’t starting anymore. After removing Docmost, it runs again.

❌ Paste the full error output (if available).

[ERROR] in line 1115: exit code 0: while executing command pct start "$CTID"

🖼️ Additional context (optional).

No response

Originally created by @domoticauser on GitHub (Feb 22, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Docmost LXC ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/docmost.sh)" ### 📝 Provide a clear and concise description of the issue. I have used the script, but i have an error ⠦ Creating LXC Container Message from syslogd@pve at Feb 22 12:37:47 ... kernel:[ 436.011843] EXT4-fs (dm-15): failed to convert unwritten extents to written extents -- potential data loss! (inode 134098, error -5) ✔️ LXC Container 102 was successfully created. ⠙run_buffer: 571 Script exited with status 32 lxc_init: 845 Failed to run lxc.hook.pre-start for container "102" __lxc_start: 2034 Failed to initialize container "102" startup for container '102' failed ⠹ [ERROR] in line 1115: exit code 0: while executing command pct start "$CTID" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. After the error, I restarted, removed the container, and tried again. The same problem occurred. Another container (Domoticz) isn’t starting anymore. After removing Docmost, it runs again. ### ❌ Paste the full error output (if available). [ERROR] in line 1115: exit code 0: while executing command pct start "$CTID" ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 04:50:38 -05:00
saavagebueno commented 2025-11-20 04:50:39 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 22, 2025):

kernel:[ 436.011843] EXT4-fs (dm-15): failed to convert unwritten extents to written extents -- potential data loss! (inode 134098, error -5)

Your FS has Issues. Not the lxc

@MickLesk commented on GitHub (Feb 22, 2025): kernel:[ 436.011843] EXT4-fs (dm-15): failed to convert unwritten extents to written extents -- potential data loss! (inode 134098, error -5) Your FS has Issues. Not the lxc
saavagebueno commented 2025-11-20 04:50:39 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Feb 22, 2025):

whats funny is, how in the hell he ever concluded that script that does installation of one container can break his other ones...

@tremor021 commented on GitHub (Feb 22, 2025): whats funny is, how in the hell he ever concluded that script that does installation of one container can break his other ones...
saavagebueno commented 2025-11-20 04:50:40 -05:00
Author
Owner
Copy Link

@domoticauser commented on GitHub (Feb 22, 2025):

Thanks, It looks like my HD is broken. I just added a external HD, and that works fine.
How do i access the config file of docmost?

@domoticauser commented on GitHub (Feb 22, 2025): Thanks, It looks like my HD is broken. I just added a external HD, and that works fine. How do i access the config file of docmost?
saavagebueno commented 2025-11-20 04:50:40 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 22, 2025):

All stored in /opt/docmost

@MickLesk commented on GitHub (Feb 22, 2025): All stored in /opt/docmost
saavagebueno commented 2025-11-20 04:50:40 -05:00
Author
Owner
Copy Link

@domoticauser commented on GitHub (Feb 22, 2025):

Thanks! The file size was 0, i changed it to
FILE_UPLOAD_SIZE_LIMIT=10mb
Maybe good to set that default.

@domoticauser commented on GitHub (Feb 22, 2025): Thanks! The file size was 0, i changed it to FILE_UPLOAD_SIZE_LIMIT=10mb Maybe good to set that default.
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 bug
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#584
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?