Posts by Berti

    Hi. Wenn ich über OMV-Extras, Kernel, das CloneZilla einmalig starte und dann über das Terminal mein Backup erledige, habe ich momentan das Problem, dass nach Beenden des Backups und dem Reboot nicht das OMV5 wieder startet, sondern immer wieder das CloneZilla. Ich muss dann Notgedrungen Bildschirm und Tastatur am Server hängen und manuell OMV5 starten und den Bootkernel wieder als Standard-Bootkernel festlegen. Ist das ein Bug oder mache ich da etwas falsch?


    Hi. If I start the CloneZilla once via OMV-Extras, Kernel and then do my backup via the terminal, I currently have the problem that after the backup and reboot have ended, the OMV5 does not start again, but the CloneZilla again and again. I then have to hang the screen and keyboard on the server and start OMV5 manually and set the boot kernel as the default boot kernel again. Is this a bug or am I doing something wrong?


    LG Berti

    Hi.


    Also..... Platte einbinden mit bestehenden Daten geht. Die Platte einfach abziehen im laufenden Betrieb ist nicht so tolle, wenn man bedenkt, dass Du von einem NTFS-System sprichst. Vorher ein umount oder wenigstens ein normales herunterfahren wäre schon angebracht. Ich rede prinzipiell von Ext4- oder BTRFS-Systemen. Das sind dann schon gewaltige Unterschiede. Ja ich weiß. als normaler Anwender haben die wenigsten einen Linux-Rechner parat. Aber einen alten Laptop wirst Du doch bestimmt in deiner Bekanntschaft auftreiben können. Schmeiß dort ein Debian mit einem Desktop drauf und du bist glücklich :-) und dort kannst du dann auch die Platten auslesen. Ich schlage mittlerweile jeden vor, der mit Linux arbeitet, keine NTFS zu nehmen. Soll die Windows-Schei...... auch dort bleiben^^




    LG Berti

    Hi. I installed Debian Buster and fetched and set up OMV5 using script. User created, network card on fixed IP, etc. ... The usual. Now my problem.
    All shared folders created cannot be displayed under / sharedfolders in MidnightComander. The main folder / sharedfolders is there, but not a created folder is shown there. I log in as root in the terminal. Theoretically, this cannot be the reason. I first used a Samsung stick as a data plate. To rule this out as an error, I also used a small 60GB SSD. The same problem here. I can now also exclude btrfs as a source of errors, because nothing else happens under ext4.


    Current setup: System is on the 16GB internal memory of the Atomic Pi on ext4. The data disk, a 60GB SSD, also ext4.



    Version: 5.5.5-1 (USUL)
    Processor: Intel (R) Atom (TM) x5-Z38350 CPU @ 1.44GHz
    Kernel: Linux 5.4.0-0.bpo.3-amd64



    Can someone maybe give me a tip on how to progress?



    Created folders in OMV are available, Samba release also works, only in Debian under / sharedfolders there is nothing to see ...


    Clipboard01.jpg



    Best regards



    Berti

    h2testw


    Achtung: Nur 14859 von 14860 MByte getestet.
    Fertig, kein Fehler aufgetreten.
    Sie können die Testdateien *.h2w jetzt löschen oder nach Belieben
    nochmals überprüfen.
    Schreibrate: 9,58 MByte/s
    Leserate: 76,3 MByte/s
    H2testw v1.4


    Warning: Only 14859 of 14860 MB tested.
    Done, no errors occurred.
    You can now delete the test files * .h2w or at will
    check again.
    Write rate: 9.58 MByte / s
    Read rate: 76.3 MByte / s
    H2testw v1.4



    But installing it again on this card brought the same error again. And I can't imagine Balenaetcher shooting the card. In any case, it works with the Samsung Evo.



    Berti

    Problem solved.


    We would have an article for the "times" again. The Kingston SD Card, although NEW, caused this error. A second card (original package) from this manufacturer also caused the error. Whatever is with these things - it's not good.


    With my "Samsung Evo", luckily still found, everything is going well. The simplest things are on hand, the problems are always in front of the PC or sometimes are in the hardware :-)



    Thank you @ryecoaaron, thank you @macom for your help.



    Berti

    Well, unfortunately I don't have the error as a screenshot. But I can say that with the error message the yellow bar "try again" or "restore" always comes back. Even if I ignore the error and open the browser window again, the yellow bar jumps at me immediately. And things are not taken over either.



    I will then do the upgrade again. then i can post the error. Before that, I quickly install raspian on another sd card (I just found an originally packaged evo. 64GB) and do the upgrade immediately after the raspian installation. Let's see if the script goes through afterwards.



    Berti

    The SD card is new, but a cheap product from Kingston. Unfortunately the evo ran out. I have already ordered 10 pieces.


    To the OMV. Abstract: Everything that needs an additional confirmation, the yellow bar at the top of the screen, does not work. There always appears the error, where it is indicated in the last line that there is a salt problem. Unfortunately I didn't take any screenshots, but it is always the same mistake.
    The installation of extensions worked and docker. but that was almost the only thing.


    First example: Include drive in omv - salt error. Integrating a drive in the terminal works.
    Second example: creating a shared folder - salt error. I can create folders in the terminal.
    Third example: changing the port from 80 to 90 (I always do) - salt error.


    I did not test anything else, since I assume that this will go through everything that needs an extra confirmation from omv.


    Everything is going well at the moment. I just don't dare to upgrade.


    Berti

    I just set up the system for the fourth time. For the time being, of course, without the upgrade. Now a backup of the SD card. This saves a lot of time in further attempts. Just for info. I came across it by accident because I am soon to set up the OMV5 on the Raspi 3b + for a friend. I myself have been working with OMV5 for a long time, almost since the beginning of beta. Back then on the Raspi3, since the release of the Raspi4, I use it. There are no problems.



    Berti

    Unfortunately there is no error with apt-get upgrade. All of this is processed without errors. All functions in the terminal work. Only not in OMV.


    BErti

    Hi. Ich habe ein Problem, nach der Script-Installation am RaspberryPi 3b+ ein "apt-get upgrade" zu machen. Installiere ich OMV5 und richte alles ein und mache auch das "apt-get update", ist alles in Ordnung. Sobald ich ein "apt-get upgrade" mache, funktioniert in der Weboberfläche fast nichts mehr. Immer der gleiche Fehler, dass mit Salt etwas nicht stimmt, sobald ich Änderungen machen möchte. Auf dem RaspberryPi 4 habe ich diese Probleme nicht. Wenn ich ein dd-Systembackup auf dem RaspberryPi4 mache und die SD-Card mit dem Restore in den RaspberryPi 3b+ verwende, funktioniert auch alles. Nur hat nicht jeder einen RaspberrPi 4 daheim.
    Wo liegt der Fehler und wie kann ich diesen beheben?



    Ich habe Raspian-Buster-Lite-Netinstall installiert und dann folgende 2 Sachen installiert



    sudo apt-get install wget sudo



    sudo wget -O - https://github.com/OpenMediaVa…Script/raw/master/install | sudo bash



    Berti





    Hi. I have a problem doing an "apt-get upgrade" after installing the script on the RaspberryPi 3b +. If I install OMV5 and set up everything and also do the "apt-get update", everything is fine. As soon as I do an "apt-get upgrade", almost nothing works in the web interface. Always the same mistake that something is wrong with Salt as soon as I want to make changes. I don't have these problems on the RaspberryPi 4. If I do a dd system backup on the RaspberryPi4 and use the SD-card with the restore in the RaspberryPi 3b +, everything works. Only not everyone has a RaspberrPi 4 at home.
    Where is the error and how can I fix it?


    I installed Raspian-Buster-Lite-Netinstall and then installed the following 2 things


    sudo apt-get install wget sudo


    sudo wget -O - https://github.com/OpenMediaVa…Script/raw/master/install | sudo bash


    Berti

    Oder schaust einfach auf Technikaffe, wo Du die gleiche Frage gestellt hast, und siehst Dir meine Antwort an. Vielleicht wars das dann schon.


    LG Berti

    Restarting the server usually regulates.


    And you do the access rights with ACL. Select shared folder in omv, click ACL and read, write, execute other options. Click recursively. apply.


    Berti

    Did you maybe change the ports in OMV? Then you should also log in with the set port number. So the server-IP-address:port number. Otherwise, keyboard and monitor on the server, check the IP address with

    Code
    ip addr

    and maybe check error messages during the startup process. Entering omv-firstaid on the server can also help.







    Berti