Use a surface cleaner first. You wanna get the majority of the crud broken up and off first, wiping towards the middle then go get the whole thing with a glass cleaner using a microfiber cloth if you don’t have a squeegee.

• Write down GUID for sda6
• copy sda5 contents somewhere
• dd sda6 to sda2
• delete sda6
• change the GUID for sda2 to the one written down
• fsck sda6 to fix size
• make sda1's type EFI
• copy sda5 contents to sda1
• delete sda5
• you can now resize whatever is left (if your partition tool doesn't have resize, just delete and recreate with the same starting sector, again you have to keep GUID for root and fsck it to fix size)

Careful with wiping anything with the "boot" flag. That can backfire very badly depending on how your system is set up. Those are small anyways so i would just leave them and only kill the ntfs partitions and combine that space into an extra partition that you can store stuff in.

Resizing partitions is messy so if you want a clean setup with one big home partition i would just reinstall. You could also copy everything in the home partition to a backup drive and just try out resizing. If it breaks you can create a new home partition and copy everything back.

Kinda already covered by others here, but my summary:

You won't have partitions nicely numbered from 1~3 unless you start again.

1 - Backup

2 - Check the backup

3 - Boot from GParted Live (feel free to use another live distro with gparted on)

4- Delete sda1, sda2, sda3 & sda4

5- Move sda5 to the beginning of the drive and resize down to 512MB

6- Slide sda6 & sda7 down next to sda5. I like to have 1MB gap between all partitions to deal with future issues (sometimes restoring a partition might nip the next one)

7- resize /home to fill the rest of the drive

8- redo another backup

If you wanted, you can apply each of those steps and then reboot to check it's all working, then you'll gain confidence in what's happening for the future.

I also advise doing a health scan of your drive to check it's SMART parameters. Something like smartmontools (with gsmartcontrol if you like a GUI). Then you'll know if the drive's going to die during all that data moving...

For historical reasons, I've had a /space partition for several machines now. It's used for large media archives, buffering towards other servers (which only grab stuff every now and then), cold storage and the like.

I would simply delete sda1 and sda2, then that whole part will be available as 1. Format as ext4.

If you play games with steam you could then use it as a space to put games. Steam handles it for you. When you add a disk via Steam settings, it will be listed as an option.

Moving partitions is a tedious task and doesn't always pan out, I personally wouldn't risk it. Let it be a thing to do if you would ever reinstall completely for whatever reason and start fresh then.

Also, backup backup backup.

Everything with a lock means it’s mounted and in use. sda1, sda2, sda3 and sda4 should be safe to format, however as others have mentioned, booting into a live environment is the best course of action as it lets you freely move or extend partitions.

I suggest finding a thumb drive and flashing Gparted onto it.

Personally I'd just boot into a live environment so the SSD isn't in use, backup important things, then wipe windows partitions and resize /home to use the rest of the space on the disk

I would delete the first two partitions and put a new partition there to use as /home. Then expand / where /home was.

It's easy to expand a partition towards the end of the disk. I would not recommend expanding one towards the start of the disk. That would have to move all of the data. It's slow and much more likely to cause problems.

I wouldn't suggest messing with a boot partition unless you are comfortable using a live boot disk to reinstall the bootloader if something goes wrong.

The easiest solution is to format windows partition and mount it as separate mount point (for example /mnt/extra) and use it for storing any large files you have (movies, songs, books, photos, backups, downloaded files ...)

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.

Boot a live image from USB, copy /home to a separate physical disk preserving ownerships and permissions, and save anything from the windows partitions that you want you keep. Once you've verified the copy is good delete all the original partitions on the screenshot.

From here you install from scratch. You'll appreciate it later when things aren't a jumbled mess.

If you have any kind of ssd install the OS to that instead, then use that spinning drive for /home. If you have two ssd drives do /home on the second one and use the spinning one for longer term storage like music or videos or the like.

Also don't put your swap partition on an ssd, use the spinning drive for it so you're not wearing out the ssd. You can do a swap file instead of a partition if you miss the windows way. 😆

I am assuming everything other than the two ext4 partitions will have to go.

Your /dev/sda5 the FAT32 mounted at /boot/efi has to stay too! That's your EFI System Partition, it's essential for the boot chain.

What you can do is delete the "Microsoft" directory that's on there, but definitely keep the one named after your distribution!

that is an odd layout, even for a windows system with linux added later.

what's the actual order of the partitions on disk?

The sda1 and sda2 partitions seem safe to format. Just be sure that you really copied everything you need from there. Like others said, better not to mess with the boot partitions

If you want to increase the space of the linux partitions, insead of creating a new extra partition, that may be a bit tricky in that layout, but one thing you can do is (from a live boot) is:
1- delete both windows partitions and create a new ext4 one with ~530gb
2 - clone your /home partition into there and change the fstab to point to the new partition
3- manually check if all your files were safely copied, just to be sure
4 - delete the old /home and expand the size of the / partition into it

you will end with a / partition with ~300gb and a /home of ~530gb

Generally, it's as simple as just deleting the Windows NTFS partition. I would leave the others for now. Depending on how you installed your distro they may be related to your Linux installation. Deleting them could prevent you from booting into your Linux installation.

I'm not as familiar with UEFI as BIOS, but I believe UEFI uses a FAT formatted partition for booting into the OS proper.

You may need to adjust the boot order in your UEFI/BIOS afterwards to get it to boot back to Linux afterwards, but that is fairly uncommon in my experience.

The most likely issue you might run into is accidentally wiping your active Linux partition instead of the Windows one.

I would make backups and have your distros install disk handy before you wipe the partitions.

Afterwards, you can resize your linux root to include the now free space or move your home directory to the new partition after formatting it. Your call.