[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Software RAID with Debian Installer



On Sunday 10 July 2005 11:04 pm, Luke Pacholski wrote:
> On Sun, 10 Jul 2005 michael@etalon.net wrote:
> > Quoting Luke Pacholski <lukpac@lukpac.org>:
> > > [?] Partition disks
> > > Warning!
> > > The kernel was unable to re-read the partition table on /dev/md/0
> > > (Invalid argument). This means Linux won't know anything nothing about
> > > the modifications you made until you reboot.  You should reboot your
> > > computer before doing anything with /dev/md/0.
> >
> > I think you may want to check your syntax.
> > It should be /dev/md0
>
> Two things to note:
>
> 1) I did not set the device - that's what the installer used.
>
> 2) Looking in /dev, md0 does not exist. /dev/md/0 does.
>
> Luke

Are you using mdadm?  (It sound it, but I don't know what else is out there.)  
If so, just as a point of reference, I set mine up with mdadm, and it set it 
to /dev/md0.  I just did a "ls" of /dev/md* and got:

brw-rw----  1 root disk 9,  0 2001-06-02 14:23 /dev/md0
brw-rw----  1 root disk 9,  1 2001-06-02 14:23 /dev/md1
brw-rw----  1 root disk 9, 10 2001-06-02 14:23 /dev/md10
brw-rw----  1 root disk 9, 11 2001-06-02 14:23 /dev/md11
brw-rw----  1 root disk 9, 12 2001-06-02 14:23 /dev/md12
brw-rw----  1 root disk 9, 13 2001-06-02 14:23 /dev/md13
brw-rw----  1 root disk 9, 14 2001-06-02 14:23 /dev/md14
brw-rw----  1 root disk 9, 15 2001-06-02 14:23 /dev/md15
brw-rw----  1 root disk 9,  2 2001-06-02 14:23 /dev/md2
brw-rw----  1 root disk 9,  3 2001-06-02 14:23 /dev/md3
brw-rw----  1 root disk 9,  4 2001-06-02 14:23 /dev/md4
brw-rw----  1 root disk 9,  5 2001-06-02 14:23 /dev/md5
brw-rw----  1 root disk 9,  6 2001-06-02 14:23 /dev/md6
brw-rw----  1 root disk 9,  7 2001-06-02 14:23 /dev/md7
brw-rw----  1 root disk 9,  8 2001-06-02 14:23 /dev/md8
brw-rw----  1 root disk 9,  9 2001-06-02 14:23 /dev/md9

I don't know if this helps, but it would lead me to believe that the problem 
is that somehow it's working with the wrong device (/dev/md/0), but that's 
just a guess.

Hal



Reply to: