Beiträge von totopesce

    For anyone that might have had the same problem, I has to do something called brain dead, i think, that means unplugging it from the power and disconmecting the battery, pressing the power button for a while to discharge anything that might still have power on the ups to reset it. After that I left it plugged by usb to my server connected battery then power and let it start again, after that omv recognizes it with lsusb and the plugjn installs no problem. Remeber to test to see if the ups powers the server down.

    Code
    nut-driver.service - Network UPS Tools - power device driver controller
         Loaded: loaded (/lib/systemd/system/nut-driver.service; static)
         Active: failed (Result: exit-code) since Mon 2023-10-09 11:14:25 -03; 50mi>
        Process: 337647 ExecStart=/sbin/upsdrvctl start (code=exited, status=1/FAIL>
            CPU: 13ms

    Thanks for the reply, I did an ip a and it had the right ip and while there I rebooted, and that fixed it. Never even thought about rebooting as I always do it through the GUI and didnt remember the command (it was reboot) and after the reboot it appeared as it should.

    Removed all previous network interfaces for the VM and added the bridge as the new one and now its working, can ping 8.8.8.8 and the VM and the omv server from each other.


    Thanks a lot for the help, forgot the basics if it doesnt work reboot.


    If I might though, in the wiki it could be the last step to reboot? Dont know if its necessary for everyone, but dont think it would hurt.

    Thanks again.

    Yeah, followed the guide completely stwp by step, did it twice and it gives the same error both times.

    Deleted the old interface

    Added the bridge

    Used the sam ip, netmask, gateway and dns

    Save the bridge interface and then confirm changes on the yellow box.

    After that I get no more access to the omv machine.

    Tried using omv-firstaid and a br0 appeared in the fix network interface option.

    Clicked that and followed all the steps and used the same settings as before and get the error at the end.

    I can use omv-firstaid to go back to the old interface with the same settings no problem.

    yeah chente said the same, but when trying to follow this https://wiki.omv-extras.org/do…0_bridge_interface_on_omv to add it when I finish all the steps I loose the gui and cant connect through ip ot hostname, also not able to ssh in.

    Tried fixing it through omv-firstaid, but I get this error https://imgur.com/a/WOkfxKs.

    I can go back to the old interface with no problem with the same settings I had before through firstaid, but havent managed to grt the bridge adapter working.

    I installed Home assisntant in a vm with the plugin in OMV, and wanted to get them to communicate to share UPS info the VM, but I cant manage to get them to connect or ping one another.

    I created the VM with bridge 0yA5zbWNMqvp, also read somewhere that adding a macvtap could fix it, but no dice.

    Both machines have separate ips in the router and able to ping the router and 8.8.8.8.


    What can I do to get them to communicate with each other?

    That did it!!!! I added this entry to the file /etc/openmediavault/config.xml

    run sudo omv-salt deploy run fstab , and now it appears in the filesystems. Rebooted and its still there.

    It had nothing to do with the disk being full most likely as I deleted like 500mb and what I did with the other disks didnt work.


    Thanks a ton ryecoaaron.

    Sorry about that grabbed the wrong code, this should be the mntent.


    Read here What is this crazy error? I'm stuck , that someone was running omv-salt deploy run quota and was throwing an error because the disk was full, but it seemed to had to do with that it couldnt write the quota because of lack of space, the command just seemed similar.

    This is the mntent now


    I believe it has more entries now, after doing omv-salt deploy run fstab I think it allowed me to mount most of the disks through the GUI.

    Now theres only 1 that I cant add, its also the hdd thats most full (I believe its completely full).

    I didnt add them manually, I could add 6 of the 7 hdd through the GUI, the last throughs the aquota error. The ones that worked I just has to go to mount and existing filesystem in the GUI and add them.


    Maybe it seems I added them manually because they came from an old omv4 install and Im trying to mount them with the existing data and filesystem?

    Tried ctrl-shift-r, also tried clearing cache and another browser, and no luck.



    Code
    sudo blkid
    
    /dev/sda1: LABEL="2T" UUID="107023e1-5a23-4dc5-a810-0f73fe6c778a" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="912281a0-24dd-4f6b-b590-f1ced6a1d772"
    /dev/sdb1: LABEL="HDD2" UUID="c4ea1ab6-6342-42ff-977f-cb7d3c834d4d" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="6ef735e2-1635-4251-ad42-ef03abe34bd0"
    /dev/sdd1: UUID="753e933d-d692-4250-9e16-89d7bd48f577" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="82fa39d1-01"
    /dev/sdd5: UUID="2a4d268a-2c87-4a29-86f2-6ac30b621a99" TYPE="swap" PARTUUID="82fa39d1-05"
    /dev/sdc1: LABEL="HDD" UUID="beb32fc3-68a4-49da-8c84-54b62e9fab74" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="83ca8f0a-bd75-48ba-b4f3-521c871fb989"
    /dev/sdf1: LABEL="Bck" UUID="b280838f-d6e0-4eb6-b13f-af3a5a5e1d8b" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="2817f573-be0e-4be6-a7a2-c00b6ebfcdf2"
    /dev/sdg1: LABEL="HDD3" UUID="aa3e040c-9f14-4c66-b232-997bab362f74" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="510dde00-b291-4b8a-93e7-54aff5087785"
    /dev/sdh1: UUID="0235a908-2725-4c2a-8a95-11de7b7ad68d" UUID_SUB="376c545b-f422-471d-b016-4c13a18445f6" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="922e4f78-c2d6-48c6-af92-720d3dcc8431"




    Thats the output off all the commands, will trying other stuff I did remove aquote from fstab so thats why it doesnt appear on these outputs.


    After that all but 1 disk could be mounted, that one throws the same error 500.


    Another fstab, it added aquota back to all the disks, though now only 1 is giving the rror, all others appear as mounted and in the list.

    Ive rebooted several times since, if they were mounted they should appear with the rest of the filesystems right? But they appear only in disks, but no in filesystems.

    Tried running mount -a -t ext4 , but nothing.

    If I try mounting the filsesystem I get that its already mounted, but still doesnt appear on the GUI or on the dropdown.

    Code
     mount -t ext4 /srv/dev-disk-by-uuid-beb32fc3-68a4-49da-8c84-54b62e9fab74/
    mount: /srv/dev-disk-by-uuid-beb32fc3-68a4-49da-8c84-54b62e9fab74: /dev/sdf1 already mounted on /srv/dev-disk-by-uuid-beb32fc3-68a4-49da-8c84-54b62e9fab74.

    I tried removing aquota from one disk, the one with less data in it, from fstab and removed all aquota files inside, but it still isnt appearing in the GUI.

    It appears as mounted and I can access it in /srv/dev/disk-by-uuid really long string/ , but I cant get it to appear in the GUI.