[still stuck] LXC won't start after Passing block storage to container

[GankUnlo]

EDIT 1: It seems CLI is the only option for passing block storage to my container. Follow the example provided; pct set <VMID> --mp<#> /dev/disk/by-id/<your disk ID + partition #>mp=<path to mount>

EDIT 2: this method worked for me, until I tried removing the 101 file server container and re-building it with a different root disk from zfs pool, now I can't reboot the container with the external HDD passed to it via previously working command

Edit 3: i'm wondering if upgrading proxmox is at the root of my troubles smh





Hello, i'm Stuck trying to add an external USB HDD to my LXC File Server.
I've deployed Proxmox Virtual Environment 6.0-4 onto an Odroid H2 with 8gb DDr4 and a 500 gb nVme Boot disk
I have a 120gb SSD (not yet utilized), and a 4tb USB HDD. I would like to attach the USB HDD to the LXC File Server 101. I also have a Domain Controller LXC created as well 102.





I thought following this guide. . . https://pve.proxmox.com/wiki/Physical_disk_to_kvm
or this ... https://petertaylor.me/passing-disk-proxmox-specific-vm/
Would help me but I'm stuck.

Both seemed promising, and I thought I was on the right track when my output showed

root@xkey:~# ls -l /dev/disk/by-id
total 0
lrwxrwxrwx 1 root root  9 Jan  7 20:03 ata-SanDisk_SSD_PLUS_120GB_1838DB803634 -> ../../sda
lrwxrwxrwx 1 root root 10 Jan  7 20:03 ata-SanDisk_SSD_PLUS_120GB_1838DB803634-part1 -> ../../sda1
lrwxrwxrwx 1 root root  9 Jan 22 20:37 ata-ST4000DM000-1F2168_Z30091R1 -> ../../sdb
lrwxrwxrwx 1 root root 10 Jan 22 20:37 ata-ST4000DM000-1F2168_Z30091R1-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Jan  7 20:03 dm-name-pve-root -> ../../dm-1
lrwxrwxrwx 1 root root 10 Jan  7 20:03 dm-name-pve-swap -> ../../dm-0
lrwxrwxrwx 1 root root 10 Jan 22 17:54 dm-name-pve-vm--101--disk--0 -> ../../dm-6
lrwxrwxrwx 1 root root 10 Jan 27 18:02 dm-name-pve-vm--102--disk--0 -> ../../dm-7
lrwxrwxrwx 1 root root 10 Jan  7 20:03 dm-uuid-LVM-lbHbk9d5xqWiJidZ7JVeKUa7pB7AQ6X5icimOheJ1N88Agzw4AznNg03CW7c0N22 -> ../../dm-1
lrwxrwxrwx 1 root root 10 Jan 27 18:02 dm-uuid-LVM-lbHbk9d5xqWiJidZ7JVeKUa7pB7AQ6X5IshG7xmjYEF4kRuXXX6WutfX9NiuVERU -> ../../dm-7
lrwxrwxrwx 1 root root 10 Jan  7 20:03 dm-uuid-LVM-lbHbk9d5xqWiJidZ7JVeKUa7pB7AQ6X5IsxlpgDlYxcL2fORJKkbjVkF2SePmcAT -> ../../dm-0
lrwxrwxrwx 1 root root 10 Jan 22 17:54 dm-uuid-LVM-lbHbk9d5xqWiJidZ7JVeKUa7pB7AQ6X5qNW6wQmTZB9e5EHXxT0ZnBjRlN5kkcUD -> ../../dm-6
lrwxrwxrwx 1 root root 15 Jan 27 18:02 lvm-pv-uuid-t9eMbC-bmI1-7UX6-zgvj-lt2Q-V5tS-wQJg3q -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 13 Jan  7 20:03 nvme-CT500P1SSD8_1932E2178EB9 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 Jan  7 20:03 nvme-CT500P1SSD8_1932E2178EB9-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Jan  7 20:03 nvme-CT500P1SSD8_1932E2178EB9-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Jan 27 18:02 nvme-CT500P1SSD8_1932E2178EB9-part3 -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 13 Jan  7 20:03 nvme-eui.000000000000000100a07519e2178eb9 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 Jan  7 20:03 nvme-eui.000000000000000100a07519e2178eb9-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Jan  7 20:03 nvme-eui.000000000000000100a07519e2178eb9-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Jan 27 18:02 nvme-eui.000000000000000100a07519e2178eb9-part3 -> ../../nvme0n1p3
lrwxrwxrwx 1 root root  9 Jan 22 20:37 wwn-0x5000c500501111d1 -> ../../sdb
lrwxrwxrwx 1 root root 10 Jan 22 20:37 wwn-0x5000c500501111d1-part1 -> ../../sdb1
lrwxrwxrwx 1 root root  9 Jan  7 20:03 wwn-0x5001b448b98d4a9f -> ../../sda
lrwxrwxrwx 1 root root 10 Jan  7 20:03 wwn-0x5001b448b98d4a9f-part1 -> ../../sda1

