Problem Moving from External HDD to SSD

Hi …
I’ve been using my PI 4 for a couple or month now, simply listening to my music stored on a 2Tb external USB HDD, directly connected to one of the pi4 USB ports, no problem.
I listen with a headphone pluged in the iqaudio hat installed.
Volumio (2.917) software IS stored on the micro SD,
Only flac files on the HDD.
Now I’ve got a brand new Samsung T5 SSD, fat32 formatted, and copied all my music on it with my PC.
This new T5 is cable wired on one of the pi4 usb3 terminal.
For some reason I don’t understand, the T5 is not detected or recognised automatically on the USB !
IS there anything special to do be able to access a SSD?
I’ve gone through the complete resetting of volumio, still stuck there.

Thanks a lot for your help
JM, almost desperate.

Hi again

I guess I’m not very much talented in debian, linux etc, but I’m a bit disappointed by that kind if issue.
I’ve read here and there plenty of good things about SSD and Pi … and ok … I guess this is an already documented issue.
I juste did some more going back and forth from HDD to SSD.
HDD is automatically detected and scanned, but absolutely nothing for my Samsung T5 2 tb.
I’ll stay with the hdd and wait for an update …

What kind of partition table does both drives use? It could be the difference between MSDOS and GPT partitioning. Or the the SSD is using hardware 4K blocks while the fat32 driver is expecting 512B blocks. I see that this model is USB powered maybe it asks too much power and would a using a USB hub the solution.


My 2Tb HD (working fine) was Fat32 formatted on a PC.
This new SSD was originally exfat formatted in its box. As I’ve tried it like this on the pi4 with some music files and could not access them, I performed a fat32 using the guiformat tool on my PC.
I don’t think power is the issue as this SSD is supposedly using much less than the HD, and recommended for standalone use.
I’ve read here and there users writing good things about this Samsung T5 unit, I’d be glad to know how they’re using/format it !


Ok, maybe I should partition this SSD using gpart under debian?
But, will the SSD be accessed without issue on a Windows PC whilst updating my music files ?


1 Like

that is a misconception and not always true, please google to get more info on the subject.

The ssd will eventually be shared with samba (unless you are wanting to remove it & physically connect it to your PC to transfer files), and so it shouldn’t matter how it is formatted as long as your RPi is able to read it. Windows will just see a network share and won’t be bothered what the underlying filesystem is.

Hi again
And thank you for your help.
I found lots of posts on my concern with google’s help.
For various reasons, what matters most for Me is just to be able to read audio files on my pi 4 and volumio, no need to be able to write with the pi.
And then, What I need is to be able to read/write on any Windows PC.
From what I understand, NTFS format should be fine and simple enough for me.


There are two scenarios here, and it is not clear to me, which you are trying to follow.

  1. Your ssd stays attached to the RPi, and you do file transfers to it over the network (via Samba) from your Windows PC.

  2. You remove your ssd from the RPi when you want to do file transfers, attach it to your Windows PC for the transfers, and then reattach to the RPi.

For case 1, the filesystem is irrelevant as long as the RPi can read it (fat32, ntfs or ext4 will all be fine).

For case 2, the ssd must be readable by Windows, so ntfs or fat32.

Formatting as FAT32 should actuallly be ok.
It may be helpful if you could produce a log, perhaps there is another reason why this unit is being skipped.

Howto produce a log
Ideally after a fresh reboot.

Ok, case 2 is what I need.

I don’t want to go into 1


No way, I can’t read my fat32 SSD on the pi/volumio.
I’ll try to get a log, thank you.


Here is what I get After disconnecting the HD (everything working fine) and reboot on the SSD:

