I’ve been using refurbished business laptops, thinkpads spesifically, for at least a decade. Both for business and for personal use. They just work and at least in here you can get pretty good deals from companies which re-sell previously leased machines. For some I’ve upgraded RAM and/or storage drive, but that 300-400€ gets you something far better than a new Acer from grocery store aisle. And reputable vendors even offer some kind of warranty even on used machines.

Other brands might work just fine too, but as I’ve had thinkpads since the brand was owned by IBM I’ve just stuck with them. T, W and X series are all pretty solid. And there’s a reason why you don’t see Acer or other consumer brands on refurbished market.

this community is dominated by the systemd fanboys

Hey now. There’s dozens of us who had that thing force fed for us. I’ve been on Debian for decades, so even if I don’t really like systemd it’s the lesser evil than switching a distro to something without it.

Absolutely. And 1980s was about 20 years ago.

I came to say excactly that.

It’s a full VM, so OS and docker creates some overhead, but before I upgraded the server it ran on far less resources and specially big imports were painfully slow. Also that’s just the number from proxmox console, so there’s likely some cache included, but stats show that the VM pulls over 10G every now and then with shorter spikes over 20GB of consumed RAM.

As I mentioned, it can run on way less, but it feels a lot more responsive when it has enough resources.

16GB of ram is a bit low for the load you’re planning. That can work, but Nextcloud and Immich are pretty hungry for memory. My immich instance right now is using 7GB of RAM and nextcloud uses a bit over 4. I have the hardware to give them pretty much all the memory they want, so those are not absolute minimum amounts, but I wouldn’t try to run either with less than 6GB allocated memory on my load (few users, about a terabyte of data on both).

With 16GB you can pretty much forget using ZFS, but that’s not a big loss. LVM works just fine and with thin provisioning you can use snapshots too just fine. Bigger SSD/NVME for drive cache would be good. And of course all-SSD setup would be nice, but that gets expensive pretty fast. Second ethernet port might be nice to have, depends on how you’re planning to build your setup. Otherwise that hardware looks pretty good, altough I’d search for something second hand. CPU is most likely a bit overkill for what you need, I have Xeon E5-2620 v3 @ 2.40GHz and it’s running on around 10% load most of the time.

You’re of course correct on that, but Mullvad the company gave (somewhat) clear news release that their company is against far right (or left or any ‘far’ direction) politics. I’m not a customer and I couldn’t care less about Mullvad, but I think it’s worthwhile to keep in mind that company isn’t the same than one of it’s founders.

Of course if that is a breaking point to you, feel free to vote with your wallet and I can very much understand the decision, but there’s very few fully reputable companies around so I can also understand if that’s not a hill to die on.

Don’t send spam, behave nicely, have proper configuration on postfix and dovecot, set up SPF and preferably DKIM, keep your domains reputation clean and so on. You’ll likely still end up on some lists, so you need to manually dig them trough and ask nicely for removal.

Self hosting email has a pretty bad reputation and many will strongly advice against it, but in reality it’s really not that bad. But email as a whole is more complex beast to manage than simple website or running Jellyfin for your family and friends. You need to understand how the mail routing side of things work (SMTP itself, authentication for it encryption included and so on) and also you need to understand how DNS works and how various entries are related to mail transport. Then you’ll likely want at least some kind of spam filtering and so on. And with email you’ll need to have proper backup scenario too so that you don’t lose the likely pretty important data. All of that is perfectly doable and it’s not as difficult as many claim it to be, but there’s a bunch of stuff you need to understand and implement all of them correctly.

There’s various permission errors on the log file, I’d start from those. Also your dovecot configs seem a bit funny to me, usually mails are not stored to user home directories with dovecot, but instead somewhere under /var, likely you’ll want /var/vmail. Logfiles are pretty good with these tools, so pay close attention to those.

And take your time to understand what the config options actually do. Too permissive configurations will get your sever to every spamlist on the world pretty quickly.

As others have said, this is something software can’t do, so there’s no linux tools for it. There is charge profiles which may help in the long run, similar than what your smartphone likely has. But that absolutely requires that your charger outputs the voltage and current your laptop requires.

If the physical connector ‘kind of fits’ I personally wouldn’t use it, even if the voltage was correct as it’ll likely damage the connector on the motherboard and then you’re looking for a much more complex repair. Laptop power bricks are pretty cheap.

I had RaZberry7 Pro or whatever that pi-hat was called. It never worked reliably and pushed my interest to whole home automation stuff back by a quite lot, since it should’ve been at least decent enough. Then I switched to ZWA-2 and the difference was way more massive than I could’ve imagined. I got few shelly devices lately and they’re currently on wifi, but I’m planning to add zbt-2 on the mix and start to migrate towards zigbee/threads. There’s plenty of light switches and other stuff still on the house which would benefit from smart controls and zigbee feels like more future-proof than z-wave.

unless the data is off site, its not truely a backup

Two is one and one is none. No matter if it’s offsite or on top of your main server. Also 3-2-1 is an industry standard for a reason. Plus unless you test that you can actually restore your backups they don’t really exist (also known as Schrödinger Backups).