However I got an error there was no 101.conf in
/etc/pve/qemu-server

So I thought adding a line to /etc/pve/lxc/101.conf would be a better Idea .. I slipped in.

scsi0: /dev/disk/by-id/ata-ST400DM000-1F2168_Z30091R1

but that Didn't work so I tried

scsi0: /dev/disk/by-id/ata-ST400DM000-1F2168_Z30091R1:VM-101-DISK-1

This also is not working...



Anyone have any tips or pointers for me to check out i'm open to suggestion. thank you in advance

 

[t.lamprecht]

Hi,

I thought following this guide. . . https://pve.proxmox.com/wiki/Physical_disk_to_kvm

This is a guide for Virtual Machines, which cannot work for CT as is.

scsi0: /dev/disk/by-id/ata-ST400DM000-1F2168_Z30091R1

scsiX is a configuraiton key only available in Virtual Machines (VMs), so this cannot work.

See:
https://forum.proxmox.com/threads/container-with-physical-disk.42280/#post-203292
or
https://gist.github.com/Yub0/518097e1a9d179dba19a787b462f7dd2#gistcomment-2625690

For a guide working with Containers.

 

[GankUnlo]

hello,

thank you for the links. and suggestions. I can't say this left me feeling confident.
The first link was difficult to follow so I attempted the second link first.
However, even with clear instructions. this did not work for me either

Just as the post suggested
I stopped my LXC file server then...

root@xkey:~# lsusb
Bus 002 Device 003: ID 0bc2:3320 Seagate RSS LLC SRD00F2 [Expansion Desktop Drive]
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


root@xkey:~# ls -l /dev/bus/usb/002/003
crw-rw-r-- 1 root root 189, 130 Jan 22 20:37 /dev/bus/usb/002/003

So, based on this guide I should add

lxc.cgroup.devices.allow: c 189:* rwm
lxc.mount.entry: /dev/bus/usb/002/003 dev/bus/usb/002/003 none bind,optional,create=file

to my 101.conf

I've done this.

Restarted the LXC, and still don't see the drive visible on the file server, or in the GUI


I was really hoping for a step by step from proxmox. I guess i'm not crazy, this just doesn't exist anywhere. I don't understand why there isn't a mechanism in the GUI for what should be a relatively easy task.

i've followed the second link exactly . I didn't find the first link to be as easy to follow but i'lll give it another try i suppose. or scrap this whole project altogether. pretty frustrating adding a disk could be this hard.

 

[t.lamprecht]

I mean, as this is a HDD and not some general USB device you could also go the much more simpler way of passing through the whole block device:

pct set <VMID>  --mp0  /dev/disk/by-id/ata-ST400DM000-1F2168_Z30091R1,mp=/mnt/HDD,backup=0

Then the disk should get mounted to "/mnt/HD" inside the CT. Sorry for not recommending that from the beginning.

 

