Node 2i randomly reboots with NAS shared folder
Beantwortet
Ever since the October update my Node 2i, which worked flawlessly for 3 years, started rebooting randomly while playing music from a network share, more precisely from a Qnap NAS. Support said it was an issue with my network, nas, dhcp and what not... that sounded like bullshit but yet I tried to reset the network, backup my music, factory restore the NAS and reconfigure everything. Nothing changed. Then support said it was a known bug that affected connections via ethernet, I tried to plug an access point to my eth port and let the Node work in wifi with the same result. Thinking that maybe the problem was partially NAS related (the main problem was of course the firmware update) I tried to share the music collection via my Windows11 PC, and yes, it worked like a charm. Then a new firmware update was available, so thinking that this finally solved the issue I switched back to NAS, and "surprise", the node started rebooting again. The last test was 2 days ago when I borrowed a brand new Synology NAS only to find that the problem remains. So now I'm still sharing via my PC, but that's a suboptimal solution for a series of reasons and I wish that Bluesound was finally able to allow me to use their player as it was meant to, and like it did for 3 years straight. Is that too much to ask??
-
Offizieller Kommentar
Hi Enrico,
We have identified the issue you are experiencing and like what my colleague suggested, please make sure that your NODE 2i is connected to a wireless connection. When you do, please make sure that the ethernet cable is unplugged to the port of the NODE 2i. -
Hi Mark, it doesn't work with wifi either, plus it works with windows shares, so it seems to me that it's more related to smb protocol than ethernet connection, but of course I could be wrong. The only fact so far is that such issued was identified 2 months ago and it is still not fixed in the latest update. Any change your team is giving us a solution with the nex one?
0 -
I'm guessing that your NAS music library has more tracks than what your Windows computer have. Please continue working with our support crew with your support request.
0 -
I'm afraid you're guessing wrong, my PC has the same music library that's in my nas (in fact, I copy-pasted it) and it's not even that large at around 4800 tracks.
I long gave up with your support crew, every time a request is made I get the standard reply which doesn't address the problem,nor offers any real solution. The log file is also useless since the player doesn't cast any error prior to rebooting, the only useful piece of info is that it appears to search for a firmware update via the usb port on startup, which is what I asked since the very beginning. Can I have the previous, stable, working firmware? And the answer is always NO. For "security reasons" Bluesound won't provide older firmwares but will happily leave me with a buggy one, go figure!
In fact, rather than from the support crew, I was hoping to hear from the members of the community with my same problem, maybe some of them found a solution
0 -
Other Node 2i user here, not having your issue. Things I would try in your case.
If not done already, configure DHCP reservations for both the Node and NAS, so they always get assigned a predetermined IP in the LAN. After configuration make sure / verify these IPs get assigned to the Node and NAS.
Activate SMB v1 on the NAS, note this is an insecure protocol!!! I have my library connected directly to my router, but it can only be accessed with v1 activated. Seen similar reports by other users. If this enables access, get back in touch with Bluesound for further analysis, you do not wish to enable v1 permanently on a NAS.
Verify if there are no "ghost" shares under Settings - Diagnostics - Connected Shares. It should only list shares defined in Settings - Music library - Network shares and should not list any share twice. Only way I know to get rid of a ghost share is factory reset of the Node.
0 -
Hey Gerben, thanks for your insight. Everything you propose was already done, including factory reset the node2i,.Interestingly support said that they use smb v3 for security reasons (I thus disabled v1 and v2 with no differrence at all) but your experience says otherwise... who knows?
Anyway, I didn't try wifi connection since the latest update, so I borrowed a brand new Aruba Instant On AP (instad of the cheapo I used with the previous firmware update) and this works, I could play a 40-something hour long playlist with no issues.
That's still a suboptimal solution (app is more laggy even though player and ap are 2 feet apart) but at least I don't need a pc running.So I can confirm with the current firmware:
ethernet to nas -> reboots randomly
ethernet to windows share -> works
wifi to nas -> works
cheapo wifi to nas -> may reboot (totally rebooted with previous firmware)Now it would be interesting to know if this ethernet issue affects also the new Nano or it's just node2i related
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
6 Kommentare