Bug#795500: dosfstools: mkfs.vfat -F32 don't work correctly

[Plançon]

Hi Andreas, Thank for your reply and your attention. I made a mystake in my first mail, It lacks the main command : $mkfs.vfat -F32 /dev/mapper/loop0p1 And the command sequence is $dd if=/dev/zero of=OSMC_TGT.img bs=1M count=256 256+0 enregistrements lus 256+0 enregistrements écrits 268435456 octets (268 MB) copiés, 1,05195 s, 255 MB/s $parted -s OSMC_TGT.img mklabel msdos $parted -s OSMC_TGT.img mkpart primary fat32 1M 256M $kpartx -a OSMC_TGT.img $mkfs.vfat -F32 /dev/mapper/loop0p1 mkfs.fat 3.0.27 (2014-11-12) unable to get drive geometry, using default 255/63 $mount /dev/mapper/loop0p1 /mnt $touch /mnt/file.txt $umount /mntI'm sending you more information on my problem today. And can you say if I must work with a specific version kernel ? $sync $kpartx -d OSMC_TGT.img loop deleted : /dev/loop0 My problem is that I can not mount the special device and I can't write on. I'm sending you more information on my problem today. And can you say if I must work with a specific version kernel ?. Best regard Phil On 15/08/2015 13:23, Andreas Bombe wrote: On Fri, Aug 14, 2015 at 08:17:39PM +0200, aimless wrote: I can't create a FAT32 partition with this command dosfstools: mkfs.vfat -F32. For example, you can try this : $dd if=/dev/zero of=OSMC_TGT.img bs=1M count=256 256+0 enregistrements lus 256+0 enregistrements écrits 268435456 octets (268 MB) copiés, 1,05195 s, 255 MB/s $parted -s OSMC_TGT.img mklabel msdos $parted -s OSMC_TGT.img mkpart primary fat32 1M 256M $kpartx -a OSMC_TGT.img mkfs.fat 3.0.27 (2014-11-12) unable to get drive geometry, using default 255/63 $mount /dev/mapper/loop0p1 /mnt $touch /mnt/file.txt $umount /mnt $sync $kpartx -d OSMC_TGT.img loop deleted : /dev/loop0 I tried this, and it works. Just like it appears to work for you. What is the problem here exactly? Before, I don't have this message : unable to get drive geometry, using default 255/63 Can you help me please ? With suppressing an informational message? Your bug report doesn't point to anything actually a bug, as far as I can see. Please explain better, otherwise I can only close this bug report.