[GankUnlo]

Interesting...

This was the first command I tried before searching forum posts.
I wasn't able to get this command to work initially and I can't recall why at this moment. I went back and removed the previous lines from my 101.conf

stopped the container
and then..

pct set 101  --mp0  /dev/disk/by-id/ata-ST400DM000-1F2168_Z30091R1,mp=/mnt/HDD,backup=0

no errors ok good

then

root@xkey:~# pct start 101
Job for pve-container@101.service failed because the control process exited with error code.
See "systemctl status pve-container@101.service" and "journalctl -xe" for details.
command 'systemctl start pve-container@101' failed: exit code 1

also trying to start container from gui fails..

yes, If I recall, I tried this before, and had to remove the entire container and try again b/c I was never able to get it to start

Is there a way to revert the previous command so i can at least start the container again to continue testing? or am I going to have to delete it and start again?

 

[t.lamprecht]

also trying to start container from gui fails..

Are you sure that /dev/disk/by-id/ata-ST400DM000-1F2168_Z30091R1 is correct and exists:
ls -l /dev/disk/by-id/ata-ST400DM000-1F2168_Z30091R1

Because I just tried above with a USB pen drive successfully before recommending that to you.

If it exists, is there already a filesystem on it or is this a unformated/unpartitioned drive?
My pendrive is formatted to use the whole device as filesystem, if yours uses a specific partition you may want to use a path from:

ls -l /dev/disk/by-partuuid/

Is there a way to revert the previous command so i can at least start the container again to continue testing? or am I going to have to delete it and start again?

Yes: pct set 101 --delete mp0

 

[GankUnlo]

Yes: pct set 101 --delete mp0

Thank you

root@xkey:~# pct set 101 delete --mp0
Option mp0 requires an argument
400 unable to parse option
pct set <vmid> [OPTIONS]
root@xkey:~# pct set 101 delete  --mp0  /dev/disk/by-id/ata-ST400DM000-1F2168_Z30091R1,mp=/mnt/HDD,backup=0
400 too many arguments
pct set <vmid> [OPTIONS]
root@xkey:~# pct set 101 delete  --mp0
Option mp0 requires an argument
400 unable to parse option
pct set <vmid> [OPTIONS]

unable to start container

I should have mentioned previously, my apologies, yes my external HDD already has data on it. Not bootable, just an external expansion drive with my backups from a previous computer.

here is my edited output showing my desired disk

root@xkey:~# ls -l /dev/disk/by-id/
lrwxrwxrwx 1 root root  9 Jan 22 20:37 ata-ST4000DM000-1F2168_Z30091R1 -> ../../sdb
lrwxrwxrwx 1 root root 10 Jan 22 20:37 ata-ST4000DM000-1F2168_Z30091R1-part1 -> ../../sdb1

Output from below suggests the partition I want from external drive is not viewable by host?

root@xkey:~# ls -l /dev/disk/by-partuuid/
total 0
lrwxrwxrwx 1 root root 10 Jan  7 20:03 5d42689e-01 -> ../../sda1
lrwxrwxrwx 1 root root 15 Jan 27 18:02 7b1f8c51-3acd-4bb9-a904-cb802207240e -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 15 Jan  7 20:03 dc0de018-7ea1-4168-906e-502fc6c9f551 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Jan  7 20:03 e610b299-f6c5-4295-a768-e99220a7ee88 -> ../../nvme0n1p1

 

[t.lamprecht]

ata-ST4000DM000-1F2168_Z30091R1-part1

Ok, could you adapt your previous try with adding the "-part1" suffix?

Output from below suggests the partition I want from external drive is not viewable by host?

It has not partittion UUID, that can be OK - maybe due to being factory preformatted or formatted on a Windows system (not sure from top of my head, but nothing completely unheard off).

 

[GankUnlo]

Thank you Thomas.

This did the trick for me.



