Every time I reboot or shutdown and start the RPI my library is empty. I have around 100GB of FLAC files on an external USB SSD drive. After this, even trying to manually rebuild the library doesn't do anything. I have to manually unplug the drive and plug it back in, this operation starting the automatic update, which works.
Please help!
What version are you using?
The latest one, it'a a clean install I did less than a week ago.
That's probably not the latest version. Please check the version under "About". It should be 2020xxxx
It says "Up to date", version 20200805.
Yes, but it's not the latest version ;-) It's just the latest marked as "stable". Go to the update screen, set automatic updates to "Quick" and you should see an update (this has also been improved in the new version). First try this version as some improvements - also when mounting USB devices - have been implemented in the latest version. If this still doesn't work, we need to debug this further.
Updating as we speak! Thanks!
After shutting down and restarting the library was there, but MPD was stopped and all the covers were missing (covers are local, download is disabled). I enabled MPD, clicked the update button which ran for a second, cleared my library and basically had the same behavior as before.
Ok, please reboot first, then run the commands
lsblk
mount
and post the output
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 238.5G 0 disk
`-sda1 8:1 0 238.5G 0 part /mnt/a33d580b-01
mmcblk0 179:0 0 29.8G 0 disk
|-mmcblk0p1 179:1 0 32M 0 part /boot
|-mmcblk0p2 179:2 0 1.4G 0 part
|-mmcblk0p3 179:3 0 1.4G 0 part /
`-mmcblk0p4 179:4 0 26.9G 0 part /data
# mount
/dev/mmcblk0p3 on / type ext4 (rw,noatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=330128k,nr_inodes=82532,mode=755)
sysfs on /sys type sysfs (rw,relatime)
proc on /proc type proc (rw,relatime)
tmpfs on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=666)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,relatime)
/dev/mmcblk0p1 on /boot type vfat (ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,quiet,errors=remount-ro)
/dev/sda1 on /mnt/a33d580b-01 type ntfs (ro,relatime,uid=0,gid=0,fmask=0177,dmask=077,nls=utf8,errors=continue,mft_zone_multiplier=1)
overlay on /data/library/music/a33d580b-01 type overlay (rw,relatime,lowerdir=/mnt/a33d580b-01,upperdir=/data/library/overlaydir,workdir=/data/library/workdir)
/dev/mmcblk0p4 on /data type f2fs (rw,relatime,lazytime,background_gc=on,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,fsync_mode=posix)
Hmm, this all looks fine. But you don't see any music? Let's see if the Beocreate software might not load correctly. Try restarting the web UI:
systemctl restart beocreate2
Didn't do anything. The only way of getting the library back is removing the drive and reinserting it.
I think the library shouldn't change or update automatically. This should be done only manually and the OS should always remember it's last version. This way there are no interactions with it except for the cases the user wants to.
I don't agree with this. Manually updating something should be an exception. It doesn't make sense to display a library that's not correct. Why should the system display music that isn't there? That doesn't make sense. You would try to start something and nothing would happen - that's not good at all.
However, if you help us debugging this, we might find what's causing this and fix it. Therefore, DO NOT remove and insert the drive after boot as we won't be able to find out what's wrong.
Now, let's check if the music is really there. Let's do an
ls /mnt/a33d580b-01
ls /data/library/music/a33d580b-01
OK! I had the library before rebooting. After reboot, the library was shown for a minute or so, but without the covers and after that it disappeared.
The music is there, /mnt/a33d580b-01 contains all the folders and files. The other folder is instead empty.
Ok, this shows that there is a problem with the overlay mount. As the files are not there, the system can't show any covers and the library will be cleaned. We'll try to reproduce this here.
Regarding my proposal... if you scan the library on each start, what would happen if it would be 10TB on a mechanical drive? It would take a lot of time to rescan it just to be updated automatically. It takes a few minutes even to scan my 100GB SSD library. And this with artist/album cover download disabled.
If you'd just store it, the user knows when something updates and would update the library too. If a file would be missing you could just show an error that the file isn't there anymore.
I think updating the library automatically affects every user on each boot. A file missing would affect just a few users and only occasionally.
We use it here with huge libraries without any problems. Re-scanning a library for changes isn't a resource-intense job. It doesn't matter if this is an SSD or an "mechanical drive". Let's just agree to disagree.
BTW: Your problem has nothing to do with the re-scan of the library - it is caused by the fact that the library isn't correctly mounted. Even without a re-scan you would not be able to play any music.
All I'm saying is that as an end user I don't mind having to manually update it. If you can fix it and maintain the automatically updating, of course it's better. I just hope you find a way to fix it, because I like your software very much.
Keep up the good work, I'm available if you need any other help from my side!
I encounter the same problem as Alex. Need to replug my USB drive after every restart. Using the latest version 20200901.
I also have the same opinion as Alex about the update of the library. Every restart takes a lot of time for what....How often do you update your library? When you add or remove files, as a user you know when...then you can update the library manually. At least provide both options so the user can choose what he prefers.
With the new update the problem with the long ''artists list' gets even worse on a smartphone, now you only show 1 artists iso 2 on each "line"
Some points of improvement.
- Alphabet searchbar in artists and album screen.
- Displaying playing time/ total time of a song
- How you stop a playing song?
- In the maximise screen of the playing song, it would be nice if you can go back to the album screen by clicking on the album icon.