pinion

Diag attached Recently I had my parity 1 and disk 2 red ball saying there were read errors. Since then I've bought 5 disks to replace them. All of them being refurbs so I was expecting some to be bad anyway but I was going to deal with Amazon and take the hassle to save money. But 4 of the 5 nearly immediately reported read errors when trying to rebuild and red balled themselves. Last night I finally got the server configured with disks that didn't red ball immediately but this morning I look and disks 7 and 15 are throwing thousands of read errors. They didn't red ball though. Maybe because I'm in safe mode? Maybe I shouldn't be doing a data rebuild in safe mode? Can someone look at my diags and help me? I'd really appreciate it. unraid-diagnostics-20230427-0701.zip

Decided to boot back up, stop array, unassigned those two disks, start in maintenance mode, disable Docker and VMs and some userscripts I had, Stop array again, reassign disks back to where they were, and start the array and data/parity rebuild. Fingers crossed.

Before I do something dumb (if I haven't already) I'm stopping to take a breath and ask for help. My server froze up for some reason today and I couldn't get it to do anything so I had to kill power. When it came back up my Parity 1 and Disk 7 were red balled. Now, I don't think anything should be wrong with them so I killed parity check, shut down, reseated everything and checked for anything obvious. I definitely could have bumped something while jostling it around and I have 24 bays with the quick swap release in the front so you never know. I've ran a self test on both of them and they both look fine. Attaching diags but I may have grabbed them too late. What should my next step be? Please and thank you. I'm going to lay down and take some deep breaths. unraid-diagnostics-20230326-1411.zip

Had this issue today 6.11.5. I didn't upgrade but I was trying to add a drive to my array. And yes, using firefox. Working ok in chrome mobile. Firefox needs some lovin!

If they moved everything under / that would have started moving /mnt/user/ as well, right?

So first don’t panic. No point in that and you’ll just make it worse. So where did you mv the files to? I’m not familiar with the -T option but with ${pwd}\* you definitely moved everything from your root directory “/“ to somewhere. I’d start there and try to find where the files got moved. I would also make a copy of my current flash drive.

Sharing my solution since the new Nerd Tools doesn't include it. I know a few people have requested it but since it's still not there here is what I do. Please share your solution too! You will need the User Scripts plugin then create a new script with this: #!/bin/bash mkdir -p /mnt/cache/appdata/unraidEXTRA cd /mnt/cache/appdata/unraidEXTRA wget https://slack.conraid.net/repository/slackware64-current/mosh/mosh-1.4.0-x86_64-1cf.txz wget https://slack.conraid.net/repository/slackware64-current/protobuf/protobuf-21.9-x86_64-1cf.txz installpkg --upgrade *txz The #!/bin/bash should already be there. I run this at array start and it seems to work well.

I'm also here to beg for mosh. Not sure if it was part of nerdpack or devpack before but I'd love for it to come back.

Does unraid officially support being ran on top of a hypervisor like proxmox? I know it didn't years ago when I looked. If I can't use unRaid as a general purpose linux box then it should be able to be virtualized so my hardware can do other things I need. Only here because gcc from devpack is complaining about not having libisl.so.22 and I was searching the forums and found this thread.

Can you tell me how you determined what process was causing the iowait and how you determined the disk it was using? I have the same issue I'd like to figure out where the bottleneck is and I'm struggling to find what you see in the screenshots.

Thank you for the response. To install an older version I selected v510.73.05 which is in my available version list similar to your screenshots. Once it completed I closed the window and had the notification I needed to reboot. Upon reboot the GPU did not show up in the settings for the plugin. I rebooted again and this time the latest driver was installed. This entire thing happened a second time. Additionally, I had been running v510.73.05 for awhile so I'm not even sure how the latest got installed. I am now running the version I want after uninstalling the plugin, rebooting, installing the plugin, installing the driver I want, then rebooting again. Games on Whales (GOW) https://games-on-whales.github.io/gow/index.html It's a project that lets you steam games from retroarch, steam, etc that's containerized using a docker-compose file. Why it needs to download the nvidia driver. I think uniput is needed for controllers? I'm not totally sure. For xorg I have it point to the nvidia stuff that I think you have installed so again I'm not sure why the plugin downloads anything. - /usr/lib64/xorg/modules/drivers/nvidia_drv.so:/nvidia/xorg/nvidia_drv.so:ro - /usr/lib64/xorg/modules/extensions/libglxserver_nvidia.so:/nvidia/xorg/libglxserver_nvidia.so:ro I wish I knew if this was an issue before or after I started messing with GOW. Regardless after uninstalling and reinstalling the plugin I'm back on the driver version I wanted. Thanks for your help!

Has anyone ran into an issue where if you reboot the GPU isn't visible to the plugin and if you reboot again it suddenly is? Edit: It appears that it won't let me use an older driver. And when I try after the reboot no GPU. Reboot again and I'm the latest driver again. Diag attached unraid-diagnostics-20220729-1634.zip

Thank you. I was able to get it going again by hitting Add Container at the bottom of the Docker page and selecting it. I think that's a bit of an old way from before we had CA. My question is more how foes that happen and how can I make it stop so the container doesn't disappear on me?

I sometimes have this issue where I screw up a setting in a container and then when I apply the settings I get "Command Failed" and then the container is gone in the Docker tab. I wish I would have grabbed some logs last night but I didn't so I'm sorry I don't have that. When I go to Apps and try to reinstall I see the LSIO Plex container but it doesn't say reinstall just install and all my old settings are gone. Does anyone know why this happens and how to prevent it?

For this esync issue you need to edit the Docker Container for Steam-Headless and enable the Advanced view (default is Basic just check the slider). Then in the Extra Parameters: add --ulimit nofile=1024:524288 Restart the container and you should be good to go. Worked for me with Disco Elysium from GOG.

I thought I was isolating 2-15 and 18-31 for use in Docker and VMs. Then in my main VM I had pinned most of the cores but as you can see only 0,1 and 16,17 were being used, I assume by the VM, while the rest were probably isolated to the OS. That's why I say I must have done it backwards. Things look better now but I still have no idea if I'm doing it right.

So I take it I did this backwards?

I'm also curious. I've been an unRaid user for a long time so 4 of my 20 disks are still on ReiserFS. I plan to use Unbalance to start getting data off of them but don't want anything to write to them. If I come back and reply on this old old thread it means I found a solution. Otherwise if I don't I just ended up disabling the disk on each of my User Shares in the share tab. I have like 30 shares so I;d prefer something easier. Hopefully those disks don't brutally murder each other anytime soon (Sorry that was in poor taste). Edit: I looked and searched and looked some more. I can't find a good way to disable a drive on all shares easily. Seems the only option right now is to just exclude it in Share Settings for the Share. I just disabled it in the shares that are likely going to have writes today instead of all 30 so only like half a dozen. I'd request the feature but I assume the use case is so small that it's not worth it.

I'm unsure how dependencies work with NerdPack but I've been having an issue where Mosh quit working after a clean install of NerdPack. libprotobuf.so.18: cannot open shared object file: No such file or directory After messing around way to long to try to figure out what I need to install I figured out I could install protobuf-3.7.1-x86_64-1cf.txz from NerdPack and now it works. I would expect when selecting Mosh in NerdPack it would know I need this and install it alongside Mosh.

Probably not the best way but I ssh’d in and created the node folder and did a chown nobody:users

Thank you so much. That was the issue. I swear I read through that (probably more like skimmed) and just didn't realize probably because I wasn't trying to make the other container go through the VPN. Looks like for containers that go through the VPN it's a lot easier to add their ports now than it used to be.

I have a script I'm trying to run on completion of a file (via execute plugin). It basically just runs a curl command but it is timing out. In trying to troubleshoot the issue I've realized that I can curl google.com and get results and of course get my ip with curl ifconfig.co but when I try to curl my unraid IP it times out. I'm actually trying to issue a curl to an API at 192.168.0.5:9393 but regardless just trying to run curl on any internal IP times out. Is this expected behavior or do I have some other issue?

The cheapest. Which is usually shucked WDs.

You are correct that's where it's at. Need to toggle Advanced View but it's there.

Almost definitely but I'm not 100%. Tried to upgrade to 6.10 last night hoping that would just fix it. But the upgrade said it worked but the server wouldn't reboot saying to insert a device called UNRAID. So I put the bz(stuff) from before over on top of the usb and I was able to get back in. After that I didn't have time to mess with it and now tonight I've gotten another kernel panic. So I'm currently backing up the USB. Going to try and upgrade. And then I'll check if anything has a custom IP. By custom IP I assume you're talking about a container that I set the IP to something other than what unraid has. So if unraid = 192.168.0.5 and I setup a container with IP 192.168.0.6 then that's custom. Are there any other situations that would be considered a custom IP.