shinobar wrote: Sat Sep 14, 2024 11:13 pm
rockedge wrote: Sat Sep 14, 2024 5:36 pm
Seems like the partition being formatted as NTFS is what is requiring the extra parameter(s) pupsfs=1E74E51174E4EC89 psave=1E74E51174E4EC89 being needed.
I guess this is the BookwormPup specific issue.
Fossapup64 has no problem, but the BookwormPup fails. Both on the same ntfs partition, sda2.
probepart shows:
/dev/sda1|ntfs|50M
/dev/sda2|ntfs|39.3G
/dev/sda3|ntfs|564M
/dev/sda4|ext4|10.0G
/dev/sdb1|vfat|1.2G
/dev/sdb2|ext3|6.0G
/dev/sr0|none|1023M
but the script init of the BookwormPup omits ntfs partitions.
HAVE_PART shows:
sda4|ext4
sdb1|vfat
sdb2|ext3
(grub.cfg entries)
menuentry 'Dpupbw64 10.0.7 (sda2/dpupbw64-10.0.7)' --class puppylinux{
search --no-floppy --set=root --fs-uuid FABC3FAEBC3F6473
linux /dpupbw64-10.0.7/vmlinuz psubdir=/dpupbw64-10.0.7 pmedia=atahd pfix=fsck
if [ -e /dpupbw64-10.0.7/ucode.cpio ]; then
initrd /dpupbw64-10.0.7/ucode.cpio /dpupbw64-10.0.7/initrd.gz
else
initrd /dpupbw64-10.0.7/initrd.gz
fi
}
menuentry 'Fossapup64 9.5 (sda2/fossapup649.5frugal)' --class puppylinux{
search --no-floppy --set=root --fs-uuid FABC3FAEBC3F6473
linux /fossapup649.5frugal/vmlinuz psubdir=/fossapup649.5frugal pmedia=atahd pfix=fsck
if [ -e /fossapup649.5frugal/ucode.cpio ]; then
initrd /fossapup649.5frugal/ucode.cpio /fossapup649.5frugal/initrd.gz
else
initrd /fossapup649.5frugal/initrd.gz
fi
}
@shinobar , @dimkr
It seems the failed init detection of ntfs partitions may be due to the kernel definition of filesystems in /proc/filesystems.
If I understand correctly, the modern init of BookwormPup64 defines builtin filesystem support (KFILESYSTEMS) as follows:
Code: Select all
KFILESYSTEMS="$(cat /proc/filesystems | grep -v "nodev" | grep -v "fuseblk" | sed -e "s#\t##g" | tr '\n' '|' | sed -e 's#|$##g')
which returns the following for my system which has vfat and ntfs partitions:
Code: Select all
KFILESYSTEMS="ext3|ext2|ext4|squashfs|vfat|msdos|exfat|iso9660|ntfs3|udf|xfs|f2fs|btrfs#"
NOTE: the above report specifies support for 'ntfs3' filesystems
---
On my system, probepart -hr returns the following:
/dev/sda1|vfat|260M
/dev/sda2|none|16M
/dev/sda3|ntfs|117.9G
/dev/sda4|ntfs|1000M
/dev/sdb1|vfat|28.6G
/dev/sdc1|vfat|28.9G
However, the init (HAVE_PARTS) searches specifically for filesystems defined by KFILESYSTEMS.
Consequently, on my system the search for 'ntfs3' fails and the 'ntfs' partitions are not detected:
sda1|vfat
sdb1|vfat
sdc1|vfat
Maybe the init (HAVE_PARTS) could be adjusted to correctly detect and define ntfs3 as ntfs.
