Hi Frans, On Tue, Dec 05, 2017 at 02:43:48PM +0100, Frans van Berckel wrote: > Silo does not ask for a device, it just installs. Rebooting goes into a
Hmm - priority=low is set in the installer? > disk errors and searching for the dhcp network device. > > Rebooting with command: boot > > Bad magic number in disk label > Can't open disk label package Sounds like the sun partition table is not ok after installation - what does "fdisk /dev/sda" tell you ? Does "hexdump -C /dev/sda" (or sdb) contain stuff like: 00000000 53 55 4e 33 36 47 20 63 79 6c 20 32 34 36 32 30 |SUN36G cyl 24620| 00000010 20 61 6c 74 20 32 20 68 64 20 32 37 20 73 65 63 | alt 2 hd 27 sec| 00000210 00 00 00 00 00 00 40 00 53 49 4c 4f 30 2e 39 39 |[email protected]| 000003a0 10 6f ff f4 d6 75 20 28 66 69 6e 64 64 65 76 69 |.o...u (finddevi| 000003b0 63 65 00 67 65 74 70 72 6f 70 00 62 6f 6f 74 70 |ce.getprop.bootp| 000003c0 61 74 68 00 73 74 64 6f 75 74 00 6f 70 65 6e 00 |ath.stdout.open.| 000003d0 63 6c 6f 73 65 00 73 65 65 6b 00 72 65 61 64 00 |close.seek.read.| 000003e0 77 72 69 74 65 00 2f 63 68 6f 73 65 6e 00 65 78 |write./chosen.ex| 000003f0 69 74 00 00 00 00 00 00 00 00 00 00 00 02 21 bc |it............!.| Another way which might work is setup the raid1 in the shell, then make in the installer an ext2 on /dev/md1 (boot) and format it. Stop the raid in the shell and in the installer install with /boot on the /dev/sda1 without formatting. Finish installation and test reboot from sda: "boot disk" Idea with that is to install silo like a single disk setup, only that the boot partitions ext2 is a bit smaller to allow for the md block at the end of the boot partition. Then dd the first 8k or so to /dev/sdb and add /dev/sdb1 to /dev/md1. Good luck, greetings Hermann -- Netzwerkadministration/Zentrale Dienste, Interdiziplinaeres Zentrum fuer wissenschaftliches Rechnen der Universitaet Heidelberg IWR; INF 205; 69120 Heidelberg; Tel: (06221)54-14405 Fax: -14427 Email: [email protected]
