Vu+ duo HDD error after crash- help!

Hello buddy,

Can you tell us which image you have installed on your Duo please??

Ok, I take it you updated the image from 600 to 626 or maybe a earlier version??? or the image may have been set to update automatically with a stable update when it comes out.The only reason I am asking this is because when I updated my solo 2 from Vix build 600 to 626 I had exactly the same problems, I couldn't even get the crash logs from the box to be able to send to Vix to have a look at to see what the problem is.

The only saving grace is that your settings etc should have been backed up before the image updated itself, the only way I was able to update the image this time was to flash it on from scratch, then my hdd etc auto mounted as usual,i was then able to re-instate my settings.

Or maybe you have a full backup done of your image before this happened??? if so you could always flash this on to resolve the problem.

If you reflash with the latest Vix image bud you will not need to update it: http://linuxsat-support.com/oe…hangelogs.html#post103919

I can't really say what has caused it as I don't know, the only way of finding out is being able to get the crash logs from the box.

This sounds just like the problem I was having on my Solo2 http://linuxsat-support.com/vu…rive-wont-initialize.html

It wouldnt mount the drive whenever I tried in the menus some python program would crash adding a line to fstab. I added my own entry into fstab and manually mounted the drive but on reset the line I put in fstab was gone. In the end I gave up and went back to BlackHole.

Quote from mckee25

Ok, I take it you updated the image from 600 to 626 or maybe a earlier version??? or the image may have been set to update automatically with a stable update when it comes out.

The image is coded so this can never happen, the user is always presented with a yes/no challenge screen even for stable updates, only when using a telnet session can you bypass this challenge screen.

you can manually save your timers.xml file and autotimers.xml file from the etc/enigma2 folder and just FTP them back once you have setup the new image. this way you dont loose any of your timers and can setup the box from fresh without using a backup.