I connected a USB drive. exАat. Drive has a Media folder. If I connect as a Guest, I can’t delete or add files to the drive. I can’t connect as a registered user. I tried volume:volume, VolumeHIFI:volumio, root:root, root:volumio. It won’t let me in. Media folder is root-root 755. MacOS by Finder. smb://192.168.1.101/media/Media What I do wrong?
How about
| Attribute | Value |
|---|---|
| Username | volumio |
| Password | volumio |
The only combination you have not listed as attempted so far.
Kind Regards,
I make a mistake - not volume:volume but volumio:volumio - do not work. Sorry long day.
Judging by the lack of answers and solutions, no one uses a USB drive and has no idea how to add or delete files from it?
It’s hard to support since I can’t replicate your setup
I don’t have a Mac. But you mentioned you can do everything you need as a guest, so why insist on doing it as a registered user?
Hey @VictorDUA,
I tested this on my end with an exFAT USB thumb drive and can do whatever I want with it. My working theory is that your USB drive filesystem has a dirty flag set.
When an exFAT filesystem has a dirty flag - from improper unmount, power interruption, or disconnecting the drive unsafely - Linux kernel reports this at mount time with a message like:
exFAT-fs (sdXn): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
When this happens, the filesystem may be mounted with write restrictions to prevent further corruption. This would explain why you can browse via SMB but cannot add or delete files - the underlying filesystem is blocking write operations regardless of credentials.
To confirm this theory, I need to see your Volumio system log. The dirty flag warning will appear in the kernel messages when the USB drive is mounted.
Please provide a log link:
Kind Regards,
In the first post I wrote: “If I connect as a Guest, I can’t delete or add files to the drive.”
So no, I can’t.
I think I format HD with FAT and check it one more time. If I still can’t add or delete files, I’ll attach the log. Thanks.
Sorry my bad, missed the 't
Convert HDD to FAT and everything (with HDD) is fine … but with plugged HDD bluetooth RC stop working. No scan, no connect. Power supply 4A, pi4B with 3,5 LCD and 6631 transport.
Madhouse.
Is there a reasonable explanation why the Bluetooth RC (not RF and without a USB dongle) stops working when connecting a USB drive? Thank you.
Hey @VictorDUA,
There is, in the logs you have not shared. You know the drill.
If you wonder why there is a slow uptake, perhaps this post may shed some light:
Kind Regards,
Excuse me.
http://logs.volumio.org/volumio/OGT2NJU.html
compatible.txt (35 Bytes)
cpuinfo.txt (1.2 KB)
Add .txt to upload. Thanx.
Hey @VictorDUA,
Infamous JMicron JMS5xx
Yes, there is a reasonable explanation. This is a known USB 3.0 / Bluetooth interference problem on Raspberry Pi 4.
From your log I can see you have a JMicron JMS583 NVMe-to-USB bridge enclosure connected at USB 3.0 speed (5000M). USB 3.0 data transmission emits radio frequency noise in the 2.4GHz band - the same frequency used by Bluetooth. This RF interference blocks Bluetooth scanning and pairing.
This is not a Volumio bug - it is a hardware-level RF problem documented by Intel years ago and affects all devices with USB 3.0 ports near 2.4GHz radios.
Mitigation options:
USB extension cable - Use a 30-50cm USB 3.0 extension cable to move the NVMe enclosure away from the Pi. Distance reduces interference.
Ferrite clamps - Add clip-on ferrite cores to the USB cable as close to the Pi as possible. These suppress RF emissions.
Better shielded cable - Replace cheap USB cable with quality shielded one.
Aluminum foil shielding - Wrap the NVMe enclosure completely in aluminum foil (with non-conductive layer underneath to prevent shorts). Include the cable connector area.
Metal Pi case - Can help contain RF emissions.
USB 2.0 port - Moving the drive to a USB 2.0 port eliminates interference completely but significantly reduces transfer speed.
The USB extension cable is usually the easiest and most effective solution.
Kind Regards,
Thank you very much. I move HDD to USB 2.0 and try another USB HDD.
Connecting the hard drive to USB 2.0 solved the problem. Both the drive and the RC works. Thanx.
