Lifebandit666

Well I'll keep it in mind for if I get any issues but it seems to be running ok ATM with USB ports passed through to OMV and then CIFS back to Proxmox so I can save backups.

As it is, at most 2 drives will be in use at a time with the third as a backup drive doing rsync at night (still to set up).

I'm not using flash storage. These are proper spinning Hard Drives with a usb 3 cable (and a power cable) to the host.

Not quite there yet. I need to add the CIFS connection to Proxmox now to save to the drives (I'll have to do a little research). I still have to set up the Google Drive add-on in Home Assistant again, and set it up properly this time so it actually schedules backups.

Also need to figure out how to off site backup my Proxmox backups. More research

Edit: worked out CIFS to Proxmox now, got a backup solution. Just have to work out how to get them off-site but I could maybe have my PC pull the files for now and maybe sync to Drive as off-site.

Edit2: Gdrive add-on added and set up in Home Assistant now.

I'm giving you these updates because you held me to account on the backup side, and I appreciate that. I had my head in setting my server back up, not back-ups. So thanks!

Funnily enough I was looking at these usb Sata cases yesterday, but I was expecting them to be cheaper then they are (I'm a Yorkshireman and we're notorious for not liking spending money).

As to your point (which I will look into) are you talking about an actual external Hub here or the USB in my machine? I ask because I have 5 usb 3.0 ports on the machine and do not actually use an external hub, but when you use the word "hub" you could also be referring to the USB controller on the machine.

Also I haven't dabbled with RAID yet but I had considered it, so this may sway me to invest some money before considering it properly.

Yeah I was considering passing usb though, or even nofail mounting usb instead of UUID.

They're sata connection but my host is a tiny pc with minimal internals. I just had the drives lying around so decided to try a USB to Sata cable which worked until it didn't. That's why usb.

I did not realise that Proxmox would fail if the devices did, and I'm a little annoyed I didn't notice it on Sunday when it died for the first time, because I started fresh and ended up losing YEARS worth of Home Assistant automations.

Live and learn.

I'm not as knowledgeable as some in here but in my short experience I can say I bought something with 16gb of RAM and while it is currently doing everything I want it to, it's using 12gb ram currently...

Oh, sorry I'm no help then

I thought iframes had been phased out in the latest release of HA? It's webpages in views now isn't it? Try updating and having another go (I updated yesterday and haven't had a play yet but heard about it on the HA podcast btw)

Thomann crew checking in! Bought my first "real" guitar from them and she's still my favourite despite being given a Les Paul by Bowling For Soup this year. I really should play that baby

I'll try that asap!

No rush, take your time. HA OS was pretty simple to get running, you'll just have to learn how to pass through your usb (top tip, just have that one usb plugged in then you only have 1 device to choose from).

Learn how to make a backup (HA has an add-on called Google Drive Backup that's REALLY useful) just in case you tinker and kill something.

Above all, don't kick yourself for making mistakes, it's how we learn.

Hi, I read your update and you're just a little behind me on the trail, so here's some breadcrumbs.

Proxmox is awesome, stop wondering and install it, it's awesome.

Ok so you can do 2 things, VM or LXC. You're wondering what the difference is.

VM is a computer

LXC is a container.

Now as far as I can tell a container is kinda like a little computer that's made to do one thing. So it needs less resources, just what it needs to do that one thing. It also needs less permissions to do that one thing, so it has less permissions.

Now Docker is a container engine. It's beautiful because you can just tell it what to make and it'll make it. If you remember what you told it, you can do it again really quickly.

Docker is also beautiful because it will run on anything. So you can make a container on a Linux machine, then make it again on a Windows machine if you remember what you told it. This is done with a bunch of text, so as long as you can save that text and get it on another machine, well you have the container again.

Not knowing this, I've been trying to make docker work in LXC containers with a bit of success and a lot of failure. I thought I could just have a bunch of cloned LXC containers with Docker on, and make a bunch of services using minimal resources.

But now I know I'm trying to run a container inside a container and that's why I'm hitting walls.

So Proxmox VMs are gonna be your friend. It will be tempting to try and migrate to containers, but as a beginner you can save a lot of headaches by making a couple of VMs and cramming a bunch of stuff on em.

This is where Docker is useful. If you use a docker hypervisor (?) app, there's Portainer for example which I use, you can just use one instance to control a bunch of other instances of Docker.

This makes it easy to try something out on a test machine, then just move it over to another machine when it's ready. The more similar the machines are, the easier the transfer. In Proxmox you can clone things, so you can make a computer, clone it, then set things up on one and move em over when they're working right, then just turn the test machine off.

So in my opinion, boot a VM of Home Assistant OS and get that working. Make another for playing with of whichever flavour you fancy. Windows, Linux, both?

Bang docker in it and have a play. I like Portainer, made Docker easier to mess with, but I like a UI. So I got Portainer working first and used that to put Docker Compose files into "Stacks" in Portainer and poked them.

Then when I found stuff I liked I tried booting them so they work, be that in a VM, and LXC or in Docker if I had got it working to my liking already. Because Docker is containers I hit a lot of problems running stuff (and I don't know what I'm doing) but found an LXC or VM easier.

Try getting piHole (and try Adguard, I prefer it) going in Docker. I found Adguard works perfectly fine in Docker, so once I got it working I just had to decide where I wanted it and ended up having an instance in Docker in an LXC (container in a container, not great, but it works.

Then I copied it onto a raspberry pi, just put Docker on it and and used the same file. That means that if I knackered up my Proxmox my internet won't go down.

Hope that helps

I'm glad you commented as I didn't know I can define 2 networks in Docker. At the moment I'm trying to get Arr working in docker and it was going well until I realised my containers can't communicate with Plex. I believe it's because I'm using Gluetun and I haven't enabled LAN networking on my VPN. but theoretically the apps that need to see Plex don't need to be behind the VPN, but they didn't work when they weren't because they couldn't talk to Prowlarr.

So theoretically I could just slap "bridge" in my network as well, and then they'll be in Gluetun and out of it at the same time.

I may try it tomorrow. Thanks for your comment

Recently set this up myself in Ubuntu with the Mullvad app. I noticed in the qBittorrent settings that you have to tell it which ip to use. Mine was set to "any" so I had a quick look at the IP address of Mullvad and selected that one in the drop down