Search results

I'm having a difficult time using a disk in my machine. It is not being used for anything, i've successfully don a sgdisk -Z on the drive and it shows that nothing is on it. Disk /dev/sda: 233.8 GiB, 251000193024 bytes, 490234752 sectors Units: sectors of 1 * 512 = 512 bytes Sector size...

What do you mean by non-free-firmware package? Do you have that available?

I'm seeing this issue as well on three of my machines. Is there a way to get the chelsio driver updated? I was thinking of trying to compile the driver from source and installing it on one of the proxmox servers but not sure if that will resolve the issue...any advice would be welcomed!

Thank you!! Finally its working. I tried doing that after installed Debian Stretch on its own and it wasn't able to. tom -- I have an older NUC, so maybe it had a tough time with the install? Not sure, but glad its working now.

I have an intel NUC that was successfully running 4.4, but when I go through the upgrade instructions on it it is not starting services. I try to see the pvecm status and it is saying that the command is not found! Not sure what could have happened, but I've been trying multiple different ways...

I am getting this same error...any insight into what could be causing this?

Thanks for the help fabian! I thought I had expanded this lxc's inotify, but i hadn't...its set to 8192. I'll expand that and test. Hopefully that helps. my df for that host is: Edit: I'm not able to edit the inotify on this lxc. Is there a service I need to stop to be able to write to...

I've been getting this error on ALL of my LXC's within proxmox. Not sure what is causing the no space available errors. Need some help on this one. I get this error whenever I try and stop/start a service...

Hi All, I have just realized that all of my CTs are getting a UTC timezone set by default for some reason. Is there anyway to automate the timezone I want for my CTs? I would have thought that they would take the same timezone from the proxmox host, but that doesn't seem to be the case. I...

Aha! That is where the logs would be!! I was looking for them for a while, definitely makes sense. This is the error it shows:

Just want things to be running on Baremetal whenever possible. I see the reasoning why it makes sense on KVM, but would be nice to try on CT as well.

According to https://github.com/docker/docker/issues/6783 it should be able to, shouldn't it? I saw some discussion on the forum regarding this, but not sure. Just to be clear, I'm able to get docker running in the LXC, i'm just getting that error when attempting to use docker to pull an image...

Hi All, Looks like i'm having issues with a CT with Docker installed. The Error i'm receiving is as follows: Does anyone have any advise?

Is there a way to automate that and pass it to the GUI?

Can you link me to the new features. I'd love to do that but a lot of stuff relies on my local disks...maybe in the future!

Thanks for the information! I'm running a Dell R710 and these are local disks...not sure if the onboard RAID Controller can pass SMART data or not. I'll take a look.

I have never used S.M.A.R.T. with proxmox, but i would love to! I looked it up and saw some quite old information on how to use/install S.M.A.R.T. and want to make sure i'm doing this properly. I believe the reason my proxmox server isn't passing S.M.A.R.T. is because my local disks are all...

Anymore info on how you did this? Would be awesome if we could spin up NGINX, LDAP, etc systems that have been custom made. Is there documentation on that?

Just want to say that this is a great conversation and taught me a lot about why i'm having issues with Docker within Proxmox. I'm just looking to learn more about Docker, since as you all say it is becoming a HUGE technology. Since i'm running this in a homelab the overhead of a VM isn't...

Okay, so just for anyone else that wants to solve it. "pvecm e 1" worked to create a quorum and delete all nodes that were and even werent listed. I went into /etc/pve/nodes and found that there were a LOT of extra nodes in there that I had previously added, but hadn't been properly removed...