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 can't see a good reason not to roll back to V3 ASAP.
My Inbox is filling up with posts about V4 issues right now. Prior to V4's arrival, I'd received 14 emails all year in relation to Bluesound community posts. That's less than two a month. Since V4 has arrived, however, I've received a further 44 posts. That's nine a day, i.e., over 3,000 a year.
The large number of issues reported regarding V4 suggests the likelihood of continued disruption for a quite while as Bluesound tries to iron out the issues. This isn't what one would wish upon existing users, let alone a new customers.
I can therefore see all brand-new Vaults and Nodes that are being unboxed right now being sent back as no good because, put simply, they won't work properly.
V4 is, therefore, already causing issues with retailers and distributors and will be doing no end of reputational damage right now. It's also worth remembering that it's affecting NAD as well as Bluesound.
With the number of problems being reported it'll take many days to identify the root causes, let alone devise proper 'root and branch' fixes and then test them thoroughly.
If two months of Beta testing with a large number of users wasn't enough to ensure a relatively trouble-free release, then how will a couple of days of hurried guesswork and trial and error help?
I've seen this before, and time and a breathing space are what's needed in order to work out the correct approach to take with V4 going forward.
Rolling back to V3 will grant that time and space.
Remaining on V4, however, will just subject developers and testers to excessive pressure and will create conditions under which their effectiveness will be reduced while, at the same time, the entire user base struggles with their products and, in some cases, wonders what to replace their Node or Vault with.
If this were a corporate system then it would have brought the business to a halt, and a rollback would already have happened.
One question.... was the correct software build deployed?
6 -
Ian Shepherd
My suspicion is that the development was done on the Node, not the Vault which is a pretty niche product.
But yes, I agree making V3 available again and removing V4 until the bugs are ironed out makes a lot fo sense.
I for one didn't feel a need for a new OS at all.
Dave0 -
Exactly my thoughts Ian. But it seems we're talking to a wall here.
0 -
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 -
My guess is that development and testing was carried out on all devices and all controllers, but either the test strategy and test scripts used weren't good enough, or somewhere along the line some incorrect components were incorporated into the final build, or there was some other problem with the build and its deployment. Worst of all would be if the fundamental design of V4 was flawed.
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.
0 -
Looking at how quick this forum was flooded with issues after release, they should include users in a beta-test program.
0 -
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 -
Thank you, Tony. I suspect - in fact, I'm sure - that at least some of the "successful" remedies have worked only temporarily. If I'm wrong, I hope you're able to identify a remedy that will work for all of us.
2 -
The task at hand must be enormous and frustrating for the dedicated Bluesound team. It is highly likely that the project may take quite some time to produce satisfactory results. Therefore, there is no shame in providing a possibility to obtain a former firmware version for those users who encounter serious problems and are willing to install the image themselves. Just in case the development takes longer than foreseen. This would relieve the pressure on the technicians a bit and allow users to enjoy their equipment in anticipation of a more stable release.
3 -
I tried to rebuild the index on my Vault 2.i using the command under the Diagnostics menu. It failed (stuck) the first two times, so I searched for help and found this:
https://support1.bluesound.com/hc/en-us/articles/204103486-Why-is-my-BluOS-index-not-completing-
I followed that advice and initiated the rebuild from my PC: this time it worked. So I turned off all the BS devices, waited, rebooted the network, waited, reintroduced the BS devices.
So far this seems to have resolved the problem with playing music directly from the Vault HDD to the attached amp and speakers. I've played music that way for about 2.5 hours now with no problem - way longer than at any other time since I installed 4.0.2
But when I streamed from the HDD over the (ethernet cabled) network to a Pulse mini it stopped within 20 minutes.This time it displayed an error message on the app controller: FLAC__STREAM_DECODER_ABORTED
As ever, the only way to make it work again was to unplug the Vault then power it up again.
Like others, I don't believe this is solely a network issue. All the BS devices on my network, Vault 2i included, still play streams from various online sources without any problem at all. Its only when I switch from streaming sources to playing music from the Vault HDD that the freezing problem occurs.
2 -
@Eric Reiss
If you go to the top of the first page of this thread you'll see 'official' advice by Tony W, both about rebuilding the Vault index and - lower down, via a link to another thread - rebooting your network and your BS devices.
The link I included does say that its about submitting a log file with a support message. But the command there initiated a successful rebuild of my library, after the rebuild command in 'diagnostics' failed to do so twice.
I appreciate it could just be third time lucky but posted the information in case that method also worked for others whose rebuilds have failed.
Hope this helps, good luck.
2 -
Excellent. Yes, I figured out the command and am trying it now. I appreciate the response. Thanks much!
0 -
I performed a reindex using the instructions that John Cromby provided. The reindex seemed to work, although it didn't take as long as it usually would. Also all artwork is missing *except* from the albums that had never been indexed before, so perhaps that command does not perform a full delete/reindex of the database? Tony W can you weigh in?
0 -
Reindex does not update artwork - only adds new - you want Settings, Diagnostics, Rebuild Index to purge the Album Artwork
0 -
I put a usb drive into the vault, enabled server mode. Reindex and it's playing without freezing, plus streaming to the node as well. It's a quick fix at least until BS sort this mess out..
0 -
I just woke up (this is Australia) and found a new controller update, labelled 4.0.1.
Has anyone tried it?
I sent off the support request as asked and instantly I have been given a new number for it.
I think that is the third.
Must be time for a cup of coffee.0 -
Well,
I waited a good 6 months for the big update and now this immature mess is offered. Extremely embarrassing performance!
Interesting to learn that the Vault 2i is a niche product,
on the other hand one is "proud of it"...
No friends, that's not how it works.
You had long enough time -our better alternative is ordered now.
Eversolo - DMP A6
You could take a leaf out of their book.
I wish you a lot of fun with the update.0 -
Based on Peter's feedback above, I plugged a USB stick into the vault, enabled server mode and reindexed. The reindex seems to have been successful and so far I'm able to play music through the vault's rca output. *HOWEVER* when I try to play music from my library on either of my pulse mini 2i's I get a file not found error. It seems like the pulse mini's didn't get the message that the library was reindexed. I'm trying to do a reindex of both the pulse mini's, but this not something I have ever had to do before. Has anyone experienced something similar?
0 -
Thank you all for your patience and understanding. A special shout-out to those of you who have used the long-standing Send Support Request feature in BluOS so we could review your log file.
As suspected we are seeing two separate issues with the VAULT. The recommendation of disabling server mode as per the KB I have posted earlier (here it is again; https://support.bluos.net/hc/en-us/articles/360037137354) will resolve your issues if your symptoms are;
- Music Library is missing
- Not all my music is there
- Host is down
- Cannot Rip CDs
To resolve this;
- Disconnect all USB drives
- Disable Server Mode in Music Libary
- Reboot the VAULT
- Rebuild the Index from the Diagnostics Page
- If you want Server Mode and have multiple players, consider installing the USB drive on another player
This will NOT resolve music stopping when the VAULT is playing Music by itself or as part of a group. We are continuing to find the root cause of that issue. Some recommendations I can make to help this;
- Please ensure the VAULT is not ripping or Indexing while playing Music
- Temporarily - if you can, avoid using the VAULT as a playback device in a group
- If you do use it in a group, try making it the primary player meaning start the Music with the VAULT then add other players
- Disable background services if you don't need them such as Bluetooth or Server Mode
There is no need to factory reset your VAULT and there is no need to restore backups. In fact restoring backups are adding processing to the VAULT.
I will continue to keep you updated as news becomes available.2 -
not sure of the category this slots in.
In readiness for V4, I wiped Vault Library to replace with refreshed metadata/track gained revision.
From V4 release day Ive tried many times to load to Vault, with 3 computers, 3 networks.
The fail point seems to be the Sharepoint instability in both initial connection and short duration before disconnect.
Best effort was only 10GB of 700.
now in the hands of Support Request Team.0 -
Hi Central Scrutinzer
This is a common issue and often due to your laptop or PC timing out and not new to 4.0. If you are dragging and dropping, you need to do periodic drags and drops. Even disabling all power savings on your PC doesn't always work...
-1 -
not happened till now, V4. happened on M1 Macmini, M1 MacStudio, 2013 MacPro
newoorks. “regular” LAN. next tried Archer D9 router with only Mac and Vault then MacMini with Vault direct to LAN port. used Finder copy, and Terminal cp & scp
V3 - i have done both methods multiple times, waiting for 30 hours, but succesful completion.
i also had a backup usb, and that failed to transfer. that indicates the Vault at issue.
if it was such a common issue, where is documented0 -
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 -
Have had issues with vault drag and drop stopping. My two cents says that the vault is going to sleep, have found that having the music playing keeps it from sleeping, drag and drop then runs without stopping. Cheers from Oz
0 -
Tony W. "As suspected we are seeing two separate issues with the VAULT" Multiple users have also reported issues with the vault stalling during Rebuild Index. Do you have any troubleshooting suggestions for this? Thanks!
0 -
I followed the directions for rebooting my router, unplugged my BluSound devices (Vault, Pulse Flex and Flex) for 5 Minutes, then brought them up one at a time and performed a factory reset on each. After this, reindexed the library from the diagnostic tab on the Vault which took about 8 hours to do 26,800 songs. While I could stream at least one album today from my Vault, the other devices do not show access to the Vault library…i can see the connected share to the vault ip address in the diagnostic tab, but I cannot access the music on the music tab or Home Screen…also the 4.0.4 upgrade was pushed through tonight…not sure if that caused something here on top of this.
0 -
Martin Layding
4.0.4???
I seem to be fully up top date with 4.0.2.0 -
Tony W.
Just clarifying. I must be one of the lucky then.
Drag'n'Drop or Terminal cp commands worked for 3+ years with no fails or Sharepoint drop-offs, all with 700GB or more files. Slow as heck but it worked. In one instance I loaded fresh library onto the BackUp drive (copied via extFTS app on Mac) and attached to Vault, using Restore 5 times faster.
I believe the Sharepoint issue is within Vault, as with V4 neither Backup or exFTS worked in efforts to get files back on. and the 3 "LANs" and 3 Macs used couldn't all be wrong??I've had support tickets, only one re Vault where permissions were screwed. Others were re M3U imports and a day one Flex 2i that finally was replaced after a long period. Eric and Kyle were helpful.
0 -
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 -
4.0.4 tried loading tracks ex Mac.
- terminal copy command
- finder copy
both failed with less than 10GB & ~ 40 minutes
I later tried a single Artist Folder of 8GB, the method Tony W. suggested, and after 5 minutes that failed with the same Mac Error Code I'd previously seen 100060.
I must be somewhere in the line waiting for the lodged Support Ticket to be actioned, but like others who are spending testing time rather than playing music might prefer the V3 Rollback to materialise, let the developers knuckle down with V4, rather than this whole congregation be treated as beta testers.2
Please sign in to leave a comment.
Comments
192 comments