Posts by e36Alex

    Hello,


    again i got the same problem like in this already solved thread. last months it happend from time to time, but i could solve it by doing the discribed steps again.
    Clean, degraded Raid (Mirror)


    but today it doesnt work, because i cant umount the raid. i get this error-message:

    Code
    root@HomeServer:~# mdadm --stop /dev/md127
    mdadm: Cannot get exclusive access to /dev/md127:Perhaps a running process, mounted filesystem or active volume group?

    of course i tried to umount the raid before without getting a error-message - but the raid is still mounted.


    even these commands dont bring up a result:



    Code
    root@HomeServer:~# lsof /dev/md127
    root@HomeServer:~# fuser -m /dev/md127

    can you help me to get the raid unmounted?


    thanks, alex!

    yes, this is the board i use for my omv...


    plex is already running on my tv, thats not the problem - the problem is, that iso-images are not supported by plex, but by kodi - and i am not interessested in converting my ripped movie collection again.

    Hello,


    at the beginning my litte homeserver-nas was just used for storing of data. now i would like to use it as well as a media player. the server is located in the next room, but connected with a hdmi-cable to the tv.


    my first thought was to use plex for streaming media to the tv, but plex doenst read iso's. so i am actually thinking of using kodi as media player. my question now is, how to install a desktop environment on the omv4 installation to use kodi.


    would be great, if you could help me!


    thanks, Alex

    but there are these "new" warnings:

    i think there is no change in this error-message:

    thank you, i tried it out but the reason isnt clear for me. i get some warnings and some errors in both cases. the only difference i coult recognize ist the following error:


    Hello,


    i actually got a strange browser behavior i could need your help at.


    when i want to open the webgui in firefox by the ip-adress i get a almost empty page, just with the omv logo.
    opening the webgui by calling the domain homeserver.local works as usual.
    even calling the ip in other browsers like edge or safari on my mobile is no problem.


    so i think its a problem of the firefox. i cleared the cache, deleted the cookies, but i still can not open the webgui by entering the ip-adress.


    do you have any ideas?


    thanks,
    alex

    Problem: I mounted the drive using the command line or GUI tool and I can't pick that drive in the shared folder device dropdown.
    Solution: Never mount a drive with anything other than the OMV web interface. This creates the necessary database entries to populate the device dropdown.

    Is there a solotion for the oppsite of this problem? i "lost" a hdd and now have the problem that there is a entry of a filesystem that isnt avaible any more. i cant delete it, because i get an error message, that a special device isnt avaible. editing the fstab doenst help.


    seems like its working.....


    great! thank you very, very much! especially for beeing so patient...!


    Code
    root@HomeServer:~# cat /proc/mdstat
    Personalities : [raid1]
    md127 : active raid1 sdc[3] sdb[2]
    2930135488 blocks super 1.2 [2/1] [U_]
    [>....................] recovery = 0.6% (19746304/2930135488) finish=300.5min speed=161367K/sec
    bitmap: 6/22 pages [24KB], 65536KB chunk
    unused devices: <none>

    great! the raid is back again..... until a few seconds ago, i was a kind of nervous... thank you!


    but it is still degraded:


    so it is sdd1?


    Code
    root@HomeServer:~# fdisk -l /dev/sdd1
    Disk /dev/sdd1: 465,8 GiB, 500106796544 bytes, 976771087 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes

    ok - i tried it out - none of the drives are shown:


    oh... ok............


    after the first command i get this - should i wait until it is assembled or should i go on with the next command?


    Code
    root@HomeServer:~# mdadm --stop /dev/md127
    mdadm: error opening /dev/md127: No such file or directory

    ok, and what is the next now?


    Code
    root@HomeServer:~# umount /dev/md127
    root@HomeServer:~# mdadm --stop /dev/md127
    mdadm: stopped /dev/md127
    root@HomeServer:~# mdadm --assemble --force --verbose /dev/md127 /dev/sd[ab]
    mdadm: looking for devices for /dev/md127
    mdadm: Cannot assemble mbr metadata on /dev/sda
    mdadm: /dev/sda has no superblock - assembly aborted