unxmaal / booterizer Goto Github PK

See https://datatracker.ietf.org/doc/html/rfc5737 .

This will require an image rebuild and push.

Hi all, thanks for the cool project.

I'm trying to use booterizer, running on a Raspberry Pi 4, to install IRIX 6.5.30 to the Indigo 2, and get 2 issues:

I. Indigo2 R10K is a 64bit CPU, so fx.64 command is required for this CPU instead of fx.ARCS, please fix the description

But anyway, the fx partitioner works, so the Ethernet connection between RPi4 and SGI is working.

II. But when I try to install the system, I get this error

Enter the name of the remote host: booterizer
Enter the remote directory: /6.5.30/Overlay/disc1/dist

Setting $netaddr to 192.0.2.82 (from server )
Unable to execute network(0)bootp()booterizer:/6.5.30/Overlay/disc1/dist/sa(sash64):  invalid argument
Cannot load network(0)bootp()booterizer:/6.5.30/Overlay/disc1/dist/sa(sash64) -- invalid argument.

At the same time, I can see this error in the booterizer log:

booterizer dhcpd[840]: BOOTREQUEST from 08:00:69:0a:a3:2b via eth0
booterizer dhcpd[840]: BOOTREPLY for 192.0.2.82 to sgi (08:00:69:0a:a3:2b) via eth0
booterizer in.tftpd[999]: RRQ from 192.0.2.82 filename /6.5.30/Overlay/disc1/stand/fx.64
booterizer dhcpd[840]: BOOTREQUEST from 08:00:69:0a:a3:2b via eth0
booterizer dhcpd[840]: BOOTREPLY for 192.0.2.82 to sgi (08:00:69:0a:a3:2b) via eth0
booterizer in.tftpd[1000]: RRQ from 192.0.2.82 filename /6.5.30/Overlay/disc1/dist/sa
booterizer in.tftpd[1000]: sending NAK (4, Request not null-terminated) to 192.0.2.82

For some reason, booterizer sending a correct response for the disc1/stand/fx.64 file but sending NAK for the disc1/dist/sa.
Any ideas, what can be wrong?

Thanks

Hello,
iscp doesn't start if eth0 doesn't have a link (ethtool eth0 -> Link detected ), then ansible playbook fails on:

Nov 21 02:18:01 booterizer isc-dhcp-server[6050]: Starting ISC DHCPv4 server: dhcpdcheck syslog for diagnostics. ...
Nov 21 02:18:01 booterizer isc-dhcp-server[6070]: failed!
Nov 21 02:18:01 booterizer isc-dhcp-server[6071]: failed!
Nov 21 02:18:01 booterizer systemd[1]: isc-dhcp-server.service: Control process exited, code=exited, status=1/FAILURE

I have O2 directly connected via CAT5e and wlan0 configured for internet access.
Please update an instruction that eth0 should be connected with line up before play. I suppose to setup rpi before start O2 ;-)

Hi,

i have download the booterizer_6.5.30_1.1.071321.xz and works fine on Rasp Pi B.

Only the instructions would have to be adapted somewhat. E.g. it is no longer called eth0 with Buster, but e.g. with me enxb827eb33a83c:

root@booterizer:/home/pi# ifconfig

**enxb827eb33a83c**: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255
        inet6 2003:ee:719:f500:e788:62a7:9d32:3b91 prefixlen 64 scopeid 0x0<global>

I had to reconfigure a few things:

/etc/dhcp/dhcpd.conf

INTERFACES="enxb827eb33a83c";
allow booting;
allow bootp;

subnet 192.168.1.0 netmask 255.255.255.0 {
#       ignore unknown-clients;
        range 192.168.1.80 192.168.1.200; # **you need now this line, Service will not start otherwise**

        host sgi {
                hardware ethernet xx:xx:xx:xx:xx:xx; # you mac
                fixed-address 192.168.1.82 ;
                option domain-name-servers 192.168.1.1;
                option domain-name "iris.local";
        }
}

nano /etc/default/isc-dhcp-server
INTERFACES="enxb827eb33a83c"

nano /etc/dhcpcd.conf:

interface enxb827eb33a83c
static ip_address=192.168.1.1/24
static routers=192.168.1.1
static domain_name_servers=192.168.1.1

Doing ansible-playbook -i inventory.yml rpi_booterizer.yml
Gives

fatal: [localhost]: UNREACHABLE! => {"changed": false, "msg": "Invalid/incorrect password: Permission denied, please try again.", "unreachable": true}

Here is some questions or notes about the README.md file:

• In requirements is line "VM host with TWO network interfaces". Why is this? I'm pretty sure booterizer worked out-of-the-box for me on a computer with a single NIC. Or does "VM host" here refer to the Vagrant VM? In either case I'm missing the point of this requirement/recommendation.
• It remains bit foggy if this version supports IRIX 5.3 or not. It is mentioned, with a slightly confusing link to "Callahan's Booterizer", but not mentioned elsewhere. Notably not in the target table or OS list.
• Inconsistent use of both spellings 'booterizer' and 'Booterizer' leaves it unclear which should be followed.
• irix_ansible guide here seems bit incomplete and possibly confusing. Would it be better just to provide a very brief description and a link to corresponding repository readme, to avoid redundancy?

I just deployed 6.5.22 to my Indigo2 successfully, using a Pi 3B, with just 2 minor hiccups:

