Posts by oxidizer

    Quote

    Is this update persistant?


    I don't know but I rather suspect No because I added lines in


    /var/www/openmediavault/js/omv/module/admin/diagnostic/system.js and
    /usr/share/openmediavault/engined/rpc/system.inc

    May be this is for other users with a HP raid controller interest too.


    I have a HP P212/256 Raid controller. With hpacucli there is a tool you can get information of your raid status like this:



    or this:




    I want to make a new tab in OMV GUI under SystemInformations called RaidInfo. To make a new tab is not a problem but how I can get to run a script in this tab like in the report tab? I have read the plugin guide but I can not get it.

    so, after spending a lot of time to search for a solution I found a way:


    after fsck.ext4 -v /dev/sdb1 the output was:



    with mke2fs -n /dev/sdb I searched for superblock backups. The output was:



    With e2fsck -b 294912 /dev/sdb1 (the first 4 superblocks don't work) I repaired my bad superblock. The output was:



    Now I have the problem my Raid10 is mounted as a USB Media. A look in /media/usb/ now I find my data and folders again (Thank god). How can I correct it?


    The ouput of blkid


    Quote

    [/dev/sda1: LABEL="Raid10" UUID="203d4f4e-02ae-4698-8bc9-04d55006d7d9" TYPE="ext4"
    /dev/sdb1: UUID="2ee5aa4b-5279-4ac9-ba47-b89982c40585" TYPE="ext4" LABEL="Raid10"
    /dev/sdc1: UUID="75760480-8ea4-45d1-9068-f2eca417cbda" TYPE="ext4"
    /dev/sda5: UUID="524a94b7-536c-4c53-8e1a-172a25e13ac4" TYPE="swap"


    My fstab look like this:



    is it right if I delete line
     [color=#FF0000][/color]/dev/sdb1 /media/usb0 auto rw,user,noauto 0 0[color=#FF0000] [/color]


    and put a new line at the end like this:


    UUID="2ee5aa4b-5279-4ac9-ba47-b89982c40585 /media/UUID="2ee5aa4b-5279-4ac9-ba47-b89982c40585 ext4 defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0 0 2


    Sorry for my English.


    EDIT: I did it and it is runs properly.

    I have trouble with my raid10. I dont know how but it seems my raid10 is broken and i dont know how to repair it (if there is any chance). my problem raid is /dev/sdb


    the output from

    Quote

    fdisk -l



    outpout from

    Quote

    blkid

    is:


    Code
    /dev/sda1: LABEL="Raid10" UUID="203d4f4e-02ae-4698-8bc9-04d55006d7d9" TYPE="ext4"
    /dev/sdb1: UUID="2ee5aa4b-5279-4ac9-ba47-b89982c40585" TYPE="ext4" LABEL="Raid10"
    /dev/sdc1: UUID="75760480-8ea4-45d1-9068-f2eca417cbda" TYPE="ext4"
    /dev/sda5: UUID="524a94b7-536c-4c53-8e1a-172a25e13ac4" TYPE="swap"


    output from

    Quote

    fsck /dev/sdb




    is there a chance to get my data back?

    If I want to install openmediavault-pxe with: apt-get install openmediavault-pxe then I get this:


    Die folgenden Pakete haben unerfüllte Abhängigkeiten:
    openmediavault-pxe : Hängt ab von: openmediavault-dnsmasq ist aber nicht installierbar
    E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte Pakete.


    What can I do?

    ls -al /etc/monit/conf.d/:


    drwxr-xr-x 2 root root 4096 Sep 20 20:09 .
    drwxr-xr-x 5 root root 4096 Sep 14 12:34 ..
    -rw------- 1 root root 194 Sep 20 20:09 openmediavault-collectd.conf
    -rw------- 1 root root 228 Sep 20 20:09 openmediavault-engined.conf
    -rw------- 1 root root 1093 Sep 20 20:09 openmediavault-filesystem.conf
    -rw------- 1 root root 295 Sep 20 20:09 openmediavault-netatalk.conf
    -rw------- 1 root root 194 Sep 20 20:09 openmediavault-php5fpm.conf
    -rw------- 1 root root 198 Sep 20 20:09 openmediavault-rrdcached.conf
    -rw------- 1 root root 198 Sep 20 20:09 openmediavault-shairport.conf
    -rw------- 1 root root 23 Sep 20 20:09 openmediavault-system.conf

    I have uninstall shairport because I dont use it. Now I have this messages in my syslog:


    Sep 21 18:03:29 OpenMediaVault monit[3874]: 'shairport' process is not running
    Sep 21 18:03:29 OpenMediaVault monit[3874]: 'shairport' trying to restart
    Sep 21 18:03:29 OpenMediaVault monit[3874]: 'shairport' start: /etc/init.d/shairport
    Sep 21 18:03:59 OpenMediaVault monit[3874]: 'shairport' failed to start
    Sep 21 18:04:29 OpenMediaVault monit[3874]: 'shairport' process is not running
    Sep 21 18:04:29 OpenMediaVault monit[3874]: 'shairport' trying to restart
    Sep 21 18:04:29 OpenMediaVault monit[3874]: 'shairport' start: /etc/init.d/shairport
    Sep 21 18:05:00 OpenMediaVault monit[3874]: 'shairport' failed to start
    Sep 21 18:05:01 OpenMediaVault /USR/SBIN/CRON[22197]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
    Sep 21 18:05:30 OpenMediaVault monit[3874]: 'shairport' process is not running
    Sep 21 18:05:30 OpenMediaVault monit[3874]: 'shairport' trying to restart
    Sep 21 18:05:30 OpenMediaVault monit[3874]: 'shairport' start: /etc/init.d/shairport
    Sep 21 18:06:00 OpenMediaVault monit[3874]: 'shairport' failed to start
    Sep 21 18:06:30 OpenMediaVault monit[3874]: 'shairport' process is not running
    Sep 21 18:06:30 OpenMediaVault monit[3874]: 'shairport' trying to restart
    Sep 21 18:06:30 OpenMediaVault monit[3874]: 'shairport' start: /etc/init.d/shairport
    Sep 21 18:07:01 OpenMediaVault monit[3874]: 'shairport' failed to start


    How can I fix it?
    Thanks for your help.

    I have a N40L with 4 HDDs, 2 HDDs as a raid and the other 2 HDDs as a raid too. Both raids are in a LVM as 1 drive.


    If I want to make an update to OMV 1.0 with a fresh install with Debian Wheezy Net-Install and install OMV on it, are all my data lost? Or is it no problem for OMV when I install the LVM plugin again to find my data? Because i crashed my OMV-Install via apt-get to update to 1.0


    sorry for my bad english

    Is it possible to move /var/www/openmediavault to /var/www/openmediavault/openmediavault und put a new index.html in /var/www/openmediavault with a link to /var/www/openmediavault/openmediavault without any problems?

    Hallo


    Ich habe folgendes Problem: wenn ich in der minidlna.conf Einträge verändere (vorher minidlna beendet) und dann minidlna wieder starte, wird der Eintrag, wo die Datenbank hin geschrieben werden soll, wieder zurückgesetzt. Die Datenbank wird dann immer im /tmp/minidlna geschrieben und nicht wie gewünscht in /var/lib/minidlna. Dadurch wird die Datenbank bei jeden Neustart des Servers neu geschrieben. Was kann ich dagegen tun?
    das Verzeichnis /var/lib/minidlna existiert und die Recht wurden mit chown minidlna:minidlna /var/lib/minidlna gesetzt.

    thank you. that was the problem. yesterday i read the same in an another forum.


    1. i stoped the minidlna service:

    Code
    /etc/init.d/minidlna stop


    2. i remove the files.db:

    Code
    rm /var/cache/minidlna/files.db


    3. i restart the minidlna service:

    Code
    /etc/init.d/minidlna start


    4. i restart the server
    5. minidlna rebuild the dadabase
    6. now it is alright.


    it seems so that when you forgot to stop the minidlna before you changing the minidlna.conf it comes to problems with inotify and the refreshing of the database file