The Fantastic Loki

Members
  • Posts

    12
  • Joined

  • Last visited

About The Fantastic Loki

  • Birthday 04/13/2001

Converted

  • Gender
    Male

Recent Profile Visitors

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

The Fantastic Loki's Achievements

Noob

Noob (1/14)

0

Reputation

  1. So I have a problem where my vm's will constantly have incomming connections randomly time out with no rhyme or reason. Even brand new fresh ubuntu vm. I can ping basically everything just fine from inside the vm with no problems, but connecting to the vm via ssh or pings gives constant timeout issues. I can connect and ping and such the unraid box and all docker containers fine it's limited to vms. Here is an example ping: >ping -n 20 192.168.1.129 Pinging 192.168.1.129 with 32 bytes of data: Request timed out. Request timed out. Reply from 192.168.1.129: bytes=32 time=2ms TTL=64 Reply from 192.168.1.129: bytes=32 time<1ms TTL=64 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 192.168.1.129: bytes=32 time=1ms TTL=64 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.1.129: Packets: Sent = 20, Received = 3, Lost = 17 (85% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 2ms, Average = 1ms I have tried changing the network model from originally using virtio-net to virtio at the suggestion of someone else but still didn't fix. Changing to e1000 killed the networking of the main vm I used and I had to start a fresh vm on virtio to get networking back but cannot recover by any means the networking of the first vm. This is essentially a fresh ubuntu install so nothing should be causing problems making me think it could be something I did routing wise but all commands I try via chatgpt haven't pointed me to any issues other than i noticed a shim-br0 network with the same ip and stuff as br0. I vaguely remember trying some commands to enable communication between certain networks and vlans and I think maybe that could be the cause of these issues but for the life of me I cannot remember what commands they were or how to undo those changes. If anyone has any ideas on where I can check or what to do please let me know I'm really at a loss and I have to get this fixed soon.
  2. It did fix itself but tbh that's the worst kind of fix since I have absolutely no idea what was wrong but hey at least it's working now.
  3. Hello I set up this container a little bit ago and it was working fine, had it secured over a tunnel. Now I am having an issue where nginx is timing out no matter what I do even RIGHT after a restart of the container. Can you possibly help me. I am forwarding through the container name and port but I also tried viewing the localip webgui and that won't even load. Any ideas?
  4. I did that before formatted the drive and yes that's exactly what had happened the old drive was from when it was my little sisters computer and the ssd was from when I gave it to my little brother so they both had windows installs but the boot loader was on the hdd also it didn't work still couldn't boot from windows afterwords.
  5. So intresting developement... can't boot from ssd without the other hard drive plugged in that I had unplugged while testing unraid since running out of sata cables. just formatted the old drive and plan on running the windows 10 installer in the vm to try and fix the issue and hopefully not lose a ton of stuff.
  6. I got the parrot vm to install by just wiping the entire disk and letting the installer do it all for me instead of making the partitions myself but still can't get the other vm with drive passthrough to boot. it has windows installed on it already from before I started using unraid.
  7. 1. This worked somewhat where I could get the drive to show using it's gparted in the live instance but now I get this error on installation: 2. You mean like this cause this also gets stuck on booting from hard drive.
  8. I tried this and it boots to the installer yet the drive still fails to show inside installer so I can't actually install the os. I'd also like to figure out how to just boot straight from a drive so I can implement unraid into my Main Rig, But it just gets stuck at booting from hard disk. and I see no option for where to provide the virtio iso so those can get installed or whatever.
  9. I tried gparted but then it always tries to boot straight to the drive and not the installer. idk why yet and I did what you said for the converted disk and got it to say booting from hard drive but it just stays there and never boots and doesn't throw any errors in vnc view or in logs. does the same thing when trying to boot straight from a drive passed through to a vm (need this to transfer main setup to unraid.
  10. 1. no idea how to install the virtio drivers properly and 2. I already did that for a fresh linux install I already explained the bulk of the problem in the first post which you obviously didn't read fully.
  11. Please forgive spelling errors and lack of information I'll provide as much info as needed when requested but I'm running on 28 hours of conciousness & on 3 hours of sleep at time of post.
  12. Hiya, I'm a brand new UNRAID user looking into using unraid as my main computer setup. I have UNRAID setup on another machine for testing before I purchase a license and have figured out how to setup a basic NAS for my home network but I cannot get any vm to install or boot if I try to import say an existing drive or hyper-v VHD (Converted to raw vDisk.img using QEMU-IMG) When I attempt to install a linux os wether linux, arch, or ubuntu it cannot mount /dev/sda on /media with outcome invalid argument. This I think is what causes the drive to not show up for install location/partitioning. I have followed MANY tutorials and threads to try and get this working including the very common mistake of typing GB instead of just G which can cause such mounting errors. This was also all done on latest stable version 6.9.2 I will provide my vm XML files in pastebins below there corrisponding screenshots. Screencap when booting from converted VHD: XML: https://pastebin.com/T3C5ZdEz Screencap when loading linux distro installer: XML: https://pastebin.com/dsaAd8Jd