• After running the ansible script, the resulting "selections" file in /irix has a typo. The Overlays 2 line read "from 192.0.2.99:6.5.22/Overlay/disc2/CDROM/dist", obviously the "CDROM/" part shouldn't be there.
• Raspbian seems to use so-called "predictable interface names" by default, so the wired ethernet interface is called "ethXXXXXXXXXX" where the X's are the MAC address. I needed to turn this off in raspi-config for the ansible script to succeed. I suspect it would have also worked if I had entered the "ethXXXXXXXXXX" interface name to the settings.yml in the 'bridgenic' line. One way or another the README could mention this maybe?

Image version is booterizer_6.5.30_1.1.112021.img

Otherwise this is an awesome project, thank you for putting in all the effort. Certainly made my life a heck of a lot easier! :)

Environment: Raspberry pi 2 with booterizer image (which I can confirm it works properly)
IRIX selected version: 6.5.22
Target machine: SGI Indy (R4600)

After setting everything up, the selections file from booterizer gets loaded properly, except it does not properly load disc2.

Disc2 is reported as 192.0.2.99:6.5.22/Overlay/disc2/CDROM/dist while it should be 192.0.2.99:6.5.22/Overlay/disc2/dist.

This fixes conflicts and therefore allows to continue the installation of IRIX.

the 6.5.22 overlay disc2 has an additional CDROM dir prefix:

vladimir@media:~/proj/booterizer/irix/6.5.22/Overlay/disc2$ tar tvzf disc2.tar.gz
drwxr-xr-x ftp/ftp           0 2018-05-12 02:31 disc2/
drwxr-xr-x ftp/ftp           0 2018-05-12 02:31 disc2/CDROM/
-rw-r--r-- ftp/ftp         197 2018-05-12 02:31 disc2/CDROM/.IM
-rw-r--r-- ftp/ftp        3218 2018-05-12 02:31 disc2/CDROM/CDrelnotes
drwxr-xr-x ftp/ftp           0 2018-05-12 02:31 disc2/CDROM/dist/
...

which means that it gets extracted as just 'CDROM' and then I think totally ignored during the install process. Most everything on disc2 looks like it gets replaced by either devlibs or apps later on, but not all. I noticed this because disc2 would always get re-extracted when I re-provisioned the vagrant VM.

IRIX 6.5.30 disc2 does not have this extra CDROM path; probably not many folks installing 6.5.22 :)

Using the prebuilt RPI image and images downloaded today the dist folder for Overlay disc2 is the same as 5.2.30: /Overlay/disc2/dist

This caused the installer to report many conflicts and missing subystems, and I had to manually include it in the installer.

I am not sure if this is the case for everyone, but it was for me.

Ubuntu 20.x+ (vbox6+) does not work with the provided vagrant configuration

Tested on Ubuntu 22 (virtualbox 7) and the machine doesn't seem to be come up.

adding the VDI fails, even in fix-vfi branch....

==> default: Running 'pre-boot' VM customizations...
A customization command failed:

["createhd", "--filename", "/Volumes/hitachibyte2017/code/booterizer-2019/installdisk.vdi", "--size", 51200]

The following error was experienced:

#<Vagrant::Errors::VBoxManageError: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["createhd", "--filename", "/Volumes/hitachibyte2017/code/booterizer-2019/installdisk.vdi", "--size", "51200"]

Stderr: 0%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Failed to create medium
VBoxManage: error: Could not create the medium storage unit '/Volumes/hitachibyte2017/code/booterizer-2019/installdisk.vdi'.
VBoxManage: error: VDI: cannot create image '/Volumes/hitachibyte2017/code/booterizer-2019/installdisk.vdi' (VERR_ALREADY_EXISTS)
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component MediumWrap, interface IMedium
VBoxManage: error: Context: "RTEXITCODE handleCreateMedium(HandlerArg *)" at line 450 of file VBoxManageDisk.cpp
>

Please fix this customization and try again.

virtualbox: 6.0.12,133076

During inst /irix/selections file specifies "from 192.0.2.99:6.5.22/Overlay/disc2/CDROM/dist" which is not found. Removing the "CDROM" allows it to be found and no conflicts during inst.

At the very least IMO:

patchSG0007149 - NEW FIRMWARE (l1, l2, io9, io10)
patchSG0007208 - UPDATED IP35 PROM - fixes to fibre channel
patchSG0007192 - updates to NFS

So far I have always used booterizer to install IRIX 6.5.22 on various Indigo2s, but now I tried to prepare everything to set up IRIX 5.3 on my R3k Iris Indigo, which does not support 6.x.

When I change "irixversion" in settings.yml to "5.3" and run "ansible-playbook...." it fails at some point with error:

TASK fetch_files: Fetch overlay disc 1
fatal: [localhost] failed: the task includes an option with an unidentified variable. the error was: 'dict object' has no attribute 'Overlay'.
The error appears to be in '/root/projects/github/booterizer/ansible/roles/fetch_files/tasks/setup_media.yml' line 32, column 3, ... the offending line appears to be: name: Fetch overlay disc1

Now I am not sure whether IRIX 5.3 is really supported in booterizer (I'm using the raspi version)? Although I have seen references to 5.3 in some yml files, but in the github readme it seems to be 6.5.x only?

thanks!