Possible Memory Issue? (v 2.729)

I was trying to add some music to my internal (SD) drive on my Pi Zero based Volumio streamer. When I drag the files to my, “internal” drive, I’m getting an error message that I don’t have enough memory for the additional music.

In reality, I have around 25gigs of music plus Volumio on a 64 gig SD card. I’m copying the files from my Mac via the Finder under Catalina.

Oddly enough, I also have a Pi 3B+ based streamer and I can copy the music to it’s internal SD card without any problems.

Is there any reason a Pi Zero might treat memory differently and generate this erroneous error?

Thanks!

Any thoughts?

I’m on the latest version, 2.799 and the problem persists. This only appears to be a problem on the PiZero.

Thanks

Not that anyone seems to really care, but FWIW, I can upload new music files to a RPi 3A and 3B+ internal drive (SD card) but, unfortunately continue to get an error message when I attempt to upload new MP3 files to my RPiZero based streamers.

I didn’t mention, too, that I’m using a Mac to do this via an smb connection to the finder.

I’m now up to V 2.806.

I won’t hold my breath for a response. : )

Could you share some logs?

Either from the /dev page using the livelog feature or via ssh.

# Volumio logs
journalctl -f -o cat

Note you might need sudo before these commands depending on the version of Volumio your running

Ideally you’d start things up, and then try and capture logs just before you try transferring your files. Without logs its blind guessing :slight_smile:

EDIT: I moved your post out of the MyVolumio category into the general Help one so it gets more eyeballs

ashthespy,

As requested. I tried to copy some additional music files and then ran journalctl as requested. Process wise, I ran the journalctl and then attempted to copy the new music files to the internal SD card. Attached is the requested log.

(BTW, thanks for the assistance. I really like volumio on the pi zero form factor but as you can see from my earlier post, the inability to add new files to the memory card is a deal breaker. As mentioned, this is working fine on my Pi 3A and B+ servers.)

Cheers

+++


Volumio Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent

permitted by applicable law.

volumio@volumio-allo:~$ sudo journalctl -f -o cat

Reached target Default.

Startup finished in 100ms.

Started User Manager for UID 1000.

lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory

lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory

info: [1598735140345] ControllerPandora::ExpireOldTracks::reaper

info: CorePlayQueue::getQueue

info: CorePlayQueue::getTrack 0

volumio : TTY=pts/0 ; PWD=/home/volumio ; USER=root ; COMMAND=/bin/journalctl -f -o cat

pam_unix(sudo:session): session opened for user root by volumio(uid=0)

[2020/08/29 21:06:51.126589, 0] ../lib/util/debug.c:603(reopen_logs_internal)

Unable to open new log file '/var/log/samba/log.smbd': No such file or directory

Starting Cleanup of Temporary Directories...

Started Cleanup of Temporary Directories.

[2020/08/29 21:09:51.306295, 0] ../lib/util/debug.c:603(reopen_logs_internal)

Unable to open new log file '/var/log/samba/log.smbd': No such file or directory

info: [1598735440350] ControllerPandora::ExpireOldTracks::reaper

info: CorePlayQueue::getQueue

info: CorePlayQueue::getTrack 0

info: CoreCommandRouter::volumioGetState

info: CorePlayQueue::getTrack 0

info: CoreCommandRouter::volumioGetState

info: CorePlayQueue::getTrack 0

info: CoreCommandRouter::executeOnPlugin: multiroom , getMultiroom

info: Listing playlists

info: CoreCommandRouter::volumioGetQueue

info: CoreStateMachine::getQueue

info: CorePlayQueue::getQueue

[2020/08/29 21:12:51.486295, 0] ../lib/util/debug.c:603(reopen_logs_internal)

Unable to open new log file '/var/log/samba/log.smbd': No such file or directory

verbose: ControllerMpd::sendMpdCommand status

info:

---------------------------- MPD announces state update: update

info: ControllerMpd::getState

verbose: ControllerMpd::sendMpdCommand status

verbose: ControllerMpd::parseState

info: Command Router : Notfying DB Updatetrue

info: CoreCommandRouter::Close All Modals sent

verbose: ControllerMpd::parseState

info: ControllerMpd::pushState

info: CoreCommandRouter::servicePushState

info: CoreStateMachine::pushState

info: CorePlayQueue::getTrack 0

info: CoreCommandRouter::volumioPushState

info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo

info: CorePlayQueue::getTrack 0

info: Received update from a service different from the one supposed to be playing music. Skipping notification.Current webradio Received mpd

info: ------------------------------ 554ms

verbose: ControllerMpd::sendMpdCommand status

info:

---------------------------- MPD announces state update: update

info: ControllerMpd::getState

verbose: ControllerMpd::sendMpdCommand status

verbose: ControllerMpd::parseState

info: Command Router : Notfying DB Updatefalse

info: CoreCommandRouter::Close All Modals sent

verbose: ControllerMpd::parseState

info: ControllerMpd::pushState

info: CoreCommandRouter::servicePushState

info: CoreStateMachine::pushState

info: CorePlayQueue::getTrack 0

info: CoreCommandRouter::volumioPushState

info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo

info: CorePlayQueue::getTrack 0

info: Received update from a service different from the one supposed to be playing music. Skipping notification.Current webradio Received mpd

info: ------------------------------ 339ms

verbose: ControllerMpd::sendMpdCommand status

info:

---------------------------- MPD announces state update: update

info: ControllerMpd::getState

verbose: ControllerMpd::sendMpdCommand status

verbose: ControllerMpd::parseState

info: Command Router : Notfying DB Updatetrue

info: CoreCommandRouter::Close All Modals sent

verbose: ControllerMpd::parseState

info: ControllerMpd::pushState

info: CoreCommandRouter::servicePushState

info: CoreStateMachine::pushState

info: CorePlayQueue::getTrack 0

info: CoreCommandRouter::volumioPushState

info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo

info: CorePlayQueue::getTrack 0

info: Received update from a service different from the one supposed to be playing music. Skipping notification.Current webradio Received mpd

info: ------------------------------ 676ms

verbose: ControllerMpd::sendMpdCommand status

info:

---------------------------- MPD announces state update: update

info: ControllerMpd::getState

verbose: ControllerMpd::sendMpdCommand status

verbose: ControllerMpd::parseState

info: Command Router : Notfying DB Updatetrue

info: CoreCommandRouter::Close All Modals sent

verbose: ControllerMpd::parseState

info: ControllerMpd::pushState

info: CoreCommandRouter::servicePushState

info: CoreStateMachine::pushState

info: CorePlayQueue::getTrack 0

info: CoreCommandRouter::volumioPushState

info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo

info: CorePlayQueue::getTrack 0

info: Received update from a service different from the one supposed to be playing music. Skipping notification.Current webradio Received mpd

info: ------------------------------ 542ms

verbose: ControllerMpd::sendMpdCommand status

info:

---------------------------- MPD announces state update: update

info: ControllerMpd::getState

verbose: ControllerMpd::sendMpdCommand status

verbose: ControllerMpd::parseState

info: Command Router : Notfying DB Updatetrue

info: CoreCommandRouter::Close All Modals sent

verbose: ControllerMpd::parseState

info: ControllerMpd::pushState

info: CoreCommandRouter::servicePushState

info: CoreStateMachine::pushState

info: CorePlayQueue::getTrack 0

info: CoreCommandRouter::volumioPushState

info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo

info: CorePlayQueue::getTrack 0

info: Received update from a service different from the one supposed to be playing music. Skipping notification.Current webradio Received mpd

info: ------------------------------ 283ms

verbose: ControllerMpd::sendMpdCommand status

info:

---------------------------- MPD announces state update: update

info: ControllerMpd::getState

verbose: ControllerMpd::sendMpdCommand status

verbose: ControllerMpd::parseState

info: Command Router : Notfying DB Updatefalse

info: CoreCommandRouter::Close All Modals sent

verbose: ControllerMpd::parseState

info: ControllerMpd::pushState

info: CoreCommandRouter::servicePushState

info: CoreStateMachine::pushState

info: CorePlayQueue::getTrack 0

info: CoreCommandRouter::volumioPushState

info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo

info: CorePlayQueue::getTrack 0

info: Received update from a service different from the one supposed to be playing music. Skipping notification.Current webradio Received mpd

info: ------------------------------ 183ms

info: [1598735740354] ControllerPandora::ExpireOldTracks::reaper

info: CorePlayQueue::getQueue

info: CorePlayQueue::getTrack 0

[2020/08/29 21:15:51.528020, 0] ../lib/util/debug.c:603(reopen_logs_internal)

Unable to open new log file '/var/log/samba/log.smbd': No such file or directory

@TheWalkman Just to confirm a few things…
– you didn’t have any music playing while doing this correct?
– Also do you recall the exact error message that pops up? Is it a “out of space” error on the computer when you try and copy said files?
– Or was it an out of memory error on the pi while scanning/updating the database?

No music was playing: I was trying to upload additional files to the, “internal drive”. I mounted the, “internal drive” via smb and simply attempted to drag the new mp3 files to it via the Finder on my Mac.

See attached screen shot for the error message.

IMG_5961

As mentioned earlier, I’m storing approxiamately 250+ CDs on the internal SD card (64GB) with approximately 30 gigs available.

I have several different Pi Zero based servers with 64 gig cards and they all show the same problem when adding new music.

I also have a Pi 3A and 3B+ Volumio servers also configured with 64gb sd cards and this works perfectly. For some reason, I only seem to get this error message on the Pi Zero based servers.