Cant boot manjaro after cloning disk

Support
1

hi

i have a dualboot (windows10/manjaro) setup on my ssd 1. i cloned the whole disk to another ssd 2 with clonezilla, but this somehow broke something

i wasnt too surprised that ssd 2 would not work as intended right away, but i cant even boot ssd 1 manjaro now. windows on ssd 1 however still works

when i boot from ssd 1 the following appears

i translated from german to english, so it might not be the exact phrasing

the manjaro boot menu also looks different

trying to boot ssd2 i get this

i hope thats not too hard to fix, it looks like grub broke or something. i dont know much about that, please help :smile:

edit:

i would be fine if ssd2 works, i have other plans for ssd1 anyways. trying to fix it myself with rescatux, lets see how it goes

2

boot into manjaro usb, connect to internet, open terminal and chroot:
sudo manjaro-chroot -a
post output from what kernels you have installed and if you are running bios or efi:
mhwd-kernel -li
test -d /sys/firmware/efi && echo efi || echo bios

3

sudo manjaro-chroot -a

post output from what kernels you have installed and if you are running bios or efi:

4

the chroot didnt detect any manjaro installation … so the kernel command is useless …
what kind of filesystem are you using?

5

im using btrfs

6

so manjaro-chroot -a command will not work … i dont use btrfs, so search on forum how to chroot into btrfs, then when you chrooted post output from:
mhwd-kernel -li

7

im pretty lost right now, in a thread i found they say

but as far as i understand it is already mounted. in partition manager i can see that the clone worked to some extent…and i can access the manjaro partition of sda2

8

check this on wiki for manual chroot:

again i dont use btrfs, i cant help you with that …

1 Like
9

isnt chroot supposed to mount the partition? sry i dont get it

i can access my whole manjaro partition, it IS mounted

10

thats irrelevant to your issue, you need to chroot to fix your system, use the commands from the wiki

1 Like
11

i am trying, but i dont understand it. i dont even know if this is an attempt to fix ssd1 or ssd2

12

post output from:
lsblk
use formatting, click this icon in editor: </> - copy the output here

13 
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0  21.2M  1 loop /run/miso/sfs/livefs
loop1         7:1    0 717.4M  1 loop /run/miso/sfs/mhwdfs
loop2         7:2    0   1.9G  1 loop /run/miso/sfs/desktopfs
loop3         7:3    0 645.3M  1 loop /run/miso/sfs/rootfs
sda           8:0    0 232.9G  0 disk 
├─sda1        8:1    0   100M  0 part 
├─sda2        8:2    0    16M  0 part 
├─sda3        8:3    0  77.9G  0 part /run/media/manjaro/46926F73926F6701
├─sda4        8:4    0   525M  0 part 
├─sda5        8:5    0   9.8G  0 part 
├─sda6        8:6    0   512M  0 part 
└─sda7        8:7    0 114.7G  0 part 
sdb           8:16   1   3.8G  0 disk /run/miso/bootmnt
├─sdb1        8:17   1   3.3G  0 part 
└─sdb2        8:18   1     4M  0 part 
nvme0n1     259:0    0 238.5G  0 disk 
├─nvme0n1p1 259:1    0   100M  0 part 
├─nvme0n1p2 259:2    0    16M  0 part 
├─nvme0n1p3 259:3    0  77.9G  0 part /run/media/manjaro/46926F73926F67011
├─nvme0n1p4 259:4    0   525M  0 part 
├─nvme0n1p5 259:5    0   9.8G  0 part 
├─nvme0n1p6 259:6    0   512M  0 part 
└─nvme0n1p7 259:7    0 114.7G  0 part /run/media/manjaro/58438351-f9e6-499d-acb6-b33346879fd3

