Author Topic: Unable to boot after using Systemback(SOLVED)  (Read 1392 times)

Offline alynur

  • Trusted User
  • Veteran
  • *****
  • Posts: 1232
  • Karma: 133
  • Habitual Forum Browser
    • View Profile
  • Peppermint version(s): P 9R (64bit), P 10
Unable to boot after using Systemback(SOLVED)
« on: November 15, 2019, 07:11:02 am »
Hello Peppermint people, I used systemback to make a live image of my P 9 installation on my laptop. The live image was too big to make an iso file but I was able to write it to a usb memory. My intentions are to replace an upgraded P 10 system on my desktop that isn't working very good with no known solutions, I'm talking about nemo lag and freezing. The usb memory boots up fine into the live image, which is a duplicate of my laptop system, pretty cool, but there's no way of installing from it so I had to reboot the usb and select boot into live image installer. That works good, chose the partition P 10 was installed on, deleted it, reselected the partition to make new and it all went very nicely. I booted up into the Ubuntu that is controlling boot and ran sudo update-grub, alls well. rebooted into the new installation and it doesn't boot. I get this,



blkid shows this,

Code: [Select]
albert@albert-desktop ~ $ blkid
/dev/sda1: UUID="776dba26-93d1-4d68-9cca-e7773642ee82" TYPE="ext4" PARTUUID="a67c2459-9394-427d-9c72-93872332500d"
/dev/sda2: UUID="3572D87968E542C1" TYPE="ntfs" PTTYPE="dos" PARTUUID="b620e0c9-e426-42c4-9e29-952d328d9c9a"
/dev/sdb1: UUID="AE4E-959E" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="a214246a-8542-4466-9c4a-1df2c816f958"
/dev/sdb2: LABEL="SB@" UUID="f4a64468-2bd4-450b-b573-3a1dd9ded925" TYPE="ext4" PARTUUID="693e6e4e-7542-42cf-8f12-016a74d95cc7"
/dev/sdb3: UUID="edd0242f-a8d8-4387-940d-226af5ff8f1c" TYPE="ext4" PARTLABEL="Ubuntu MATE" PARTUUID="009c32e5-2b58-433f-be02-07bc4c7a99d1"
/dev/sdb4: UUID="ec363331-1864-4320-8998-df762df7e905" TYPE="ext4" PARTUUID="082c684e-bea9-472b-a123-ce1380b4d599"
/dev/sdb5: UUID="b982ea7f-26e9-4dfb-b97a-ab9a8c86f66f" TYPE="swap" PARTUUID="7a49a2b9-0572-48f2-90e6-e0665bd90026"
/dev/sdb6: UUID="4c7dfcba-b030-4b6b-87f4-7b1e7466b05b" TYPE="ext4" PARTLABEL="Mint" PARTUUID="831b96ce-95b1-4c0c-a536-67ff1fbabeaf"
/dev/sdb7: UUID="530dfd1e-5d45-460e-9c95-b4b1f292a241" TYPE="ext4" PARTLABEL="kubuntu" PARTUUID="2bffbc02-e806-4d40-a0de-412cbd124a26"
/dev/sdb8: UUID="e7723a02-d9bc-463c-a012-07ddff2cb9a3" TYPE="ext4" PARTLABEL="feren" PARTUUID="70cc89e5-6a94-48b1-8bc4-0b3ae56e6bc5"
/dev/sdb9: UUID="d3cf32d0-fbfc-4ea4-94b3-fd73148c5090" TYPE="ext4" PARTLABEL="peppermint 10" PARTUUID="bbd40eb2-85cb-4e4a-877e-3a15f0f5122e"
/dev/sdb10: UUID="640eb672-bdbc-4d71-b7d6-5956dd0bb367" TYPE="ext4" PARTLABEL="Xubuntu" PARTUUID="97dcbb4b-ab07-42d7-9f41-9af74060a6f3"

The fstab of the installation shows this

Code: [Select]
# /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>
# / was on /dev/sda9 during installation
UUID=f4a64468-2bd4-450b-b573-3a1dd9ded925   /   ext4   noatime,errors=remount-ro   0   1

I think the UUID that is being shown as not existing was from the first attempt to install without deleting the partition and just selecting it to install into?

The UUID of the prior P 10 installation was

Code: [Select]
/dev/sdb2: UUID="b4054ac1-50c6-4114-8cd2-cc8384f1d361" TYPE="ext4" PARTLABEL="peppermint" PARTUUID="57ec59fa-6ea7-4c2f-bd07-a8494e062af7"
Any ideas on how to fix this?   :-\
« Last Edit: November 23, 2019, 08:23:25 pm by alynur »
What was I thinking?

Offline murraymint

  • Trusted User
  • Veteran
  • *****
  • Posts: 2165
  • Karma: 415
  • soft boiled with a yolk of gold
    • View Profile
  • Peppermint version(s): 7, 8, 9
