Results 1 to 14 of 14

Thread: DM800HD - Enigma2 crash when configuring hdd/recording

  1. #1
    Junior Member etcetc's Avatar
    Join Date
    Feb 2008
    Age
    63
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    197
    Reputation
    10

    Default DM800HD - Enigma2 crash when configuring hdd/recording

    My DM800 [CCcam2.1.4/NewCS 1.67] is a client of my DM500 which has a bluey. I bought a hard disk and through "Devices Manager" initialized and mounted it. The message at the end was "Execution finished!!!", even though the "Initialize One moment please remained"
    ================================================== ==
    Type : IDE (Primary Master) Model HitachiHTS545025B9A300 size 238.5GB ; Partitions : 1 ;Device:/dev/hda
    Device: /dev/hda1 Size 238.5GB Mountpoint :/media/hda1
    ================================================== ==
    df shows /dev/hda1 with 244003608 available (/media/hda1)
    ================================================== ===

    I then created a "video" directory on /media/hda1

    From menu [setup/system/recording paths] I changed both "Default movie location", first deleting the Bookmark "/hdd/movie", then adding Bookmark "/media/hda1/video". I repeated the same for "Timeshift location". I saved the new settings and as I exited, I got the "We are really sorry" Gemini2 crash message. The error message includes:
    IOError:[Errno28] No space left on device '/etc/enigma2/settings'

    After it reboots, I notice that the "saved" settings are no longer there.
    [The box comes up OK]. The drive comes up as mounted. I am sure that there is significant space on the flash drive - after all it created a crash log.

    I suspect that perhaps my problem is that the config file it is trying to
    update is perhaps write protected.

    Any assistance is greatly appreciated. I can post the full crash log if required.
    "My glasses...without them, I'm helpless!"



