Everything posted by kana
-
[Support] SpaceinvaderOne - Macinabox
I cannot second that. I run Big Sur on my Bare Metal Ryzen 5600X, and it's rock solid. A virtual machine, once configured correctly, shouldn't be worse. However, all the reports here of the issues with the new MacInABox version have convinced me I rather wait with my VM installation until that has settled.
-
Kernel Panic
I'm running 6.9.0-rc2 and I regularly (after a few hours) and reproducibly get a kernel panic. That even happens when no share is mounted on any external computer, so it's unlikely that any share services have to do with this. However, it is possible that the parity check is running at that time. Usually the connected monitor is blank, but this morning it showed the last log output on the screen which I attached. Is there anything in the log that catches your eye? BTW, I found out only this morning how to enable the syslog mirror on the flash which I activated, so I'm hoping to get more information soon. Update: attached diagnostis zip file unraid-diagnostics-20210106-1127.zip
-
ssh Permission Denied after MB/CPU Upgrade [solved]
Ouch, that easy.. I don't have any (the nerd tools is the only plugin whose description shows ssh*, but that shouldn't count). Seems I'm stuck now.
-
ssh Permission Denied after MB/CPU Upgrade [solved]
Same problem, no solution here yet. The delete /boot/config/ssh part is clear, but what are ssh plugins and how would I delete them? I'm on 6.9.0 beta 35.
-
[Support] Gitea
My data storage path indeed points correctly to /mnt/user/appdata/gitea, but I still see the same issue, all context is gone after an update. When I look in /mnt/user/appdata/gitea/gitea, I see gitea.db which has not changed for 16 days now (I made approximately 10 updates in that time), and inside the "sessions" folder I see several folders with time stamps all before my today's commit, some are several days old, so the data itself seems to be persistent. Looks like gitea loses the ability to access that data with every update. Can the reason be that I'm using unraid 6.9.0-beta35 rather than the official version? Oh, btw, the command section of the Gitea update windows shows me "root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='Gitea' --net='bridge' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -p '3022:22/tcp' -p '3000:3000/tcp' -v '/mnt/user/appdata/gitea':'/data':'rw' 'gitea/gitea' da7e22c307253a32b7c2a0121a80a97ccba831315ec2a698d56cb8f678077d12 The command finished successfully!" The reference to the appdata folder in there looks ok, I see no indication the update itself screws things up.
-
[Support] Gitea
I recently installed Gitea. This container seems to be upgraded every day, and with every update, Gitea gets installed anew, so the users and repositories, everything is gone. Do I have to backup/restore it manually before every update?
-
unRAID 6 DevPack - Dev tools (gc, gcc, glib, make, etc.)
Is there no more support from dmacia for this plugin? I'm having the same issue for several weeks now (I'm on the Unraid beta). Aas for the reddit post: there is one post deleted, is it right to assume the did something with pihole? I do not have pihole installed, so it can't be that in my system.
-
No Internet, but can be accessed locally
"Not specifying multiple default gateways", what you are actually suggesting, is exactly what my command line accomplishes by deleting superfluous ones, so why do you call it wrong? Besides, regardless of the issue at hand, the GUI in general seems to have a bug that prevents you from deleting routing entries, for that, my proposed command is a working way indeed and thus not wrong. [EDIT] Sorry, now I got you, you were referring to 905jay's screenshot with still two gateways in it and not my suggestion. Never mind... @905jay I'm pretty much a beginner myself, so I think @ken-ji 's suggestion to have only one default route in the system and specific routes for the others is perfectly sufficient and does the job.
-
No Internet, but can be accessed locally
I've had the same problem. Try the command line to delete it. This command may or may not be right, you might have to play around with it: ip route del default via 10.15.83.1 dev br2
-
No Internet, but can be accessed locally
I had similar problems that were due to wrong routing using more than one NIC. Can you post a screenshot of the bottom part of the network config with the routing? What exactly do you see when you ping/traceroute out? Is there a difference between IP adresses and host names?
-
[Support] SpaceinvaderOne - Macinabox
Ok, it was not obvious to me that this is a restriction in Unraid and not in MacInABox. Will do! [update +15min]: the Forum is "Feature Requests". You are welcome to add your thoughts about impact, possible solutions etc.
-
[Support] SpaceinvaderOne - Macinabox
That brings me to a fundamental question: apparently, the GUI and the XML way to configure the VM are conflicting. When reading this thread, I realize that this regularly causes problems for many new users (I fell for it, too). So why not try to fix this? I see three ways: 1-update the GUI configuration in a way that it does not screw up the XML and rather write the correct settings in the XML 2-abandon the GUI in favour of the XML editor 3-the other way round, abandon XML and go for the GUI While 3 is probably not an option as every little config bit had to be reflected in the GUI, 2 seems to be a reasonable way, at least temporarily. And we wouldn't lose much as for (virtually all?) settings you currently end up in the editor anyway.
-
unRAID 6 NerdPack - CLI tools (iftop, iotop, screen, kbd, etc.)
Is it possible to suggest a new tool here? If so, I'd go for convmv: https://www.j3e.de/linux/convmv/man/
-
[Support] SpaceinvaderOne - Macinabox
Ok, this one solved itself after I had restarted Unraid. But now the VM is stuck and just shows the Apple logo when I VNC it. I can't stop it either, when I choose the menu entry, I get the green wheel, after a few seconds the green triangle, all the time saying "started".
-
[Support] SpaceinvaderOne - Macinabox
Hi, I installed the VM as described, however, on first run I get an error saying "Execution error, Cannot get interface MTU on 'virbr0': No such device". In another Win 10 VM, I also have virbr0 as networking card. Any idea what I can do?