X-Original-To: alpine-user@lists.alpinelinux.org Delivered-To: alpine-user@mail.alpinelinux.org Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id AFCC7DC0084 for ; Tue, 7 Apr 2015 09:42:42 +0000 (UTC) Received: from [192.168.1.168] ([79.194.139.107]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0LgI0W-1ZB9oi3M1s-00nfzA for ; Tue, 07 Apr 2015 11:42:40 +0200 Message-ID: <5523A68A.10106@gmx.de> Date: Tue, 07 Apr 2015 11:42:34 +0200 From: Erwin Lottermann User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 X-Mailinglist: alpine-user Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 To: alpine-user@lists.alpinelinux.org Subject: [alpine-user] fdisk doesn't support disk identifier and syslinux fails at chainloading References: <551BECA9.9070305@gmx.de> In-Reply-To: <551BECA9.9070305@gmx.de> X-Forwarded-Message-Id: <551BECA9.9070305@gmx.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:sChTjaFquUO6sPGVhI/zIN3JCh5otT7cSYL7w3iWu9UXf3BNLgn bXXxQpdahRt063JGbqzapWCaC5QK/8nqguI8CoSEVnhkPjLvg1vIxs+QCzT9sXVyemfNsLD l1RK5j/4+o3mnNWd1wjQNqjHb+OFvLM1Iqx4pH8RDy7xDcknLhffDZBYmtbz+c44Zzd3xKb D0BjICLYbtzg/dJEWVUDw== X-UI-Out-Filterresults: notjunk:1; Hi, I installed Alpine 2.7.9 (from http://www.eisfair.org/home/eisfair-ng/ ) at HP Microserver Gen8. In AHCI-Mode the onboard HP Raid Controller doesn't allow to select the disk to boot from. It always tries to boot from first Disk it detects, starting from Port1. One solution is, to boot from usb stick with syslinux and direct it to the MBR to be bootet. Whith syslinux you can chainload the MBR of another disk, i.e. the one Alpine is installed. http://www.syslinux.org/wiki/index.php/Comboot/chain.c32 There are several options to address the mbr to be bootet. In case of the HP server 'mbr:' should work, where is the disk identifier shown in fdisk -l /dev/sdx. But the fdisk, used in Alpine, doesn't show the disk identifier. It also has no 'i' option in the expert menu, to set the disk identifier. With option 'd' you can see, that the alpine setup has set the disk identifier to 0x00000000 ( 4 Bytes between 1b8 and 1bb) Perhaps this http://wiki.r1soft.com/display/kb3/Creating+a+Unique+Partition+ID+with+fdisk is the reason, why there is no disk identifier option in Alpines fdisk. I booted an ubuntu and set with its fdisk the disk identifier of the Alpine disk. In next step I installed Alpines syslinux to the usb stick and created the syslinux.cfg file for the chainloading. At boot time, when the mbr of the Alpine hdd was called by syslinux from usb stick, the boot process stopped wiht HP's 'Red Screen of Death' with 'illegal opcode' and some register dumps. The reason is, that syslinux 6.02 has a failure related to chainload. http://www.syslinux.org/wiki/index.php/Syslinux_6.02_notes Booting from usb worked, after I installed e newer version of syslinux at the usb stick. After this I installed Alpine 3.1.3. Disk Identifier was cleared again. Thus I had to set it again with ubuntus fdisk. Chainloading with syslinux worked. Regards Erwin --- Unsubscribe: alpine-user+unsubscribe@lists.alpinelinux.org Help: alpine-user+help@lists.alpinelinux.org ---