linux-kernel - Re: [PROBLEM] Can't start MD devices by using /dev/disk/by-id

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <45D259DD.7040505@tmr.com>
Date:	Tue, 13 Feb 2007 19:37:49 -0500
From:	Bill Davidsen <davidsen@....com>
To:	Patrick Ale <patrick.ale@...il.com>
CC:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PROBLEM] Can't start MD devices by using /dev/disk/by-id

Patrick Ale wrote:
> Hi chaps,
> 
> I just came home, rebooted my box to git8 and *gasp* a problem :)
> 
> I can't start my MD devices anymore by defining /dev/disk/by-id/*
> devices in /etc/mdadm.conf.
> 
> When I do a: mdadm --assemble /dev/md/1 it tells me "No devices found
> for /dev/md/1"
> When I edit the file /etc/mdadm.conf and change the /dev/disk/by-id/*
> to whatever the symbolic links points to in the /dev directory, it
> does work.
> 
Just out of curiosity, why did you do this in such a manual way instead 
of just using the UUID? I would think every time you replace a failed 
drive you would have to go edit the files all over again.

-- 
Bill Davidsen <davidsen@....com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/