bamhm182
-
Posts
67 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by bamhm182
-
-
I just noticed my Docker page was reporting the same issues. I didn't try to reboot my server and it has been up for nearly 20 days, while it was working fine last night. Going to settings => docker and disabling, then re-enabling didn't work. I couldn't find the `service` command. I don't know if that's a nuance of slackware or unraid or what, but running `/etc/rc.d/rc.docker status` reported it was stopped, then I ran `/etc/rc.d/rc.docker start` and it said it was started. I then ran `/etc/rc.d/rc.docker status` and it reported running. Everything seems to be working fine now. Not really sure what that was about... I attached my diagnostics in case anyone cares to look at it compared to the ones Pillendreher uploaded. If it happens agaiin, I'll probably spend more time looking into it, but for now, I'm good with leaving it at "computers are wierd".
-
Alright, so I managed to get back to where I had it before 6.7.0rc-1/2, and I think I figured out that it was crashing there because of how I had the IDs in my syslinux file. I currently have this:
append pcie_acs_override=downstream pci-stub.ids=<others>,12ab:0380 vfio-pci.ids=12ab:0380 disable_idle_d3=1 initrd=/bzroot,/bzroot-gui
Everything works fine until I go and attach the card to a VM and try to boot it. It says unknown pci header type 127 and hard crashes the computer after a few seconds. I tail'd syslog while this happens as requested in another post with this error and I'm thinking maybe the disable_idle_d3 part is what's getting me, but the guy who made the kernel patch said that was required. Either way, I'll try it without that part tomorrow.
-
So I'm running into a new issue now (after getting 6.7.0 to cooperate) for some reason if I boot while 12ab:0380 is in the ids, I can click all over the GUI, but as soon as I click on the VMs tab, unRAID hard crashes. I tried reverting to 6.6.6 and running the patched kernel that was working fine before I tried upgrading and now that is doing the exact same thing. All I should need to do to downgrade is copy the files in the previous folder back to /boot, right?
-
I went to go give it a shot with your suggestions and I noticed that rc2 was available. This worked without any problem. Then, as I come here to say that, it came back.
So, my computer was already set up as UEFI and I couldn't find anything in my bios about secure boot. I switched the drive to a USB 2 slot and it booted fine. I put it back to a USB 3 spot and it worked fine. I put my vfio-pci.cfg file back and it died. I removed that file, still dead. Out of all the modes, it seems to boot into safe mode w/o GUI pretty consistently. Either GUI mode seems to always die. Normal CLI mode is a hit or a miss.
EDIT: I may have just found the variable. It seems that when I have everything plugged in (mouse/keyboard to PCI USB card, dvi/HDMI to GTX970, Ethernet to 4 port pci nic, Ethernet to onboard, HDMI to onboard) then it dies. With HDMI/mouse/keyboard to onboard, it boots just fine.
EDIT 2: I'm wrong. I unplugged everything and slowly plugged things in one by one and rebooting hoping it would die eventually. I now have everything plugged in and no idea why it is doing this seemingly randomly.
-
I have 32 GB of RAM and a 32 GB flash drive plugged into an adapter plugged into the USB 3 header on my motherboard. I have tried to boot into each of the modes except memtest.
-
Is there any extra information I can provide to help get an answer to why this is happening since I can't exactly pull diagnostics?
I tried reverting to 6.6.6 and doing the upgrade again with the same results.
-
My install has been booting just fine, and then I upgraded to 6.7.0-rc1 from 6.6.6 and am getting the following when I try to boot from any of my options:
Loading /bzimage... ok
Loading /bzroot... ok
Loading /bzroot-gui... ok
exit_boot() failed!
efi_main() failed!
I have moved my vfio-pci arguments over to the new config file, but other than that, I haven't touched anything since the last reboot. I'm on UEFI. Any ideas? I'm going to go remove that config file and see if that helps any.
EDIT: It didn't change anything. Also, my syslinux.cfg file entry is as follows:
label unRAID...
kernel /bzimage
append pcie_acs_override=downstream initrd=/bzroot,/bzroot-gui
-
I didn't even catch that he probably just missed the 0. Haha. I thought he actually meant 6.7.9. Glad to hear it'll be released sooner than that. >_<
-
Changed Status to Solved
-
Will do. Thanks for all the help!
-
Been running my kernel for a few days with no issues. I'm going to close this.
In other news, still can't get this card to work, I even installed Windows baremetal on a spare disk, got the card working there, then copied the disk to an img. I booted that and it still told me to reboot to finish the driver installation. I feel like the programmers put that in there instead of "it isn't working and we don't know why." I think I'm going to stop trying to get this to work with unRAID and just dual boot windows and unRAID. No fault to unRAID, just this crappy card. Keep up the great work!
-
Thanks for doing that! I'm beginning to think the card is garbage as well. I have a little mSATA drive I'm not using, I may install that and toss Windows on there just to give it one final go before I send it back to Amazon.
I've just got one final question since I've been stuck on this for a few days. What's the proper way to extract and compile the bzroot file? All the information I can find suggests piping it from xzcat to cpio, but when I do that, xzcat complains about an invalid format. I was finally able to get it to do something with cpio -id < /boot/bzroot, but all that was extracted was a kernel folder. Is that all that's in there? As for compiling it, I never had any luck.
-
That is correct. The person who originally made the patch was using Arch, but he had a virtual machine running on Arch and ran into the same issues as we are running into now. Making these changes and a few in syslinux solved the reboot VM crash for him.
He modified his sysconfig to look similar to the one I have set up here:
label unRAID OS (Elgato Fix) kernel /bzimage-new append pcie_acs_override=downstream pci-stub.ids=<removed>,12ab:0380 vfio-pci.ids=12ab:0380 disable_idle_d3=1 initrd=/bzroot-new
EDIT: Making progress! I just took a moment to step back and think about the steps and realized that this whole time I've been trying to compile both bzroot and bzimage, but I haven't really been doing anything to bzroot, but extracting and recompiling it (wrong, I might add). I was replacing bzroot for no reason, so I used the bzroot that came with unRAID and the bzimage that I have been compiling, low and behold, I CAN REBOOT! There are some issues with the card still, but I think they may not be related. It's just weird, it prompts me to reboot to finish installing the drivers, but when I reboot, that message doesn't go away and the card still doesn't work. I'm wondering if maybe Windows isn't shutting down cleanly...
-
Haha, that's true. That is the gist where I found the code, yes. I have been working on a script that checks the unRAID, Slackware and Kernel versions, then goes out and downloads the appropriate packages and files and follows similar steps to gfjardim's gist and the one on the wiki. Only problem is they're both pretty old and this is the first time I've ever tried to compile a kernel. I managed to get rid of most of the negative sounding things, except for what looks like a few warnings when running the make. I finally managed to get a bzimage and bzroot that look pretty similar to the bzroot and bzimage that come with unRAID, but it was late last night and I was unable to test it. With that, I haven't been able to verify that it fixes the problem just yet, but it worked for the Creator of that patch once he also made a few changes to syslinux.
[6.9.0-rc2] Docker crashes "Docker Service failed to start."
-
-
-
-
-
in Prereleases
Posted
No problem. FWIW, I haven't had any issues since I started it manually. I haven't rebooted either.