Re: Unable to boot after using Systemback
« Reply #1 on: November 15, 2019, 07:37:54 am »
It's looking for a swap partition that's no longer there, I think. Comment out the swap partition in the /etc/fstab and it might boot OK.

Actually maybe if you could chroot into it and update the grub it would pick up the right partition UUID.
« Last Edit: November 15, 2019, 07:39:45 am by murraymint »

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26452
  • Karma: 65531
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Unable to boot after using Systemback
« Reply #2 on: November 15, 2019, 02:32:04 pm »
If you want Peppermint to control GRUB, boot the LiveUSB and run these commands in sequence:
Code: [Select]
sudo mount /dev/sdb9 /mntthen
Code: [Select]
gksudo xed /mnt/etc/fstabwhen fstab opens make it read
Code: [Select]
# /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=d3cf32d0-fbfc-4ea4-94b3-fd73148c5090   /   ext4   noatime,errors=remount-ro   0   1
SAVE the file and exit the text editor.

Back in the terminal run:
Code: [Select]
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; donethen
Code: [Select]
sudo chroot /mntthen
Code: [Select]
grub-install /dev/sdbthen
Code: [Select]
update-grubthen hit Ctrl+D (to exit the chroot environment)

and finally reboot without the LiveUSB (after setting sdb as the primary boot device in the BIOS).
« Last Edit: November 15, 2019, 05:05:33 pm by PCNetSpec »
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline alynur

  • Trusted User
  • Veteran
  • *****
  • Posts: 1232
  • Karma: 133
  • Habitual Forum Browser
    • View Profile
  • Peppermint version(s): P 9R (64bit), P 10
Re: Unable to boot after using Systemback
« Reply #3 on: November 15, 2019, 04:15:20 pm »
Okay, I should have been a little more clear, I was trying to boot the new install of my Peppermint system into sdb2. The fstab was as listed, appears to be correct, but when I tried to boot sdb2 I got the message in the photo. Perhaps attempting to reinstall grub would have fixed it but I was perplexed by the alert about the UUID  not existing. What is the missing module that's being indicated?
What was I thinking?

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26452
  • Karma: 65531
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Unable to boot after using Systemback
« Reply #4 on: November 15, 2019, 05:01:51 pm »
Okay if Peppermint is on /dev/sdb2 (and you want it to control GRUB)

Boot the LiveUSB and run these commands in sequence:
Code: [Select]
sudo mount /dev/sdb2 /mntthen
Code: [Select]
gksudo xed /mnt/etc/fstabwhen fstab opens make it read
Code: [Select]
# /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>
# / was on /dev/sdb2 during installation
UUID=f4a64468-2bd4-450b-b573-3a1dd9ded925   /   ext4   noatime,errors=remount-ro   0   1
SAVE the file and exit the text editor.

Back in the terminal run:
Code: [Select]
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; donethen
Code: [Select]
sudo chroot /mntthen
Code: [Select]
grub-install /dev/sdbthen
Code: [Select]
update-grubthen hit Ctrl+D (to exit the chroot environment)

and finally reboot without the LiveUSB (after setting sdb as the primary boot device in the BIOS).



The problem is the grub.cfg of whichever distro is currently still controlling GRUB is expecting sdb2 to have a UUID of b4054ac1-50c6-4114-8cd2-cc8384f1d361"

But I don't know which distro if currently controlling GRUB .. so now the UUID of sdb2 has changed it's easier to just make the new Peppermint control GRUB than to fix whatever is currently controlling it.
« Last Edit: November 15, 2019, 05:11:28 pm by PCNetSpec »
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline alynur

  • Trusted User
  • Veteran
  • *****
  • Posts: 1232
  • Karma: 133
  • Habitual Forum Browser
    • View Profile
  • Peppermint version(s): P 9R (64bit), P 10
Re: Unable to boot after using Systemback
« Reply #5 on: November 16, 2019, 07:50:07 am »
Thanks PCNetSpec, I would have tried to fix this using your commands, but prior to your posting I got impatient and reinstalled P 9 from P 9's iso and went with apt-clone to get the majority of my packages installed. So at this point I'm not sure if the systemback method without an iso file works. That would be pretty cool if it did because it is a clone of the original system. Maybe I'll get ambitious and try it again so I can say it works and solved for others to know your recovery method works. Yeah, why not!  ;D
What was I thinking?

Offline alynur

  • Trusted User
  • Veteran
  • *****
  • Posts: 1232
  • Karma: 133
  • Habitual Forum Browser
    • View Profile
  • Peppermint version(s): P 9R (64bit), P 10
