Could Not Read From Cdrom (Code 0009)

Build Status

A Bare Metal Installer for ZFS on Root

This repository is intended to produce a bootable UEFI image that allows installing a full bare system with ZFS disks. Be enlightened that it is non intended for edifice dual-boot systems. While you are given the ability to choose which disks are used, the EFI kicking organization volition wipe other Bone entries.

It uses an Ubuntu kernel and a minimal ramdisk architect to host the scripts used to perform the actual install.

Using the installer image

Quick outset:

Download the installer image:
- employ a released iso image file from github
- Alternatively, build the image (see the below section on building)
Boot the image (using one of the boot options below)
Install

Download

At that place are ii unlike installer image files created:

IMG file
ISO file

In most circumstances, the IMG image is the normal version to use as information technology is a standard EFI bootable deejay image.

These installer image files can be downloaded from the github release page - Use the most recent release for your download.

Once your image file is downloaded, the simplest manner to use information technology is to put the image onto a USB stick, with a tool similar dd or Etcher

For dd:

Offset, make up one's mind what deejay to write to:

lsblk -d -o Name,SIZE,Characterization

(carefully select the correct disk device)
Then write the image to the disk:

echo "Verify and run: sudo dd if=boot.iso of=$DISK"

Boot

This installer creates boot images that will not work with Secure Boot, and then exist sure to plough this feature off if your computer has it.

You will demand to set your reckoner to boot using EFI (as opposed to "legacy" or "BIOS" boot mode) and may need to manually interrupt the boot sequence to select booting from the USB stick (systems that have an existing operating organisation installed on the hard bulldoze will probably need this transmission step)

The installer is congenital using the EFIShell tool, which volition automatically load a "startup.nsh" script to start the install process. However, if your system has more than one disk with a "startup.nsh" script, information technology may not run the right one.

If y'all find that the EFIShell is running the wrong script, you lot should reboot and interrupt the EFIShell by pressing "ESC" when it prompts yous and then manually get-go the installer by typing "install" at the "Crush>" prompt.

This boot process can take a significant amount of time - it needs to load and uncompress >200Meg of data from the (sometimes quite dull) USB stick.

TODO - make a joke about the pen (supermicro kicking card)

Install

Once booted, the VGA screen on the computer evidence a status page provided by the htop tool. The ZFS installation can be started simply past using the F10 fundamental to exit the status page.

At the start of the installation, some basic questions volition asked (See below for a consummate list with explanations) - the default values are more often than not all fine and will result in a system installed with a gnome desktop environment.

The default root password is root and should be changed. You should as well fill up in the User login, countersign and Full Name.

The installer will then find your storage devices and suggest a ZFS layout. The suggested layout will exist shown to you lot in two phases:

A series of tick boxes assuasive you to bank check and confirm which disks will be partitioned or formatted during the installation
The command line to be used to create the ZFS filesystem will exist shown for editing - allowing advanced users to make additional changes (or just right mistakes in the automatic layout detection)

In one case the install is complete, y'all will be prompted to reboot

Notation that the installer tin also be run from the control line, and that there is an unattended mode which asks no questions - to assistance with automation.

Installation Options Reference

The installer has a number of options bachelor to tune the installed organisation.

Env Name	Config prompt	Default
CONFIG_DESKTOP	Desktop Package(s)	ubuntu-gnome-desktop
CONFIG_ROOT_PW	Root Passwd	root
CONFIG_USER	User Login
CONFIG_USER_PW	User Passwd
CONFIG_USER_FN	User Total Proper noun
CONFIG_LOCALE	Organization Locale	en_HK.UTF-8
CONFIG_TIMEZONE	Arrangement Timezone	Asia/Hong_Kong
CONFIG_PROXY	HTTP Proxy
CONFIG_POOL	ZFS Zpool Proper noun	tank
CONFIG_HOSTNAME	Installed arrangement's hostname	Based on a generated name

