Puppy Linux Discussion Forum

Using a file server with multiple drives you'll run into a problem as soon as you add a card reader.
A 5-in-1 card reader will occupy five drive letters while you insert f.e. a micro SD card into it.
Drive letters will end at 'sdj'. No luck with 'sdk' and so on.

Noticed this while running Dunfell 2.8.1 and 2.8.4 so far.

I have used USB sticks and an adapter SD to micro SD for verification of the problem.

Hi, had this problem in the past with my old scsi rack, from memory, you just need to go in and tell it to create the extra /dev/nodes, I just don't remember where, hopefully barry will know.

Hi scsijon.

Yes, it is an old BIOS box from 2010.
I just double checked /dev. The proper nodes are created, but 'Pmount' will not offer it for mounting (sdk1,sdk2).

Did some more testing with older EasyOS versions.
EasyOS-Buster 2.3.3 has the same problem.

Ok, it might be the "other end" then, check if you have the /mnt/sd?? mount points, they are easy to create, they are just empty directories as normal with 747 access and should stay there on reboot.

I checked the "other end" - looks good over there too. Last mount point will be sdj1 and sdj2.

Looking at /root/.pup_event shows that "drive_sdk (type: App)" gets created but none for "drive_sdk1" and "drive_sdk2".

Is it possible that Barry limited the amount of drive icons to "12"?

/usr/sbin/pmount calls 'probepart'. Try running probepart in a terminal, see if that reports all partitions:

# probepart

It only shows sdk in it's entirety but no partitions. sdk is formated same way as sda, sdb, sdc and sdd. sde...sdi is a 5-in-1 card reader.
Please keep this in mind from my second post: "Did some more testing with older EasyOS versions. EasyOS-Buster 2.3.3 has the same problem."

# probepart
/dev/sda1|vfat|1308672
/dev/sda2|ext4|59514880
/dev/sdb1|vfat|1308672
/dev/sdb2|ext4|59514880
/dev/sdc1|vfat|1308672
/dev/sdc2|ext4|59514880
/dev/sdd1|vfat|1308672
/dev/sdd2|ext4|59514880
/dev/sde||0
/dev/sdf1|vfat|1308672
/dev/sdf2|ext4|61023232
/dev/sdg||0
/dev/sdh||0
/dev/sdi||0
/dev/sdj1|vfat|1308672
/dev/sdj2|ext4|61210624
/dev/sdk||61440000
# 

Just booted EasyOS 2.3.3-Buster - same thing.

# probepart
/dev/sda||0
/dev/sdb1|vfat|1308672
/dev/sdb2|ext4|61023232
/dev/sdc||0
/dev/sdd1|vfat|1308672
/dev/sdd2|ext4|59514880
/dev/sde||0
/dev/sdf||0
/dev/sdg1|vfat|1308672
/dev/sdg2|ext4|60129280
/dev/sdh1|vfat|1308672
/dev/sdh2|ext4|59514880
/dev/sdi1|vfat|1308672
/dev/sdi2|ext4|61210624
/dev/sdj1|vfat|1308672
/dev/sdj2|ext4|59514880
/dev/sdk|none|60825600
# 

Booted Quirky Xerus64-8.5.0
exact the same problem as Buster and Dunfell.

/sbin/probepart is the same in all releases of EasyOS, so will give the same result.

Looking at that script, starting at line 57, it screens out partitions sdk*, sdm* and sdr*.

Try this one. Has false ".gz", has to be at /sbin

You are brilliant Barry! Thank you very much.

# probepart
/dev/sda||0
/dev/sdb1|vfat|1308672
/dev/sdb2|ext4|61023232
/dev/sdc1|vfat|1308672
/dev/sdc2|ext4|59514880
/dev/sdd||0
/dev/sde||0
/dev/sdf||0
/dev/sdg1|vfat|1308672
/dev/sdg2|ext4|59514880
/dev/sdh1|vfat|1308672
/dev/sdh2|ext4|59514880
/dev/sdi1|vfat|1308672
/dev/sdi2|ext4|59514880
/dev/sdj1|vfat|1308672
/dev/sdj2|ext4|60129280
/dev/sdk1|vfat|1308672
/dev/sdk2|ext4|61210624
# 

Note that the EasyOS /sbin/probepart is the same in the legacy pups.

In woof-CE master branch, wdklmpx rewrote it in Jan. 19, 2017, so I presume that the current pups don't have that bug.

https://github.com/puppylinux-woof-CE/w ... /probepart

The legacy branch on woof-CE has the original probepart.

Anyway, the bug is fixed in EasyOS.