After upgrading to BluOs 4.02, Vault2i starts having issues with internal disk access
Shortly after upgrading to BluOS 4.02 while on my Node2i streaming from the library on the internal disk of the Vault2i, I started to have drop outs of the stream. I then started having difficulty uploading new music from a Samba share I had on my Macbook to the Music share on the internal disk. Constant errors reading and writing. Doing much of anything with the local library of the Vault2i was not possible.
So I removed the internal drive and put it on the SATA bus of my Ubuntu server, mounted a USB drive, and copied everything off since I never took a backup. I also ran a 'fsck' on the drive and it was clean.
I put the disk back in the Vault2i, did a factory reset and replaced the ethernet cable to the switch. Still having issues. It seems to be mostly Samba/ network related in my opinion but not sure since I have no access to the dmesg or other logs/ commands on the Linux appliance.
-
Offizieller Kommentar
We can confirm a low-level kernel error is causing cases where the VAULT may stop responding after 15-20 minutes of serving music or ripping. We are working to address this and push an update as soon as we possibly can.
Please follow this thread regarding the issue; https://support1.bluesound.
com/hc/en-us/community/posts/ 18490369188247/comments/ 18605640884759#community_ comment_18605640884759 -
This post looks displaced. I did not realize this was specific to the V500 device whatever that is.
0 -
hi Andrew, i'm experiencing exactly the same: disk access issues on my Vault2i device after the upgrade. not only on smb, but even from my app (upgraded version!) on my Android phone, browsing the library hangs sometimes.
Haven't removed the disk, as I only have the device for 4 weeks now, and I don't want to break the warranty
Performed a restart of the device ( soft restart from within the app, and hard restart by unplugging the powercord), rebuild of the music library, to no avail. Have opened a ticket with support just now.0
Post ist für Kommentare geschlossen.
Kommentare
3 Kommentare