Info: ___________ PLUGINS: Run onVolumioReboot Tasks ___________
info: PLUGIN onReboot : networkfs
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl reboot
info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats
pam_unix(sudo:session): session opened for user root by (uid=0)
Started Turns off Raspberry Pi display backlight on shutdown/reboot.
Started Synchronise Hardware Clock to System Clock.
Stopping Bluetooth.
Stopped target Bluetooth.
Stopping system-ifup.slice.
Removed slice system-ifup.slice.
Stopping system-systemd\x2dfsck.slice.
Removed slice system-systemd\x2dfsck.slice.
Stopping dhcpd.service...
Stopping Host and Network Name Lookups.
Stopped target Host and Network Name Lookups.
Stopping dnsmasq.service...
Stopping Authenticate and Authorize Users to Run Privileged Tasks...
Stopping Disk Manager (legacy version)...
Stopping Bluetooth service...
Stopping Graphical Interface.
Stopped target Graphical Interface.
Stopping Entropy daemon using the HAVEGE algorithm...
Stopping Multi-User System.
Stopped target Multi-User System.
Stopping mount disks automatically with standby...
Stopping volumio-remote-updater.service...
Stopping Volumio Streaming Daemon...
Stopping Volumio Log Rotation Service...
Stopping Login Prompts.
Stopped target Login Prompts.
Stopping Getty on tty1...
Stopping Login Service...
Stopping LSB: start Winbind daemon...
Stopping LSB: triggerhappy hotkey daemon...
Stopping LSB: start Samba SMB/CIFS daemon (smbd)...
Stopping LSB: start Samba daemons for the AD DC...
Stopping LSB: Start NTP daemon...
Stopping LSB: Brings up/down network automatically...
Stopping LSB: Advanced IEEE 802.11 management daemon...
Stopping LSB: set CPUFreq kernel parameters...
Stopping Avahi mDNS/DNS-SD Stack...
Stopping Music Player Daemon...
Stopping D-Bus System Message Bus...
Starting Store Sound Card State...
exiting on receipt of SIGTERM
Stopping SDP server
Disconnected from D-Bus, exiting.
Got SIGTERM, quitting.
Leaving mDNS multicast group on interface wlan0.IPv4 with address
avahi-daemon 0.6.31 exiting.
[2021/10/13 14:59:02.314065,  0] ../lib/util/pidfile.c:153(pidfile_unlink)
Failed to delete pidfile /var/run/samba/ Error was No such file or directory
haveged.service: main process exited, code=exited, status=143/n/a
haveged: Stopping due to signal 15
haveged starting up
Stopped Entropy daemon using the HAVEGE algorithm.
Unit haveged.service entered failed state.
Stopped mount disks automatically with standby.
Stopped volumio-remote-updater.service.
Stopped Volumio Log Rotation Service.
Stopped Login Service.
Stopped Avahi mDNS/DNS-SD Stack.
Stopped D-Bus System Message Bus.
ntpd exiting on signal 15
Stopping NTP server: ntpd.
info: mDNS Browse raised the following error Error: dns service error: unknown
Stopped Getty on tty1.
Stopped Disk Manager (legacy version).
Stopped Bluetooth service.
Stopped Authenticate and Authorize Users to Run Privileged Tasks.
Discovery: ERRORError: dns service error: unknown
info: mDNS Advertisement raised the following error Error: dns service error: unknown
Stopped Volumio Streaming Daemon.
Stopped dnsmasq.service.
Stopped dhcpd.service.
Stopped Music Player Daemon.
Stopped LSB: triggerhappy hotkey daemon.
Stopped LSB: Start NTP daemon.
Stopped LSB: Advanced IEEE 802.11 management daemon.
Stopped LSB: set CPUFreq kernel parameters.
Network Interface Plugging Daemon...stop eth0...done.
Stopped LSB: Brings up/down network automatically.
Started Store Sound Card State.

Please post the URL to the complete log here. This process is described in the link given by gkkpch in post #10.

OK, this log is very long, the moving from HDD TO SSD is at the very end

Thans for your patience, I’m not familiar with this procedure !!


Why do I get the feeling that you plugged in the Samsung T5 approx. 40 secs after you sent the log :roll_eyes:
Could you boot without the hdd connected, let it run for 10 minutes, then reboot with the T5 connected.
Or insert after boot, but do not send a log before the T5 is connected.

Ok… Thanks … I told you, I’m not familiar …

That’s ok, we’re here to help