Hi,
I have recently added two disks to my server, when I run fdisk -l they occupy /sdc and /sdd. Both previously occupied by disks in my apool and bpool respectively.
After installing these disks and running proxmox 3 of my containers, that used one or both of these pools for storage would not start, I narrowed the issue down to neither of these being mounted. After fiddling around trying other solutions found on these forums, all I have done is made it much worse.
Now below is the output of
This appears to show that now none of my rpool is mounted apart from the proxmox partition. None of my containers boot up.
I try to run
This is true it contains about 1.3TB worth of stuff, which I dont want to get rid off so I can mount it.
I am able to mount some things, below after I manually try to mount everything in the list:
This allows me to spin up CT102 - just a simple pi-hole container, but still noting else.
Please if anyone can help with this I would greatly appreciate it, I don't really know what to do otherwise beacuse I don't want to delete the data on the drives - this was my backup.
Thanks, more info below if needed:
I have recently added two disks to my server, when I run fdisk -l they occupy /sdc and /sdd. Both previously occupied by disks in my apool and bpool respectively.
After installing these disks and running proxmox 3 of my containers, that used one or both of these pools for storage would not start, I narrowed the issue down to neither of these being mounted. After fiddling around trying other solutions found on these forums, all I have done is made it much worse.
Now below is the output of
zfs get mounted:
Bash:
NAME PROPERTY VALUE SOURCE
apool mounted no -
apool/plex mounted no -
apool/torrents mounted no -
bpool mounted no -
bpool/youtube-backup mounted no -
rpool mounted no -
rpool/ROOT mounted no -
rpool/ROOT/pve-1 mounted yes -
rpool/data mounted no -
rpool/data/subvol-100-disk-0 mounted no -
rpool/data/subvol-101-disk-0 mounted no -
rpool/data/subvol-102-disk-0 mounted no -
rpool/data/subvol-102-disk-1 mounted no -
rpool/data/subvol-103-disk-0 mounted no -This appears to show that now none of my rpool is mounted apart from the proxmox partition. None of my containers boot up.
I try to run
zfs mount apool/plex for example I get cannot mount '/apool/plex': directory is not emptyThis is true it contains about 1.3TB worth of stuff, which I dont want to get rid off so I can mount it.
I am able to mount some things, below after I manually try to mount everything in the list:
Bash:
NAME PROPERTY VALUE SOURCE
apool mounted no -
apool/plex mounted no -
apool/torrents mounted no -
bpool mounted no -
bpool/youtube-backup mounted no -
rpool mounted no -
rpool/ROOT mounted yes -
rpool/ROOT/pve-1 mounted yes -
rpool/data mounted no -
rpool/data/subvol-100-disk-0 mounted yes -
rpool/data/subvol-101-disk-0 mounted yes -
rpool/data/subvol-102-disk-0 mounted yes -
rpool/data/subvol-102-disk-1 mounted yes -
rpool/data/subvol-103-disk-0 mounted yes -This allows me to spin up CT102 - just a simple pi-hole container, but still noting else.
Please if anyone can help with this I would greatly appreciate it, I don't really know what to do otherwise beacuse I don't want to delete the data on the drives - this was my backup.
Thanks, more info below if needed:
Bash:
path: '/dev/disk/by-id/ata-ST4000DM004-2CV104_ZFN22DH6-part1'
phys_path: 'pci-0000:02:00.0-ata-1'
path: '/dev/disk/by-id/ata-ST4000DM004-2CV104_ZFN22G93-part1'
phys_path: 'pci-0000:02:00.0-ata-1'
path: '/dev/disk/by-id/ata-ST4000DM004-2CV104_ZFN22DEX-part1'
phys_path: 'pci-0000:02:00.0-ata-1'
path: '/dev/disk/by-id/ata-ST4000DM004-2CV104_ZFN20PF9-part1'
phys_path: 'pci-0000:02:00.0-ata-2'
path: '/dev/disk/by-id/ata-ST8000VN004-2M2101_WKD29ZAV-part1'
phys_path: 'pci-0000:01:00.0-ata-1'
path: '/dev/disk/by-id/ata-ST8000VN004-2M2101_WKD2VKF9-part1'
phys_path: 'pci-0000:01:00.0-ata-1'
path: '/dev/disk/by-id/ata-ST8000VN004-2M2101_WKD303M6-part1'
phys_path: 'pci-0000:01:00.0-ata-2'
path: '/dev/disk/by-id/ata-ST8000VN004-2M2101_WKD31JZF-part1'
phys_path: 'pci-0000:01:00.0-ata-1'
path: '/dev/disk/by-id/ata-WDC_WDS500G1R0A-68A4W0_202574800385-part3'
path: '/dev/disk/by-id/ata-WDC_WDS500G1R0A-68A4W0_202574800257-part3'
Bash:
lxc-start: 100: lxccontainer.c: wait_on_daemonized_start: 843 No such file or directory - Failed to receive the container state
lxc-start: 100: tools/lxc_start.c: main: 308 The container failed to start
lxc-start: 100: tools/lxc_start.c: main: 311 To get more details, run the container in foreground mode
lxc-start: 100: tools/lxc_start.c: main: 314 Additional information can be obtained by setting the --logfile and --logpriority options
Bash:
lxc-start 100 20200920175341.143 ERROR conf - conf.c:run_buffer:323 - Script exited with status 2
lxc-start 100 20200920175341.144 ERROR start - start.c:lxc_init:804 - Failed to run lxc.hook.pre-start for container "100"
lxc-start 100 20200920175341.144 ERROR start - start.c:__lxc_start:1903 - Failed to initialize container "100"
lxc-start 100 20200920175341.961 ERROR conf - conf.c:run_buffer:323 - Script exited with status 1
lxc-start 100 20200920175341.961 ERROR start - start.c:lxc_end:971 - Failed to run lxc.hook.post-stop for container "100"
lxc-start 100 20200920175341.961 ERROR lxccontainer - lxccontainer.c:wait_on_daemonized_start:843 - No such file or directory - Failed to receive the container state
lxc-start 100 20200920175341.961 ERROR lxc_start - tools/lxc_start.c:main:308 - The container failed to start
lxc-start 100 20200920175341.961 ERROR lxc_start - tools/lxc_start.c:main:311 - To get more details, run the container in foreground mode
lxc-start 100 20200920175341.961 ERROR lxc_start - tools/lxc_start.c:main:314 - Additional information can be obtained by setting the --logfile and --logpriority options
Last edited:
