BeardElk
-
Posts
148 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by BeardElk
-
-
Okay, so my USB drive just shat its fucking pants.
Its deteriorating quckly.
Anyone got a recommendation for a known Good usb drive???Don't know if I just got a dud, but my it's a samsung drive thats failing.
-
On 1/29/2024 at 6:19 PM, BeardElk said:
Thanks!
It’s already in a usb 2.0 port, it’s been in that port since I built the server so the usb drive is probably going bad, gonna order a new one.For shits and giggles I changed usb port and I'm gonna see if it happens again. At least now I know what it is.
I had it on an interal usb to "normal" usb adapter, just so it never gets unplugged by mistake, but I moved it to the back.
Its all the same usb controller so I don't think it should make a difference, and I don't think the internal adapter just suddenly went bad, so the most likely culprit is the usb stick.
But time will tell. -
32 minutes ago, JorgeB said:
an 28 22:25:56 BelK kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s Jan 28 22:25:56 BelK kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 24 cf ba 00 00 08 00 Jan 28 22:25:56 BelK kernel: I/O error, dev sda, sector 2412474 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Jan 28 22:25:56 BelK kernel: usb 1-13.2: USB disconnect, device number 15 Jan 28 22:25:56 BelK kernel: device offline error, dev sda, sector 2412474 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2Flash drive is dropping offline, try a different USB port, ideally USB 2.0, if issues persist replace it.
Thanks!
It’s already in a usb 2.0 port, it’s been in that port since I built the server so the usb drive is probably going bad, gonna order a new one. -
So for the last couple of months, my serves has randomly become unreachable on my local network, but all my dockers still work.
So to try and find the problem I've had syslog running the last couple of weeks to catch whats happening when it happens, and 22:25 last night (january 28) it happened again.
Now I don't have the skills to figure out what the errors are in the syslog, so I'm hoping someone on here can help me.
I'm able to reboot the machine by using the onboard terminal, and when I do, it always failes to find the unraid USB stick, so I have to turn off my psu, wait 5-10 sec and then turn the machine on again for it to find the USB stick.
Is my USB stick failing?
Its a Samsung Bar Plus 32gb flash drive, not that old, might be coming up on 2-2,5 years, cant remember exactly when i bought it.
Diag and Syslog attached. -
On 8/22/2023 at 1:01 AM, wgstarks said:
This usually means that you are mapping the backup to a destination in the image. Attach your docker run command to your next post.
Thanks for your input, but I've decided to not continue forward with my timemachine setup as I already have a nextcloud thats working and it would only be a few apps that the timemachine would govern over.
-
2 hours ago, falkfyrebeard said:
Quick question. I don't have a Mac VM set up right now. I've tried multiple times to and have an RX580 I passthrough to it but I've never been able to get audio, even from the display ports. In order to get it to work do I need to flash it? I've tried passing the VBIOS through instead of using what is on the card but no matter what I get no audio at all. I'd love to get a Mac VM set up at some point.
The gpu video and audio needs to be on the same bus, by default (if you use the gui) the audio are gonna be on the next bus, for example it'll look something like this if you save with the gui =
<hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/vbios/vega56.rom'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev>
But you NEED to change the bus to the same as the gfx, and add the function '0x1' to the audio adress, like this =
<hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/vbios/vega56.rom'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </hostdev>
The video and audio needs to be on the same bus in osx.
And you don't need to use macinabox after editing the xml, just make sure add something like this at the end of the xml =
</devices> <qemu:commandline> <qemu:arg value='-global'/> <qemu:arg value='ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off'/> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='************************'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+avx2,+aes,+fma,+fma4,+bmi1,+bmi2,+xsave,+xsaveopt,+rdrand,check'/> </qemu:commandline> </domain>
But if you're still having trouble, i'd suggest reading up on a bunch of forums found on google.
-
So, for some reason, whenever the I run timemachine on my mac, my docker.img is filling up?
I'm not sure what I've done wrong!
I've run sudo chown -R 1000:1000 /mnt/user/timemachine/ and everything seems to be working as it should except that it fills up my docker.img. -
On 7/21/2023 at 9:59 PM, BeardElk said:
As the titles says, I've got a manjaro vm that doesn't boot anymore/gets stuck at splash screen/ wont initialize screen after splash screen.
When I boot it up, I only get "Unraid", then the screen turns off, then "Unraid" again, but nothing else happens after that.
I've got a Windows 11 vm that's working just fine, but the Manjaro vm wont boot with a gpu passthrough.
It does however boot if I run it with VNC.This happened at the same time as I upgraded to 6.12.X, so I figure its related somehow, I just cant figure out how to fix it on my own.
Neither of my gpus work as a passthrough on the manjaro vm, it only boots/gets past splash screen with vnc.
All the logs are clean / no error shows up, but diag is included.
For anyone in the future having the same problem, I was on a deprecated kernel version, so when I ran the updates it couldn't grab nvidia-linux6x bc it didnt exsit, and I didin't catch it at the time, so it just freaked the f out every time the display was initialized to the desktop.
But all is good now!, I changed kernel version using vnc and after that everything worked again.
-
As the titles says, I've got a manjaro vm that doesn't boot anymore/gets stuck at splash screen/ wont initialize screen after splash screen.
When I boot it up, I only get "Unraid", then the screen turns off, then "Unraid" again, but nothing else happens after that.
I've got a Windows 11 vm that's working just fine, but the Manjaro vm wont boot with a gpu passthrough.
It does however boot if I run it with VNC.This happened at the same time as I upgraded to 6.12.X, so I figure its related somehow, I just cant figure out how to fix it on my own.
Neither of my gpus work as a passthrough on the manjaro vm, it only boots/gets past splash screen with vnc.
All the logs are clean / no error shows up, but diag is included.
-
Im experiencing the same thing, for some reason it works "fine" if I remove the gpu and run it through VNC, but if I add the gpu and start it up it Extremely slow, unusable slow!
I've got other linux vms that run fine on both my gpu so I know it's a Windows thing..
-
3 hours ago, Tiller said:
I just performed an update and afterwards I am only seeing this screen. I believe this happened back in November after an update as well. Is there a reason this is happening multiple times after performing an update for this application? I did some searching and saw sometimes this happens if the database is corrupted, so I started following one of Spaceinvader One's videos on fixing a corrupt Plex DB. But when I got to the step of performing a "PRAGMA integrity_check", it came back as "ok" without any errors.
Do I just need to wait for the migration to finish? I still don't understand why this has happened multiple times, though, and only immediately after an update. So any guidance or explanation would be appreciated. Thanks in advance.
I've got the same, and after "migration" my hardware transcode doesn't work anymore.
I tried to downgrade to a previous version but hw transcode for me is totally broken right now.
This could be something else entirely, ie user error or something, just wondering if anyone else has experienced this.
I let the migration run it's course and plex starts up just fine btw. Just give it time depending on your library. -
On 12/3/2022 at 8:15 PM, cassiusdrow said:
The "netclient" machines must use the IP address of the "netserver" machine, not 127.0.0.1.
Yeah but if I input the correct address it cant connect, bc the netserver is setup with 127.0.0.1 and is greyed out so I cant change it.Edit:
Got it working!
Followed this and pieced it together! -
Does anyone know how to change the IP address of the nut plugin when running as a netserver?
I'm trying to connect my synology nas to it, but it wont accept 127.0.0.1 as an ip -
On 9/27/2022 at 9:10 PM, autumnwalker said:
Hi All. I've forked this plugin and web searched my way through getting NUT 2.8.0 and net-snmp 5.9.3 working.
I AM NOT A DEVELOPER. USE THIS AT YOUR OWN RISK. I don't even know how to use Git efficiently.
https://github.com/autumnwalker/NUT-unRAID
If you want to install this - open Unraid, navigate to Plugins, click the "install plugin" tab and paste the following URL into the URL field (next to "install") button, then click "install".
https://raw.githubusercontent.com/autumnwalker/NUT-unRAID/master/plugin/nut.plg
If this works for you then I'm glad. If it doesn't work I probably cannot help you. It took me all day to get this working based on what I was reading in the thread here and cobbling things through google-fu.
If anyone wants to take this and "make it right" or validate what I have done please feel free to provide feedback. I'm sure there are better or more efficient ways to do what I've done with the code.
I tried this just for the heck of it, and it broke the NUT plugin to the point I had to uninstall both your plugin and @dmacias original plugin, then reinstall the "old og plugin" to get it working again.
Anyway, I've got an annoying problem.
Sometimes, only sometimes, when I reboot my server, the NUT plugin freaks the f-out and thinks the ups is on battery with 0% left, and instantly orders a safe shutdown of the system.
This has been ongoing since day one, but it happens so scarcely, that it's more of an annoyance then a problem.If anyone has a any idea on how to fix it, I'll happily try it!
-
On 9/6/2022 at 3:46 PM, trurl said:
That's not a fix, it's a workaround because you didn't figure out how to fix it.
The usual cause of filling rootfs (which is in RAM) is an application writing to a path that isn't mounted storage, such as a container with a host path that isn't a disk or user share. In the case of plex, transcode path would be a likely suspect.
Post docker run for plex, and also post new diagnostics just before that script runs.
You can monitor rootfs usage yourself from the command line with this:
df -h /
So, I'm running binhex-plexpass docker, and I've followed everything in his guide to setup transcoding, I've got Key-1 /transcode, then added /transcode - path /tmp/plex-ramdisk (made a ramdisk to limit the amount it can use), and all that is working fine, the only thing that "solved" my problem was the "custom user script" to reboot it every morning.
Here is docker run and diag :
docker run
-d
--name='Plex'
--net='host'
-e TZ="Europe/Berlin"
-e HOST_OS="Unraid"
-e HOST_HOSTNAME="BelK"
-e HOST_CONTAINERNAME="Plex"
-e 'TRANS_DIR'='/transcode'
-e 'NVIDIA_DRIVER_CAPABILITIES'='all'
-e 'NVIDIA_VISIBLE_DEVICES'=''
-e 'UMASK'='000'
-e 'PUID'='99'
-e 'PGID'='100'
-l net.unraid.docker.managed=dockerman
-l net.unraid.docker.webui='http://[IP]:[PORT:32400]/web/index.html'
-l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/plex-icon.png'
-v '/mnt/user/Media/':'/media':'rw'
-v '/mnt/user/Backup/Backup/Annan Media/Filmer/':'/marvel':'rw'
-v '/mnt/user/Backup/Backup/Annan Media/Musik Videos/':'/musikvideor':'rw'
-v '/tmp/plex-ramdisk':'/transcode':'rw'
-v '/mnt/user/appdata/binhex-plexpass':'/config':'rw'
--device='/dev/dri' 'binhex/arch-plexpass'remove actual plexpass
-
So, it was plex-docker that were filling up the ram, and I fixed it with a simple script to run every other day to just reboot plex-docker!
-
-
3 hours ago, trurl said:
Do you mean the Dashboard page?
Yeah sorry, my head was in another thought when i typed that😅 (Im from Sweden, and Im autistic, sometimes I just "wander off" and keep typing without checking what I just wrote..)
-
Here's an updated diag with a syslog over the past 6 days.
I hope you guys can help me! -
On 7/23/2022 at 2:41 AM, trurl said:
What are you looking at specifically that tells you?
Memory utilization on the diag page. (edit, Dashboard, not diag, my thoughts were elsewhere when i typed that)
-
Im gonna start by apologizing for the lack of information on my og post.
I´ve started a syslog server now, and in a couple of days im gonna post the output of the syslog.
(The indication I got for my RAM filling up, is that my RAM is filling up after I start my server. If I boot with 16gb free, I´ve got 10gb free a day later. (Im exaggerating, english is a second language for me)
-
15 minutes ago, trurl said:
Diagnostics are attached.
And why do I need to setup a syslog server?
I get that I need to log as much as possible, but my main goal is to not have to reboot the server every week. -
For some unkown reason (to me at least) my ram keeps filling up to the point where I have to shut down VM:s or reboot my server.
I´ve got no syslog-server running and I don´t understand why this is happening.
Since I'm not fluent in logs, or even what to look for, I'm turning to you golden gentlemen's (and lady's) who have saved me so many times before.On a fresh reboot I've got between 69-72% ram utilization, but 48h later its up at 85%.
Got 3 vms running and 17 dockers (normaly 19, but have still not gotten around to fix the fuckall nextcloud/Collabora thing) so they are offline.
As I said, no syslog running in the background, and I really cant find what is filling up my ram over time.
And before someone says it, I know I'm running kinda short on ram, and its next on my "to do/upgrade list".
Diag was downloaded before I rebooted the machine.Since I got my UPS my "record" is 1 month 18 days, but had to shut down vms one after one as it filled up, and I tried solving it myself by looking through everything and googling but I lack the skills.
(Fuuuuck me, I forgot to upload the diag, but here it is!)
-
I'm kinda new to all this, and just switched over from swag bc this just looked so much easier to use.
But I got on quick question, can I run npm on my unraid server, and have it redirect to other stuff on my local network?
I've got a 3d printer with octoprint running on a raspberry pi on my network, and npm can see the device and everything "should" work, but I dont even get the welcome page...
Just this a "page is unreachable".
Server randomly becomes unreachable on local network and usb is not found upon reboot.
in General Support
Posted
I had a Samsung Fit 128gb usb drive on hand, and I didn't wanna risk getting any more data corruption bc of the usb drive disconnecting, so I plugged that in.
Feels like its totally overkill but, if it works it works!
The samsung fit was recommended as well.