Search results

  1. D

    Can't rename a bind mount?

    Hi there. I've run into a bit of a snag with the bind mount for a container. Initially, when setting up the container, I had added the following line to /etc/pve/lxc/118.conf: mp3: /data/docs/agreements-archive,mp=/archive I noticed an error in a program running in the container, and then...
  2. D

    Can't start container restored from backup - unable to detect OS distribution

    A further development: I had restored a bunch of other containers yesterday and started each of them and they seemed to run just fine yesterday, except for the one I was having problems with. I tried starting them today and am now getting the same error with every single one of them. The debug...
  3. D

    Can't start container restored from backup - unable to detect OS distribution

    Actually I just noticed something else that might or might not be a bit worrisome. The backup file for the container is 257 GB, but when I check the size of the mounted filesystem, it seems to use only 6GB. root@fava2:/var/lib/lxc/100/rootfs/lib# df -h /var/lib/lxc/100/ Filesystem Size...
  4. D

    Can't start container restored from backup - unable to detect OS distribution

    My single node Proxmox recently got very messed up. Gave up on it, killed it and reinstalled Proxmox from scratch (a couple of days ago - v. 5.4). I then restored containers from backups. However, one container (originally CT 100 and restoring to CT 100) does not start. That container had been...
  5. D

    Messed up ZFS pool

    Hey thanks Guletz. Yeah, I figured by the limited response that my system in its current state is well and truly borked. Oh well. Hopefully I don't mess up the recovery.
  6. D

    Messed up ZFS pool

    Thank you. No worries about your English - just happy to have some feedback. Yes, I removed them from the server. Just to clarify, the two HDDs I removed were new drives and did not have anything important on them. When I rebooted, the system seemed to confuse the two SSDs comprising the rpool2...
  7. D

    Messed up ZFS pool

    Well, things seem to be going from bad to worse. I had tried testing out the creation of a new container and restoring a container backup on rpool, which seemed to work. As they were for testing only I destroyed them after doing so. But when I rebooted Proxmox went into emergency mode. Looking...
  8. D

    Messed up ZFS pool

    Well, looks like my system is well and truly messed up, so I'm really hoping someone here can offer some suggestions. When my system was running OK, I had two ZFS drive pools set up. The first was called rpool and was created by Proxmox when I initially installed it. It consisted of a mirror of...
  9. D

    Writing to Bind Mount Inside of an Unprivileged Container?

    Thanks sigo - yes that was a typo in the post.
  10. D

    Storage Options for VMs, CTs and Client Computers

    @Etique57 - Happy to do so. In retrospect, you're probably right. It's just that once I set down the path with using acl permissions I thought I might as well finish it. Never did look much further into passthroughs. When you do get it set up, it would be great if you could post a quick note...
  11. D

    Storage Options for VMs, CTs and Client Computers

    @Etique57 - No, that's not the case. I am currently using mergerfs + snapraid. See my response to floh above. Or did you mean putting mergerfs + snapraid in a container? I decided against that as it would have been a bit more complex to set up the disk passthroughs. Don't disagree with your...
  12. D

    Can't add new drive - shows as "partitions" under Usage

    Managed to figure this out. Even though fdisk didn't show any partitions, lsblk seemed to indicate that there was in fact a partition for about half the space of the drive. As I wasn't able to delete it, I just decided to create a new empty GPT partition table using fdisk. That seemed to do the...
  13. D

    Can't add new drive - shows as "partitions" under Usage

    Hi there. Was hoping someone can help with what I thought would be a fairly simple operation: I was planning on adding some additional storage to my single node PVE system, so bought a couple of SSDs and plugged them in. I was planning on adding both as a new mirrored ZFS pool. However, when I...
  14. D

    Expanding ZFS root file system

    Hey thanks frenchfries, that is helpful. I thought that was the case as well but then started to think I had misunderstood the requirement when I saw Jim's post, so was thinking of different approaches to avoid the need to even deal with it - namely, instead of trying to expand the system drive...
  15. D

    Expanding ZFS root file system

    Hey thanks for the notes Jim. For some reason I thought that the rule on same sized devices only applied to drives within a given vdev, but not to the various vdevs within a pool. So for example I could have a ZFS pool comprised of two drives each, with one pool being 500 GB on each drive and...
  16. D

    Expanding ZFS root file system

    Hi there. I have a Proxmox installation that I installed on a ZFS zpool. The zpool was configured with the Proxmox installation and consists of two mirrored 500 GB SSDs, like this: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror-0...
  17. D

    Storage Options for VMs, CTs and Client Computers

    Hey floh. Since I didn't really get much in the way of suggestions, I more or less set up what I had described above. I gave some thought to implementing Snapraid+mergerfs in a VM with disk pass-through but decided against it. Instead, I installed Snapraid and mergerfs at the host level...
  18. D

    Writing to Bind Mount Inside of an Unprivileged Container?

    Interesting. Thanks very much for the info. That's very helpful information indeed. I might give that a try at some point but ended up getting heavily invested in the setfacl approach, which seems to work well enough for my needs, at least for the time being.
  19. D

    Odd warning message when upgrading

    Thanks for the note Alwin. No, I did not as I didn't realize that was required. I've now done so (by running "apt install --reinstall pve-kernel-4.13").