Beiträge von Cissou

    it says :


    mdadm --assemble --force --verbose /dev/md127 /dev/sd[cdefgh]
    mdadm: looking for devices for /dev/md127
    mdadm: /dev/sdc is identified as a member of /dev/md127, slot 3.
    mdadm: /dev/sdd is identified as a member of /dev/md127, slot 0.
    mdadm: /dev/sde is identified as a member of /dev/md127, slot 1.
    mdadm: /dev/sdf is identified as a member of /dev/md127, slot 4.
    mdadm: /dev/sdg is identified as a member of /dev/md127, slot 5.
    mdadm: /dev/sdh is identified as a member of /dev/md127, slot 2.
    mdadm: forcing event count in /dev/sdd(0) from 35080 upto 35088
    mdadm: forcing event count in /dev/sdc(3) from 35080 upto 35088
    mdadm: added /dev/sde to /dev/md127 as 1
    mdadm: added /dev/sdh to /dev/md127 as 2
    mdadm: added /dev/sdc to /dev/md127 as 3
    mdadm: added /dev/sdf to /dev/md127 as 4
    mdadm: added /dev/sdg to /dev/md127 as 5
    mdadm: added /dev/sdd to /dev/md127 as 0
    mdadm: /dev/md127 has been started with 6 drives.
    root@openmediavault:~#

    hello after a reboot, omv lost my 6*2TB raid5.
    It doesn't appear in the web interface


    At boot it said that 2 drive were faulty, but the drive appear green in the web interface


    so

    • cat /proc/mdstat

    Personalities : [raid6] [raid5] [raid4]
    unused devices: <none>


    • blkid

    /dev/sda1: UUID="3abc1926-a277-4c6b-a4c1-e8fc9a4db381" TYPE="ext4" PARTUUID="a9d47ec6-01"
    /dev/sda5: UUID="ba395bad-8304-4088-8cbf-423a5570e3d9" TYPE="swap" PARTUUID="a9d47ec6-05"
    /dev/sdc: UUID="c42bd49b-4735-0adb-4252-69c01fec9ead" UUID_SUB="75769897-88a7-8f4a-2fa7-cbfedcbbf4ca" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
    /dev/sdb1: LABEL="NGS" UUID="c266f89c-ade1-4474-acb3-b06328d0c430" TYPE="ext4" PARTUUID="7d9760d7-cfc6-4234-89d6-183e289607cc"
    /dev/sdd: UUID="c42bd49b-4735-0adb-4252-69c01fec9ead" UUID_SUB="c8ada145-ff08-0c8b-62dd-e0d256e5bcaa" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
    /dev/sde: UUID="c42bd49b-4735-0adb-4252-69c01fec9ead" UUID_SUB="8361d72b-1bf4-a501-e97c-285ee2e72bff" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
    /dev/sdf: UUID="c42bd49b-4735-0adb-4252-69c01fec9ead" UUID_SUB="abe575c5-e310-7a7a-5419-eb0764b00054" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
    /dev/sdg: UUID="c42bd49b-4735-0adb-4252-69c01fec9ead" UUID_SUB="ba626cc6-4be5-7aee-503a-19f6f177f8ff" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
    /dev/sdh: UUID="c42bd49b-4735-0adb-4252-69c01fec9ead" UUID_SUB="281b8ef3-eff4-f085-9472-611ae4620f64" LABEL="openmediavault:NAS" TYPE="linux_raid_member"


    • fdisk -l | grep "Disk "

    Disk /dev/sda: 7,5 GiB, 8004132864 bytes, 15633072 sectors
    Disk identifier: 0xa9d47ec6
    Disk /dev/sdc: 1,8 TiB, 2000398934016 bytes, 3907029168 sectors
    Disk /dev/sdb: 279,5 GiB, 300090728448 bytes, 586114704 sectors
    Disk identifier: 9DDDBB99-C85E-48CD-BB9D-7849E4777D92
    Disk /dev/sdd: 1,8 TiB, 2000398934016 bytes, 3907029168 sectors
    Disk identifier: 0x00011257
    Disk /dev/sde: 1,8 TiB, 2000398934016 bytes, 3907029168 sectors
    Disk identifier: 0x0005e98b
    Disk /dev/sdf: 1,8 TiB, 2000398934016 bytes, 3907029168 sectors
    Disk identifier: 0x000a55a7
    Disk /dev/sdg: 1,8 TiB, 2000398934016 bytes, 3907029168 sectors
    Disk /dev/sdh: 1,8 TiB, 2000398934016 bytes, 3907029168 sectors



    • cat /etc/mdadm/mdadm.conf

    # mdadm.conf
    #
    # Please refer to mdadm.conf(5) for information about this file.
    #


    # by default, scan all partitions (/proc/partitions) for MD superblocks.
    # alternatively, specify devices to scan, using wildcards if desired.
    # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
    # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
    # used if no RAID devices are configured.
    DEVICE partitions


    # auto-create devices with Debian standard permissions
    CREATE owner=root group=disk mode=0660 auto=yes


    # automatically tag new arrays as belonging to the local system
    HOMEHOST <system>


    # definitions of existing MD arrays
    ARRAY /dev/md127 metadata=1.2 name=openmediavault:NAS UUID=c42bd49b:47350adb:425269c0:1fec9ead


    • mdadm --detail --scan --verbose

    nothing appears....

    if the second command is systemctl start sickbeard.service


    then
    systemctl status sickbeard.service -l
    ● sickbeard.service - SickBeard Daemon
    Loaded: loaded (/lib/systemd/system/sickbeard.service; enabled)
    Active: active (running) since dim. 2017-11-12 20:53:31 CET; 2s ago
    Process: 2058 ExecStart=/usr/bin/python /opt/sickbeard/SickBeard.py --quiet --daemon --datadir /var/opt/sickbeard/ (code=exited, status=0/SUCCESS)
    CGroup: /system.slice/sickbeard.service
    ├─2071 /usr/bin/python /opt/sickbeard/SickBeard.py --quiet --daemon --datadir /var/opt/sickbeard/
    ├─2091 /bin/sh -c "/usr/bin/git" fetch origin
    ├─2092 /usr/bin/git fetch origin
    └─2093 git-remote-https origin https://github.com/SickRage/SickRage.git


    nov. 12 20:53:31 openmediavault systemd[1]: Started SickBeard Daemon.

    I tried almost 20 times, then reboot, then no sickbeard at launch


    If i try to see some info :
    systemctl status sickbeard.service
    ● sickbeard.service - SickBeard Daemon
    Loaded: loaded (/lib/systemd/system/sickbeard.service; enabled)
    Active: failed (Result: timeout) since dim. 2017-11-12 20:50:40 CET; 5s ago
    Process: 1221 ExecStart=/usr/bin/python /opt/sickbeard/SickBeard.py --quiet --daemon --datadir /var/opt/sickbeard/ (code=exited, status=0/SUCCESS)


    nov. 12 20:49:03 openmediavault systemd[1]: Starting SickBeard Daemon...
    nov. 12 20:50:34 openmediavault systemd[1]: sickbeard.service start operation timed out. Terminating.
    nov. 12 20:50:40 openmediavault systemd[1]: Failed to start SickBeard Daemon.
    nov. 12 20:50:40 openmediavault systemd[1]: Unit sickbeard.service entered failed state.

    Hello all,


    I'm a teacher who want to teach to my student a server configuration


    They do :
    - creating the filesystem,
    - creating folder share,
    - creating user with some access right,
    - activate some service (FTP, SMB/CIFS, SSH),
    - create a videosurveillance with motion,


    at the end of the work session, I want to reinit omv in its fresh installation state.
    Do it manually is too long and I'll sure forgot some stuff to delete.


    I don't want to use a VM machine, cause I also teach them in the activity network wiring in real.


    I try omv-initsystem but does nothing


    Thanks
    Cissou

    hello,
    I try to update the openmediavault-omvextrasorg package but i have an error

    Code
    dpkg : erreur de traitement de openmediavault-omvextrasorg_0.5.38_all.deb (--install) :
     tentative de remplacement de « /usr/share/keyrings/deb-multimedia-keyring.gpg », qui appartient aussi au paquet deb-multimedia-keyring 2012.05.10-dmo4
    dpkg-deb: sous-processus coller tué par le signal (Relais brisé (pipe))
    Traitement des actions différées (« triggers ») pour « openmediavault »...
    Restarting engine daemon ...
    Updating file permissions ...
    Updating locale files ...
    Des erreurs ont été rencontrées pendant l'exécution :
     openmediavault-omvextrasorg_0.5.38_all.deb


    it's in french.
    the error is something like trying to replace « /usr/share/keyrings/deb-multimedia-keyring.gpg » which is in the deb-multimedia-keyring 2012.05.10-dmo4 package.


    i tried

    Code
    apt-get -f install

    with no luck
    i tried to remove then reinstall the package, no luck either.