Boot Fails ... Flash-Plugin? USB-Mount?

  • After Installing the Flash-Media-Plugin the system crashed when Mounting the Backup-Medium (ext. USB-HD) ... My System: Asrock Q2900, 2x HD (Array Data Raid1), 1x SSD (System)


    The Frontend won't come up and dies:


    Code
    Error #6000:
    exception 'OMVException' with message 'Failed to open file (filename=/var/cache/openmediavault/cache.omvwebguilogin_js.json, mode=w+).' in /usr/share/php/openmediavault/util.inc:168
    Stack trace:
    #0 /usr/share/php/openmediavault/htmlpage.inc(163): OMVJsonFile->open('w+')
    #1 /var/www/openmediavault/index.php(41): OMVHtmlPageAbstract->render()
    #2 {main}


    What have I done wrong, what can i test?


    Micha

    ____________________
    Grüße aus Berlin


    Q29000-ITX
    omv 4.1.8.2 | 64 bit | backport kernel | omvextras

  • Tested ... no effect ... sabnzbd is up, omv not ...


    remains:

    Code
    Error #6000:
    exception 'OMVException' with message 'Failed to open file (filename=/var/cache/openmediavault/cache.omvwebguilogin_js.json, mode=w+).' in /usr/share/php/openmediavault/util.inc:168
    Stack trace:
    #0 /usr/share/php/openmediavault/htmlpage.inc(163): OMVJsonFile->open('w+')
    #1 /var/www/openmediavault/index.php(41): OMVHtmlPageAbstract->render()
    #2 {main}

    ____________________
    Grüße aus Berlin


    Q29000-ITX
    omv 4.1.8.2 | 64 bit | backport kernel | omvextras

  • Did you reboot after enabling the plugin???


    You should have this openmediavault folder in /var/cache


    cd /var/cache
    mkdir openmediavault
    chmod 755 openmediavault
    chown openmediavault:openmediavault openmediavault



    Then try to login.


  • I don't remember, if I rebooted after installing. But after installing the openmediavault-dir I can enter omv again. Many thanks! But is It all done now?


    You quoted for the fsram.conf, cat /etc/fs2ram/fs2ram.conf shows



    I add the Information from the /etc/fstab


    I recommend the line


    # swap was on /dev/sdc5 during installation
    # UUID=c409be98-4aab-40b9-96c7-9308a11935b4 none swap sw 0 0


    I uncommented the line above during the installation ...



    the line is "tmpfs /var/cache keep_file_content - tmpfs" ... right? But what happens with it next? Mal die Suchfunktion bemühen.


    PS: Is their a way to check trimming and installation of the ssd in general?
    PPS: Is using a SSD appropriate?


    Micha

    ____________________
    Grüße aus Berlin


    Q29000-ITX
    omv 4.1.8.2 | 64 bit | backport kernel | omvextras

  • The swap partition is not used with the flashmemory plugin. If you uncommented a swap line in fstab you should have not done this. A swap file is used with the flashmemory pluigin instead of using a swap partition.

  • SChon wach? Willkommen in meiner Welt ... ;)


    I can't remember, on which step in the Installation I was reccomended to do so. Should I leave it uncommented or redo it in the fstab?


    What is on my question how to test it? Do you have a answer? Am I shure with my installation? This question is virulent, because I have the old NAS-Hardware, which I wanted to transfer from a formerly used readybuilt-Zyxel-NAS.

    ____________________
    Grüße aus Berlin


    Q29000-ITX
    omv 4.1.8.2 | 64 bit | backport kernel | omvextras

  • I am in bed on my tablet, can't get back to sleep.


    It should look like this, with the comment (#) at the beginning:
    # UUID=c409be98-4aab-40b9-96c7-9308a11935b4 none swap sw 0 0


    I think your system is fine but the openmediavault folder is missing it can't write to that folder. Did you recreate and what happens then?

  • Ja ... added the dir after your Instructions than it worked .. thanks once more, but: where had it gone?


    The line with the quotation-Mark?


    # swap was on /dev/sdc5 during installation
    # UUID=c409be98-4aab-40b9-96c7-9308a11935b4 none swap sw 0 0


    This is how it looks like after installation ... kann so bleiben! ;)

    ____________________
    Grüße aus Berlin


    Q29000-ITX
    omv 4.1.8.2 | 64 bit | backport kernel | omvextras

  • Mist, eben installiere ich ein neues Modul (Plex) mit neuetart ... selbes Spiel:


    Code
    Error #6000:
    exception 'OMVException' with message 'Failed to open file (filename=/var/cache/openmediavault/cache.omvwebguilogin_js.json, mode=w+).' in /usr/share/php/openmediavault/util.inc:168
    Stack trace:
    #0 /usr/share/php/openmediavault/htmlpage.inc(163): OMVJsonFile->open('w+')
    #1 /var/www/openmediavault/index.php(41): OMVHtmlPageAbstract->render()
    #2 {main}


    Das ist jetzt aber was, was in eure Zuständigkeit fällt, oder?

    ____________________
    Grüße aus Berlin


    Q29000-ITX
    omv 4.1.8.2 | 64 bit | backport kernel | omvextras

  • Recreate the openemdiavault folder if missing again with instructions above....


    Your system drive is SSD yes???
    If so edit the system drive in /etc/fstab and use these options:

    Code
    ext4 noatime,discard,errors=remount-ro 0       1


    Then try rebooting...

  • Gonna try this ... you can see my fstab quoted before in the thread ...


    fstab looks now like this:



    PS: Booting and Fileservices are up, it is the frontend what is failing


    PSS: Creating the dir makes the frontend working ... trying too reboot ...

    ____________________
    Grüße aus Berlin


    Q29000-ITX
    omv 4.1.8.2 | 64 bit | backport kernel | omvextras

    Einmal editiert, zuletzt von mipi ()

  • I rebooted to halt and brought up again, its working ... please understand me to be a little nervous, when the system won't come up ... even the fileserver is up ... ;)


    many thank, but understand when i'm sitting here with with perked ears at my new baby ...

    ____________________
    Grüße aus Berlin


    Q29000-ITX
    omv 4.1.8.2 | 64 bit | backport kernel | omvextras

  • This fs2ram stuff is fairly new here. It is not perfect but it is running very well on many systems now. I think if your system drive options had been correct you would not have had this problem.


    Any time you hold back writes in ram there is more risk involved. That is the nature of the beast.


    With a good SSD you do not have to use fs2ram. If you are using any type of flash like a usb drive/sd card you really need to use the flash memory plugin because if you don't it will kill these type of devices in perhaps weeks.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!