From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hard drives not detected in repeatable order.
Date: Mon, 3 Oct 2011 20:38:19 +0100 [thread overview]
Message-ID: <201110032038.28690.michaelkintzios@gmail.com> (raw)
In-Reply-To: <4E8A067C.8070507@binarywings.net>
[-- Attachment #1: Type: Text/Plain, Size: 1004 bytes --]
On Monday 03 Oct 2011 20:01:16 Florian Philipp wrote:
> Am 03.10.2011 20:40, schrieb Grant Edwards:
> > 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).
Is it perhaps because /dev/sda is PATA on IDE and the rest are SATA?
> > What's the recommended way to fix this?
>
> Mount by UUID or label. In /etc/fstab, specify UUID=foo or LABEL=bar
> instead of /dev/sdx1. You can current UUIDs and labels with `ls -l
> /dev/disk/by-uuid` and `ls -l /dev/disk/by-label`, respectively.
UUID or labels will solve this problem for sure, but if you are still trying
to find out what changed to cause this, have you looked at your BIOS settings
and how it recognises the drives?
Have you changed anything on the physical side (jumpers, cables, etc)?
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-10-03 19:45 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 18:40 [gentoo-user] Hard drives not detected in repeatable order Grant Edwards
2011-10-03 18:47 ` Canek Peláez Valdés
2011-10-03 18:48 ` Volker Armin Hemmann
2011-10-03 18:49 ` [gentoo-user] " Grant Edwards
2011-10-03 19:03 ` Canek Peláez Valdés
2011-10-03 19:28 ` Paul Hartman
2011-10-03 19:47 ` Michael Mol
2011-10-03 19:49 ` Canek Peláez Valdés
2011-10-03 21:37 ` Neil Bothwick
2011-10-04 2:25 ` Walter Dnes
2011-10-04 2:45 ` Canek Peláez Valdés
2011-10-04 15:43 ` bill.longman
2011-10-04 3:15 ` Dale
2011-10-04 4:54 ` Spidey
2011-10-04 5:00 ` Canek Peláez Valdés
2011-10-04 5:02 ` Adam Carter
2011-10-04 5:09 ` Canek Peláez Valdés
2011-10-04 5:29 ` Florian Philipp
2011-10-04 5:36 ` Canek Peláez Valdés
2011-10-04 5:10 ` Paul Hartman
2011-10-04 5:20 ` Canek Peláez Valdés
2011-10-04 5:25 ` Adam Carter
2011-10-04 5:28 ` Canek Peláez Valdés
2011-10-04 14:23 ` Grant Edwards
2011-10-04 14:18 ` Grant Edwards
2011-10-04 15:12 ` Canek Peláez Valdés
2011-10-04 14:02 ` Michael A. Koerber
2011-10-04 14:29 ` Grant Edwards
2011-10-04 14:47 ` Spidey
2011-10-04 15:59 ` Florian Philipp
2011-10-05 5:53 ` Walter Dnes
2011-10-05 13:29 ` Michael A. Koerber
2011-10-05 14:34 ` Florian Philipp
2011-10-05 18:54 ` walt
2011-10-05 19:57 ` pk
2011-10-05 20:31 ` Paul Hartman
2011-10-05 20:33 ` Florian Philipp
2011-10-04 14:48 ` Paul Hartman
2011-10-04 15:01 ` Dale
2011-10-03 18:50 ` [gentoo-user] " Michael Mol
2011-10-03 19:01 ` Florian Philipp
2011-10-03 19:15 ` Bill Longman
2011-10-03 19:34 ` Paul Hartman
2011-10-03 20:13 ` [gentoo-user] " Grant Edwards
2011-10-03 19:38 ` Mick [this message]
2011-10-03 20:20 ` Grant Edwards
2011-10-03 19:46 ` [gentoo-user] " Dale
2011-10-03 19:54 ` Mark Knecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201110032038.28690.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox