Thema: Box crashing at 3:30am

Code:

...
03:29:59.9916 {   } Screens/LogManager.py:119 JobTrash [LogManager] probing folders
03:30:03.9154 [   ] gdi/grc.cpp:193 thread [gRC] main thread is non-idle! display spinner!
...

Yes. This is a well known feature.
This trashjob at that time wants to cleanup the logfiles (@3:30 in fulljob-mode), and therefore tries all known mounted shares to cleanup.
Does any of the devices or mounts at your box also contain folders like /log, /usr, /var or so on, usually used by the system in the root directory of the flash?
Can you please supply a zip-archive containing the following files:
/etc/fstab
/etc/auto.network
/etc/enigma2/automounts.xml
Hopefully you don't have changed any other files corresponding to mount-methods in other images (in VTi there was sometimes /etc/auto.master used by users)?
Since few days (~ before 6.1.18) i allways had a spinner shown for 5s in livetv at that time. But never a lock of any of my boxes.
It cleared up the reason for some users in the Giga-board. They had wrong mount decalrations in their configs. Therefore the above files are needed to be checked.

I see your problem. When you don't want to have that lockup of your box, you would have do ensure, that the mounted shares are rechable ANY time, the Box could run. Your decision was, to mount them fixed via [fstab].
Otherwise, i would suggest to switch the mounts from [fstab] to [autofs]:

Code:

<?xml version="1.0" ?>
<mountmanager>
 <autofs>
  <cifs>
   <mount>
    <active>True</active>
    <hdd_replacement>False</hdd_replacement>
    <ip>192.168.0.27</ip>
    <sharename>EDPC</sharename>
    <sharedir>E</sharedir>
    <options>rw,utf8</options>
    <username><REMOVED></username>
    <password><REMOVED></password>
   </mount>
  </cifs>
 </autofs>
 <autofs>
  <cifs>
   <mount>
    <active>True</active>
    <hdd_replacement>False</hdd_replacement>
    <ip>192.168.0.27</ip>
    <sharename>Downloads_DaveDPC</sharename>
    <sharedir>Downloads_Dave</sharedir>
    <options>rw,utf8</options>
    <username><REMOVED></username>
    <password><REMOVED></password>
   </mount>
  </cifs>
 </autofs>
</mountmanager>

These mounts now go from /media/net/<sharename> to /media/autofs/<sharename>
You have to remove the mounts from your /etc/fstab.
They will be added by the mount manager to the /etc/auto.network, when once opened and saved again - that takes pretty long time here (~20-30s), so be patient.
The corrected /etc/fstab would look like that:

Code:

/dev/mmcblk0p1		/boot		auto		defaults				1  1
rootfs			/		auto		defaults				1  1
proc			/proc		proc		defaults				0  0
devpts			/dev/pts	devpts		mode=0620,gid=5				0  0
usbdevfs		/proc/bus/usb	usbdevfs	noauto					0  0
tmpfs			/var/volatile	tmpfs		defaults				0  0
/dev/mmcblk0p10 none swap defaults 0 0
UUID=08d37230-4266-488a-b329-20f3c1e646b5	/media/hdd	auto	defaults	0 0
UUID=1E29-F23E	/media/usb	vfat	defaults	0 0
############      empty line at the end     #############

Let the correct /etc/auto.network be created by the system.

And again:
If you don't want to switch the mount-method to [autofs], which was included exactly to overcome those problems of nonexisting shares, then you will have to wait for a fix. Maybe, that there can be a possible solution.