You are not logged in.

#1 2018-03-30 13:53:58

alexander_schoch
Member
From: Lucerne, Switzerland
Registered: 2018-03-30
Posts: 5

Copied Arch not shown in EFI

Hi all,

I tried to copy the entire arch install onto another hard drive (form HDD [/dev/sda] to SSD [/dev/sdb], both internal).

This is how I tried to do it:

    - booted live arch stick
    - mounted both root partitions
    - cp -a /mnt/HDD/* /mnt/SSD
    - same for boot and efi partition
    - chrooted into SSD
    - reinstalled grub
    - run grub-install
    - updated /etc/fstab

Everything seemed to work, but the SSD system is not displayed in my computer's EFI. What do I do wrong?

Thanks in advance!

Last edited by alexander_schoch (2018-03-30 13:54:28)

Offline

#2 2018-03-30 14:00:30

dockland
Member
From: Sweden
Registered: 2015-06-06
Posts: 861

Re: Copied Arch not shown in EFI

Post your fstab along with your blkid output


I possess a device, in my pocket, that is capable of accessing the entirety of information known to man.
I use it to look at funny pictures of cats and to argue with strangers.

Offline

#3 2018-03-30 14:11:01

alexander_schoch
Member
From: Lucerne, Switzerland
Registered: 2018-03-30
Posts: 5

Re: Copied Arch not shown in EFI

dockland wrote:

Post your fstab along with your blkid output

/etc/fstab

# /dev/sdb4
UUID=2cf020f8-fdb2-41fe-a200-bb29d74074aa    /             ext4          rw,relatime,data=ordered    0 1

# /dev/sdb2
UUID=40bdb382-77e4-4fd8-8d5c-5fefcfaa3dc8    /boot         ext4          rw,relatime,data=ordered    0 2

# /dev/sdb3
UUID=D407-D048          /boot/efi     vfat          rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro    0 2


blkid:

What option should I post?

Offline

#4 2018-03-30 14:25:47

dockland
Member
From: Sweden
Registered: 2015-06-06
Posts: 861

Re: Copied Arch not shown in EFI

Actually the whole output

Just so we can see it the UUID's match with the ones in your fstab.

(you have to blkid as root)


I possess a device, in my pocket, that is capable of accessing the entirety of information known to man.
I use it to look at funny pictures of cats and to argue with strangers.

Offline

#5 2018-03-30 14:30:22

alexander_schoch
Member
From: Lucerne, Switzerland
Registered: 2018-03-30
Posts: 5

Re: Copied Arch not shown in EFI

dockland wrote:

Actually the whole output

Just so we can see it the UUID's match with the ones in your fstab.

(you have to blkid as root)

Okay, sorry for that stupid question. Here's the output:

/dev/sda4: UUID="0309a070-4474-4891-b78b-bab22c20a84f" TYPE="ext4" PARTUUID="7f9645a0-7a7c-224f-b09c-5abe4f2d7081"
/dev/sda5: UUID="cdd82cd9-10b8-4278-ba51-8601b360deda" TYPE="ext4" PARTUUID="2a107278-21fb-bd45-80c8-adca680d9b08"
/dev/sda6: UUID="2fb64590-134a-46bf-8f4e-f9d6b34b2b00" TYPE="swap" PARTUUID="fa86c990-ebe3-fe45-995b-778a56a627ba"
/dev/sda7: UUID="8859-B3AB" TYPE="vfat" PARTUUID="9d0251a2-e56a-aa42-8619-58f6e0660f71"
/dev/sdb1: UUID="7ed7a431-439d-4ebd-94dd-26d522351d69" TYPE="swap" PARTUUID="6473718e-8366-4144-90ca-4e49589e3763"
/dev/sdb2: UUID="40bdb382-77e4-4fd8-8d5c-5fefcfaa3dc8" TYPE="ext4" PARTUUID="c1ce99ff-be1e-8c42-8cf5-257ecdb18e83"
/dev/sdb3: SEC_TYPE="msdos" UUID="062C-542E" TYPE="vfat" PARTUUID="deb23b07-6d77-2a47-ba5f-06e03ccc1f0a"
/dev/sdb4: UUID="2cf020f8-fdb2-41fe-a200-bb29d74074aa" TYPE="ext4" PARTUUID="34bb8085-0a79-6c43-b12e-5ad55ba8840e"



And i just got grub-install to run correctly. I now have two entries in my EFI, but both start the same arch install, which is the one on HDD (/dev/sda4)

Offline

#6 2018-03-30 14:34:49

dockland
Member
From: Sweden
Registered: 2015-06-06
Posts: 861

Re: Copied Arch not shown in EFI

The two lines...


/dev/sdb3: SEC_TYPE="msdos" UUID="062C-542E" TYPE="vfat" PARTUUID="deb23b07-6d77-2a47-ba5f-06e03ccc1f0a"

and 

# /dev/sdb3
UUID=D407-D048          /boot/efi     vfat          rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro    0 2

...does not match.


I possess a device, in my pocket, that is capable of accessing the entirety of information known to man.
I use it to look at funny pictures of cats and to argue with strangers.

Offline

#7 2018-03-30 14:45:55

alexander_schoch
Member
From: Lucerne, Switzerland
Registered: 2018-03-30
Posts: 5

Re: Copied Arch not shown in EFI

dockland wrote:

The two lines...


/dev/sdb3: SEC_TYPE="msdos" UUID="062C-542E" TYPE="vfat" PARTUUID="deb23b07-6d77-2a47-ba5f-06e03ccc1f0a"

and 

# /dev/sdb3
UUID=D407-D048          /boot/efi     vfat          rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro    0 2

...does not match.


I changed the line in /etc/fstab, but the problem still occurs...

Offline

#8 2018-03-30 14:55:43

dockland
Member
From: Sweden
Registered: 2015-06-06
Posts: 861

Re: Copied Arch not shown in EFI

Post fstab after your change please,


I possess a device, in my pocket, that is capable of accessing the entirety of information known to man.
I use it to look at funny pictures of cats and to argue with strangers.

Offline

#9 2018-03-30 15:07:39

ua4000
Member
Registered: 2015-10-14
Posts: 418

Re: Copied Arch not shown in EFI

UEFI Bios uses only *one* EFI Partition - which one do you indend to use ?
What exactly did you run at grub-install ?
Also post sudo efibootmgr --verbose

Also please state: Do you plan an entire system move from HDD --> SSD, remove HDD afterwards, or do you plan to use them both in parallel ?

Offline

#10 2018-03-30 15:45:13

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,544

Re: Copied Arch not shown in EFI

There's no such thing as a "UEFI Bios" and the number of ESPs doesn't matter.

You need to take a look at the UEFI NVRAM entries (efibootmgr --verbose, like ua4000 said), see where each entry is loading grub from. You'll also want to take a look at each grub.cfg and see what all it's doing.

Offline

#11 2018-03-31 11:45:59

alexander_schoch
Member
From: Lucerne, Switzerland
Registered: 2018-03-30
Posts: 5

Re: Copied Arch not shown in EFI

Okay, following update.

I had the honor to solve the problem with one person in SE chat. The problem could be fixed with
`grub-install --target=x86_64-efi --efi-directory=/dev/sdb3 --bootloader-id=arch_grub`
after updating the fstab.

And fyi: I planned to move the system to the SSD and remove the old one in order to load a kubuntu on it. All that perfectly worked.

So, thank you all for your help!

Best,
Alexander Schoch

Offline

Board footer

Powered by FluxBB