Is there perhaps something I did incorrectly during initial setup that would prevent my disks from showing up in the Add drop down in the image above?

I think I can do this again via CLI for some other disks and containers. I'm just thinking there has to be an easier way, and it may be because I forgot something during setup?

 

[t.lamprecht]

I'm just thinking there has to be an easier way, and it may be because I forgot something during setup?

No, I think you did all well and fine

Is there perhaps something I did incorrectly during initial setup that would prevent my disks from showing up in the Add drop down in the image above?

The "Add" drop down currently does not allow to select full physical disks/blockdevices for pass through.
It allows to create "virtual" disks on configured storages (like "local" and "local-lvm" in your case). That's why you do not see it there. We may want to allow passing through those via the Webinterface for the root user, but for now it's simply not possible through GUI only.

For blockdevice passthrough you need to use the CLI for now.

 

[GankUnlo]

Hello again. I've made some changes / upgrades, and i'm running into an issue.

I upgraded to ProxMox Virtual Environment 6.1-7
I tore apart my odroid H2 build and added two new platter drives and increased RAM.
I decided to rebuild my File Server container still 101 but i've added a larger root disk from zfs pool.
Nothing about the external disk has changed.
I used the same command only adding 'ro=0' to the end

pct set 101  --mp0  /dev/disk/by-id/ata-ST400DM000-1F2168_Z30091R1-part1,mp=/mnt/HDD,backup=0,ro=0

In my earlier attempt this was all that was required if my memory serves me.
However, now after this command is run and I try and restart the container I get an error

Job for pve-container@101.service failed because the control process exited with error code.

See "systemctl status pve-container@101.service" and "journalctl -xe" for details.

TASK ERROR: command 'systemctl start pve-container@101' failed: exit code 1

This error persists until I edit /etc/pve/lxc/101.conf and comment out the line for mount point - then Container starts ,but without the mount point obviously.
I thought perhaps the previous mount point was causing issues.
I tried mp2 as well. with the same command above. And the mount point shows up correctly in the gui but when I try to restart the container I get the same error as above.

My goal seems simple - mount the external block storage as I did previously, only NOT read only.

I'm not sure what i'm doing wrong, i'm following the previous example.

 

[GankUnlo]

I changed the mount point again. mp1 this time

pct set 101  --mp1  /dev/disk/by-id/ata-ST400DM000-1F2168_Z30091R1-part1,mp=/mnt/extHDD,backup=0,ro=0

Still ... unable to reboot



I can confirm my command changed 101.conf



I can confirm host see's the disk as well

 

[GankUnlo]

 

[GankUnlo]

I tried following meroupatate's suggestion here

Edited /usr/share/perl5/PVE/LXC/Setup/Debian.pm and added version 11 to the list:


however, version 11 is in the list and this line was already what he suggests changing it to for me

 

[GankUnlo]

to be on the safe side, I destroyed 101 file server container. I recreated it as 100 - followed all my steps from above. and not shocked. same results... hoping someone can spot my mistake or provide some insight on this issue. thank you

 

[GankUnlo]

this seems to be what I should be focusing my attention on.. output from journalctl -xe




i'm wondering if I should NOT Have upgraded

 

[oguz]

hi,

this seems to be what I should be focusing my attention on

yes

* you should get debug logs[0] as it suggests in the journalctl output

* pveversion -v

* pct config CTID

* /etc/pve/storage.cfg


[0]: https://pve.proxmox.com/wiki/Linux_Container#_obtaining_debugging_logs

 

[GankUnlo]

Well, i'd removed my mount point as I couldn't start the CT obviously.

I posted my previous journalct -xe output
however i can try this again if we need more info

I re-added it as MP5 - with the command mentioned above. and it does show up in Gui correctly,
and then same error when I try to restart

root@xkey:~# pct set 100 --mp5 /dev/disk/by-id/ata-ST400DM000-1F2168_Z30091R1-part1,mp=/mnt/extHDD,backup=0,ro=0

