9.0.2/Pi3b+: freeze when scanning library for the first time

[the_bertrum]

What breed of NAS do you use?  I have a similar freeze on a Pi3A+ with 9.x moode.  8.x was fine, my Pi4B+ is fine.  I've bee doing a deal of investigations (need to write up some more on the thread I have about it), but I'm not coming to suspect that it's the SMB share from my Synology NAS that's the cause.  If you are on SMB from a Synology too it would be another data point in support of my hypothesis.

yes, dsm7 and smb

thank you @TheOldPresbyope for testing! ram was unlikely in regard that the device did not have a forced reboot or something similar that would happen on a ram overflow

could it be that I use the same  read only smb user on both my moode devices? normally this should be no problem for smb, right?

that synology/the nas could play a part can't be out ruled... yet, if you hear hoofs clacking, don't think it's zebras... the most likely cause for my issue is still my very own library/tags/files

but I don't understand why, with the same files, there is a different behavior between moode 8 and 9

So I'm seeing the same with SMB on DSM 7.  Worked fine in 8.x, works fine on a Pi4, but no dice on a Pi3 9.x.  There's SOMETHING here, just can't figure out what...

[TheOldPresbyope]

@Iacov 

I have no new information to add but had to respond anyway because

yet, if you hear hoofs clacking, don't think it's zebras.

That's the best line I've read in a long time

Long ago, when SMB support was still young in moOde, lots of new users were reporting trouble adding their NAS. So many were using Synology products that I finally spent time installing an old copy of DSM 6.1 as a virtual OS in VirtualBox on my Linux laptop (don't ask...). I never saw any substantive differences between accessing shares on it and on my OMV NAS as far as moOde was concerned.

I can't bump the copy of DSM I have to 7.x (again, don't ask...) so I have no way to test your conjecture that it is implicated.

Have you tried Tim's suggestion of setting up NFS service on the NAS?


Regards,
Kent

[Tim Curtis]

What breed of NAS do you use?  I have a similar freeze on a Pi3A+ with 9.x moode.  8.x was fine, my Pi4B+ is fine.  I've bee doing a deal of investigations (need to write up some more on the thread I have about it), but I'm not coming to suspect that it's the SMB share from my Synology NAS that's the cause.  If you are on SMB from a Synology too it would be another data point in support of my hypothesis.

yes, dsm7 and smb

thank you @TheOldPresbyope for testing! ram was unlikely in regard that the device did not have a forced reboot or something similar that would happen on a ram overflow

could it be that I use the same  read only smb user on both my moode devices? normally this should be no problem for smb, right?

that synology/the nas could play a part can't be out ruled... yet, if you hear hoofs clacking, don't think it's zebras... the most likely cause for my issue is still my very own library/tags/files

but I don't understand why, with the same files, there is a different behavior between moode 8 and 9

So I'm seeing the same with SMB on DSM 7.  Worked fine in 8.x, works fine on a Pi4, but no dice on a Pi3 9.x.  There's SOMETHING here, just can't figure out what...

I've lost track but did you try pinging the seemingly frozen Pi from another host? If it can't be reached by ping it would suggest a failure in the network stack in Bookworm on the 3A+. This would be kind of unusual but certainly possible.

I don't have much experience with Bookworm's NetworkManager but it does have a "monitor" feature. I think it only logs something when the state of a connection changes.

Code:

nmcli monitor

ETA: Also just to be sure that adapter power save is off

Code:

pi@moode9:~ $ iw wlan0 get power_save
Power save: off

[Iacov]

@Iacov 

yet, if you hear hoofs clacking, don't think it's zebras.

That's the best line I've read in a long time

that's an age old Dr house quote. I have never watched the series but saw one episode once where he said that... and the logic burned itself into my brain to this day xD (I heard the quote in German back then so I'm not sure if I translated it on point)

unfortunately no, I did not try NFS :/
I will try when I have more time again, though 

pinging... I think it was still pingable as I think to remember that my uptime Kuma only reported moode being down when I turned the power off. 
the device was completely frozen though, at least the touchscreen (it was enabled the first few tries) was as unresponsive as SSH or the web GUI via ip

@the_bertrum a Pi4 works via smb on dsm7?
maybe its a difference in hardware? does the pi3b+ maybe handle mp3 and flac differently than the Pi4? does it handle embedded images differently?

I think it definately has to do. something with my files... because I have two different "sources" that I add (both in the same nas)... one share for my music and one share for my children's audio books. I have two moode devices, both sport the same hardware. the children's device only reads the audio book share, whilst the "main" moode device reads both shares... and mpd only froze during scans of the music share

maybe that's why it's tough to nail down... a combination of specific hardware, OS and music files (and maybe protocol)

once I have time again I will test if it was the defective SD card.
- when I reinstall moode, enable the Touchscreen and can finish the media scan, it would be a soft evidence towards that 
- if it fails again it might have not been a faulty sd
- if I disable the touchscreen and it finishes it could hint towards... I don't know
- if that fails too, I'll test nfs