Re: Unable to boot after using Systemback
« Reply #6 on: November 16, 2019, 10:43:03 am »
Okay, I reinstalled the Systemback live image into sdb2, I left the boot manager control on sdb9, P 10, changed the fstab of sdb2 to reflect the correct uuid and also the automount of my DATA partition. I booted up into P 10 and ran sudo update-grub and attempted to boot into sdb2 which failed. So I tried to install bootmanager of sdb2 into sdb and this is what I got.

Code: [Select]
peppermint@peppermint ~ $ sudo mount /dev/sdb2 /mnt
peppermint@peppermint ~ $ for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
peppermint@peppermint ~ $ sudo chroot /mnt
root@peppermint / # grub-install /dev/sdb
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
   

Could it be I was supposed to install grub in sdb1? Looks like I have a missing EFI directory somewhere.
What was I thinking?

Offline alynur

  • Trusted User
  • Veteran
  • *****
  • Posts: 1232
  • Karma: 133
  • Habitual Forum Browser
    • View Profile
  • Peppermint version(s): P 9R (64bit), P 10
Re: Unable to boot after using Systemback
« Reply #7 on: November 16, 2019, 11:20:05 am »
Usually when I want to change the distro that is controlling bootloader I run these commands and it works,


Code: [Select]
sudo mount /dev/sdXXX /mnt
sudo mount /dev/sdXX /mnt/boot/efi
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
sudo chroot /mnt
grub-install /dev/sdX
update-grub 
Note : sdX = disk | sdXX = efi partition | sdXXX = system partition

and that's how I got the missing EFI directory. Could I copy the directory from another distro installed on my harddrive, like P 10 and copy it into sdb2?
What was I thinking?

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26452
  • Karma: 65531
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Unable to boot after using Systemback
« Reply #8 on: November 16, 2019, 11:29:04 am »
Sorry, I missed the EFI partition :-[

Boot the LiveUSB and run these commands in sequence:
Code: [Select]
sudo mount /dev/sdb2 /mntthen
Code: [Select]
sudo mount /dev/sdb1 /mnt/boot/efithen
Code: [Select]
gksudo xed /mnt/etc/fstabwhen fstab opens make it read
Code: [Select]
# /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>
# / was on /dev/sdb2 during installation
UUID=f4a64468-2bd4-450b-b573-3a1dd9ded925   /   ext4   noatime,errors=remount-ro   0   1
SAVE the file and exit the text editor.

Back in the terminal run:
Code: [Select]
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; donethen
Code: [Select]
sudo chroot /mntthen
Code: [Select]
grub-install /dev/sdbthen
Code: [Select]
update-grubthen hit Ctrl+D (to exit the chroot environment)

and finally reboot without the LiveUSB (after setting sdb as the primary boot device in the BIOS).
« Last Edit: November 16, 2019, 11:31:02 am by PCNetSpec »
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline alynur

  • Trusted User
  • Veteran
  • *****
  • Posts: 1232
  • Karma: 133
  • Habitual Forum Browser
    • View Profile
  • Peppermint version(s): P 9R (64bit), P 10
Re: Unable to boot after using Systemback
« Reply #9 on: November 16, 2019, 11:57:43 am »
Sorry, I missed the EFI partition :-[

Boot the LiveUSB and run these commands in sequence:
Code: [Select]
sudo mount /dev/sdb2 /mntthen
Code: [Select]
sudo mount /dev/sdb1 /mnt/boot/efithen
Code: [Select]
gksudo xed /mnt/etc/fstabwhen fstab opens make it read
Code: [Select]
# /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>
# / was on /dev/sdb2 during installation
UUID=f4a64468-2bd4-450b-b573-3a1dd9ded925   /   ext4   noatime,errors=remount-ro   0   1
SAVE the file and exit the text editor.

Back in the terminal run:
Code: [Select]
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; donethen
Code: [Select]
sudo chroot /mntthen
Code: [Select]
grub-install /dev/sdbthen
Code: [Select]
update-grubthen hit Ctrl+D (to exit the chroot environment)

and finally reboot without the LiveUSB (after setting sdb as the primary boot device in the BIOS).

I caught that after trying with your original instructions. I ran it the correct way and I still get the EFI directory missing, appears to be no efi directory in sdb2. Can I copy one over?
What was I thinking?

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26452
  • Karma: 65531
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Unable to boot after using Systemback
« Reply #10 on: November 16, 2019, 12:20:05 pm »
There won't be an efif directory in sdb2 .. that's mounted as /

the efi directory is sdb1

have you actually tried running the above commands now ?



Let's see if the efi partition has any bootloaders in it

Boot the LiveUSB and run these commands in sequence:
Code: [Select]
sudo mount /dev/sdb2 /mntthen
Code: [Select]
sudo mount /dev/sdb1 /mnt/boot/efinow what's the output from
Code: [Select]
sudo ls /mnt/boot/efi/EFI
« Last Edit: November 16, 2019, 12:27:34 pm by PCNetSpec »
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline alynur

  • Trusted User
  • Veteran
  • *****
  • Posts: 1232
  • Karma: 133
  • Habitual Forum Browser
    • View Profile
  • Peppermint version(s): P 9R (64bit), P 10
Re: Unable to boot after using Systemback
« Reply #11 on: November 16, 2019, 12:28:29 pm »
yup

Code: [Select]
albert@albert-desktop ~ $ sudo mount /dev/sdb2 /mnt
[sudo] password for albert:
albert@albert-desktop ~ $ sudo mount /dev/sdb1 /mnt/boot/efi
mount: /mnt/boot/efi: mount point does not exist.
albert@albert-desktop ~ $ for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
albert@albert-desktop ~ $ sudo chroot /mnt
root@albert-desktop / # grub-install /dev/sdb
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
root@albert-desktop / # update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/50_peppermint.cfg'
Generating grub configuration file ...
Found background image: grub-background.png
Found linux image: /boot/vmlinuz-5.3.0-23-generic
Found initrd image: /boot/initrd.img-5.3.0-23-generic
Found linux image: /boot/vmlinuz-5.3.0-22-generic
Found initrd image: /boot/initrd.img-5.3.0-22-generic
Found linux image: /boot/vmlinuz-5.0.0-23-generic
Found initrd image: /boot/initrd.img-5.0.0-23-generic
Found linux image: /boot/vmlinuz-4.15.0-70-generic
Found initrd image: /boot/initrd.img-4.15.0-70-generic
Found Ubuntu 18.04.3 LTS (18.04) on /dev/sdb10
Found Ubuntu 19.04 (19.04) on /dev/sdb3
Found Linux Mint 19.2 Tina (19.2) on /dev/sdb6
Found Ubuntu 18.04.3 LTS (18.04) on /dev/sdb7
Found Feren OS (18.04) on /dev/sdb8
Found Peppermint 10 Ten (10) on /dev/sdb9
Adding boot menu entry for EFI firmware configuration
done
What was I thinking?

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26452
  • Karma: 65531
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Unable to boot after using Systemback
« Reply #12 on: November 16, 2019, 12:32:45 pm »
Let's see if the efi partition has any bootloaders in it

Boot the LiveUSB and run these commands in sequence:
Code: [Select]
sudo mount /dev/sdb2 /mntthen
Code: [Select]
sudo mount /dev/sdb1 /mnt/boot/efinow what's the output from
Code: [Select]
sudo ls /mnt/boot/efi/EFI
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26452
  • Karma: 65531
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Unable to boot after using Systemback
« Reply #13 on: November 16, 2019, 12:48:58 pm »
What happens if you try this:-

Boot the LiveUSB and run these commands in sequence:
Code: [Select]
sudo mount /dev/sdb2 /mntthen
Code: [Select]
sudo mount /dev/sdb1 /mnt/boot/efithen
Code: [Select]
gksudo xed /mnt/etc/fstabwhen fstab opens make it read
Code: [Select]
# /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>
# / was on /dev/sdb2 during installation
UUID=f4a64468-2bd4-450b-b573-3a1dd9ded925   /   ext4   noatime,errors=remount-ro   0   1
SAVE the file and exit the text editor.

Back in the terminal run:
Code: [Select]
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; donethen
Code: [Select]
sudo chroot /mntthen
Code: [Select]
grub-install --efi-directory=/mnt/boot/efithen
Code: [Select]
update-grubthen hit Ctrl+D (to exit the chroot environment)

and finally reboot without the LiveUSB (after setting sdb as the primary boot device in the BIOS).
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline alynur

  • Trusted User
  • Veteran
  • *****
  • Posts: 1232
  • Karma: 133
  • Habitual Forum Browser
    • View Profile
  • Peppermint version(s): P 9R (64bit), P 10
Re: Unable to boot after using Systemback
« Reply #14 on: November 16, 2019, 02:21:01 pm »
Let's see if the efi partition has any bootloaders in it

Boot the LiveUSB and run these commands in sequence:
Code: [Select]
sudo mount /dev/sdb2 /mntthen
Code: [Select]
sudo mount /dev/sdb1 /mnt/boot/efinow what's the output from
Code: [Select]
sudo ls /mnt/boot/efi/EFI


This happens 

Code: [Select]
peppermint@peppermint ~ $ sudo mount /dev/sdb2 /mnt
peppermint@peppermint ~ $ sudo mount /dev/sdb1 /mnt/boot/efi
mount: /mnt/boot/efi: mount point does not exist.
peppermint@peppermint ~ $ sudo ls /mnt/boot/efi/EFI
ls: cannot access '/mnt/boot/efi/EFI': No such file or directory
peppermint@peppermint ~ $
What was I thinking?