RyanServer711

Members
  • Posts

    23
  • Joined

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

RyanServer711's Achievements

Newbie

Newbie (1/14)

3

Reputation

  1. I had to put in the actual IP and not the local host name. For example: http://192.168.x.x:8080 not qbittorrent:8080. Hope that helps.
  2. Figured it out, we need to add the path /var/run/docker.sock for both host and container, set as read only. (found in the youtube comments of the IBRACORP video) Just edit the Homarr container and click Add another Path, Port, Variable, Label or Device. Here is a pic of the inputs.
  3. I'm in the same boat, just saw the Ibracorp video and tried installing. I see the possible solution on this page. Homarr v0.8.0 (20th of July 2022) I assume we need to put in the command listed below into the container. I'm not super savvy on the deeper details of docker. -v /var/run/docker.sock:/var/run/docker.sock "Docker integration provides a simple way to start, stop, restart and delete containers. To get started, simply mount your docker socket by adding -v /var/run/docker.sock:/var/run/docker.sock to your Homarr container !"
  4. Crashed it, is there a recommended mount point? I just picked a folder in my backup share on my array. /mnt/disk1/backup/HATEST I'm going to try again
  5. Wait?!? Is the VM running out of memory? Isn't the default cap lower than 32G?
  6. This is what I have with the correct list command Device Start End Sectors Size Type /dev/nbd0p1 2048 67583 65536 32M EFI System /dev/nbd0p2 67584 116735 49152 24M Linux filesystem /dev/nbd0p3 116736 641023 524288 256M Linux filesystem /dev/nbd0p4 641024 690175 49152 24M Linux filesystem /dev/nbd0p5 690176 1214463 524288 256M Linux filesystem /dev/nbd0p6 1214464 1230847 16384 8M Linux filesystem /dev/nbd0p7 1230848 1427455 196608 96M Linux filesystem /dev/nbd0p8 1427456 67108830 65681375 31.3G Linux filesystem Also I did the dirty bit removal on this copy of qcow2
  7. I assumed they were lost in the corrupted qcow2. Either way I'm learning a very good lesson in backing up my stuff
  8. So loading a fresh install would have my backups in there? I thought they would be inside the corrupted qcow2? I've done regular backup within home assistant but I didn't think they left the VM unless specifically done so.
  9. I tried fsck /dev/nbd0p1 and received this message. fsck /dev/nbd0p1 fsck from util-linux 2.37.4 fsck.fat 4.2 (2021-01-31) Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. 1) Remove dirty bit 2) No action [12?q]? Should I go ahead and try to remove dirty bit? Thanks for the help btw 👍
  10. I did the first 2 commands and received this on the 3rd. fdisk -1 /dev/nbd0 fdisk: invalid option -- '1' I tried the first 2 again and received this message. I assume this means the first 2 commands worked. qemu-nbd: Failed to blk_new_open '/mnt/disks/00000000000000001358/domains/home_assistant/haos_ova-7.5.qcow2': Failed to get "write" lock Is another process using the image [/mnt/disks/00000000000000001358/domains/home_assistant/haos_ova-7.5.qcow2]?
  11. I had some issues with my server. Longs story short, I now have a seemingly corrupted qcow2 image file. Every time I try to use it it either doesn't load or crashes my system. Tried to copy it to my windows machine but it fails part way through. Is there any way to open it up or search through the files? I'm desperately trying to get my backups hidden inside and really don't want to start from scratch again. Any help would be greatly appreciated.
  12. Post realization....after I updated the bios, "Fast Boot" was enabled. That was the reason I had trouble restarting.