Hello.
I have manjaro installed on a sata ssd. I bought a larger m.2 ssd. Used gparted live to copy all partitions including the unallocated space in the beginning, as well as partition flags.
When booting the new disk, I get the following error:
error: no such partition.
Entering rescue mode…
grub rescue>
on you M2
all UUID are different
see lsblk - fs
then go in chroot and update /etc/fstab ,
return in chroot ( /boot or /boot/efi have to be ok )
2) unless you have copied /boot/ you need to re-install grub ( for UEFI or Bios )
recheck with gparted that flag boot ,esp ( uefi ) is ok
Thank you for your response. Can you guide my in the right direction for chroot?
~ lsblk -fs
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
loop0
squash 4.0 0 100% /var/lib/s
loop1
squash 4.0 0 100% /var/lib/s
loop2
squash 4.0 0 100% /var/lib/s
loop3
squash 4.0 0 100% /var/lib/s
loop4
squash 4.0 0 100% /var/lib/s
loop5
squash 4.0 0 100% /var/lib/s
loop6
squash 4.0 0 100% /var/lib/s
loop7
squash 4.0 0 100% /var/lib/s
loop8
squash 4.0 0 100% /var/lib/s
loop9
squash 4.0 0 100% /var/lib/s
loop10
squash 4.0 0 100% /var/lib/s
loop11
squash 4.0 0 100% /var/lib/s
loop12
squash 4.0 0 100% /var/lib/s
loop13
squash 4.0 0 100% /var/lib/s
loop14
squash 4.0 0 100% /var/lib/s
loop15
squash 4.0 0 100% /var/lib/s
loop16
squash 4.0 0 100% /var/lib/s
sda1 vfat FAT32 5759-F02A 299.1M 0% /boot/efi
└─sda
sda2 ext4 1.0 8ddaa5e3-9f1d-4233-a023-29ea2cad9e44 2.5G 94% /
└─sda
sdb1 ext4 1.0 SSD2 e4cc1477-ad3f-4b63-99f1-83e07b0d347e 80.4G 60% /mnt/ssd2
└─sdb
sdc1 iso966 Jolie MANJARO_GNOME_2102
│ 2021-04-19-09-09-21-00 0 100% /run/media
└─sdc
iso966 Jolie MANJARO_GNOME_2102
2021-04-19-09-09-21-00
sdc2 vfat FAT12 MISO_EFI
│ 1DD5-8963
└─sdc
iso966 Jolie MANJARO_GNOME_2102
2021-04-19-09-09-21-00
nvme0n1p1
│ vfat FAT32 5759-F02A
└─nvme0n1
nvme0n1p2
│ ext4 1.0 8ddaa5e3-9f1d-4233-a023-29ea2cad9e44
└─nvme0n1
# /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).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=5759-F02A /boot/efi vfat umask=0077 0 2
UUID=8ddaa5e3-9f1d-4233-a023-29ea2cad9e44 / ext4 defaults,noati>
tmpfs /tmp tmpfs defaults,noati>
/dev/disk/by-uuid/e4cc1477-ad3f-4b63-99f1-83e07b0d347e /mnt/ssd2 auto nosuid,no>
I think the cloned partition nvme0n1p1 has the same ID as the original partition on the sata ssd. Is this what is causing my issue?
you have used a cloning tool ( like clonezilla )
1 - UUID are the same
2 - size partitions are the same ( lost space )
see df -Th and sudo fdisk -l
3 - only /boot/efi from sda3 is created on efibootmgr
in thes situation avoid to boot with both disks ,
because having same UUID , you dont know on which disk it will write
redo partition with gparted on nvme for zize , then copy with grsync
update UUID on nvme
sudo lsblk -fs
sudo manjaro chroot -a
nano /etc/fstab
exit ( quit chroot )
for next chroot with boot/efi to get mounted
sudo manjaro chroot -a
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck --verbose
efibootmgr -v
update-grub
exit ( quit chroot )
Issue is resolved. This worked for me: Cloning a Root Disk (Linux) · GitHub
1 Like
system
Closed
6 May 2021 11:28
7
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.