|
This topic comprises 2 pages: 1 2
|
Author
|
Topic: update ShowVault to 2.8.20 failed - IMB not recognized
|
|
Leo Enticknap
Film God
Posts: 7474
From: Loma Linda, CA
Registered: Jul 2000
|
posted 09-05-2018 03:23 PM
My guess would be one of three possibilities.
1 - You accidentally installed 2.8.20 for a DCP2000 or DCP2K4 (server with a Dolphin media block rather than an IMB), rather than 2.8.20 for a ShowVault, and it's trying to communicate with a Dolphin board and not finding it.
2 - 2.8.20 will only work if the firmware and security manager (both are flashed into the IMB) are updated to a newer version than the one they're on. I'd be surprised if this is the problem, because Dolby's instructions say to always update a ShowVault/IMB in the order server > security manager > firmware. Logically, therefore, a new version of the server software should not break communication with an IMB running an older SM or firmware, because it needs to see it in order to update it.
3 - The flash drive that holds the operating system image got corrupted during the upgrade. If that's happened, you may be able to rescue it by creating an emergency boot drive on a USB flash stick, from a working ShowVault, and then using that in the problem machine to get you going (but the permanent fix, I'm afraid, is to buy a replacement boot flash card from Dolby). I have an instruction sheet on how to do this, but this site won't let you upload PDFs directly. Please email me if you'd like it.
Also, apologies if this is so obvious as to insult your intelligence, but I take it that you have tried pulling and reseating the PCI-e cable, and checking that the IMB <> projector marriage is still OK?
| IP: Logged
|
|
|
|
Ioannis Syrogiannis
Expert Film Handler
Posts: 147
From: Reykjavík, Iceland
Registered: Jun 2005
|
posted 09-06-2018 01:56 AM
Carsten, you can "create" an emergency USB stick by copying the SSD drive of another ShowVault, bit by bit (dd command via terminal as root - be extremely careful on what you write there, if you try to copy the wrong way around, you'll wipe the drive). If you do it while the server is on, the most possible, you will see an error that the machine did not close properly when you first use the USB drive for booting, since no power down commands were logged in your copy. Other than that, you'll have to retrieve the certificates of your server, either online or by a diagnostics package you previously created and place them properly. The actual placement procedure of the USB stick is described by doremi/dolby, so no reason for me to go by memory right now. CAUTION: The motherboard of ShowVault, just like DCP2000 and the 2K4/SV4 series does not support USB3, use a USB2 stick, if you want the ampers to be proper. I tried once with a USB3 thumb drive and I wasn't able to get it to boot. Changing to USB2 did the trick. Also, you might find that SV3 and SV4 SSDs have different capacities. I am not certain if that has to do with the series (SV3/SV4) or the date of manufacturing. My estimation is that either 2GB or 4GB, the actual space used on both is the same, but it might need different USB sticks (they have to be equal or bigger capacity...).
If you don't have an SV3/4 handy, in order to create the emergency USB, PM me your e-mail and we'll try to retrieve a back-up for you to use, but -mind you- it'll be a v2.6.4 one.
| IP: Logged
|
|
|
|
|
|
Carsten Kurz
Film God
Posts: 4340
From: Cologne, NRW, Germany
Registered: Aug 2009
|
posted 09-06-2018 10:01 AM
So... first, I created an emergency boot stick on a 2K4 (Dolphin). Creation works, the ShowVault starts with it, but then somewhere goes into a PCI/dolphin detection loop. So, basically it works, but I can't get it to start the GUI to change the network config.
...interesting, after a while, it exits that loop and starts the GUI, now trying to reconfigure the proper IP addresses...
Will try to remove the IMB from device manager...
- Carsten
| IP: Logged
|
|
|
Carsten Kurz
Film God
Posts: 4340
From: Cologne, NRW, Germany
Registered: Aug 2009
|
posted 09-06-2018 11:20 AM
Hmm,. wow, that was weird - I was about to give up - and the final reboot actually saved us - suddenly, the secure clock warning was gone, KDM were there, diagnostic manager showed the media block/IMB present. I was able to play unencrypted and encrypted content.
Now, the system is running from the emergency boot stick created on our 2K4 running 2.6.4-0 - all I did was adding the DCP2000_DDR memory upgrade, and some IP reconfig. And many reboots... the first one added Certainty automatically. When it still didn't work, I removed all devices (projectors, Certainty, etc.), rebooted, added the NEC series 2 projector. After another reboot, it did NOT automatically add the IMB/Certainty. I was frustrated, power down both server and projector, restartet one more time - and now it works. Probably the projector/IMB needed another power kick as well...
We are now waiting for a new innodisk to arrive tomorrow. Maybe the old one was corrupt and didn't survive the update to 2.8.20...?
Glad, we were just about to start todays showings, so we didn't lose a single one...
- Carsten
| IP: Logged
|
|
|
|
|
|
All times are Central (GMT -6:00)
|
This topic comprises 2 pages: 1 2
|
Powered by Infopop Corporation
UBB.classicTM
6.3.1.2
The Film-Tech Forums are designed for various members related to the cinema industry to express their opinions, viewpoints and testimonials on various products, services and events based upon speculation, personal knowledge and factual information through use, therefore all views represented here allow no liability upon the publishers of this web site and the owners of said views assume no liability for any ill will resulting from these postings. The posts made here are for educational as well as entertainment purposes and as such anyone viewing this portion of the website must accept these views as statements of the author of that opinion
and agrees to release the authors from any and all liability.
|