my profile | my password | search | faq & rules | forum home

» Film-Tech Forum ARCHIVE   » Operations   » Digital Cinema Forum   » update ShowVault to 2.8.20 failed - IMB not recognized (Page 2)

This topic comprises 2 pages: 1  2

Author Topic: update ShowVault to 2.8.20 failed - IMB not recognized Carsten Kurz Film God Posts: 4340 From: Cologne, NRW, Germany Registered: Aug 2009 posted 09-06-2018 04:52 PM                     Maybe it fits WeTransfer. And by the way - thanx to everyone... - Carsten  |  IP: Logged Marcel Birgelen Film God Posts: 3357 From: Maastricht, Limburg, Netherlands Registered: Feb 2012 posted 09-07-2018 08:17 AM                     Looks like you had a rough night. Do you already have a clue what triggered the SNAFU? I somehow doubt it's a corrupt innodisk. It would somehow be pretty weird that a corrupt disk would allow you to boot the entire Linux distribution, including all modules and services, but not the necessary drivers and infrastructure for the IMB.  |  IP: Logged Carsten Kurz Film God Posts: 4340 From: Cologne, NRW, Germany Registered: Aug 2009 posted 09-08-2018 08:06 AM                     Dolby assumed that one of the many reboots/powercycles finally solved it, and that the IMB might be in a dicey condition. However, I created an emergency USB from the 2K4 running 2.6.4, and after adjusting it to the IPs, etc., the IMB is working flawlessly from that USB stick with 2.6.4. When I switch to the ill-fated 2.8.20 innodisc, the problem persists. When I switch back to the emergency USB, all is well. Tells me the software installation on the 2.8.20 innodisc is the reason. I tried the same measures, removing all devices, full powercycle, etc., but that 2.8.20 simply won't work with the IMB. Maybe, although it shouldn't matter, that IMB needs to be running a later version of SM and/or firmware? I think it is currently on 5.0.31 and 30.07y (I need to dive into the detailed reports to see the correct numbers). After the experience with the 2.8.20, I am hesitating to update the SM and firmware, as that is more critical. Also, Dolby always recommends updating software first, then SM, then firmware. But as the 2.8.20 can't see the SM, I can't update anyway, I would need to have a working 2.8.20 installation first. I haven't had a problem updating 2.6.4 to 2.8.20 to date. Maybe the specific SM/firmware was the reason, or the fact that the IMB/projector was powered up during the software update. - Carsten  |  IP: Logged Ioannis Syrogiannis Expert Film Handler Posts: 147 From: Reykjavík, Iceland Registered: Jun 2005 posted 09-08-2018 08:42 AM                     May be, now that you have the USB stick up and running, configured as it should, you could transfer the image from the USB thumb drive to the innodisk MoD. If the problem is software, and not hardware, the system will run properly. I am wondering, though if there is any kind of dependencies on system software upgrading. If you had to update from, say, 2.4.4, you'd have to install 2.6.4 first. Normally, from 2.6.x you can go straight to any 2.8.x, could it be that that rule was somehow broken? Anyway, if you want to experiment, you can copy the USB thumb drive to the innodisk MoD and give the upgrade another go, with a newly downloaded .pkg...  |  IP: Logged Carsten Kurz Film God Posts: 4340 From: Cologne, NRW, Germany Registered: Aug 2009 posted 09-09-2018 05:13 PM                     While the creation of the emergency backup stick uses a dd on the block device level - the resulting copy seems to be no full copy of the innodisk operating system. I learned this the hard way - while the original 2.6.4 innodisk had the vnc package installed, it didn't work when booted from the USB stick. I had to reinstall the xvnc package after the copy to get it working. Also, when I tried to upgrade to 2.8.20 from another 2.6.4 emergency boot stick - the update failed with the message, that the upgrade module was not available. I was able though to reverse copy the running 2.6.4 backup stick to the unusable 2.8.20 internal innodisk by simply switchting source and target device in the command. This results in a running 2.6.4 system, but, it appears that some components are again missing. Can someone shed some light onto this? How do I get a 'full' OS installation back onto the innodisk? I can hardly believe that with dd it would at all be possible to miss components that reside on the source device? - Carsten  |  IP: Logged Ioannis Syrogiannis Expert Film Handler Posts: 147 From: Reykjavík, Iceland Registered: Jun 2005 posted 09-12-2018 10:11 AM                     I find it rather peculiar to randomly miss files or features. I for one would troubleshoot the dd copy procedure. One thing I would try is to create the same copy with the server NOT booted from the media that have to be copied. I have used the dd if/of command several times for backing up my PC or laptop operating system, be it Linux, Windows or MacOS and, even though the procedure resulted in a HUGE file every time, I had no problem whatsoever when I had to restore such an image. (I am not suggesting that particular way to back up, there are fine utilities out there that can do the trick, and MacOS has its own for free.) The truth, though, is that in all such cases, I never had to clone the OS system while it was active. I usually use a live linux CD or USB to boot from and follow procedure. When I had the chance to do so with a DCP2000/2K4 or a SV3/4 though, I had to follow procedure while the server was on and running. I hadn't the issue you describe in the occasion I used the back-up, but that might be just luck. That factor, and, in addition to that, a possible physical corruption, may create issues. I *guess* the actual copying procedure environment is to be considered here. I 'd like, for the sake of showing the importance of it, to revisit the need for a USB 2 thumb drive for the whole task, so it can be sufficiently powered. doremi (now dolby) was describing the procedure just the same, on its portal (at least some time ago), followed while the server was on. Other than that, there is the option conv=sync,noerror that can be added after the command, for skipping bad blocks, but I wouldn't suggest it, just to be more loyal to the original doremi plan, not being in any case able to claim better understanding of the linux caveats than the doremi technicians.  |  IP: Logged Carsten Kurz Film God Posts: 4340 From: Cologne, NRW, Germany Registered: Aug 2009 posted 09-14-2018 05:28 AM                     quote: Ioannis Syrogiannis I find it rather peculiar to randomly miss files or features. Me too. Even if the dd is done from an actively running system, there should only be some small inconsistencies resulting in the copy - like log files, etc., but nothing serious. The Doremis are very well documented, but the structure of the file system, mount points, possible RAM discs, etc., I haven't seen anything about this. There is, of course, the possibility of imaging the innodisk separately, and, I may follow that route. I also guess it should be possible to run something like a GPARTED boot USB stick on a Doremi and do the imaging from there. When I copied the USB emergency boot stick back to the non-working 2.8.20 innodisk, I used a short USB extension to connect the innodisk to the front USB port instead of the internal USB6, where the boot stick needs to be. That way, I do not even have to take out the innodisk from the hub board. - Carsten  |  IP: Logged

All times are Central (GMT -6:00)

This topic comprises 2 pages: 1  2

Printer-friendly view of this topic

Hop To: Select a Forum: Category: Operations -------------------- Digital Cinema Forum Film Handlers' Forum Large Format Forum Ground Level Feature Info, Trailer Attachments & REAL Credit Offsets Category: Community -------------------- Film-Yak Film Handlers' Movie Reviews The Afterlife Bob Maar's Joke-A-Thon Category: Classified -------------------- Equipment and Supplies Wanted/For Sale Help Wanted/Seeking Employment Category: System -------------------- Software Beta Testing Forum

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.