Search results

so for ref, here is output from my host showing mount point based on previous message I inserted into 410.conf And rebooted VM however, it doesn't look like my previous attempt to mount on the VM was persistent anything wrong with how i'm mounting here? I don't see the option in the GUI...

so after thinking about it, you are saying add this to my 410.conf? mp0: /mnt/HDD,mp=/mnt/HDD

I really wish I could follow what you are saying, but again, " replace folders name" what folder are you talking about? then "add this " where is this added? the .conf on the host? I'm not sure about this last line either "the second mp its folder in your VM" what folder? sorry for inability...

this OpenMediaVault instance is a VM, not LXC, I'd tried using LXC file server and was stuck with a read only drive. decided on trying open media vault. I realize the external HDD file system isn't mounted in the VM -isn't select-able in the GUI (second print screen shows this) here is the conf...

I can confirm the drive mounted with the command from my previous post however, I'm still unable to share anything in openmediavault dashboard nothing under devices, for sharing. this is maddening

thanks for trying, but that vague response isn't getting me any further. I have a whole thread devoted to my issue which has been following me across LXC and now VM. I can see my mounted disk in the OpenMediaVault webmin dashboard not at all visible under file systems unable to share...

i'd love to know more about this set up. been struggling with creating / adding an external usb drive to any lxc or vm with write access.

hello I've had an on-going issue for some time. https://forum.proxmox.com/threads/still-stuck-lxc-wont-start-after-passing-block-storage-to-container.64179/page-2#post-299084 i have 4tb Samsung external USB HDD connected to an Odroid H2 via usb 3 > running proxmox 6.3 a while back I attempted...

i've reached my limit on trying 'random' ideas. i'm about to start researching downgrading... smh so frustrated this was working before update... :( Edit: I read also, at some point it was best to mount disk by-id and this did work for me in the past. however, it now seems the only way i'm...

I re-did this , i'd read somewhere removing the /dev directory from mp may fix the issue. but that is not the case root@xkey:~# pct set 100 --mp0 /disk/by-id/ata-ST400DM000-1F2168_Z30091R1-part1,mp=/mnt/extHDD,backup=0,ro=0 root@xkey:~# pct stop 100 root@xkey:~# pct start 100 Job for...

thank you, momentary lapse, CT recreated now to get log I believe I already posted this but here it is again 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 -...

interesting. it seems now i'm unable to create a new container Task viewer: CT 107 - Create OutputStatus Stop Logical volume "vm-107-disk-0" created. mke2fs 1.44.5 (15-Dec-2018) Discarding device blocks: 4096/2097152 done Creating filesystem with 2097152 4k blocks and 524288 inodes...

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...

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...

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...

damn, i thought I was special. I'm getting the same error. I can create a new Debian file server container just fine. As soon as I pass block storage to it via CLI, and then try and restart.. i get the same error. I've been scratching my head since yesterday ... I'll add that I CAN remove the...

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 :(

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

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