Search results

think i figured it out, pool is Bigdata and you then create the zfs location after... so zpool then zfs. so in my case I just made Bigdata and then Bigdata/Zeus and re-did the samba share for Bigdata/Zeus and restarted it and now I can see the files transfering and I'm not getting smb errors...

so I recently had to upgrade some hardware, and after doing so couldn't keep the ZFS pools for some reason. I destroyed the pool and recreated it, installed samba on the proxmox root (I just like it that way). And chmod the main zfs share.. I've followed this guide in the past to get the...

having a similar issue, should I not be removing the 6.1.0-9 headers? dpkg: error processing package linux-headers-amd64 (--configure): dependency problems - leaving unconfigured Setting up pve-headers-6.2 (8.0.2) ... Setting up pve-headers (8.0.1) ... Errors were encountered while processing...

that fixed it. So is PVE looking at that directory for a status.cfg and if ones there it breaks metrics?

root@pve:~# cat /etc/pve/status.cfg influxdb: server 192.168.22.21 port 8089

I had installed a lxc grafana image, but have since uninstalled it and purged the info. rebooted. Still throwing the same error.

root@pve:~# systemctl status pvestatd.service ● pvestatd.service - PVE Status Daemon Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2022-12-20 17:24:05 PST; 16h ago Process: 1984770...

Happened after updating from the GUI the packages.... no idea why and nothing I've found about restarting services has helped. Some screenshots of the GUI below Reboot didn't fix and restarting services from other forum posts didn't fix it either.

I've been racking my brain on this as all the setups I've found online show this should be easy. I have a ZFS zpool named Bigdata and a sub called Files Bigdata/Files I've installed turnkey file server and added a mount point that shows /Files as the store (50TB for backups of another...

so maybe I have a complete misunderstanding of ZFS and how I setup my system. I was probably moving too fast and not comprehending the setup. My initial impression is that with Proxmox, I was able to setup a zfs pool and from there sub volumes. SSD has iso and vm's on it /Bigdata (10x10tb...

So the deeper explanation is that it's the same proxmox install. What happened is I had to reboot for some reason and the turnkey file server lxc wasn't able to boot (no idea). So knowing I had created a zfs file store (mount point) for that lxc, I figured I'd just spin up a new turnkey lxc...

Trying to understand what to do here, it's been since covid started and I've been putting this off for a while. I have the latest proxmox installed with a zfs pool, created some pools and installed turnkey file server.... some how it got jacked up and I don't know why (literally never touched...

nevermind, found it using dmidecode

how can I tell what slot that is on the motherboard? It's not in slot 1.... trying to figure out how to correlate c1:00 to a slot

so that's what happens... all three HBA's work only in slots 2,4,6. If in 1,3,5 they don't show in proxmox. With them in 2,4,6 and I put the nic in slot 5, I lose 2 of them. I'm just struggling with Supermicro in trying to understand that they would have a brand new board in 2020 that has 6...

Also updated the avago device list in the first post.

root@pve:~# systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● pve-container@102.service loaded failed failed PVE LXC Container: 102 ● zfs-import-cache.service loaded failed failed Import ZFS pools by cache file LOAD = Reflects whether the...

Any thoughts based on the information above?

also with the nic plugged in Systemctl status gives the following ● pve State: degraded Jobs: 0 queued Failed: 2 units Since: Fri 2020-05-29 07:34:54 PDT; 12min ago CGroup: / ├─1440 bpfilter_umh ├─user.slice │ └─user-0.slice │...

ok so after plugging the card back in to slot 5, no bios changes to what you see above, the following is what happens. So I'm not sure from googling what this actually is. This is a brand new Supermicro server board, can't think that they would disable slots based on a card being in one like...