root@xkey:~# pct start 100 Job for pve-container@100.service failed because the control process exited with error code.
See "systemctl status pve-container@100.service" and "journalctl -xe" for details.
command 'systemctl start pve-container@100' failed: exit code 1


● pve-container@100.service - PVE LXC Container: 100 Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2020-03-02 15:19:40 EST; 15s ago Docs: man:lxc-start man:lxc manct Process: 14396 ExecStart=/usr/bin/lxc-start -n 100 (code=exited, status=1/FAILURE) Mar 02 15:19:40 xkey systemd[1]: Starting PVE LXC Container: 100... Mar 02 15:19:40 xkey lxc-start[14396]: lxc-start: 100: lxccontainer.c: wait_on_daemonized_start: 865 No such file or directory - Failed to receive the container state Mar 02 15:19:40 xkey lxc-start[14396]: lxc-start: 100: tools/lxc_start.c: main: 329 The container failed to start Mar 02 15:19:40 xkey lxc-start[14396]: lxc-start: 100: tools/lxc_start.c: main: 332 To get more details, run the container in foreground mode Mar 02 15:19:40 xkey lxc-start[14396]: lxc-start: 100: tools/lxc_start.c: main: 335 Additional information can be obtained by setting the --logfile and --logpriority options Mar 02 15:19:40 xkey systemd[1]: pve-container@100.service: Control process exited, code=exited, status=1/FAILURE Mar 02 15:19:40 xkey systemd[1]: pve-container@100.service: Failed with result 'exit-code'. Mar 02 15:19:40 xkey systemd[1]: Failed to start PVE LXC Container: 100.


root@xkey:~# pveversion -v
proxmox-ve: 6.1-2 (running kernel: 5.3.18-1-pve)
pve-manager: 6.1-7 (running version: 6.1-7/13e58d5e)
pve-kernel-5.3: 6.1-4
pve-kernel-helper: 6.1-4
pve-kernel-5.0: 6.0-11
pve-kernel-5.3.18-1-pve: 5.3.18-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.14-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-12
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-4
libpve-storage-perl: 6.1-4
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-19
pve-docs: 6.1-4
pve-edk2-firmware: 2.20191127-1
pve-firewall: 4.0-10
pve-firmware: 3.0-5
pve-ha-manager: 3.0-8
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-2
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-5
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1
root@xkey:~#


root@xkey:~# pct config 100
cores: 2
hostname: ES1
memory: 2048
mp5: /dev/disk/by-id/ata-ST400DM000-1F2168_Z30091R1-part1,mp=/mnt/extHDD,backup=0,ro=0
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=B6:3C:4A:87:1A:E8,ip=dhcp,ip6=dhcp,type=veth
ostype: debian
rootfs: RAIDZ0:subvol-100-disk-0,size=100G
swap: 1024

root@xkey:~# cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content vztmpl,backup,iso

lvmthin: local-lvm
thinpool data
vgname pve
content rootdir,images

zfspool: RAIDZ0
pool RAIDZ0
content images,rootdir
mountpoint /RAIDZ0
nodes xkey

 

[GankUnlo]

