From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RAnjT-00046c-2w for garchives@archives.gentoo.org; Mon, 03 Oct 2011 18:59:23 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EA82521C092; Mon, 3 Oct 2011 18:59:03 +0000 (UTC) Received: from mail-bw0-f53.google.com (unknown [209.85.214.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 6247321C036 for ; Mon, 3 Oct 2011 18:57:37 +0000 (UTC) Received: by bkbzt12 with SMTP id zt12so7221964bkb.40 for ; Mon, 03 Oct 2011 11:57:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=7vZ+1596PZDPuyI9a1beB55zFigSKib0g7zYWhOSS5c=; b=gzku/akS18viWa74C9U+AN7PhXy3ww4lhu54wteLxra8JCpz7qWgltv5QpWg3V3m8I IEpzEWOKzDFiyVRuFe9/gLP5c6sZUWvQLHN72NbFS2UMz/ir05Z33Rw9VEdDMNTqofSr Uv+cEi5/68hEt3t1SitOc4Q1OroDmiRoPg+C8= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.204.143.26 with SMTP id s26mr161773bku.181.1317667830486; Mon, 03 Oct 2011 11:50:30 -0700 (PDT) Received: by 10.204.177.199 with HTTP; Mon, 3 Oct 2011 11:50:30 -0700 (PDT) In-Reply-To: References: Date: Mon, 3 Oct 2011 14:50:30 -0400 Message-ID: Subject: Re: [gentoo-user] Hard drives not detected in repeatable order. From: Michael Mol To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: X-Archives-Hash: 01ee8d8d76510a99e782d065806ea80c On Mon, Oct 3, 2011 at 2:40 PM, Grant Edwards wrote: > Just recently I've run in to problems because my hard drives are not > detected in a predictable order, so my fstab that mount /dev/sdb1 and > /dev/sdc1 sometimes result in directory trees in the wrong places > (/dev/sda seems consistent, but I don't know why). > > What's the recommended way to fix this? Mount by volume name or UUID. For example, from fstab: UUID=bddee12c-0047-4b4b-b1d2-9e137a9a8915 / auto noatime 0 1 UUID=857d7723-9dbf-4222-ac28-e05b87b41997 none swap sw 0 0 UUID=8d3648cf-5260-4064-b6a5-50df42acb3d8 /mnt/prevhome auto noatime 0 2 UUID=d7c17623-255b-4313-b50b-99f0f79a0681 /home auto noatime 0 2 UUID=33cc682d-0dd4-4c2b-bf37-876e9f8d3ef4 /boot auto noatime 0 2 To find the UUID: shortcircuit:4@serenity/dev/disk/by-uuid Mon Oct 03 02:49 PM !509 #9 j0 ?0 $ ls -l total 0 lrwxrwxrwx 1 root root 10 Sep 24 00:11 33cc682d-0dd4-4c2b-bf37-876e9f8d3ef4 -> ../../sda1 lrwxrwxrwx 1 root root 10 Sep 24 00:11 857d7723-9dbf-4222-ac28-e05b87b41997 -> ../../sda2 lrwxrwxrwx 1 root root 10 Sep 24 00:11 8d3648cf-5260-4064-b6a5-50df42acb3d8 -> ../../sda3 lrwxrwxrwx 1 root root 10 Sep 24 00:11 bddee12c-0047-4b4b-b1d2-9e137a9a8915 -> ../../sda4 lrwxrwxrwx 1 root root 10 Sep 24 00:11 d7c17623-255b-4313-b50b-99f0f79a0681 -> ../../dm-0 -- :wq