No bootable device error after restoring debian image to annother ssd disk
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
I created an image of debian 7 on an SSD disk and later restored it on another computer with excatly same type of HW. however I'm getting the error message:
No bootable device -- insert boot disk and press key
The image was created using a live OS with the command:
dd if=/dev/sda conv=sync,noerror bs=64K | gzip -c > backup.img.gz
And later restored to disk with:
gunzip -c backup.img.gz | dd of=/dev/sda
I've done this before on older computers and it usually works fine. If i restore the image on the computer i created from it seems to be working.
These computers has EFI, could this be the issue? Any ideas, or workarounds?
Thanks
linux debian uefi dd disk-image
asked Jun 14 at 5:01
user1754598
111
add a comment |Â
up vote
2
down vote
favorite
I created an image of debian 7 on an SSD disk and later restored it on another computer with excatly same type of HW. however I'm getting the error message:
No bootable device -- insert boot disk and press key
The image was created using a live OS with the command:
dd if=/dev/sda conv=sync,noerror bs=64K | gzip -c > backup.img.gz
And later restored to disk with:
gunzip -c backup.img.gz | dd of=/dev/sda
I've done this before on older computers and it usually works fine. If i restore the image on the computer i created from it seems to be working.
These computers has EFI, could this be the issue? Any ideas, or workarounds?
Thanks
linux debian uefi dd disk-image
asked Jun 14 at 5:01
user1754598
111
1
Yes, efi is the issue.
– Ipor Sircer
Jun 14 at 7:40
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I created an image of debian 7 on an SSD disk and later restored it on another computer with excatly same type of HW. however I'm getting the error message:
No bootable device -- insert boot disk and press key
The image was created using a live OS with the command:
dd if=/dev/sda conv=sync,noerror bs=64K | gzip -c > backup.img.gz
And later restored to disk with:
gunzip -c backup.img.gz | dd of=/dev/sda
I've done this before on older computers and it usually works fine. If i restore the image on the computer i created from it seems to be working.
These computers has EFI, could this be the issue? Any ideas, or workarounds?
Thanks
linux debian uefi dd disk-image
asked Jun 14 at 5:01
user1754598
111
I created an image of debian 7 on an SSD disk and later restored it on another computer with excatly same type of HW. however I'm getting the error message:
No bootable device -- insert boot disk and press key
The image was created using a live OS with the command:
dd if=/dev/sda conv=sync,noerror bs=64K | gzip -c > backup.img.gz
And later restored to disk with:
gunzip -c backup.img.gz | dd of=/dev/sda
I've done this before on older computers and it usually works fine. If i restore the image on the computer i created from it seems to be working.
These computers has EFI, could this be the issue? Any ideas, or workarounds?
Thanks
linux debian uefi dd disk-image
asked Jun 14 at 5:01
user1754598
111
asked Jun 14 at 5:01
user1754598
111
asked Jun 14 at 5:01
user1754598
111
asked Jun 14 at 5:01
user1754598
111
111
1
Yes, efi is the issue.
– Ipor Sircer
Jun 14 at 7:40
add a comment |Â
1
Yes, efi is the issue.
– Ipor Sircer
Jun 14 at 7:40
1
1
Yes, efi is the issue.
– Ipor Sircer
Jun 14 at 7:40
Yes, efi is the issue.
– Ipor Sircer
Jun 14 at 7:40
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
1
down vote
On EFI systems the location of the bootloader is stored in motherboard non-volatile storage.
If you have a UEFI shell available you can use that to run the bootloader (typically locate in the EFI directory in root of the boot partition, alternatively either rename the bootloader to default name (bootx64.efi for x86-64) or boot from removeable media. Then you can reconfigure the grub-efi package which will reset the firmware configuration.
answered Jun 14 at 9:23
Timothy Baldwin
1662
add a comment |Â
up vote
0
down vote
You basically need to run grub-install in a chroot with your Debian system mounted there (including /boot/efi, /dev, /proc and /sys); the rescue image can be any live one booted in EFI mode (plug: ALT Rescue should do).
Rod's books on the topic are highly recommended to understand what's going on.
answered Jun 14 at 11:22
Michael Shigorin
69259
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
On EFI systems the location of the bootloader is stored in motherboard non-volatile storage.
If you have a UEFI shell available you can use that to run the bootloader (typically locate in the EFI directory in root of the boot partition, alternatively either rename the bootloader to default name (bootx64.efi for x86-64) or boot from removeable media. Then you can reconfigure the grub-efi package which will reset the firmware configuration.
answered Jun 14 at 9:23
Timothy Baldwin
1662
add a comment |Â
up vote
1
down vote
On EFI systems the location of the bootloader is stored in motherboard non-volatile storage.
If you have a UEFI shell available you can use that to run the bootloader (typically locate in the EFI directory in root of the boot partition, alternatively either rename the bootloader to default name (bootx64.efi for x86-64) or boot from removeable media. Then you can reconfigure the grub-efi package which will reset the firmware configuration.
answered Jun 14 at 9:23
Timothy Baldwin
1662
add a comment |Â
up vote
1
down vote
up vote
1
down vote
On EFI systems the location of the bootloader is stored in motherboard non-volatile storage.
If you have a UEFI shell available you can use that to run the bootloader (typically locate in the EFI directory in root of the boot partition, alternatively either rename the bootloader to default name (bootx64.efi for x86-64) or boot from removeable media. Then you can reconfigure the grub-efi package which will reset the firmware configuration.
answered Jun 14 at 9:23
Timothy Baldwin
1662
On EFI systems the location of the bootloader is stored in motherboard non-volatile storage.
If you have a UEFI shell available you can use that to run the bootloader (typically locate in the EFI directory in root of the boot partition, alternatively either rename the bootloader to default name (bootx64.efi for x86-64) or boot from removeable media. Then you can reconfigure the grub-efi package which will reset the firmware configuration.
answered Jun 14 at 9:23
Timothy Baldwin
1662
answered Jun 14 at 9:23
Timothy Baldwin
1662
answered Jun 14 at 9:23
Timothy Baldwin
1662
answered Jun 14 at 9:23
Timothy Baldwin
1662
1662
add a comment |Â
add a comment |Â
up vote
0
down vote
You basically need to run grub-install in a chroot with your Debian system mounted there (including /boot/efi, /dev, /proc and /sys); the rescue image can be any live one booted in EFI mode (plug: ALT Rescue should do).
Rod's books on the topic are highly recommended to understand what's going on.
answered Jun 14 at 11:22
Michael Shigorin
69259
add a comment |Â
up vote
0
down vote
You basically need to run grub-install in a chroot with your Debian system mounted there (including /boot/efi, /dev, /proc and /sys); the rescue image can be any live one booted in EFI mode (plug: ALT Rescue should do).
Rod's books on the topic are highly recommended to understand what's going on.
answered Jun 14 at 11:22
Michael Shigorin
69259
add a comment |Â
up vote
0
down vote
up vote
0
down vote
You basically need to run grub-install in a chroot with your Debian system mounted there (including /boot/efi, /dev, /proc and /sys); the rescue image can be any live one booted in EFI mode (plug: ALT Rescue should do).
Rod's books on the topic are highly recommended to understand what's going on.
answered Jun 14 at 11:22
Michael Shigorin
69259
You basically need to run grub-install in a chroot with your Debian system mounted there (including /boot/efi, /dev, /proc and /sys); the rescue image can be any live one booted in EFI mode (plug: ALT Rescue should do).
Rod's books on the topic are highly recommended to understand what's going on.
answered Jun 14 at 11:22
Michael Shigorin
69259
answered Jun 14 at 11:22
Michael Shigorin
69259
answered Jun 14 at 11:22
Michael Shigorin
69259
answered Jun 14 at 11:22
Michael Shigorin
69259
69259
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f449723%2fno-bootable-device-error-after-restoring-debian-image-to-annother-ssd-disk%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
Yes, efi is the issue.
– Ipor Sircer
Jun 14 at 7:40