Container start issue

Z

Zashtys

New Member
Apr 2, 2020
3
0
1
30
I just started using containers and I ran it then shut it off and now it won't start again. Any help would be appreciated as I can't get any further than this.

Code: 
root@parrottrepairs:~# lxc-start -n 102 -F
lxc-start: 102: conf.c: run_buffer: 352 Script exited with status 32
lxc-start: 102: start.c: lxc_init: 897 Failed to run lxc.hook.pre-start for container "102"
lxc-start: 102: start.c: __lxc_start: 2032 Failed to initialize container "102"
Segmentation fault
root@parrottrepairs:~# pct fsck 102
fsck from util-linux 2.33.1
/dev/mapper/pve-vm--102--disk--1: clean, 53089/1310720 files, 390827/5242880 blocks
root@parrottrepairs:~# systemctl status pve-container@102.service
● pve-container@102.service - PVE LXC Container: 102
   Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-04-01 17:15:55 MDT; 26s ago
     Docs: man:lxc-start
           man:lxc
           man:pct
  Process: 23263 ExecStart=/usr/bin/lxc-start -n 102 (code=exited, status=1/FAILURE)

Apr 01 17:15:55 parrottrepairs systemd[1]: Starting PVE LXC Container: 102...
Apr 01 17:15:55 parrottrepairs lxc-start[23263]: lxc-start: 102: lxccontainer.c: wait_on_daemonized_start: 865 No such file or directory - Failed to receive the container state
Apr 01 17:15:55 parrottrepairs lxc-start[23263]: lxc-start: 102: tools/lxc_start.c: main: 329 The container failed to start
Apr 01 17:15:55 parrottrepairs lxc-start[23263]: lxc-start: 102: tools/lxc_start.c: main: 332 To get more details, run the container in foreground mode
Apr 01 17:15:55 parrottrepairs lxc-start[23263]: lxc-start: 102: tools/lxc_start.c: main: 335 Additional information can be obtained by setting the --logfile and --logpriority options
Apr 01 17:15:55 parrottrepairs systemd[1]: pve-container@102.service: Control process exited, code=exited, status=1/FAILURE
Apr 01 17:15:55 parrottrepairs systemd[1]: pve-container@102.service: Failed with result 'exit-code'.
Apr 01 17:15:55 parrottrepairs systemd[1]: Failed to start PVE LXC Container: 102.
root@parrottrepairs:~# lxc-start -n 102 -F
lxc-start: 102: conf.c: run_buffer: 352 Script exited with status 32
lxc-start: 102: start.c: lxc_init: 897 Failed to run lxc.hook.pre-start for container "102"
lxc-start: 102: start.c: __lxc_start: 2032 Failed to initialize container "102"
Segmentation fault

-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pvesr.service has successfully entered the 'dead' state.
Apr 01 17:19:01 parrottrepairs systemd[1]: Started Proxmox VE replication runner.
-- Subject: A start job for unit pvesr.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pvesr.service has finished successfully.
--
-- The job identifier is 100131.
Apr 01 17:20:00 parrottrepairs systemd[1]: Starting Proxmox VE replication runner...
-- Subject: A start job for unit pvesr.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pvesr.service has begun execution.
--
-- The job identifier is 100203.
Apr 01 17:20:00 parrottrepairs systemd[1]: pvesr.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pvesr.service has successfully entered the 'dead' state.
Apr 01 17:20:00 parrottrepairs systemd[1]: Started Proxmox VE replication runner.
-- Subject: A start job for unit pvesr.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pvesr.service has finished successfully.
--
-- The job identifier is 100203.
Apr 01 17:20:37 parrottrepairs pvedaemon[21236]: <root@pam> successful auth for user 'root@pam'
Apr 01 17:21:00 parrottrepairs systemd[1]: Starting Proxmox VE replication runner...
-- Subject: A start job for unit pvesr.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pvesr.service has begun execution.
--
-- The job identifier is 100275.
Apr 01 17:21:00 parrottrepairs systemd[1]: pvesr.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pvesr.service has successfully entered the 'dead' state.
Apr 01 17:21:00 parrottrepairs systemd[1]: Started Proxmox VE replication runner.
-- Subject: A start job for unit pvesr.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pvesr.service has finished successfully.
--
-- The job identifier is 100275.
 
I found the main issue.

Code: 
mount: /var/lib/lxc/102/rootfs/mnt/External: special device /dev/sdd2 does not exist.
mounting container failed
command 'mount /dev/sdd2 /var/lib/lxc/102/rootfs//mnt/External' failed: exit code 32

I tried to mount a zfs partition cause freenass won't recognize it no matter what I do.

Code: 
pct set 102 -mp0 /dev/sdd2,mp=/mnt/External
Annotation 2020-04-01 180214.jpgAnnotation 2020-04-01 180237.jpg
 
From what i've found during my couple hour research is that I can't mount my zfs external USB 3 hdd for some reason
 
You must log in or register to reply here.
Top Bottom