What I am Trying To Do: I am trying to move my root file system from its small partition on /dev/sda6 to a new larger partition on /dev/sda8.
My Problem: The small partition sda6 is still being mounted on boot, despite changing the fstab root file system UUID to the UUID of sda8.
Edit About Accepted Answer
The accepted solution takes a few steps back and just moves around and resizes partitions so that the original root and home partitions have more space. All this trouble about fstab and partitions mounted on boot is completely avoided.
What I Have Done So Far:
- Create new partition
sda8. - Copy small partition
sda6tosda8. - Create new UUID for
sda8. - Modify
sda6(small partition)/etc/fstabfile to usesda8UUID as root file system.
I expect the problem to be related to grub, or that I am editing the old partition's fstab, or something about the new partition's fstab file. I might have a fundamental misunderstanding here.
sda6 (small partition) /etc/fstab
UUID=7aead843-45c2-4456-a1d4-02c67af0769c / ext4 errors=remount-ro 0 1
UUID=485E-AB22 /boot/efi vfat umask=0077 0 1
UUID=ec4e914c-caaa-43e2-aeb2-4f346ba0411c /home ext4 defaults 0 2
UUID=cc8208be-d94f-493a-a19f-94d7083c0f84 none swap sw 0 0
block ids
/dev/sda6: UUID="39c4c3de-19ec-4fea-917d-45e0a0178f76" TYPE="ext4" PARTUUID="c5096f2e-5526-4801-8612-ae385d3c3e6e"
/dev/sda8: UUID="7aead843-45c2-4456-a1d4-02c67af0769c" TYPE="ext4" PARTUUID="05db311f-a362-4ba2-8a0b-c7ae4fc2c380"journalctl section of last boot
...
Jan 04 17:37:23 GL4D2B kernel: sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8
Jan 04 17:37:23 GL4D2B kernel: sd 1:0:0:0: [sda] Attached SCSI disk
Jan 04 17:37:23 GL4D2B kernel: scsi 3:0:0:0: Direct-Access Kingston DataTraveler 3.0 PMAP PQ: 0 ANSI: 6
Jan 04 17:37:23 GL4D2B kernel: sd 3:0:0:0: Attached scsi generic sg2 type 0
Jan 04 17:37:23 GL4D2B kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
Jan 04 17:37:23 GL4D2B kernel: sd 3:0:0:0: [sdb] 15360000 512-byte logical blocks: (7.86 GB/7.32 GiB)
Jan 04 17:37:23 GL4D2B kernel: sd 3:0:0:0: [sdb] Write Protect is off
Jan 04 17:37:23 GL4D2B kernel: sd 3:0:0:0: [sdb] Mode Sense: 23 00 00 00
Jan 04 17:37:23 GL4D2B kernel: sd 3:0:0:0: [sdb] No Caching mode page found
Jan 04 17:37:23 GL4D2B kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
Jan 04 17:37:23 GL4D2B kernel: sdb: sdb1
Jan 04 17:37:23 GL4D2B kernel: sd 3:0:0:0: [sdb] Attached SCSI removable disk
Jan 04 17:37:23 GL4D2B systemd[1]: Inserted module 'autofs4'
Jan 04 17:37:23 GL4D2B systemd[1]: systemd 240 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -ID
Jan 04 17:37:23 GL4D2B systemd[1]: Detected architecture x86-64.
Jan 04 17:37:23 GL4D2B systemd[1]: Set hostname to <GL4D2B>.
Jan 04 17:37:23 GL4D2B systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument
Jan 04 17:37:23 GL4D2B kernel: Lockdown: systemd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7
Jan 04 17:37:23 GL4D2B kernel: Lockdown: systemd: BPF is restricted; see man kernel_lockdown.7
Jan 04 17:37:23 GL4D2B systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
Jan 04 17:37:23 GL4D2B systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
Jan 04 17:37:23 GL4D2B systemd[1]: /lib/systemd/system/spice-vdagentd.service:8: PIDFile= references path below legacy directory /var/run/, updating /var/run/spice-vdagentd/spice-vdagentd.pid → /run/spice-vdagen
Jan 04 17:37:23 GL4D2B systemd[1]: Listening on udev Kernel Socket.
Jan 04 17:37:23 GL4D2B systemd[1]: Listening on udev Control Socket.
Jan 04 17:37:23 GL4D2B systemd[1]: Created slice system-systemd\x2dfsck.slice.
Jan 04 17:37:23 GL4D2B kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
...
Gparted Screenshot