Perfect. So you’ve got separate /boot and /boot/efi partitions, which means dual booting will be much easier if you want to do that.

The ubuntu--vg-ubuntu-lv is the logical volume you’ll want to resize. So now we need to see how much space is available on the volume. To get that, run the command sudo df -h and paste that output into a comment.

From there we can figure out how much space you have and how you might want to resize the volume to prep for a new install.

What is challenging about this is that your data is under your root (/) mount, which is also the ubuntu os. If in the end you want to entirely remove ubuntu, it’ll be a little trickier than if your data was in a separate logical volume that you mounted into your root system during boot.

For example many people have a separate logical volume for /home, which makes it easier to switch distros while preserving your home folder with all of your user data, config files, etc…

But that’s getting a little ahead of ourselves. Start with sudo df -h for the filesystem usage info and we can go from there.

Happy to help!

lsblk will give exactly the info needed. Copy the output of lsblk and paste it into a reply and that will be perfect. Or a screenshot. Whatever’s easier for you

Okay, more details will be required, but here’s what I’m thinking will work.

One of the benefits of an LVM is its pretty easy to resize it.

The outline of what you can do is this (and we can refine the steps with more details)

Right now you’ve got your 8TB physical volume, and within that, you should have your volume group, and within that volume group, you should have one or more logical volums that are mounted for your system. The idea is to resize the existing logical volume by shrinking it, creating addition space within the volume group that can be used to create a new logical volume. Then, that new logical volume can be used to install Fedora.

Depending on how much free space you have on the entire physical volume, you could potentially dual boot Fedora and Ubuntu. Roughly speaking, the steps would look like this:

WARNING: These steps are not exhaustive because I don’t know the full details of your system. This is not meant to be a guide for you to immediately implement and follow, but to help get you down the right path DO NOT FOLLOW THESE STEPS WITHOUT FIRST FULLY UNDERSTANDING HOW THIS WILL APPLY TO YOUR UNIQUE SYSTEM SETUP.

1. Download a Linux ISO of your choice. Ubuntu, Fedora, it doesn’t really matter. This one is going to be used to live boot on your server so you can make adjustments to your lvm without having the lvm mounted.
2. Boot into the live usb
3. Once you get to the desktop environment of the live usb dismiss any installation prompts, etc and open a terminal
4. Install the logical volume tools with sudo whatever-the-package-manager-install-command-is lvm2
5. If your volume group is encrypted (typically with LUKS), you’ll need to decrypt it to make sizing changes to the lvm(s) in the volume group. You can decrypt it with:
   1. cryptsetup open /dev/your-disk-here name-of-your-volume-group
   2. For example, on my system if I were doing this it would be cryptsetup open /dev/nvme0n1p2 server (I very creatively named my server volume group server)
6. Once you can access your volume group, you can use the df command to see how much space is free in your volume group. The full command you’ll want to run is:
   1. sudo df -h
   2. This command will list all mounted disks along with filesystem usage data. With this you should be able to determine how much free space you have in your volume group.
7. Once you’ve determined how much free space you have, you can decide how big you want to make your new logical volume. For example, if your current usage is 6TB out of the 8TB total, you could resize the current logical volume down to 7TB, and then create a new logical volume that’s 1TB in size for the Fedora install
8. You will do the resize using the lvm2 tools installed. The command to shrink the logical volume looks like this:
   1. sudo lvreduce --resizefs --size -1TB /dev/your-volume-group/the-lvm-name
9. Once you’ve shrunk the lvm, You can create your new lvm

IMPORTANT NOTES:

1. If at all possible, you should really back up the data. If you don’t have any kind of backups in place, you’re risking losing all of your data, not just in doing this operation, but in general.
2. If you want to dual boot, things are more complicated because of where your /boot exists

Can you detail the storage and is drives and mounts as well as the lvm structure? Knowing that will help people give useful advice.

BBSes are back!

That is a lovely setup. I’m gonna drop that into my bash_aliases so much more elegant than me adding the alias for each server.

I do have the servers in ~/.ssh/config. I just got tired of typing ssh server and wanted the be able to just type server to ssh in.

Hahaha. Fucking autocorrect. Git log.

alias gl='git log'
alias server-name-here='ssh server-name-here'

I have a bunch of the server aliases. I use those and gl the most.

If you do go with nextcloud, use the docker AIO (all in one) setup. It’s the officially supported method and it’s worked really well for me.

I don’t use OMV, but I have a nas server I built and here is my .02

• set up an smb share in OMV for windows. Mounting that in windows should be trivial (don’t hold me. Haven’t used windows in years now, but last I used win10 smb was super easy to mount)
• look into docker on OMV for deploying stuff. I run docker on my NAS and host a bunch of stuff including:
  • jellyfin for all the rips of my DVDs
  • navidrome for all the rips of my CDs
  • nextcloud to replace google stuff
  • radicale for my calendars
  • Joplin server for my notes
  • mealie for recipes
  • more stuff I can’t think of right now
• with docker, if you want a GUI for creating, managing and interacting with your stuff, look at Dockge and Portainer

Edit: added more stuff

I’ll give ultrasonic a try. Thank you.

🤜🤛

Have you had problems on android with tempo not continuing playback?

I also run navidrome, and have tried tempo, substreamer, and another client I can’t think of, and any of the clients that stream keep stopping playback after one song when the screen is locked.

I’ve given the client all the permissions for running in the background and using battery that I can and no matter what I do, it’ll just stop after one song.

I’m on a pixel 7a with gOS.

For now I’ve settled on Poweramp with tla selection of the music on my phone since I can’t fit it all in storage. Its been really frustrating.

As a self-hoster, I love docker. It’s been an amazing deployment tool.

Happy to help!

Awesome! Glad it worked. I’m no expert regarding the battery, but it should be okay. Lots of people use laptops as servers with them plugged in all the time. Just keep an eye on it and if you see any signs of swelling or excessive heat, pull and/or replace the battery.

Goid luck!!

That’s the process I’ve used when switching machines for seeding, and it works great, just takes time for it to recheck all the files.

On the Mac, open qbittorrent, select all torrents in the client, and export them as torrent files or magnets, whichever you prefer.

Copy all the torrent/magnet files to a thumb drive or something and copy them to the elementary laptop.

On the elementary laptop, start without an internet connection. Connect the external drive with all the downloaded files, mount it if elementary doesn’t auto mount it, and note the path.

Open qbittorrent.

Set the default save path in qbittorrent to the path of the mounted drive with all of your downloaded files.

If you want to do it in bulk, now add all the torrent files to QBittorrent. You may have to verify the file location for the torrents to make sure it sees the files on the drive.

Once you’re certain all the loaded torrents are pointing to the save path for the files, you can close qbittorrent, connect the laptop to the internet, and relaunch qbittorrent.

It should verify all the files it finds for the torrents, which can take some time if you have a lot of torrents, and once verified it’ll automatically start seeding

For me it’s Perl’s rename, which of course cones in a variety of package names depending on the distro you use. In trying to find a link, I landed on this stack exchange answer that gives a great overview of how the tool works and the different packages available on different distros.

I have to bulk rename files every day, and using regex and the other features of Perl’s rename makes it so much easier to do.