Install slot

[Rob van der Does]

Like I said above, can we have some debug logs please, otherwise we might as well close the thread as unsolvable.

As you said above: debuglog would be useful, but not possible as it's all before E2 starts.

What I don't understand: my old VU-DUO2 starts instantly when no (W)LAN is available, and th GB waits some 2 minutes (with the BW ViX screen) before starting.

 

[Joe_90]

The timestamps in the files in /var/log/ may give you some clue as to the delay before E2 start. My GB Quad+ takes almost two minutes to start, irrespective of (W)LAN availability. My AX61 will boot in 35 seconds with WLAN or 45 seconds with no network.

 

[Rob van der Does]

I found the solution: when only one image is available (i.e. in slot 0, other slots are empty), boottime is very much faster.

 

[Aust-VAST]

Oh dear, interesting thread, I noticed the only DUO² [in use] offered a chkroot.

So, I stored / backed up the 3.8TB movie folder to a spare 4TB Seagate and just now enabled chkroot.

On reboot there was no storage device and I have just initialized it and commenced exporting the cache of the user's TV onto another spare 4TB Seagate to swap back in.

The reboot menu no longer shows chkroot !

His nibs won't be happy when home from skool in a few minutes, methinks.

 

[twol]

For chkroot multiboot you need a usb for images, which once initialised will not show in mounts plus hdd/usb for your normal storage

 

[Rob van der Does]

Oh dear, interesting thread, I noticed the only DUO² [in use] offered a chkroot.

So, I stored / backed up the 3.8TB movie folder to a spare 4TB Seagate and just now enabled chkroot.

On reboot there was no storage device and I have just initialized it and commenced exporting the cache of the user's TV onto another spare 4TB Seagate to swap back in.

The reboot menu no longer shows chkroot !

His nibs won't be happy when home from skool in a few minutes, methinks.

Exactly the same happened to me, also on the DUO2. Luckily I have all recordings on an external HDD, do te-initialising the intetnal one didn't much harm.
Some help text might have helped me.

 

[twol]

well, in my original post I said insert new usb stick for images and select in device list.

 

[Rob van der Does]

Yes, that's help text for people who read every post on the forum, not for users who suddenly find a new option on their box.

 

[twol]

Yes, that's help text for people who read every post on the forum, not for users who suddenly find a new option on their box.

The code also checks for HDD, so that should not be in selection list, apart from that its difficult to work out out if the device is currently in use for something.... but I will look at changing text to emphasise chosen device will be initialised.
As always don,t select something if you have no idea what it might do!

 

[Rob van der Does]

The code also checks for HDD, so that should not be in selection list, apart from that its difficult to work out out if the device is currently in use for something.... but I will look at changing text to emphasise chosen device will be initialised.
As always don,t select something if you have no idea what it might do!

Well, my internal HDD was on the list, and has been formatted as a result.

Of course: not experimenting is always the safest way of life (but not always the one we want).
IMHO introducing a major change like this one, especially as it's also a complicated one, requires some extended help text. And yes, I know and realize that's easy to say and not so easy to do.

 

[twol]

Well, my internal HDD was on the list, and has been formatted as a result.

Of course: not experimenting is always the safest way of life (but not always the one we want).
IMHO introducing a major change like this one, especially as it's also a complicated one, requires some extended help text. And yes, I know and realize that's easy to say and not so easy to do.

Yes -- I have fixed the code that looks for the HDD, so hopefully now with text changes, we will not get that situation

 

[abu baniaz]

Thanks for the change. However, most people will understand what "Format" does better than "INITIALISE" . You have used format elsewhere. Can you consider changing that "INITIALISE" to "FORMAT" in menu.xml?

 

[twol]

Thanks for the change. However, most people will understand what "Format" does better than "INITIALISE" . You have used format elsewhere. Can you consider changing that "INITIALISE" to "FORMAT" in menu.xml?

The disk is initialised (same as Harddisk setup terminolgy) - which wipes everything, and then formatted with 3 partitions.
To be honest, I don’t think the terminology is important as long as the user understands that this is an irreversible change, hence the use of capital text.
The big change is making sure the user cannot unwillingly destroy the HDD

 

[abu baniaz]

Initialise = to start to use
Initailise = to format

Most users on forums are windows users and forget that initialise in linux terms means format and destroys existing content on HDD. My request was to simplify the language and avoid problems for common users. Anyway, its done. Thanks for taking the time to consider the request. By the logic being applied, for synergy, should the "format" used in the python file be changed to "initialise"?

 

[Aust-VAST]

Yes, my bad, maybe another day, after about 13 hours of restoration, no loss here.

Now I have another puzzling disk access to discuss in a new thread.

For chkroot multiboot you need a usb for images, which once initialised will not show in mounts plus hdd/usb for your normal storage

 

[Rob van der Does]

I found the solution: when only one image is available (i.e. in slot 0, other slots are empty), boottime is very much faster.

Well, that was only a short time solution.
After updating the image, the extreme long boot time was there again (although I have no idea if it's related to the update). I'm out of ideas now: it seems I'll have to live with it. I gave all my recordings an extra 2 minutes pre-record time to make up for it.

 

[Aust-VAST]

Now I have another puzzling disk access to discuss in a new thread.

No longer any PC disk access problem; By returning to the correct path with admin authenticated access.

\\ENIGMA II\Harddisk\Movie

\\ENIGMA II\Movies