Re: Missing device nodes

[Ron Johnson <ron.l.johnson@cox.net>]

So it's md that can't find them?

On 06/07/2011 09:52 AM, titantoppler@gmail.com wrote:
> Hi,
>
> I'm actually not too concerned about the "missing" partitions, as I do know
> that they exist - fdisk shows the partition table, and partprobe will make
> the partitions show up in /dev again.
>
> I'm thinking it might have something to do with udev, but I'm not sure.
>
> Googling for this issue usually throws up results from more than 5-6 years
> ago, mostly from the static devfs to udev transition period.
>
> On Tue, Jun 7, 2011 at 9:30 PM, Ron Johnson<ron.l.johnson@cox.net>  wrote:
>
> > On 06/07/2011 04:00 AM, titantoppler@gmail.com wrote:
> >
> > > Hi list,
> > >
> > > I'm running Debian Wheezy (testing) on the latest kernel (2.6.38-2-686)
> > > as my file server. This server has a RAID 5 array composed of 4 SATA
> > > hard disks connected to the motherboard controller.
> > >
> > > mdadm complains that it is unable to start the array on boot up (it says
> > > that only 1 out of 4 drives are found).
> > >
> > > "ls /dev" shows that the other 3 drives are present, but the partitions
> > > are not. That is, /dev/sd[a-c] are present, but /dev/sd[a-c]1 are missing.
> > The *partitions* have disappeared???  That's scary, and what I'd google
> > about.
> >
> >
> >   A "partprobe /dev/sd[a-c] -s" usually makes the partitions appear again,
> > > and I can then remount the mdadm array without complaints.
> > >
> > > However, it is getting pretty irritating. Is there a permanent fix for
> > > this?

--
"Neither the wisest constitution nor the wisest laws will secure
the liberty and happiness of a people whose manners are universally
corrupt."
Samuel Adams, essay in The Public Advertiser, 1749