-
[Support] SpaceinvaderOne - Macinabox
Hi all, is there a recommended minimum for the primary vdisk for macos? How do you manage userdata? Ideally I would like to store data directly on an unraid share, is that practical? Thank you and kind regards, SnakeZZ
-
PSA on SanDisk USBs
For me, the above Link actually goes to a product called "Kingston DataTraveler Kyson USB-Stick USB3.2, 32GB" It seems to be a different product than the one mentioned ("Kingston DataTraveler SE9 G2"). Does anyone have experience if this is a good stick for Unraid?
-
6.11.5 No boot after Nvidia driver install [solved]
I got it running again by throwing all devices but the USB stick out of the boot sequence in BIOS. I don't know why this only came up now, it worked fine before, I didn't change the BIOS at all.
-
[Plugin] Nvidia-Driver
Me neither... But thank Flying-Spaghetti-Monster and Invisible-Pink-Unicorn, I got just it running again on the old stick. I had a lot of devices in the boot sequence in BIOS and threw out everything but the USB stick. That solved it. Very strange. Thank you very very much for your help... I posted a similar post before posting here in the General Forum, but got no replies at all đ
-
[Plugin] Nvidia-Driver
I had a second USB Stick lying around (bought 2 back in the day), so I used the USB Flash Creator and manually copied back the config folder. Unfortunately, I now get the same issue from that stick. Stuck on the blinking cursor again. Now I am a bit stuck... can my HW be faulty? It was running fine before. I have ECC RAM, so I suppose RAM shouldn't be an issue. Man.... this s*cks.
-
[Plugin] Nvidia-Driver
Deleting the plugin folder and .cfg didn't help. It directly goes in to a blank screen/blinking cursor after "Loading /bzroot". So... I guess something else is wrong with the stick... how do I recover from that? I've been running Unraid on a Supermicro CSE-848 for nearly 3 years now. Boot stick is a Kingston data traveler 16 GB - if that makes any difference.
-
[Plugin] Nvidia-Driver
Hi all I had the plugin and drivers working a while back, but upgraded to 6.11.5 a while back and didn't bother to install/reinstall the drivers again. In a state of temporary mental derangement, I clicked "Install latest driver" from the plugin page today and waited until I got the reboot message. Unfortunately, my system now won't boot anymore.... it only goes past "Loading /bzroot....", but then I only get a blinking cursor on an otherwise empty screen. What did I do wrong? How can I revert back to the state before, where at least my unraid was running smoothely? Thank you and kind regards, SnakeZZ
-
6.11.5 No boot after Nvidia driver install [solved]
Hello everybody, I used to run the Nvidia plugin a while ago (>10 months). Later, I did some Unraid Updates and didn't care to install the drivers again at that time, so I essentially didn't use it anymore. Today, I tried installing the NVidia driver through the plugin page again (by installing the latest driver). When the plugin asked me to reboot, I did so, but now the server won't come back up again. I can see the boot menu come up, and after 5 secs, I get Loading /bzImage... OK Loading /bzroot... and after that I only have a blinking cursor on an otherwise blank screen. Is there a way of going back to the previous, running state? I tried: booting in Safe Mode (no success) taking all GPUs except the onboard one out (didn't make a change) Thank you and kind regards, SnakeZZ
-
SnakeZZ started following [Support] SpaceinvaderOne - Macinabox , [Support] SAL-e - phpIPAM and VLAN/Docker
-
[Support] SAL-e - phpIPAM
When looking at the logs in phpipam cron, I noticed this: ERROR: https://dl-cdn.alpinelinux.org/alpine/v3.15/community: temporary error (try again later) Any ideas what this is and what to do about it? Thanks SnakeZZ
-
VLAN/Docker
Ich hab mal versucht, bei 2 Containern die gleichen IPs zu benutzen und hab einen Fehler bekommen. Das geht demnach nicht oder mach ich was falsch? Danke und Gruss SnakeZZ
-
VLAN/Docker
Hallo Zusammen, ich habe bei mir VLANs konfiguriert und ein VLAN 4 mit Interface br0.4 angelegt. Wenn ich nun ein Dockerimage mit br0.4 nutze, bekommt das die IP 192.168.4.2. Wie wird die IP vergeben? Eine DHCP Lease sehe ich jedenfalls nicht.... ?!? Hab ich das richtig gelesen, dass Docker kein DHCP 'kann'? Wo setze ich die IP fĂźr das Interface auf eine andere IP? Gruss, SnakeZZ
-
[Support] SpaceinvaderOne - Macinabox
Hello, I haven't updated the Macinabox Docker for ages (way before the "How to Install Big Sur and Other macOS Versions with New Macinabox" video came out). I am also running a Catalina VM I created a long time ago. I tried finding instructions on how to upgrade my existing VM, but with >2070 posts in this topic, I was unsuccessful đ Are there some instructions around somewhere? Thank you and kind regards, SnakeZZ
-
[Support] SpaceinvaderOne Deconz
Hi! The upgrade using 'marthoc/deconz:latest' works for me, even with VNC. Thanks, good stuff! SnakeZZ
SnakeZZ
Members
-
Joined
-
Last visited