Brydezen

Members
  • Posts

    119
  • Joined

  • Last visited

Recent Profile Visitors

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

Brydezen's Achievements

Apprentice

Apprentice (3/14)

0

Reputation

  1. I could not get it to even boot into legacy mode for some reason. It just kept telling me it's not a bootable device. So i'm giving up now. going back to 6.8.3 - don't wanna waste more time troubleshooting when nothing seems to help at all. Hopefully the next release will work for me.
  2. I might just redo the installation on try to go with legacy boot and see if that will fix anything for me.
  3. Pretty sure it's UEFI. I said yes to the UEFI option when running the make_bootable script. And made sure my boot order was using UEFI: General USB 1.0 or something. I do install all the virtio drivers the vm needs. But not 100% sure I have installed the guest agent tho. I might need to try and do that using vnc EDIT: I just tried installing the guest agent. It had no positive effect on the virtual machine.
  4. I just did a fresh install of unraid on my usb copied all the files over. Tried 5.1, 5.0 and 4.2 I still get the same result. Nothing seems to work for me.
  5. I have tried all the new machine types. And the 4.2 it was on when I ran 6.8.3. Don't seem to have any difference at all. I did see that in the announcement. I also had to reformat my drive for the 1MiB "alignment bug" as I was getting crazy read and writes for some reason.
  6. Weird. Maybe I will just reinstall my usb using the unraid tool. And transfer my settings files over. If not I will just downgrade I think. It's on my second day of troubleshooting.
  7. I have tried using the vBIOS. Both one I dumped myself and downloaded. Nothing works with that either.
  8. I recently updated from 6.8.3 to 6.9.2 - everything worked fine. But none of my virtual machines works when passing through any gpu to them. They just boot loop into windows recovery or just don't load up at all. I get the tianocore loading screen on my display just fine. But after that it either freezes or boot loops. I have tried many different things I could find in other threads but nothing seems to work for me. I have no idea what to do at this point. tower-diagnostics-20210412-1039.zip
  9. Hello. I just decided to take the jump to 6.9.2 today, as the threads seems to have slowed down on bug reporting. Everything worked just fine on 6.8.3. After the first reboot into 6.9.2 my main windows 10 vm was really slow. And I check the ssd and it seemed to have been effected in regards to the 1 MiB alignment "bug". So I moved everything from it and reformatted using unassigned devices plugin. And moved my vm's back. Everything seemed fine for around 30 minutes and it just crashed on me. The funny thing is that it works just fine using VNC. Their is no problems at all. Everything seems to work fine just up until the gpu driver seems to be loaded in windows. Then everything freezes or crashes. I have tried rebooting. removing the gpu from vfio and back in. Nothing seems to help me at all. - I then found this thread and followed the guide by removing all the gpu drivers using vnc. Added the gpu back in. Booted just fine into windows with display on my screens. Then when I tried installing the gpu driver it just crashed. And now i'm back to square one. I got a flash drive backup from before upgrading. So might just end up downgrading again. But I hope someone can help me out here. I get this line almost everytime I boot up a VM with my gpu passed through to it. Tower kernel: vfio-pci 0000:81:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 - not sure if this is intended or not. I have not seen it before. But could ofc be a 6.9 thing. Best regards, Brydezen tower-diagnostics-20210410-2236.zip
  10. Hello, when I turned on my server this morning nothing seemed wrong at first. But when I went in to check the unraid web interface it had a red X by the parity disk. And says it's disabled. Have read some other threads, saying that their device might be offline since. They could not perform any SMART tests. But mine seems to do it just fine. So I decided to run a parity check. And it just passed without any errors. But still reports as disabled. What should I do about it? Best regards, Brydezen tower-diagnostics-20200409-1950.zip
  11. What about downgrading maybe? Don't like the idea of running the newest release candidate. It's just weird that it all of a sudden happens out of nowhere. But two CPU's in the log CPU 11 & 8 are all pinned to my windows 10 VM I use as my daily driver. Could it maybe be the VM that is causing the kernel bug or maybe a plugin? I seems to happen more and more frequently now. Just had another one this morning. Have not logged at the log yet. As I'm currently out of the house now. But thanks for the response. And again, are you sure that it can not be caused by a plugin or my VM? Will try and switch up the CPU pinning for it. Best regards!
  12. Hi @John_M I did as you said and "just" catched a bug in the syslog from when my server crashed. it's at 19:48 - my VM was stuck at that time down in the corner. And the log says: BUG: unable to handle kernel NULL pointer dereference at 0000000000000030 at line number 5 BUG: unable to handle kernel NULL pointer dereference at 000000000000066c at line number 43 I have my newest diagnostics file and my syslog from the flash drive. As the syslog in the diagnostics zip is not reflecting the "bug" tower-diagnostics-20191109-2016.zip syslog
  13. BUMP. I'm still having this issue I have no clue what to do. How can I do a clean install of the unraid server and still keep my parity drive and array in sync? This seems to be the only thing I have not tried now.
  14. I have recently ran into a weird issue I can't explain or fix. All of a sudden my server just randomly freeze up for good. Can't move the mouse use the keyboard, the web interface for unraid is also unresponsive and even when I hit the power button nothing happens. I have to press and hold the power button for a hard shutdown and then power it up in order to use the server or any VM's again. And I got no clue why this problem just apperead out of nowhere. I have not changed any settings recently. I have uploaded my diagnostics file in hope that someone can spot the problem tower-diagnostics-20191025-1252.zip
  15. I only have one user named lol and the password is also lol. Does it only work if the username is admin? EDIT: I just tried doing the auth in a new browser (firefox) and it worked flawlessly. But chrome seems to mess me up.