jbartlett
-
Posts
1896 -
Joined
-
Last visited
-
Days Won
8
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by jbartlett
-
-
14 hours ago, bonienl said:
This message comes from the mover plugin, pleas report it overthere.
Gotcha - I thought this was the built in functionality, I'll report it on the Mover Tuning plugin thread.
-
5 hours ago, Bolagnaise said:
I've just tried to run this as ive also had the server not boot after upgrade. Error shows UNRAID device not found on boot. Running the make_bootable file also shows error saying:
E:\syslinux\syslinux.exe -maf E:
Writing MBR: Access is denied.
Did not successfully update the MBR; continuing...Make sure your antivirus, Acronis Home, etc are disabled and ensure you have the prompt to run as Admin show up.
-
One thing to note is that the memtest86 that comes with UNRAID is an old version* - if you want the most recent, you have to download it from https://www.memtest86.com/ and create your own boot flash. Note that this version restriction placed by memtest86.
* At least this was the case the last time I used the tool, YMMV
-
4 hours ago, noties said:
Yes, ran a memtest on each of the RAM sticks individually. I was having BTRFS issues with my previous RAM and that sparked me to test the memory. I've not seen BTRFS errors since swapping out the RAM and the RAM passed memtest.
I changed a few things all at once and this seems to be biting me. I swapped motherboards, RAM, and upgraded to 6.9rc2. I had zero problems with my previous mobo, RAM and 6.8.3.
Note that the version of memtest built into UNRAID is a much older version that doesn't have the newer testing capabilities of the current version located on memtest's website. This is no fault of unraid, the people behind memtest won't allow anything newer to be installed by 3rd parties.
-
18 hours ago, Darksurf said:
I could be wrong, but IIRC Unraid is based on Slackware. The delayed release of 6.9 may have something to do with this magical announcement : https://www.itsfoss.net/slackware-linux-15-0-alpha1-release/
This is pure speculation on my part. I'm super happy and excited to see my first Linux distro is still alive and well! Thank you Slackware for being such an amazing distro over the years!I doubt they'd be considering putting Slackware 15.0 in the UNRAID OS until it's released as stable, it's not even in the beta phase yet.
-
48 minutes ago, bfh said:
Can the GPU be used for dockers then switched to VMs as needed, or is that not supported? I understand it would be difficult.
If that's not possible, is it possible to reserve one GPU for dockers and another for VMs?This is largely a case-by-case basis and depends on the motherboard, it's physical PCI slot to CPU/NUMA/device connections, and even BIOS version.
If you populate a video card in a given PCIe slot and it shows up in its own IOMMU group, you should be able to pass it to different VM/Dockers. If that is true for multiple PCIe slots, you should be able to populate all of those PCIe slots with a different graphics card and pass each one to a different VM/Docker.
In theory.
You can have many VM/Dockers set up to use a given video card but only one of those can be active at any given time.
-
22 hours ago, zer0zer0 said:
I rolled back to UnRAID version 6.9.0-beta35, and this issue is resolved.
I'm not sure what changed exactly, but it might be something to do with CPU microcode
The plugin "Disable Mitigation Settings" might help you troubleshoot that.
-
Changed Status to Retest
-
Fixed in RC1 on my system
-
I noticed this on the devices page when hovering over the reset icon. Is this a placeholder for future functionality or just a FYI?
Asking because I could have used this today.
-
2 hours ago, Richard Aarnink said:
Because I have an ITX board with 1 PCI slot which is already in use... Thus no slot available for an NIC board.
I wonder if unraid supports a USB3 NIC?
-
Changed Status to Open
Changed Priority to Annoyance
-
Checking the php behind the Docker settings, it does have a default value for it as "/mnt/user/appdata/" (good) in dockerconfig.php, line 20. However, in DockerSettings.page line 192, the placeholder tip does not include a trailing slash (cosmetic).
I edited the docker.cfg file to remove the trailing slash and rebooted, Docker started up without issue (reproducing original configuration)
-
That worked but note it I did not change any value since installing the 6.9.0 beta. It had the non-slash value previously and it was working (doing active dev against a docker).
This looks like a path check is needed on upgrading to 6.9.0+ to append a trailing slash if it does not exist.
-
As per the nvidia plugin install instructions, I disabled docker but when I tried to enable it, the "Default appdata storage location:" setting turns red and the change does not apply. The path exists. Rebooting does not allow it to enable.
Bug post created.
-
I switched my TR2 box back from Windows 10 bare metal (was trying to understand my use case was handling numa nodes) to unraid and gave b30 a shot with running a Win10 VM under a 24/7 CPU & YouTube streaming load - and other than the glitch I posted a bug thread about passing a graphics card, the VM has been running rock solid for a couple days now.
-
After changing the VNC port to the P2000, I edited the XML and removed this block
<graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='cirrus' vram='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video>
I then saved it and edited the VM again and switched it to the form editor. It still had VNC listed, probably by default. I changed it to the P2000 again and the change stuck.
-
My issue with not being able to see my graphics cards was that full IOMMU enumeration wasn't enabled in the BIOS. That is resolved but I still have only a blinking cursor in GUI mode. Updated diagnostics file attached
-
Booted into Safe mode, GUI - no change in behavior.
-
I'm having this same issue but I can remote in via the web gui. Diagnostic file attached.
I'm wondering if it's related to the fact that I don't see any of the nvidia cards in the web PCI list?
-
8 hours ago, Jaster said:
New Issue: I can't unpin CPUs from dockers. When I do so in pinning and I press apply, everything seems fine. After entering the pinning settings, everything is back to "as it was".
If I go into the container settings for the docker and change settings there, it persists.
There is already a defect for this. You may want to review and add any new details you have.
-
We haven't even hit the RC stage yet.
-
It was a Corsair RGB keyboard. It's a VM host that's gone live now with my 24x7 foster kitten cam and it's not something I can shut down to test this with. Sorry.
-
I believe the PCI bridge is the slot itself and not the devices connected to that slot.
Logrotate causes apcupsd to be restarted even if disabled in config.
in Stable Releases
Posted · Edited by jbartlett
I get this in my syslog every week.
Looking at /var/log, I see that apcupsd.events rolled over at 4:40 am at the same time.