alright, good news, you probably are using qemu. the disk images (that’s the hard drives for the vm) are usually in the .local/share/gnome-boxes/images/ in your home directory. if the images are .qcow2 files then you’re running qemu.

deleted by creator

Even if you know how to do stuff, I’d avoid doing ostree on a universal blue derivative.

I been using Linux for 25 years and just recently embraced the “don’t break Debian” part of the backport manual.

Stuff you do and don’t document or don’t force yourself to recognize comes back to bite you years later when you can’t use the normal tooling in order to deal with it.

Anyway, good luck, it sounds like you’ll be fine.

Also, don’t jump straight into a universal blue derivative. Actually learn how to use Linux before you start in with something that relies on a bunch of convenience features.

Iotop will help you figure out what process is causing zfs to timeout when syncing.

Yes

Alternately, since the vm has network access, just use ssh from your windows vm to scp your files from the windows vm to the Linux host.

Just turn off the vm (shutdown the windows install running in the vm, not pause), mount the vm block device, navigate to the file and get it that way.

Are you using qemu?

It’s easy if you have a second computer or phone or something and can read and plan first.

It’s hard if you want to just click click click through.

Don’t look too deeply into this unless you’re comfortable discovering that the military and security state is a prolific contributor to many open source projects.

Swap em around if they’re the same interface.

When the time came to pick which boring old man distro to use, the people who picked and would recommend fedora all got jobs supporting rhel. They don’t have time or energy to devote to computer touching when they get home from their serious business jobs making sure the computer keeps increasing shareholder value.

Fedora is very good.

Hell yeah!

Take some time to get familiar with using chroot or boot-repair to fix the bootloader when a windows update inevitably breaks it.

Yep. As long as you pick install alongside it won’t screw up windows. If you don’t see that option in the “disk selection” part of the process then bail out.

Nah, you’re gonna boot from usb and go through till you get the option to install alongside and pick that.

It’ll only show you that option if you have some unallocated space on your disk from resizing the c drive though.

alright, go through the ubuntu installer and pick the “install alongside” option when it comes up. it ought to be at the same time that it offers you the option to erase the disk altogether. the “installation type” menu. if you don’t get that option, stop and say so.

e: i just finished installing ubuntu desktop lts alongside windows 11 in a vm using the process you’re doing. its the disk selection menu, not the installation type.

right on, you have enough space to not end up in trouble!

in windows, right click the start menu and choose “disk management”

it’ll bring up an old looking MSI that shows your drive and the different partitions it has.

right click the C drive and choose “shrink”.

you’ll get asked how much you want to shrink it by iirc. type in the number and click okay.

once that is done, the disk management window will show the new free space.

if everything goes as planned, make sure you turned off bitlocker and restart into windows.

okay, that’s fine! make sure to turn off bitlocker.

once you’ve done that you’re gonna resize your partitions in windows. i’ll walk you through that.

so your C: drive is 210 GB, how much free space do you have on it?

I wouldn’t. Go ahead and make a new bootable usb using rufus or something.

What’s your partitions look like right now?

Imma just start typing and see where this goes:

Sd cards arent the same as usbs or ssds. They seem the same because it’s like the same thing right? But they’re not.

Most usbs and all ssds have a controller that actually handles writing and reading to and from the memory chip. The controller lets them do things like recognize bad spots and write data elsewhere, perform secure erase functions, wear leveling and all sorts of the kinda stuff we expect of components we’re gonna use as hard drives.

Sd cards almost universally don’t have that controller. The goal for sd cards was to provide bulk storage to all kinds of embedded devices like cameras and later, phones. Because there’s no controller, there’s no wear leveling, no overprovisioning, no secure erase. That’s fine because the goal was always to just slam the sucker full of pictures and never erase it till it gets full, then start all over again.

But if sd cards aren’t acceptable hard drives then how come we use them in little sbcs like raspberry pi and whatnot?

Well the install process in that case almost always writes the system to the card first instead of doing a million reads and writes to figure out what repositories are available, updating packages, etc. sbc systems using sd cards as their storage are also (or should be!) configured to do minimal writes, with constrained log sizes and minimal swap.

So don’t use an sd as a usb or hard drive.

People might say that I’m wrong in replies to this post. They’ll say that sd cards are fine and that they have over 20k write cycles on their hyinx megacard128. Sd fails silently. I am not wrong. You literally just had problems installing from an sd. I can’t tell for sure if your problems came from using an sd or misconfiguring the new partition scheme but it sure as heck didn’t help that you used an sd as your install media.

Okay, now you said you have windows back up and running. Is it fully recovered and working good?

Is it using the whole drive?

Do you have all your files back?

Have you made a backup?

If you answer these questions I can walk you through the process of setting up windows to dual boot Linux in a way that won’t fuck up.