From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 27 22:15:14 2014 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F1DEB3D2; Sat, 27 Sep 2014 22:15:13 +0000 (UTC) Received: from mail-yh0-x22d.google.com (mail-yh0-x22d.google.com [IPv6:2607:f8b0:4002:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A6F14995; Sat, 27 Sep 2014 22:15:13 +0000 (UTC) Received: by mail-yh0-f45.google.com with SMTP id a41so4646339yho.32 for ; Sat, 27 Sep 2014 15:15:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VB+ng4gitQhat1p5JQEZ840uyZir95NAp2rHLoiRud4=; b=VGKcz/Fa7n66OwtqZMHx59t06jDp7x+fB7VStN05Rvc1s+O7/GbDHtprsNyv5uAf+Z 4myWbenvRGEN6nqcOvpL3HIydC6T8PAdq/JcyDVtTQlYGHtQ9vv0E+BLTkto6/7ewlXe ci77gJfXE+p+mo16Av26/iDOy9ozPDi8Jt6i2hWvo9Fc8ju6i9ZznDtWdaxXKPo2oBWm vq1Kci3Wx86ITJJeH8FmWsTrB4uQBcleqE/Xh+ztBZQHERfHlHfVWk6FGdI2eRq5IYV/ ndIFxvaM+40EGvGww4KEZM/l60P4Ri7EDC2aT0t0ZnlWLsAyk5PxHSlAd4QEqU/Zz0A5 gDgw== MIME-Version: 1.0 X-Received: by 10.236.132.20 with SMTP id n20mr17611916yhi.94.1411856112705; Sat, 27 Sep 2014 15:15:12 -0700 (PDT) Received: by 10.170.206.10 with HTTP; Sat, 27 Sep 2014 15:15:12 -0700 (PDT) In-Reply-To: <1411851225.9364.YahooMailNeo@web180902.mail.ne1.yahoo.com> References: <1411851225.9364.YahooMailNeo@web180902.mail.ne1.yahoo.com> Date: Sat, 27 Sep 2014 15:15:12 -0700 Message-ID: Subject: Re: Inproper ada# assignment in 10-BETA2 From: Mehmet Erol Sanliturk To: Jin Guojun Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "hackers@freebsd.org" , questions freebsd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Sep 2014 22:15:14 -0000 On Sat, Sep 27, 2014 at 1:53 PM, Jin Guojun wrote: > Installed 10-BETA2 on SATA port 4 (ad8) and then added another SATA port 3 > (ad6), the system has not correctly enumerate the ada # for the boot device. > As original boot (without the second SATA drive), the ad8 is enumerated as > ada0 -- the boot drive: > > Sep 24 22:51:30 R10-B2 kernel: ada0 at ahcich2 bus 0 scbus2 target 0 lun 0 > Sep 24 22:51:30 R10-B2 kernel: ada0: > ATA-8 SATA 2.x device > ... > Sep 24 22:51:30 R10-B2 kernel: ada0: Previously was known as ad8 > > > However, after added another SATA drive (ad6), this new drive is assigned > to ada0, but ad8 has changed to ada1. This is incorrect dynamic device > assignment. FreeBSD has kept using fixed disk ID assignment due to the same > problem introduced in around 4-R (or may be slightly later), and after a > simple debate, a decision was made to use fixed drive ID to avoid such > hassle. > > If now we want to use dynamic enumeration for drive ID# assignment, this > has to be done correctly -- boot drive MUST assigned to 0 or whatever the # > as installation assigned to; otherwise, adding a new drive will cause > system not bootable, or make other existing drive not mountable due to > enumeration # changes. > > Has this been reported as a known problem for 10-R, or shall I open a bug > to track? > > -Jin > One point should be checked : On mainboards SATA ports are numbered from 0 or 1 to upward . BIOS always uses first SATA drive for boot . This is NOT related to the operating system . Therefore , it is necessary to check port numbers of existing drives and the bootable SATA drive should be connected to the smallest numbered SATA port among existent drives . For example , assume bootable drive is connected to SATA port 2 . New drive should be connected to a higher numbered SATA port . If there are only two SATA ports , then bootable drive should be connected to the first SATA port . If mainboard BIOS allows definition of any SATA port for boot , and bootable SATA port and drive is specified in there , again it may boot from that drive . Up to now , I did not see any BIOS which supplies such an ordering among SATA ports . Please check your BIOS for such a feature . If it is present you may use it , otherwise it is necessary to reconnect SATA cables . Thank you very much . Mehmet Erol Sanliturk