Posted: Sat Apr 16, 2022 21:03 Post subject: Samba and Sonos crash on r43171 on Linksys WRT3200ACM
Hi everyone! I have a Linksys WRT3200ACM running r43171. I was running a newer build, but when researching my issues with Samba, found several posts pointing to build r43171 as being "THE" build with stable Samba. I've been running it maybe a month now and the Samba does not seem stable. Most times if I log into the router and click on "Apply Settings", Samba is back up and running. This also seems to fix issues when not connecting to my Sonos wireless speakers. I could go into the specifics of my issues, post the logs and whatever, but really I just want to know what is the most stable build for my hardware. I don't think its my config because it works until it doesn't and then a reboot fixes it and then it works again....
Posted: Sun Apr 17, 2022 0:13 Post subject: logs from event last night
Last night I had issues accessing the Samba share so rebooting it fixed it. But I noticed later today an alert for a logging rate increase. Papertrail shows normally ~600 events in 12 minutes, but jumped up to 1.2M last night. Here is what kicked it off:
r43171 may have been a build to use May 2020 certainly not the case today or from any perspective.
Unfortunately, nobody can help to solve deprecated builds with security problems etc. r48607r48646
If concerned about bleeding edge builds and want to avoid a recent ksmbd changeset choose r48567.
Flash a build, allow reboot, then reset: GUI factory defaults, reset button 10 seconds or nvram erase.
I have no problem updating to a newer build. My main desire is that the build have stable Samba. When I was searching the forums, it sounded like there were issues with Samba in the later builds. I didn't see newer posts saying the Samba issue was finally resolved. Does r48567 have stable Samba?
OK, updated to r48567 as you suggested. Having strange issues with the mounting of drives in this build. I have a USB HD attached that has 3 partitions. I have volume labels for SDA1->3 as Share, BAD, and Video (I have a section of the disk with bad sectors that I located and partitioned off so I don't use it). For some reason, this build mounted the SDA2 as Video partition and mounted the video partition as SDA3. So I pulled the drive, deleted the file system of the bad partition and remounted. Now its showing SDA2 mounted to Video and SDA3 also mounted to Video. It shows both SDA 2 and SDA3 as the size of SDA3. Strange stuff. But at least when I mount the Video Samba share it does load up the correct drive. I'll see how stable it is.