/dev/sda16+ not recognized

Forum member eps reported this. It applies to all puppies.

The nodes in /dev in the initrd are static, and only go up to sda15. Thus, if a hard drive has more partitions, they are not recognized.

After bootup, when the main filesystem is running, the kernel will auto-create the extra nodes if new hardware is plugged in, but not in the case of an internal drive present at bootup.

However, eps found that running Gparted does cause the extra device nodes to be created.

In Woof, I have created extra nodes for the initrd, up to sda23. I also did the same thing for the main filesystem.

Woof commit:

Posted on 28 Aug 2012, 21:34


Posted on 28 Aug 2012, 24:26 by L18L
re: /dev/sda16+
ymount a lighter alternative to Pmount
created by Iguleder
hacked and internationalized by L18L
was never having that limitation to 15 partitions.

see forum:

Posted on 29 Aug 2012, 7:00 by K Godt
I am guessing there would come the day when


Posted on 29 Aug 2012, 8:40 by shinobar
The 431JP2012(Japanese edition) has no /dev/sd* stuff in the main sfs at all, and has no problem.


Posted on 29 Aug 2012, 8:47 by technosaurus
devtmpfs, hotplug etc...
Devtmpfs basically just uses /sys to create char/block devices in /dev, but is a bit slower than a static /dev. Correct me if I am wrong but pupevent* could just as easily create them prior to mount.

Posted on 29 Aug 2012, 9:35 by K Godt
Big Q
The device nodes should be there i think, otherwise i think the kernel is not able to mount the partition itself (panic on unknown block 8:1 if root=/dev/sda1) ? The device nodes are in the initrd.gz also which would explain that shinobar's setup works (in frugal mode).

Posted on 29 Aug 2012, 18:45 by jamesbond
devtmpfs in Fatdog 600
Fatdog 600 no longer uses static device nodes, both in initrd and main sfs. Everything is dynamically managed by devtmpfs and udev.