![]() You could try Rufus, I've heard good things about it, but never used it myself. 'dd if= of=/dev/') but I'm on Linux (and Win doesn't have it) so unless you are running Linux (or OSX) somewhere handy, that won't help you. I just use the commandline tool 'dd' (e.g. But our installer is more modified (to support running live) that the one Proxmox uses?Īs for UNetbootin I haven't used it for years but I know that many people have issues using it to install more recent versions of Debian, e.g. I installed that to my new server (which also has UEFI) and it all just worked OOTB. I use the ProxmoxVE Hypervisor and install Turnkey as containers (you can download them directly through the web interface). Like I said I don't install TurnKey on bare metal. But perhaps it was in "legacy BIOS mode" off the shelf already? Also it was a while ago so things have probably changed. I don't recall doing anything special (just next, next, next) when I installed it. My laptop has UEFI and it installed (and runs) Debian Wheezy fine. Now I've already read umpteen tutorials and forum threads how to "manually" create an EFI GRUB2 BOOT USB drive but none of them has lead to success 'til now. What says to me that either the iso itself isn't EFI bootable in fact or RUFUS isn't able to handle the iso correctly, respectively to produce the right partions (EFI system partion with boot圆4.efi, etc., and a further partition for the rest). Please select an EFI bootable ISO or set Target Type to BIOS When using UEFI Target Type, only EFI bootable ISO images are supported. As UNETBOOTIN doesn't support UEFI I tried RUFUS (Win prog, shame on me -)), but RUFUS aborts installation after selecting GPT for UEFI and the with error message ![]() So I decided to use a USB stick for installation. ![]() This is so the installer can be aware of and update the existing EFI partitions. The install medium must be booted as UEFI when installing an UEFI O/S. The Debian partitioner doesn't neither support RAID nor does it offer the option to use a partition as EFI boot partition. It seems to be more difficult than I thought to install TKL to a UEFI RAID system -) I just wanted to test, if the missing driver is the reason for the connection error in fact. I know, something installed in live cd demo mode disappears on restart. Meanwhile I found the Realtec firmware package on Īccording to the installation instruction I untarred the GZ file to a usb stick and tried to load the firmware with the "debian-installer" bash command but I got the error: "command not found" :-/ No connection - no automatic driver download. Seems to me that the lan connection cannot be established due to the missing driver for the onboard realtec ethernet adapter. etc/udhcpc/default.script: Lease failed: The installation ended up with an error message of the Configuration Console "Network is not yet configured". Would you recommend to install the appliance to a single hard drive first and configure RAID in a second step? I've read in older threads that it should be possible, but is there meanwhile a more simple solution integrated in the appliance, that I don't know?ĭuring testing on the new hardware I started the Live CD demo mode. Unlike Debian standard the TKL partitioner of the installation routine doesn't offer the option to use a partion as physical volume for RAID (at least I didn't find it), so there is no chance to configure raid during installation. each one EFI system partion, one ext4 partion and a SWAP-Partiion). ![]() The drives are already partitioned with GPARTED (on each drive identical partitions, i.e. Now I tried to install the LAMP-stack to new server hardware with UEFI and two identic hard drives for software- RAID1. I installed the LAMP-stack (14.0) to a standard-pc for testing it. I started to work with it a few weeks ago. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |