1 |
On Mon, 2011-10-03 at 15:03 -0400, Canek Peláez Valdés wrote: |
2 |
|
3 |
> On Mon, Oct 3, 2011 at 11:49 AM, Grant Edwards |
4 |
> <grant.b.edwards@×××××.com> wrote: |
5 |
> > On 2011-10-03, Grant Edwards <grant.b.edwards@×××××.com> wrote: |
6 |
> >> Just recently I've run in to problems because my hard drives are not |
7 |
> >> detected in a predictable order, so my fstab that mount /dev/sdb1 and |
8 |
> >> /dev/sdc1 sometimes result in directory trees in the wrong places |
9 |
> >> (/dev/sda seems consistent, but I don't know why). |
10 |
> > |
11 |
> > I still don't know what changed to cause disks ordering to become |
12 |
> > non-deterministic. I recently upgraded from a single-core CPU to a |
13 |
> > dual-core CPU. Would that do it? |
14 |
> > |
15 |
> >> What's the recommended way to fix this? |
16 |
> > |
17 |
> > After a bit more googling, it looks like this is what disk labels are |
18 |
> > for. Never used them before, but it looks like it's time to give them |
19 |
> > a go. |
20 |
> |
21 |
> They have the advantage over UUID's in that you can set them and |
22 |
> therefore can be human readable. Also, if you use a desktop |
23 |
> environment, they look nice in file managers. |
24 |
|
25 |
I have found that use of LABEL=FOO in /etc/fstab doesn't always solve |
26 |
the problem of disks being reassigned during boot. I use |
27 |
LABEL=/Whatever for all file systems mounted on my Dell D830. The main |
28 |
drive (most of the time) is /dev/sda. Sometimes I'll insert a second |
29 |
drive in the machine (in the side battery slot) then power up. This |
30 |
drive gets the /dev/sda assignment. I'm guessing since it doesn't have |
31 |
a /boot directory on it the system fails to start. |
32 |
|
33 |
If I power up w/o this second drive, and wait until the kernel start |
34 |
reading the s/u scripts, I can insert the drive (during bootup) and |
35 |
everything is mounted the way I intended. |
36 |
|
37 |
Mike |