SDA1-3? I have a feeling I can just want to be sure.
Definitely NOT /dev/sda1 (!)
It appears to be part of your system and is therefore absolutely necessary.
Only you know what is on /dev/sda2 and /dev/sda3 and whether you need what is presently there.
If you delete them while the entries for them are still in /etc/fstab you will have problems booting the system.
It will either hang for a long time or not boot at all.
Check and edit /etc/fstab as well when you decide that you are going to remove these partitions.
Have a backup!
Absolutely not, sda1 is your linuxās (and your (former) win efi partition), donāt mess with it. Sda2/3 look like win partitions, the sda2 fat may be some win recovery and sda3 the win āc-driveā, you have to decide if you still need those partitions and the data on them. If you dual-boot with win donāt touch anything.
Just to be clear, āunallocatedā in gparted speak means āblankā, āemptyā, āwipedā.
āCan I unallocate theseā is misleading since there is no āunallocateā button. You can, however, delete those partitions which will then show āunallocated spaceā were they have been before.
Sorry only meant SDA2-3 wasnāt all the way awake. SDA2/3 is a Win install that wonāt boot up right, so SDA4 will stay SDA4 I want to make 2/3 into 1, that will no screw up Linux right?after I get rid of 2/3.This is my fstab.
!# /etc/fstab: static file system information.
Use āblkidā to print the universally unique identifier for a device; this may
be used with UUID= as a more robust way to name devices that works even if
disks are added and removed. See fstab(5).
UUID=6DB0-0A0F /boot/efi vfat umask=0077 0 2
UUID=0647dad9-3687-4eba-8d09-acc5ce30021d / ext4 defaults,noatime 0 1
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
Just lloks like Linux is in fstaab.
Grubs list doesnāt have them, just the MB boot menu.
In this case, you should be able to safely remove those and re-allocate the space for data ā perhaps include a swap partition as well?
It should not - but it might.
It can become problematic should anything fail during the operation - which will take a long time.
Nothing unsurmountable - but some work and knowledge of what you are doing is better ā¦
It involves moving the start of that partition - expanding it āto the leftā.
If you have everything backed up ā¦ you can try.
Itāll probably work ok. but better safe than sorry, no?
1 Like
Iām afraid I misinterpreted things; I thought he meant to create one new partition in the free space.
Indeed, messing with an existing / partition is not without its risks. For example, a power outage during the process will really screw things up.
1 Like
Using gparted, you should delete sda2 & sda3. Gparted then should show you a single area (~250 Mb) that you could totally use to create a partition.
Do not touch sda1, do not try to use the unallocated area before it : 1 Mb lost : not a real problem .
And do not touch sda4, of course !
What is the content of /etc/fstab ?
ā¦ but (!)
he wantās to expand /dev/sda4 - in the direction towards sda1, to the left
Not a problem - but having a backup is (almost) mandatory when doing this.
OK but I donāt see the advantage of expanding sda4 as compared to the risks of moving its beginning and so its content. Adding a new partition in fstab is easy, and having a separate data partition is preferable. But itās only my opinion.
We are on the same page.
But that is what he wantās to do ā¦ 
Iād have a backup.
Then Iād completely recreate the partition layout as I want it
and then replay from backup after having mounted the partitions in order
and adapted /etc/fstab
Much cleaner and probably even faster.
1 Like
