This weekend I will install a couple of new computers as a replacement for old desktops. The old ones run Wheezy, the new one should run Wheezy as well.

What I usually would do is partition the new disks, rsync over the complete disk contents, chroot into the root directory and install grub. That works, but then I am still using the BIOS.

But I would like to switch to UEFI as this is apparently where we are heading into.

So, what should be the correct approach?

1. Move the complete Wheezy installation in the old way, make it bootable from BIOS and then convert to UEFI? Is that possible at all? When I google I only see explanations of how to use UEFI on a new install. And then most articles are 1-2 years old, and show limitiations which should have been solved now. Any pointers?
2. Make a new Wheezy install on UEFI, install the packages with dselect, copy the /etc and /home directories?
3. Use a live USB, partition GPT, rsync over the complete installation as in scenario #1, but how to I make the disk bootable? Certainly not with installing Grub in the MBR! Any pointers?

jlinkels

why your machines turn off the the nonsence your the admin make it work. if you want to create a new installer ok go do it. Do it the micro soft way. create your UEFI kernel create your UEFI partiton and do it. copy paste have fun.
Little hint look at what they are using now. http://www.youtube.com/watch?v=DLlOd-a2wG0

https://wiki.debian.org/GrubEFIReinstall

Is this English?
What has Microsift to do with UEFI except they use the secure boot feature?
Create a UEFI kernel? That is quite new that I should create a kernel. And then copy paste it? Hmmm
This is a useful link. Thanks.

And for the rest I think this is a pretty incoherent answer, not worthy for a long time member like you.

jlinkels

EFI, without the U, has been around for a long time now on servers. The U part was forced in by MS so that they would not have to correct their crappy boot sector to not be a massive security hole.

Although I agree with you that Microsoft and security or software quality are two widely distinct concepts, according to this article: https://www.happyassassin.net/2014/0...lly-work-then/ UEFI optionally can enable secure boot. It doesn't say M$ caused the "U" to be added. It says M$ uses it and requires it if hardware vendors want to get a M$ approval. Or is the article wrong on that point?

Thinking along that lines, UEFI calls for a FAT partiton. And you know who specified FAT?

jlinkels

Can't you just move the existing partitions to gfi partition & chroot for efi & grub.
http://tanguy.ortolo.eu/blog/article51/debian-efi

Sounds viable. It was what I wrote as option #3, but you answered the question as how to convert those partitions to EFI.

However, while I was browsing LQ I was waiting for the new machine to complete installation. Eventually I choose for option #2. Created a Debian Jesse netinstaller and installed EFI natively from within the Debian installer. That was easy, straightforward and succesful. Just regular guided install.

I tried it with Wheezy first and that failed. Which was probably my own mistake because I did not disable UEFI secure boot. And I did not understand the error message. Now I am still not sure if Wheezy can do it.

In fact the hardest part was to disable the secure boot. I have Asus H81T mainboards and for the life of it I couldn't find how to disable secure boot or enable addition UEFI boot devices. Well, it turned out that you have to enter Advanced Setup -> Boot -> Security, but to find that you have to scroll down on the Advanced Setup -> Boot screen. I am just not used yet to GUI firmware screens!

jlinkels