Posts by hubertes

  • Again : bad disk, changed, no raid anymore

    Hi,


    sda was bad, changed it with a new one. Now Raid is inactive. I did dd the new one, tried --assemble or add, nothing work and in the gui table : no raid


    Code
    cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] 
md0 : inactive sdb[3](S) sdg[6](S) sde[8](S) sdd[0](S) sdf[7](S)
      8790425656 blocks super 1.2



    Code
    blkid
/dev/sdf: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="ce05af8c-7da1-c0a7-0a07-c10b0b154735" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sdg: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="440f9a88-1d42-020c-ba4d-d303afb76c7c" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sdd: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="b2460066-00b1-5070-cfe3-7ac67aae96c1" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sde: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="b243c911-8058-51ff-0413-31fb1528c36c" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sdc1: UUID="befea5ea-cd0e-4166-b3b0-6d2b79962bdf" TYPE="ext4" PARTUUID="54ca3768-01"
/dev/sdc5: UUID="cc9ca801-5eb7-4b50-9949-2102b786e751" TYPE="swap" PARTUUID="54ca3768-05"
/dev/sdb: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="ee7eab8f-dc90-e3be-146d-a4e09d104418" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sda: PTUUID="07a09a5d" PTTYPE="dos"




    Code
    mdadm --assemble /dev/md0 /dev/sd[abdefg] --verbose --force
mdadm: looking for devices for /dev/md0
mdadm: Cannot assemble mbr metadata on /dev/sda
mdadm: /dev/sda has no superblock - assembly aborted

  • plex, portainer and docker

    Quote from geaves

    You need to point it to the share under /srv/dev-disk etc that's the absolute path, then select bind not volume


    Dont see where, I had a lot of unused volume, deleted it, something linked to bad install I supposed.


    Dont see where to add volume to the share folder, and bind it.


    I tried to add volume and add "/sharedfolders/ShareName/Videos" but can't tell what to write for mountpoint.

  • Plex Docker update problem, no video playable

    Is it normal that the container upgrade multiple times ? Each time I make modification to the settings, I get :


    Code
    Attempting to upgrade to: 1.13.5.5291-6fa5e50a8
2018-08-05 12:04:39 URL:https://downloads.plex.tv/plex-media-server/1.13.5.5291-6fa5e50a8/plexmediaserver_1.13.5.5291-6fa5e50a8_amd64.deb [111469542/111469542] -> "/tmp/plexmediaserver_1.13.5.5291-6fa5e50a8_amd64.deb" [1]
Preparing to unpack .../plexmediaserver_1.13.5.5291-6fa5e50a8_amd64.deb ...
Unpacking plexmediaserver (1.13.5.5291-6fa5e50a8) over (1.13.4.5271-200287a06) ...

    EDIT :


    No OMV_FSTAB_MNTOPS_EXT4= in /etc/default/openmediavault


    I realy think it's not a plex related problem but more an OMV/DOcker problem because indeed, I can't run any transcode


    EDIT2 :


    solved here


    Some docker containers don't like it when fstab is noexec


    people developping this plugin should really add this in a guide :/


    I think I'm not the only one here who have experience this ?

  • Plex Docker update problem, no video playable

    I did all the things already ;) followed the manual


    Here is what I red,


    https://forums.plex.tv/t/pms-c…iled-to-start-up/227898/3


    And my Plex log


  • Plex Docker update problem, no video playable

    VERISON latest which I also tested already, same :



    Searchin why I get no token even if I'm loggued


    https://github.com/linuxserver/docker-plex/issues/100


    Edit : Tried with 1.13.5.5291-6fa5e50a8, no luck

  • Plex Docker update problem, no video playable

    Hi,


    I followed the guide and changed the INSTALL filed (but I think it was the right one), I did loggued once


    Still stuck on 1.13.4.5271 instead of 1.13.5.5291


    I cant' play any video though, seems a problem of transcode ? (but I prefer to update first)


    Thanks