Look Here ->
  • #2
    Premium Member
    Join Date
    Jan 2008
    Posts
    1,558
    Thanks
    65
    Thanked 84 Times in 64 Posts
    Rep Power
    269
    Reputation
    1032

    Default

    Had a little play this week adding a hdd to my DM800.

    I found the best thing to do was to initialise the hdd via the menus on the screen and let the box do all the path settings for recording etc.
    Recordings via the timer menu function then worked fine.

    I have previously also tried to mount a network drive location for recording ... could not get it to work... but that could be just me

  • #3
    Junior Member etcetc's Avatar
    Join Date
    Feb 2008
    Age
    63
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    197
    Reputation
    10

    Default

    Quote Originally Posted by checkitout View Post
    Had a little play this week adding a hdd to my DM800.

    I found the best thing to do was to initialise the hdd via the menus on the screen and let the box do all the path settings for recording etc.
    Recordings via the timer menu function then worked fine.

    I have previously also tried to mount a network drive location for recording ... could not get it to work... but that could be just me
    Thanks for your response, but I did that first... still crashed.
    "My glasses...without them, I'm helpless!"

  • #4
    Junior Member
    Join Date
    Jan 2008
    Posts
    139
    Thanks
    17
    Thanked 29 Times in 25 Posts
    Rep Power
    207
    Reputation
    252

    Default

    I had a similar issue when I first set up my box with an external esata drive. I didn't setup the recording path correctly and when I hit the record button, the recording actually filled up the DM800 internal memory. I couldn't do anything with the box which kept on green screening.

    I fixed it by ftping to the box, finding the recorded files and then deleting them.

    Did you attempt any recordings after connecting your external drive? If you did, this may be your issue.

  • #5
    Senior Member

    Join Date
    Apr 2011
    Location
    Gold Coast
    Posts
    1,504
    Thanks
    1,879
    Thanked 1,590 Times in 726 Posts
    Rep Power
    767
    Reputation
    27988

    Default

    Something really simple just on the off chance. Bring up the path settings screen and actually check that the correct path is showing. On Gemini it is easy to go one step further than necessary. If you actually click and enter the video directory and then press okay the path will not be set correctly. You need to be in the parent directory with the video directory highlighted when you press okay.

  • #6
    Junior Member etcetc's Avatar
    Join Date
    Feb 2008
    Age
    63
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    197
    Reputation
    10

    Default

    Thanks for your help guys but still no success:-

    I carefully ensured that Record Paths Settings were set to the HDD
    [hda1 is the new HDD](I created a "movie" directory on it - without a valid
    directory name, it will state that its an invalid path):-

    ---------------------------------------------------
    Record Paths Settings
    Default movie location /media/hda1/movie
    Timeshift location /media/hda1/movie

    Save

    As soon as I exit, I get the green screen.... !!! This is important, as I don't
    even need to hit the record button for it to crash!!!


    ---------------------------------------------------
    Also noted
    From the Moutpoints Menu

    device:/dev/root (99%) <<<=================== !!!!
    Mountpoint:/(jffs2)
    total 60MB, used 59.5MB free 476.9 kB
    -----------------------------
    device:/dev/mtdblock/2 (66%)
    Mountpoint:/boot (jffs2)
    total 3.8MB, used 2.5MB free 1.3MB
    -----------------------------
    device:/dev/hda1 (0%)
    Mountpoint:/media/hda1(ext3)
    total 232.8GB, used 128.2MB free 232.7GB
    -----------------------------

    I now suspect that my flash drive is full ... too full to save the config changes... so, how much free space do I need to save the config changes?
    "My glasses...without them, I'm helpless!"

  • #7
    Senior Member

    Join Date
    Apr 2011
    Location
    Gold Coast
    Posts
    1,504
    Thanks
    1,879
    Thanked 1,590 Times in 726 Posts
    Rep Power
    767
    Reputation
    27988

    Default

    You may well be right. Your root filesystem is virtually full. Whilst this is not necessarily your problem it is highly likely. My working system has 16.3 megs free of the 60. It is well worth deleting files or uninstalling software to give it a try. I also wonder what is using all the space. Is it installed packages or have you say, downloaded a lot of epg or other data to your flash. The command:

    find / -size +500k

    will show all files on your system over 500 kilobytes. This command with varied sizes can help you isolate large files, but is less help with a large nunber of small files.

  • #8
    Senior Member
    Join Date
    Feb 2008
    Posts
    693
    Thanks
    4
    Thanked 217 Times in 139 Posts
    Rep Power
    262
    Reputation
    2138

    Default

    Quote Originally Posted by DB44 View Post
    You may well be right. Your root filesystem is virtually full. Whilst this is not necessarily your problem it is highly likely. My working system has 16.3 megs free of the 60. It is well worth deleting files or uninstalling software to give it a try. I also wonder what is using all the space. Is it installed packages or have you say, downloaded a lot of epg or other data to your flash. The command:

    find / -size +500k

    will show all files on your system over 500 kilobytes. This command with varied sizes can help you isolate large files, but is less help with a large nunber of small files.
    Change to

    find / -size +500k -type f -xdev

    will stop reporting directories and files on other file systems (hdd, usb). Makes the output a bit easier to read.

  • #9
    Junior Member dishboy's Avatar
    Join Date
    Feb 2010
    Posts
    143
    Thanks
    67
    Thanked 28 Times in 17 Posts
    Rep Power
    180
    Reputation
    180

    Default

    what do the crash logs say?
    Just chasing my tail and getting nowhere.
    In my last life, I must of been a dog.

  • #10
    Junior Member etcetc's Avatar
    Join Date
    Feb 2008
    Age
    63
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    197
    Reputation
    10

    Default

    Quote Originally Posted by dishboy View Post
    what do the crash logs say?
    [TIMER] record event 4
    next real activation is Mon Apr 25 18:30:00 2011
    [timer.py] next activation: 1303718053 (in 99480 ms)
    Traceback (most recent call last):
    File "/usr/lib/enigma2/python/mytest.py", line 193, in processDelay
    callback(*retval)
    File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 1563, in recordQuestionCallback
    self.startInstantRecording(limitEvent = answer[1] in ("event", "manualendtime") or False)
    File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 1510, in startInstantRecording
    simulTimerList = self.session.nav.RecordTimer.record(recording)
    File "/usr/lib/enigma2/python/RecordTimer.py", line 650, in record
    self.saveTimer()
    File "/usr/lib/enigma2/python/RecordTimer.py", line 599, in saveTimer
    file = open(self.Filename, "w")
    IOError: [Errno 28] No space left on device: '/etc/enigma2/timers.xml'
    (PyObject_CallObject(<bound method Session.processDelay of <__main__.Session instance at 0x300345f8>>,()) failed)
    getResolvedKey config.plugins.crashlogautosubmit.sendAnonCrashlog failed !! (Typo??)
    getResolvedKey config.plugins.crashlogautosubmit.addNetwork failed !! (Typo??)
    getResolvedKey config.plugins.crashlogautosubmit.addWlan failed !! (Typo??)
    "My glasses...without them, I'm helpless!"

  • #11
    Senior Member
    Join Date
    Feb 2008
    Posts
    693
    Thanks
    4
    Thanked 217 Times in 139 Posts
    Rep Power
    262
    Reputation
    2138

    Default

    What does df /dev/root show? It looks like you may have recorded on flash, & filled up your root file system.

  • #12
    Junior Member etcetc's Avatar
    Join Date
    Feb 2008
    Age
    63
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    197
    Reputation
    10

    Default

    All sorted.. re-flashed with a different image..... All working fine.

    Thanks for everyone's help





    "My glasses...without them, I'm helpless!"

  • #13
    Senior Member nfnovice's Avatar
    Join Date
    Jan 2008
    Posts
    1,430
    Thanks
    261
    Thanked 336 Times in 213 Posts
    Rep Power
    281
    Reputation
    1840

    Default

    I think reflash same image might have fixed it as well - if it was full root
    Dm500, DM5620, DM600 x2, DM7000 x1, DM7020, DM7025, DM800, VU+DUO and a partridge in a pear tree
    All it takes for evil to prevail is for good men to do nothing

  • #14
    Junior Member
    Join Date
    Dec 2011
    Posts
    1
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Reputation
    10

    Default

    Hi,

    I have the same exact problem as the OP (internal flash drive is full) but I do not want to reflash my box just yet.

    Is there any way to free up space and if yes what should I delete from where?

    Here's the output from my box:
    Code:
    root@dm500hd:~# find / -size +500k -type f -xdev
    /bin/busybox
    /lib/libc-2.10.2.so
    /lib/modules/2.6.18-7.3-dm500hd/extra/bcm7405.ko
    /lib/modules/2.6.18-7.3-dm500hd/kernel/fs/xfs/xfs.ko
    /usr/bin/mc
    /usr/bin/enigma2
    /usr/bin/CCcam_2.1.4
    /usr/lib/libpython2.6.so.1.0
    /usr/lib/libgnutls.so.26.4.6
    /usr/lib/libstdc++.so.6.0.13
    /usr/lib/libgstreamer-0.10.so.0.25.0
    /usr/lib/libfreetype.so.6.3.17
    /usr/lib/libxml2.so.2.7.3
    /usr/lib/libgio-2.0.so.0.2200.4
    /usr/lib/libgcrypt.so.11.5.2
    /usr/lib/libglib-2.0.so.0.2200.4
    /usr/lib/libcrypto.so.0.9.8
    /usr/lib/libvorbisenc.so.2.0.6
    /usr/lib/python2.6/lib-dynload/unicodedata.so
    /usr/lib/libasound.so.2.0.0
    /usr/sbin/nmbd
    /usr/sbin/smbd
    /usr/sbin/openvpn
    /usr/share/enigma2/Kerni-HD1/skin.xml
    /sbin/ldconfig
    Many thanks!

  • Bookmarks

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •