FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 06-07-2011, 09:00 AM
 
Default Missing device nodes

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.

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?

Thanks.
 
Old 06-07-2011, 01:30 PM
Ron Johnson
 
Default Missing device nodes

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?

Thanks.



--
"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


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4DEE27EF.6040907@cox.net">http://lists.debian.org/4DEE27EF.6040907@cox.net
 
Old 06-07-2011, 02:52 PM
 
Default Missing device nodes

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?



Thanks.






--

"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





--

To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Archive: http://lists.debian.org/4DEE27EF.6040907@cox.net
 
Old 06-07-2011, 03:47 PM
Ron Johnson
 
Default Missing device nodes

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


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4DEE47F6.8070100@cox.net">http://lists.debian.org/4DEE47F6.8070100@cox.net
 
Old 06-07-2011, 03:50 PM
martin f krafft
 
Default Missing device nodes

also sprach Ron Johnson <ron.l.johnson@cox.net> [2011.06.07.1747 +0200]:
> So it's md that can't find them?

What's in /proc/partitions?

What happens if you list the DEVICES specifically in mdadm.conf (and
rebuild the initramfs)?

--
.'`. martin f. krafft <madduck@d.o> Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduck http://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems

"sailing is, after all, a kind of grace, a kind of magic."
-- phil berman
 
Old 06-08-2011, 01:17 AM
 
Default Missing device nodes

Hi,
Ron:> So it's md that can't find them?Yes, md cannot find them, but I think that's because Debian doesn't detect them in the first place.

Martin:> What's in /proc/partitions?
>
> What happens if you list the DEVICES specifically in mdadm.conf (and�rebuild the initramfs)?

I don't have access to the file server at this moment, but /etc/mdadm/mdadm.conf defines just the array (via UUID). I was under the impression that md would automatically assemble the array based on the information in the superblocks.

On Tue, Jun 7, 2011 at 11:50 PM, martin f krafft <madduck@debian.org> wrote:

also sprach Ron Johnson <ron.l.johnson@cox.net> [2011.06.07.1747 +0200]:

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



What's in /proc/partitions?



What happens if you list the DEVICES specifically in mdadm.conf (and

rebuild the initramfs)?



--

�.'`. � martin f. krafft <madduck@d.o> � � �Related projects:

: :' �: �proud Debian developer � � � � � � � http://debiansystem.info

`. `'` � http://people.debian.org/~madduck � �http://vcs-pkg.org

�`- �Debian - when you have better things to do than fixing systems



"sailing is, after all, a kind of grace, a kind of magic."

� � � � � � � � � � � � � � � � � � � � � � � � � � � �-- phil berman
 
Old 06-08-2011, 07:09 AM
martin f krafft
 
Default Missing device nodes

also sprach titantoppler@gmail.com <titantoppler@gmail.com> [2011.06.08.0317 +0200]:
> I don't have access to the file server at this moment, but
> /etc/mdadm/mdadm.conf defines just the array (via UUID). I was under the
> impression that md would automatically assemble the array based on the
> information in the superblocks.

Sure: it scans all the devices listed with DEVICE in mdadm.conf, or
in /proc/partitions if there are no DEVICEs listed.

--
.'`. martin f. krafft <madduck@d.o> Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduck http://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems

"lessing was a heretics' heretic"
-- walter kaufmann
 
Old 06-08-2011, 12:10 PM
 
Default Missing device nodes

My /proc/partitions (edited to keep only the relevant parts):
* *8 * * * 48 *976762584 sdd* *8 * * * 80 *976762584 sdf* *8 * * * 81 *976760001 sdf1* *8 * * * 96 *976762584 sdg
* *8 * * * 64 *976762584 sde
My /etc/mdadm/mdadm.conf looks like thisEVICE partitionsARRAY /dev/md0 UUID=<UUID of array>
On Wed, Jun 8, 2011 at 3:09 PM, martin f krafft <madduck@debian.org> wrote:

also sprach titantoppler@gmail.com <titantoppler@gmail.com> [2011.06.08.0317 +0200]:


> I don't have access to the file server at this moment, but

> /etc/mdadm/mdadm.conf defines just the array (via UUID). I was under the

> impression that md would automatically assemble the array based on the

> information in the superblocks.



Sure: it scans all the devices listed with DEVICE in mdadm.conf, or

in /proc/partitions if there are no DEVICEs listed.



--

*.'`. * martin f. krafft <madduck@d.o> * * *Related projects:

: :' *: *proud Debian developer * * * * * * * http://debiansystem.info

`. `'` * http://people.debian.org/~madduck * *http://vcs-pkg.org

*`- *Debian - when you have better things to do than fixing systems



"lessing was a heretics' heretic"

* * * * * * * * * * * * * * * * * * * * * * * * * *-- walter kaufmann
 

Thread Tools




All times are GMT. The time now is 07:40 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org