root@xkey:~# lxc-start -n 100 -F -l DEBUG -o /tmp/lxc-100.log lxc-start: 100: conf.c: run_buffer: 352 Script exited with status 32 lxc-start: 100: start.c: lxc_init: 897 Failed to run lxc.hook.pre-start for container "100" lxc-start: 100: start.c: __lxc_start: 2032 Failed to initialize container "100" Segmentation fault root@xkey:~# cat /tmp/lxc-100.log lxc-start 100 20200302203739.484 INFO lsm - lsm/lsm.c:lsm_init:50 - LSM security driver AppArmor lxc-start 100 20200302203739.484 INFO seccomp - seccomp.c:parse_config_v2:789 - Processing "reject_force_umount  # comment this to allow umount -f;  not recommended"                                      lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts                                                                               lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for reject_force_umount action 0(kill)                                                        lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts                                                                               lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for reject_force_umount action 0(kill)                                               lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts                                                                               lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for reject_force_umount action 0(kill)                                               lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:do_resolve_add_rule:535 - Set seccomp rule to reject force umounts                                                                               lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for reject_force_umount action 0(kill)                                             lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "[all]"                                                                                                         lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "kexec_load errno 1"                                                                                            lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for kexec_load action 327681(errno)                                                           lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for kexec_load action 327681(errno)                                                  lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for kexec_load action 327681(errno)                                                  lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for kexec_load action 327681(errno)                                                lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "open_by_handle_at errno 1"                                                                                     lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for open_by_handle_at action 327681(errno)                                                    lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for open_by_handle_at action 327681(errno)                                           lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for open_by_handle_at action 327681(errno)                                           lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for open_by_handle_at action 327681(errno)                                         lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "init_module errno 1"                                                                                           lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for init_module action 327681(errno)                                                          lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for init_module action 327681(errno)                                                 lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for init_module action 327681(errno)                                                 lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for init_module action 327681(errno)                                               lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "finit_module errno 1"                                                                                          lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for finit_module action 327681(errno)                                                         lxc-start 100 20200302203739.484 INFO     seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for finit_module action 327681(errno)                                                lxc-start 100 20200302203739.485 INFO     seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for finit_module action 327681(errno)                                                lxc-start 100 20200302203739.485 INFO     seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for finit_module action 327681(errno)                                              lxc-start 100 20200302203739.485 INFO     seccomp - seccomp.c:parse_config_v2:789 - Processing "delete_module errno 1"                                                                                         lxc-start 100 20200302203739.485 INFO     seccomp - seccomp.c:parse_config_v2:975 - Added native rule for arch 0 for delete_module action 327681(errno)                                                        lxc-start 100 20200302203739.485 INFO     seccomp - seccomp.c:parse_config_v2:984 - Added compat rule for arch 1073741827 for delete_module action 327681(errno)                                               lxc-start 100 20200302203739.485 INFO     seccomp - seccomp.c:parse_config_v2:994 - Added compat rule for arch 1073741886 for delete_module action 327681(errno)                                               lxc-start 100 20200302203739.485 INFO     seccomp - seccomp.c:parse_config_v2:1004 - Added native rule for arch -1073741762 for delete_module action 327681(errno)                                             lxc-start 100 20200302203739.485 INFO     seccomp - seccomp.c:parse_config_v2:1008 - Merging compat seccomp contexts into main context

lxc-start 100 20200302203739.485 INFO     conf - conf.c:run_script_argv:372 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "100", config section "lxc"

lxc-start 100 20200302203740.356 DEBUG    conf - conf.c:run_buffer:340 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 100 lxc pre-start produced output: mount: /var/lib/lxc/.pve-staged-mounts/mp5: special device /dev/disk/by-id/ata-ST400DM000-1F2168_Z30091R1-part1 does not exist.



lxc-start 100 20200302203740.356 DEBUG    conf - conf.c:run_buffer:340 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 100 lxc pre-start produced output: command 'mount /dev/disk/by-id/ata-ST400DM000-1F2168_Z30091R1-part1 /var/lib/lxc/.pve-staged-mounts/mp5' failed: exit code 32



lxc-start 100 20200302203740.378 ERROR    conf - conf.c:run_buffer:352 - Script exited with status 32

lxc-start 100 20200302203740.378 ERROR    start - start.c:lxc_init:897 - Failed to run lxc.hook.pre-start for container "100"

lxc-start 100 20200302203740.378 ERROR    start - start.c:__lxc_start:2032 - Failed to initialize container "100"

 

[GankUnlo]

I can see that it says mount failed. does not exist, but this is not true.

I can see the disk just as before from the host as I mentioned in post #12, this is still true. has something changed for how to properly pass a block storage device to a container? if nothing about that step has changed, i'm not sure why this won't work just as it did before.