I set up a new Raspberry PI 5, with the headless operating system. I attached a FAT32 thumb drive, mounted it with FSTAB and shared it on my home network with SAMBA. I copied some music files from another networked raspberry to the shared thumb drive. The files copied, but some of them were copied with shortened, gibberish file names. The files worked, only the names were changed. I’ve read that FAT32 drives can sometimes be a problem connected to a raspberry, so I reformatted the thumb drive to EXT4, remounted and shared. Now file transfers worked with the correct file names. But I’m curious as to why it didn’t work correctly with FAT32. I have another raspberry which runs LMS/Picore. This is a music server based on a headless version of the raspberry operating system. It is controlled from a web page on a local url. The LMS/Picore setup includes SAMBA shares so you can easily add music to a drive connected to that raspberry. My drive on the music raspberry is also FAT32 and there is no problem with the same music files which had the strange names on the new raspberry setup.
It appears that something is different between the two raspberries in the mounting or sharing, but I can’t figure out what it is. Perhaps the LMS/Picore has it’s own version of SAMBA or has installed some additional files which work with SAMBA. (Note: I haven’t found where the samba configuration is on the LMS/Picore setup. It’s not the same file structure as on a regular raspberry os. The FSTAB seems to be the same)
Any thoughts? Thanks.
It appears that something is different between the two raspberries in the mounting or sharing, but I can’t figure out what it is. Perhaps the LMS/Picore has it’s own version of SAMBA or has installed some additional files which work with SAMBA. (Note: I haven’t found where the samba configuration is on the LMS/Picore setup. It’s not the same file structure as on a regular raspberry os. The FSTAB seems to be the same)
Any thoughts? Thanks.
Statistics: Posted by dmozell — Sun Mar 30, 2025 2:27 pm