/dev/loop0                                                 squashfs 
/dev/loop1                                                 squashfs 
/dev/loop2                                                 squashfs 
/dev/loop3                                                 squashfs 
/dev/sda       gpt                                                  
/dev/sda1      gpt    c12a7328-f81f-11d2-ba4b-00a0c93ec93b vfat     EFI System
/dev/sda2      gpt    e3c9e316-0b5c-4db8-817d-f92df00215ae          Microsoft reserved
/dev/sda3      gpt    ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 ntfs     Microsoft basic data
/dev/sda4      gpt    de94bba4-06d1-4d40-a16a-bfd50179d6ac ntfs     Windows recovery environment
/dev/sda5      gpt    0657fd6d-a4ab-43c4-84e5-0933c84b4f4f swap     Linux swap
/dev/sda6      gpt    c12a7328-f81f-11d2-ba4b-00a0c93ec93b vfat     EFI System
/dev/sda7      gpt    0fc63daf-8483-4772-8e79-3d69d8477de4 btrfs    Linux filesystem
/dev/sdb       dos                                         iso9660  
/dev/sdb1      dos    0x0                                  iso9660  Empty
/dev/sdb2      dos    0xef                                 vfat     EFI (FAT-12/16/32)
/dev/nvme0n1   gpt                                                  
/dev/nvme0n1p1 gpt    c12a7328-f81f-11d2-ba4b-00a0c93ec93b vfat     EFI System
/dev/nvme0n1p2 gpt    e3c9e316-0b5c-4db8-817d-f92df00215ae          Microsoft reserved
/dev/nvme0n1p3 gpt    ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 ntfs     Microsoft basic data
/dev/nvme0n1p4 gpt    de94bba4-06d1-4d40-a16a-bfd50179d6ac ntfs     Windows recovery environment
/dev/nvme0n1p5 gpt    0657fd6d-a4ab-43c4-84e5-0933c84b4f4f swap     Linux swap
/dev/nvme0n1p6 gpt    c12a7328-f81f-11d2-ba4b-00a0c93ec93b vfat     EFI System
/dev/nvme0n1p7 gpt    0fc63daf-8483-4772-8e79-3d69d8477de4 btrfs    Linux filesystem
14

run this command:
lsblk -o PATH,PTTYPE,PARTTYPE,FSTYPE,PARTTYPENAME
and edit your previous post by putting the output there

15

since you have 2 identical disk with 2 identical efi bootloaders, you can remove one efi bootloader, and see if that helped

16

Using simple clonezilla is a bad idea. (I have never used it myself.)
Both SSDs have different UUID, you have to edit GRUB config and /etc/fstab and completely regenerating GRUB, check efibootmgr -v …

I would reinstall OS and copy/rsync some important data into new SSD instead using clonezilla.

Of course, Btrfs supports btrfs send | btrfs receive instead clonezilla.

1 Like
17

i thought thats what its for … cloning disks. and i really (!) dont understand how it could mess up ssd1, when its only supposed to read it

at this point probably a reinstall will be necessary :roll_eyes: but id really like to boot into my manjaro on more time to get an overview of what i will need to backup

can i maybe fix the system by using a snapshot? there should be 1 not too old

18

It is, but you shouldn’t have cloned it. Cloning copies everything including UUIDs and empty space. Good for building multiple identical computers, taking a copy of a drive for file recovery/forensics etc.

You now have two identical drives, that could cause problems. Perhaps clonezilla can’t handle btrfs, I don’t use either so I don’t know what complications you may or may not encounter.

Did windows have to recover? If so it may have overwritten your grub config.

First try removing one of the drives, if the filesystem on the other drive is good it should boot. :crossed_fingers: However those errors imply there’s something wrong with your grub config.

The proper way to move a partition (for btrfs there’s also send/receive): create new partition, mount both partitions, copy files over, sync, umount, update fstab, and if it’s the / partition then update grub too. (/ is best done from a live USB, chroot to update grub)

(data || settings) != OS, don’t keep them on the same partition, use a separate home partition. Then you can re-install all you want without losing user settings/data.

If you need to backup/re-format then you can do it from a live USB.

@Zesko

They did before the cloning, now they’re the same.

19

Perhaps its usefull to use :

… but i don’t know if its ok with btrfs!

I still don’t use btrfs but ext4 and backintime that backups automatic the whole system every night using rsync, so only new/changed data will be included.
This prevents me of having much trouble as you have now!

20

Hi, after few hours of searching the net I stil cant get my cloned disk to work… need help, this should be some easy fix for that problem I have, probably the grub or some boot config file need to be corrected…

I cloned working latest Manjaro KDE SSD (btrfs) to new larger SSD, using latest Clonezilla.

I have removed the old disk and retsarted PC and forced to boot from the new SSD (my system have Windows boot on another disk,. and there is one more non-booting disk, both NVMe)

Error Iam getting is very strange: “could not find the chunk descriptor, entering rescue mode…”

Partitions on the new SSD are: sda1 fat32, sda2 btrfs and two unallocated spaces. Before the cloning I had also the old boot disk in my pc, it was sdb, with same partitions as sda now. Now no sdb and the copied configuration to sda must be wrong I guess…