Vault 2i freezes.
Answered
Since the recent 4.0.2 update Vault 2i keeps freezing unexpectedly, on playback and when ripping CD's. Worked fine with no problems before the update.
-
I'd say yes it is safe, but I never lost my artwork and have been using the Vault all through last week without problems although 2 days ago it had a little tantrum.
2 -
Hi @Max
Yes - but is it really a good idea to leave your backup always plugged in and next to your VAULT? Perhaps a safe place like a fireproof box with other valuables.
2 -
central srutinizer
I tried reformatting and it didn't work. Don't think I tried it twice.
I went for the easy option and plugged the hard drive into a laptop and simply copied the Library, 35,000 items, took 18 hours but worked perfectly.
These days almost all the new music comes from download so easy enough to copy it to both the Library and the back up if the other ways don't work.2 -
Yes and your not the only one, Loads of us have the same issues.
1 -
I don't use a usb drive on mine, just done my node again but no luck. Vault still falls over when streaming to the node 😡
1 -
Also running BluOS 4.0.2, ... I *don't* use a USB drive in my Vault 2i. I am still having the same problems trying to play music stored on my Vault 2i. Problems occur when trying to play music from my library on Vault 2i, Pulse 2i, and PowerNode 2i. Â
1 -
I do NOT have any USB drives plugged into my VAULT2 but I STILL HAVE the issues since the firmwave update.  I have never used the USB port on the back of my VAult.
1 -
Yes, I have also rebuilt the index twice after shutting down, unplugging, and letting it sit without juice for five mins or so. Twice. Still having the issue.
1 -
Just adding that I don't have any USB or other drives attached to my Vault and I still have issues of freezing while ripping CDs. I haven't played much music from it as I'm trying to finish ripping my library right now, but having to reboot the Vault so much is making that take quite a long time.
1 -
Makes me wonder if this was ever tested on the vault, amount of issues with v4 is a joke
1 -
My "fix" has now been working for nearly 36 hours so it seems to have stuck, but I had a call today from the retailer I bought my Vault through.
He'd been out when I rang at the weekend.
He told me they sell very few Vaults, possibly not even 1% the number of Nodes.
My suspicion is that all the development and testing was done on the Node and so they have been taken unawares by our problems.
Not perfect but understandable.I just hope they can work it out and release a new version within a few days or the outcry to make version 3 available again will be deafening.
Out of interest, did anyone find the old OS in need of an update?
As I hardly ever stream and when I do it is mainly talk radio shows I might be a bit of an out-layer here.1 -
Dave - your "fix" was just a full index rebuild, right? This didn't appear to work for me...Â
Peter
1 -
I concur with all of Ian’s statements. V4 was touted as being the Framework core for further features, so as a base has to be rock solid as a foundation. Seems better to engage in a tactical return to base and nail it next outing, instead of triage in full view of users and prospective purchasers
1 -
The first things to do are to find out what went wrong, why it went wrong and then work out how to remedy it. Those things alone are substantial tasks if they're to be performed effectively.
Absolutely but as you stated - these are substantial tasks.
My suspicion is that the development was done on the Node, not the Vault which is a pretty niche product.
Given the current marketplace and streaming ease, I can understand how people can come to that conclusion. In fact, the opposite. We take great pride in the VAULT and are also frustrated by the situation. It is currently our highest priority to get it running again for everyone. We are as confused why some remedies are working for some and not others.
1 -
Just an update, my vault 2i and node have been playing all day, usb hdd plugged into the vault and streaming to the node. Queued 10 double albums then went to work. When I good home this evening it was just on the last track.
At least now the wife can play her music without nagging me now 🤣🤣1 -
Would be interested to know if you ever used the sleep command timer in the menu system. I actually suspect that the memory allocation for this function is not cleared, even though it shows nothing in the menu. My Vault can't drag n drop successfully unless playback is running. Mine used to stop at about the time I had used for the last sleep setting.
1 -
I wouldn't want to be someone who has just bought a new Vault.
The first task is normally to bring the software up to date and, right now, they'll wonder why nothing is working as expected after doing so.
Right now, the hole is just getting deeper and I really don't understand why rollback hasn't been adopted as yet.
Personally, I'm pee'd off as I daren't do anything apart from play music. I have CDs to rip and metadata to fix but I daren't do it.
Please, please can we roll back so I can use my Vault instead of pleading on this forum?
If you call the rollback release V5 then new owners will never know that there was a problem.
1 -
I have a Vault 2 and Node 2i. Like many others have reported, the Vault stopped working after the update. I spent several days spinning my wheels, trying to get things to work. Based on the suggestions here, I tried (again) the Diagnostics version of rebuilding the index and decided to be extremely patient with the rebuild process. The Vault LEDs stayed white at least 12 hours, even though the diagnostics menu no longer showed progress on the rebuild. I left it as it was and went to bed. This morning, the Vault LEDs were blue and I could see some of my library, but no artwork and it seemed incomplete. I tried another rebuild from the diagnostics menu and the rebuild only took minutes instead of hours. I can now see my library from the Vault. I queued several hours of music to see if there were still issues. It stopped playing after about 2.5 hours, then started again (without any prodding) in a few minutes. It played for about another 45 minutes, then stopped again. At least the library is back, but still experiencing the stop-outs.
1 -
A question for the collective intelligence unit.
My music has been playing all week.
NO problems.
Am I safe doing a library back up?
Would you bet a whole dollar on it?1 -
Try explaining all of this to a brand new Vault owner, whose just been told how wonderful and easy-to-use the product is.....
1 -
Imagine selling stuff in the state it is right now...
1 -
I have moved to Eversolo DMP A6 with the upgraded bits. My Vault will be secondary function to rip and store discs. The Eversolo is not really any dearer when adding the 2TB ssd, chose the Samsung 990 for 5 year warranty.
1 -
Just adding some details here because I haven't seen all these captured. I've now tried to rebuild my index at least 8 times. It has frozen at a different place every time, so the idea that it is a corrupt file is ridiculous as that should make it freeze at the same place every time. I've also tried toggling off the optimize album artwork as that has worked before, but that seems to make it freeze earlier in the process. Not once has my previous library been deleted as every time I force shutdown after a rebuild freeze, my entire list of artists and all 31,000+ songs show up in the diagnostics status. And at some point amid the freezes all the artwork is just gone, not most of the artwork, every single album cover is not displaying. Reload artwork does absolutely nothing, and I'm now getting stuck in navigation screens where the close button doesn't work. While I'm fairly confident a rollback to v3 would probably allow regular library playback and library art to return, I'm not sure I'm totally confident that bluesound could rollout a roll back smoothly. And in future, if they get this sorted out, I will absolutely not be updating any software from them for a longtime. I get that software is complicated, and a couple of bugs are expected, but it seems like this release is light on features and mostly bugs.
1 -
You're probably right Ian but don't forget it's all about the money...
For me its back to Plexamp with external dac to my MacBook. I really dont feel like using my Bluesound setup anymore, its a total letdown
1 -
System setup is:Vault 2 and Powernode 2,Hardwired ethernet 1Gbps, Netgear Prosafe GS752TPP switch (switch reports no cable faults), system clocks are NTP and are correct.DHCP server Windows Server, SMB is enabled and tests OK/true.
Music is stored on Vault with no current external shares attached, System was working optimally prior to 4.02 update 18th October 2023.
Current symptom is seemingly random drop outs, after a couple of songs or partway through an album when playing through the PowerNode from the Vault library. Streaming on the Powernode is unaffected, physically powering down the Vault resolves the problem until next time, rebooting the Vault from software has no effect.
On restart the Node continues playing from where the drop out occurred once the Vault has restarted and gained an IP address.
The following has been tried:
Reboot the modem, router, ASA, Edge Server, DHCP file server, reset the switch to factory defaults, reset NAS (not currently attached to Vault), DHCP leases have been cleared and refreshed, index has been rebuilt, both Vault and Powernode have been factory reset and reconfigured from cold.
Vault settings :Audio Settings - Clock trim is on
Analogue Sources - Blue tooth is disabled
A/V mode is off, CGA is off.
Optical Sources
Autosense is off, MQA Passthrough is off, A/V mode is off, CGA is Off.
Powernode Same as vault
From looking the Bluesound community pages, this is not isolated occurrence and not user network related but a bad firmware update, can you please advise on suitable action and provide a realistic timeline to resolution
Many thanks
Â
Further to my last:
Â
I have received the email below twice from Bluesound:
Hello
Our apologies - due to the overwhelming excitement over BluOS 4.0, we are seeing a higher volume of calls but have been working even harder than expected here at The Bluesound Support Crew!
Your outstanding request for support, (#376982) has not been forgotten.
A member of The Bluesound Support Crew will reach out to you as quickly as possible though. That’s the Bluesound Listening Commitment - we thank you for your patience.
To ensure our reply does not end up in your SPAM or JUNK folder, please also remember to whitelist bluesound.com, bluos.net and zendesk.com as approved senders in your e-mail application or server.
In the meantime please have a look through our Help Center. There you will find many answers to common questions, as well as helpful troubleshooting articles. https://support.bluos.net/
Here are some great articles that may help:.
Â
Â
@ Bluesound,
Â
This is not a good look for you, what an absolute shower, users have invested significant sums in purchasing what has been sold as top of the line, the support service is falling below what we the user should be able to expect, can you please either fix this mess or alternatively allow users to rollback to a previous stable version.
Please be open and transparent about the issues, rather than the opaque responses that are being sent out, this firmware update failure is at some point going to propagate beyond the BS community and BS are going to take a reputational hit.
Repeatedly advising to restart routers is not a solution, the version 4 firmware is broken, it is causing my Vault 2 to freeze when playing through my PowerNode 2.
Â
Â
1 -
I made a point of copying all my music off to a RAID1 NAS device because of these issues. That works perfectly now. In order to not have duplicate music, I scratched my internal drive. Hopefully Blusound engineers come out with a fix for this Vault2i disk access issue. I have already posted and strongly agree with having the ability to rollback to the previous version. I would not have an issue with that until the issues can be worked out.
1 -
I have the same issues stop start issues. All th rubbish about networks is irrelevant and have I never added a usb stick to my vault 2i. I am gonna use my NAS server (where I back my music to)  as a music device until this is fixed and I guess put the vault in the bin. I am feeling like a complete fool for moving away from SonoS after their fiasco over 1 and 2 series. I wish this issue was raised more widely so that BlueSound was under real pressure to fix this, but they don't seem to realise the damage it is doing to the brand
1 -
So based on what Andrew H, indicated as the fix window for a kernal issue (a few days), we should be expecting a patch in by Wednesday at the latest? It has been 3 days since his post indicating that they found and replicated the issue.
A bit of an update, since we are on the cusp of this window would be nice. Does BS have a fix in test or still in dev?
1 -
I have 2 Vaults, a Vault 2 and Vault 2i. I use the Vault 2 to store my music and I have an USB disk back up attached to it. The Vault 2i I use as a second back up. All the music there is stored in de MP3 folder. After the update to V4 the music was moved from the MP3 folder to the Music folder (i do not why and how) and could not be moved back again to the MP3 folder Because my computer told me I had no administrator rights to do so. I cannot delete the files from the music folder. I use the MP3 folder to prevend the Vault2 i to double the tracks in my Library. Otherwise I get 20 tracks in an album instead of 10 with all the tracks mentioned twice. Furthermore I experience the same issues as descibed above. No fun being a BlueSound Vault 2 owner much more no fun fun if you own 2 Vaults.....
1 -
Well, well, well...I just love the response by the Andrew H. the Brand manager:
"a kernal bug where it has been identified and replicated is a few days until fixed. We won't hold this for a general release as soon as we have a commit for the patch we will release to the affected models"
makes perfect sense to me...
I had have the same Vault 2i dropout issues over the past week and been told (via email) to reorganize my network, reboot, reindex, replace....nothing has made a difference (and has cost me over $200 in new network parts and network redesign consulting costs).
Why hasn't customer service simply say to wait for an update that works...
Very bad rollout folks...if this had happened with mainline app...the development department would have a few less employees...
I will await a true fix.
1
Please sign in to leave a comment.
Comments
192 comments