06-19-2024, 12:34 PM
(This post was last modified: 06-19-2024, 12:36 PM by Tim Curtis.
Edit Reason: eta power save
)
(06-19-2024, 10:55 AM)the_bertrum Wrote:(06-19-2024, 10:33 AM)Iacov Wrote:(06-18-2024, 07:24 AM)the_bertrum Wrote: 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