Posts by Lord_Pinhead

    Did you follow this steps: https://www.dlford.io/linux-md…sk-replacement-procedure/

    Tbh how can you make a Raid 5 with only 2 disks and they are even different sizes? They have to be the same size and at least 3 for a Raid 5. I guess, you configured a linear aka JBOD and that "stripes" the data in series like LVM, but with less options. When this is the case, I fear the raid is partly dead and you have to remove the dead drive and lose all the data on it.


    Maybe post the Raid Details, here are mine and there you can see the raid level:


    Code
    # mdadm --detail /dev/md0 
    /dev/md0:
               Version : 1.2
         Creation Time : Tue Jan 31 18:30:53 2023
            Raid Level : raid5
            Array Size : 11720658432 (11177.69 GiB 12001.95 GB)
         Used Dev Size : 3906886144 (3725.90 GiB 4000.65 GB)
          Raid Devices : 4
         Total Devices : 4

    Das klingt nicht schlecht, Syncthing kannst du einen Port deiner Wahl verwenden, dann sind die Angriffsversuche geringer, wenn auch unbedeutend.
    Ich bin mir nicht sicher ob du wirklich dauerhaft möchtest das dein Smartphone sich mit der Node abgleicht, ich hab da meine Batterie sehr schnell sterben sehen. Das hängt auch damit zusammen, dass die Verbindungsaufbauten, je nach Internetverbindung, etwas länger dauern. Eine alternative evtl. weiter unten.

    Was die Sicherheit angeht, ich hab auf meiner OMV Büchse eine Syncthing Docker Instanz über Compose erstellt, zwei Volumes für Config und Data, und das war schon alles. Wenn jemand in Docker einbricht, ist er in einem extra Netzwerk, kommt nicht raus und das schlimmste was passiert, er bekommt meine Daten. Aber ich habe auch keine offene Internetfreigabe erstellt, sondern eine Wireguard Verbindung in meiner OpnSense (wenn du eine Fritzbox hast mit FW 7.30 oder höher, geht es auch dort), also ein VPN. Ist das Smartphone an einem Ladekabel angeschlossen dann gleicht es die Daten ab, sofern die Node erreichbar ist (ohne VPN eben nicht). Das spart dir Kopfzerbrechen wegen der Sicherheit.

    Oh boy, I was searching up and down the Linux Mailing List, but you have to switch to the Kernel either with upgrade or apt-get install linux-image-5.18.0-0.deb11.4-amd64 , after that, KVM will work fine again.

    It sounds like you have problems with the bootloader on the Microserver. Did you try to reinstall the grub bootloader on the SSD?


    And of course, look at the grub boot line, if you have the ssd id in there, you will never be able to boot. Clonezilla resets the ID on your machine, but it could be different on the microserver.


    Code
    # update-grub
    # grub-install /dev/sda #or what ever your system disk is


    I had this on different machines too, so it´s somehow common.

    Just for the sake of completion: Just download the newest Winrar.de for Linux and install it with the few steps below:


    A package is to much for just a few files.

    Wiping the drives has done the trick. Should the drives not be in the list with red background or something to make it clear that the drives at least where found? I have 12 drives now in the system and just 2 where not in the list. Even 2 old lvm drives and the VG's and LV's where found without problems and could be mounted.

    Hi,


    i played around in some virtual maschines with the configuration i am targeting and so far, i had no problem. Until i switched to physical hardware.
    When i install LVM2, i just see my 2TB HTST drive, the other 2 drives with 400GB and 500GB for the VM' s are not showing up.


    I added them with "pvcreate" and then i can use it normaly, but what is the problem with showing them? Can i log something outside of /var/log/ to get information why the drives does not show up?
    Even after a reboot they still are recognized. So it could be just a minor problem. Any suggestions?


    Regards
    Lord_Pinhead