Arch Linux

nexx1

Member

Registered: 2017-08-20

Posts: 72

[solved] Issues with enlarging a partition

Hi!

I mirrored a SSD to another SSD with dd which worked just fine. System boots, everything works.

Issue: Old SSD = 250 GB and new SSD = 500GB, so there are 250GB unallocated space that i definately want to use.

Using gparted, i can see that the boot partition was at the end of the old SSD and now i sitting between the data partition and the now unallocated space.

Trying to move the boot partition to the end of the disk results in a borked grub, so booting ends in the grub rescue shell where i do not know what to do.

Do i need to somehow tell grub what changed? Or am i doing something completely wrong?

Filesystem according to gparted is "grub2 core.img" with the description "BIOS boot partition".

fdisk -l

Festplatte /dev/nvme0n1: 465,78 GiB, 500107862016 Bytes, 976773168 Sektoren
Festplattenmodell: Samsung SSD 970 EVO 500GB               
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: gpt
Festplattenbezeichner: 7997A249-94E7-4D49-BCBB-078463CB4384

Gerät               Anfang      Ende  Sektoren  Größe Typ
/dev/nvme0n1p1     2099200  65013759  62914560    30G Linux-Dateisystem
/dev/nvme0n1p3    65013760 488390655 423376896 201,9G Linux Home
/dev/nvme0n1p4        2048   2099199   2097152     1G Linux Swap
/dev/nvme0n1p128 976764928 976773119      8192     4M BIOS boot

Thanks in advance!

Edit: solved.

Last edited by nexx1 (2020-03-11 20:47:33)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,391

Re: [solved] Issues with enlarging a partition

It'll probably suffice to rerun grub-mkconfig (maybe reinstall GRUB, not sure by which heuristics it tries to find that partition on a BIOS boot). FWIW any particular reason you are explicitly using BIOS and not UEFI boot?

nexx1

Member

Registered: 2017-08-20

Posts: 72

Re: [solved] Issues with enlarging a partition

It'll probably suffice to rerun grub-mkconfig (maybe reinstall GRUB, not sure by which heuristics it tries to find that partition on a BIOS boot). FWIW any particular reason you are explicitly using BIOS and not UEFI boot?

Maybe a stupid question: But where shall i execute grub-mkconfig?
I am currently only able to do a chroot into this SSD and i can not mount the boot partition, only the two ext4 partitions.
Same thing for reinstalling grub, since i cant mount the boot partitions, i doubt it will be able to find the partition

Reason for why I use BIOS instead of UEFI... Best guess: Wrong (and poor) choice during system setup 2 years ago. Can i correct/change this afterwards?

Last edited by nexx1 (2020-03-11 16:18:07)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,391

Re: [solved] Issues with enlarging a partition

grub-mkconfig should be to where your grub confguration files lie which will normally be /boot/grub: https://wiki.archlinux.org/index.php/GR … ation_file

You don't need to mount the "boot" partition, that just has to be present for GRUB to boot in BIOS boot mode on a GPT disk. And you don't install GRUB on there, if you continue with BIOS boot you will want to install it into nvme0n1 (I'd assume, this is something you will have done during installation)

If you were to switch to EFI mode you need to boot the live disk in EFI mode, create an ESP partition that is big enough to at least house GRUB and run the EFI GRUB install command (and install efibootmgr in the chroot so it can work correctly).

nexx1

Member

Registered: 2017-08-20

Posts: 72

Re: [solved] Issues with enlarging a partition

Okay, so using grub-mkconfig in chroot doesnt change the boot behaviour. I am still landing in the grub rescue shell with this error:
"symbol 'grub_file_filters' not found".

Guess i am gonna reinstall grub then

Edit:
Hmm, when chrooted, i ran "grub-install /dev/nvme0n1" which resulted in this error:

"x86_64-efi will be installed for your platform.
grub-install: Error: EFI-directory cannot be found"

Reading the wiki helps: --target=i386-pc executed without error.

Now i am getting an error when doing grub-mkconfig -o /boot/grub/grub.cfg:

"grub-probe: error: cannot find GRUB-device for /dev/sda1. Check your device.map"
but the last line is just "done"

Where does the sda1 now come from?! I did not specify this. Only sda1 active is the USB-drive i am currently booting from.
Doesnt matter, since i have now successfully booted
Now i just gotta fix the awful delay between logon and the window manager. Before it took maybe 1 seconds, now its about 1 minute. But thats another topic, thanks V1del!

Last edited by nexx1 (2020-03-11 17:14:44)

WorMzy

Administrator

From: Scotland

Registered: 2010-06-16

Posts: 13,662

Website

Re: [solved] Issues with enlarging a partition

Please remember to mark your thread as solved by editing the first post and amending the topic title.

https://wiki.archlinux.org/index.php/Co … ow_to_post

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.