Recent content by whataboutpereira

This has persisted into 7.0 so I guess this motherboard is out of luck with future updates. :/

6.17 kernel breaks USB 2 ports on Intel S1200BTL motherboard. 6.17 [ 0.000000] DMI: Intel Corporation S1200BTL/S1200BTL, BIOS S1200BT.86B.02.01.0044.072520181346 07/25/2018 [ 1.359727] ehci-pci 0000:00:1a.0: EHCI Host Controller [ 1.360032] ehci-pci 0000:00:1a.0: new USB bus...

Hello! I see a PVE update I ran a week ago has introduced a new backup hook script phase 'job-init'. Since my hook script sanitizes its input and job-init isn't included in allowed values, the script exits. The result is that I've had no backups running for a week and I haven't received any...

I ended up installing the backup hook scripts on each node with ansible. Also realized I can test with 'pct exec 120 pidof mysqld' if there's a running mysql or redis server in any container and flush/save, so I don't have to hardcode container ids in the scripts. Just to mention another thing...

I now manager to restore the container on ZFS with unprivilieged 1 accompanied by nesting 1, but permissions are still broken. /home/user: Access: (0700/drwx------) Uid: ( 1001/ UNKNOWN) Gid: ( 1001/ UNKNOWN) bash-4.4$ whoami whoami: cannot find name for user ID 1001: Permission denied...

Apparently permissions are broken also on the original node after restoring from backup (where I could restore without errors in unprivileged mode). On the node with ZFS storage I can restore it with only privileged mode, but permissions are likewise broken.

Uh oh. I fired it up as privileged now which resulted in: -bash: /etc/profile: Permission denied -bash-4.4$ Statting my home dir shows: Access: (0700/drwx------) Uid: ( 1001/ UNKNOWN) Gid: ( 1001/ UNKNOWN)

Hello! I've this one container on a node with LVM storage that I now want to move to another node with ZFS storage. Both the source and target are running PVE v7.1. The container is unprivileged on the source node. Restore on the ZFS node fails with permissions denied. I can successfully...

Wonderful! :)

Thanks! Should I expect any side effects from it?

# zfs get all / | grep acl rpool/ROOT/pve-1 aclmode discard default rpool/ROOT/pve-1 aclinherit restricted default rpool/ROOT/pve-1 acltype off default That probably means no?

Already done and running nicely. :) Is there anything I can do to get rid of the systemd-journald error?

Successfully upgraded one member now. I'm seeing that the 6.4 node is happily still replicating to 7.1, however the 7.1 containers are giving replication errors. Is that expected until I upgrade the other member as well? These containers were migrated away and back after the upgrade. 2021-12-09...

Thanks for the replies. I might have a go at in-place upgrade then. Fingers crossed that I won't be affected by all the recent kernel trouble.

I see there are two main options outlined in v6->v7 upgrade documentation (new cluster and upgrade using apt), but I'm wondering if it might be okay to upgrade my small cluster like this: - Migrate all containers off a member - Remove the member from cluster - Clean install v7 on the machine -...