Oops. I had a wrong command there at the start on text, vgcreate is for creating volume group, not lvcreate. I edited it. That would just be a syntax error of sorts, nothing would happen with a wrong command.

USB GUI method is called ‘installer’ ;) Messing around with partitions is inherently a dangerous thing to do, no matter if you use a GUI or CLI. Today tools like fdisk or parted are pretty good at protecting yourself from yourself, but it’s still just one wrong command and your partition table is broken which will be a pain in the rear to fix.

About the default setting, there’s plenty of reasons to not choose LVM, even if it is pretty neat. For example if you have a smaller drive on a laptop it usually doesn’t add much to even have multiple partitions at all. And also LVM has a small overhead compared to ‘raw’ partitions, so if you need to squeeze the last drop of disk-io out of the system LVM might not be the right choise. Or you might prefer zfs or brtfs. All solutions have their own pros and cons.

i still need to find a way to setup a simple sambashare via a web gui and a good backup solution.

I’m running openmediavault as an VM for file shares and backups with proxmox backup server. Works pretty well. I’ve got a physical backup server in detached garage and another in a VPS which syncs the most important parts to remote location.

Swapfile refers to a file at /. As long as you have rootfs there’s a place to put that swap file too, so no worries there. Usually there’s a separate partition for swap, but that works too.

So, what you need to do is remove sda1 and sda2 windows partitions. That’ll leave you ~520GB of unallocated space at the start of the drive. Create a partition there and set it to ‘Linux LVM’ -type. Then create LVM ‘filesystem’ on that partition, or more accurately, assign that partition as an LVM physical volume with ‘pvcreate’. After that you need to create a volume group with ‘vgcreate’. Now you’ll have 520GB allocated to LVM. Create new partition for your home with ‘lvcreate’, use all the space if you like, but at least as big as your current consumption on /home. Then create an filesystem on it and mount it as /mnt/newhome (or whatever).

Log out with your main user and make sure there’s no processes running on that user afterwards. Then you can copy data from current home to newhome and unmount the now old home (sda8). Change fstab so that your new home will be mounted on /home (blkid to get UUID and change that to fstab). Mount new home in it’s proper place, old home partition will be unmounted at this stage. Verify that everything works.

Now you can change your current sda8, a.k.a. old home, to Linux LVM-type, assign that as LVM physical volume and extend your volume group with vgextend to include the another partition. And now with lvextend you can expand your brand new home directory to that ~850GB total.

But, as I mentioned, make sure that you have your backups in good shape. These steps, if done incorrectly, will destroy your data. That’s also why I’m being somewhat vague on the instructions, you’ll need to understand what you’re doing. There’s plenty of information to push you in the right direction, but trust me, it’s better for you to take a minute or two and read documentation so that you’re actually confident on the steps.

Just to add, for this you need to use some kind of live boot / rescue media from USB. You can’t do that on a live system. Also after moving your rootfs change your fstab to reflect the new setup.

Well, moving partitions is at least a bit tricky and somewhat unreliable. So, unless you do a full repartitioning you will have sda1 with 520GB(ish). Current /home partition you can extend to fill the ~550MB from end of the drive.

Then it’s up to you what you want to do with that 520GB. One option would be to build LVM (or zfs if you wish, LVM likely makes more sense on your case) setup from that and current /home partition and that way you could have ~850GB logical partition for home. Or you can just format the new sda1 as ext4 and mount it to /home/youruser/Media or whatever and have your home directory data split to two different partitions.

But whatever you decide, when messing around with partitions make absolutely sure that your backups are in good shape. One small error somewhere and your data might be gone, or at very least you need to learn how to rebuild partition tables. Also when changing partitions check that your fstab uses UUIDs instead of device paths or your system may not boot cleanly. Broken fstab is fairly simple to fix, but it’s easier to check that while the system is up and running.

I definitely didn’t suspect there to be a whole new standard of wireless communication to that.

There’s multiple. Some devices are on wifi, some on z-wave and as zigbee is getting quite a lot of support from vendors I’ll likely add that to the mix soon-ish. Also I could use bluetooth for some automations, but at least for now I don’t really see any advantages over that.

As for pihole, it’s main DNS server for devices in my network and rest of the family uses the net quite a lot too (IPTV and streaming services included) so any longer downtime would cause at least annoyance for them so it’s nice to have an option to keep things running and take my time to maintain hardware or whatever. I of course could change DHCP server to offer something else too, but it’s simpler and faster to just migrate a VM to another host.

Is there a benefit for splitting your services on 2 hosts?

I don’t know about OPs situation, but I have a mini-PC as proxmox hypervisor too addition to my main server. Mini-PC is located middle-ish of the house as it’s running home assistant with ZWA-2 and the location helps a lot with Z-wave coverage. But added benefit is that I can (within the pretty strict resource limits) move VMs to the mini-pc when doing maintenance on main server. It’s pretty handy to move PiHole and some other small stuff to another host so that everything on network still functions even if one hypervisor is down.

I don’t have Fedora around, but in general just install all the desktop environments you wish from package manager. Most (if not all) login managers support changing the environment on every login. I don’t remember exactly how that works on plasma login manager, but there should be a pretty obvious menu item to pick from before inputting your password.

You obviously need to have autologin disabled in order to see the selection screen.