Diagnosing bug

Error log

The interactive installation keeps a log of the installation process in "/zfs.log". If the install fails, this file can be checked for error letters.

TODO

change this log file to exist kept after a successful install

Lock file

To ensure that two installs are non running on the same organisation, when the installer is started, information technology creates a lock file "/zfs.lock".

If the installation fails for a temporary reason, this lock file will need to exist manually deleted before retrying the install (or, only reboot the installer)

Ways to Login

Unless you have built your ain paradigm, the default root password used by the installer is root

Network

The installer epitome is running an ssh server. If you built your own paradigm, in that location is an piece of cake process to add ssh authorized keys to the installer.

For simple network discovery, the installer paradigm is as well running a mactelnet server. If you are on the same network segment as a booted installer, you tin can quickly discover the IP accost it has used with the mactelnet-client software: mactelnet -50 will wait for broadcasts and prove the systems detected. (If yous build your own image, you lot could add a mactelnetd.users file to allow logins via this service, merely past default it is only for network discovery)

Serial Console

A series console is started on ttyS1, it is running at 115200 bits per second and is expected to be used when installing server equipment (Configure your IPMI Serial-over-LAN and connect remotely to this panel)

Local VGA Screen

In addition to the default htop status screen, at that place is a login prompt on the virtual console ii - this can be reached with Ctrl-Alt-F2, and the htop status screen returned to with Ctrl-Alt-F1

Ways to Boot

Booting with a IPMI virtual media

If yous are booting using a BMC and wish to employ the virtual media to boot from then you will most probably need the CDROM ISO image.

Adhere the kicking.iso file using the virtial media controls

Booting with a USB Stick

When using the ISO image, exist aware that some EFI versions do not back up booting from the stick as if it was a cdrom.

The ISO file is mainly built for people who are remotely installing a server using a IPMI or BMC controller and a Virtual CDROM.

Some notes on UEFI

The install image is a EFI bootable disk, and this may crave you to change your firmware boot order to select the installer. The kicking image has a startup.nsh file that tells the EFI Shell the file to load and the parameters to utilize in order to boot (This is the place where the serial console is specified)

Booting with PXEboot

There are two files built for use with pxebooting.

kernel/ubuntu.amd64.kernel - This is the bootable linux kernel combined.initrd - This is the initrd containing the installer

Using pxelinux, the following stanza could be added to your pxelinux.cfg:

                label baremetalzfs     linux kernel/ubuntu.amd64.kernel     append initrd=combined.initrd panel=ttyS1,115200     card characterization Blank metal Installer with ZFS on root

Edifice the image

Before edifice the image for the starting time time, ensure that all required software is installed:

Then build the main installer images:

The completed boot.iso and boot.img tin be used to kicking a system.

Not all the dependancies are correctly managed, and then if you need to ensure a full rebuild is done, a clean tin can be done before the build:

If the cached large downloads are too out of date, they can exist removed with the actually clean target:

Test targets

To allow simpler examination of the arrangement and further development, there are a number of test targets available:

test_quick - By directly booting the kernel, avert loading the EFI and thus kicking the system faster (broadly similar to a PXE boot)

test_efi - Boot via EFI - allowing confirmation that the congenital epitome is a valid EFI kicking disk. This target does non open a graphics window and assumes only a series console is in utilize.

test_efigui - Boot via EFI with a graphic panel. This is basically the same as "test_efi", except that a window showing the VGA screen is opened in addition to the serial console output on the terminal.

test_efigui_persist - The aforementioned as "test_efigui" with the addition of a virtual difficult drive. This can exist used to test running the ZFS installer scripts to completion and then booting the installed system. The virtual hard drive is only created if it is missing, so it will persist between test runs (if this is not desired, either delete the file manually, or run "make reallyclean".

ISSUES

configure apt proxy settings from install environment to installed environ
Ctrl-Left keystroke sequence doesnt piece of work on text console (x11 is OK)