Troussdesoin

Hello Guys, I haven't touched at my reverse proxy in at least 6 months and i don't think that i have done anything to my server/ network this week. However my setup stopped working : - I can access locally all my containers - If i point my website to my server IP, i reach the swag front page - But if i try adding my subdomain, it ends up in an Error Connection Timed out.( If i try any subdomain that links to nothing, it tells me straight away that it does not exist.) What i tried : - No errors in Swag log, and i deleted the resolver/ proxy.conf to be sure - restarted everthing - tested cloudflare is working So i'm starting to go mad. From above i conclude that cloudflare is working + Local containers are working + Modem/router are redirecting all request to the containers. So why is swag not opening the containers? Starting to go mad here, if you have any ideas. Edit for Solution: After a while searching and trying out stuff. I switched dns only in cloudflare in the Cname (it used to work before, as shown in space invader video) to proxied. It worked instantly.

Any update on the subject, i'm getting the same now

Well, I switched Disk 1. It rebuilded with a few errors (most likely a few seconds of a film were lost). Did a few preclear on the dying disk, and it was really dyning. I'm waiting for a second disk to come in to replace the other failing drive. I'm also waiting for a new controller, Just to be sure. Overall it was a good learning experience. Thanks guys for the help.

I did a parity check (non correcting). It returned with 0 errors (with the two failing drives). I am rebuilding the array with a new drive. And then i'll do some preclear on the old drive to see if it was really failing or it was from something else.

All right, it's settled then, i'll switch both of them. And how can i test the Cable/controller? So that i know if i need to replace them as well?

Ok, I just did it. I got Raw read error rate of 0 on disk 2 and 3, and error rate of 5 on the disk 1. Actually after reading into it, it does not seem to matter much because the worst is at 199. which is far above the trehold. Also the multi zone error rate on disk 1 is also at 1. I was wondering if it could be that only the controller /Cable is bad? Could it provoke all those errors? Should i replace the drives now or wait for the new controller/ cables to arrive?

Yes i think you're right, i got disk1 read errors as well on the parity check

You're right, Thanks for that, i edited the first post

Hello, guys, This week end, i installed a new cache drive. But in the process, it bend the cables and the card from the M.2 controller where 3 of my HDD were. when i started unraid, they did not show up, then after fiddling a bit, they showed up. But it was not stable and one disconnected in the middle of a write operations. One of the drive became disabled (red cross on disk 1). I did a smart short test on the three drives and they seemed fine. So i rebuild the array with the disk 1 in place. It finished this morning, but there was 504 errors. Mainly because of disk 2 and a current pending sector. I did smart extended test on all three drives. Disk 3 came back fine, but there was errors on disk 1 and 2 (errors occured - check smart report). I just launched a parity check (without correction). I ordered a new m.2 controller just in case there are more errors (could mean that the controller was damaged). What do i do for disk 1 and 2? it's only media on it, i would not die if i lose some of it. Are the errors really bad? or if there is no more errors, i should be fine? Right now, the overall server is working fine. Thanks for the help WDC_WD40EFRX-68N32N0_WD-WCC7K6SKLNHN-20210830-1651.txt WDC_WD40EFRX-68N32N0_WD-WCC7K5VY4XY7-20210830-1604.txt WDC_WD40EFRX-68N32N0_WD-WCC7K5VY42E9-20210830-1727.txt unraidchoupi-diagnostics-20210830-1727.zip

Hello Guys, i successfully installed the docker and Git cloned one of my Mobile project. However when i tried to npm install it and expo install it, i got error code EACCS with permission denied to /usr/lib/modules. Does anyone of you actually succeeded on creating an node.Js developing environment? edit 1: I saw the Docker mods, so that's working, i need to open a few more ports for expoto work. But it seems a lot smoother than last time i tried edit 2 : I made Expo.io work, but same as node.js , i need to reinstall it everytime. Is there a dockerMods for Expo.io?

Hey there, I'm trying to access the CLI of OpenRGB I tried opening the console from the docker menu but i can't make it work. Do you have any idea how to make it work? I want to change the profile from the console (to automate it eventually). I know the CLI exist in OpenRGB, i just don't know how to access it in the docker format

Hey, I had the same question. Maybe a plugin is required to make it work in Unraid.

Ok thanks a lot, i'll check

Hum, the Two tests completed without Error , here are the reports. It doest not seem like there is a major problem. What do you think? WDC_WD40EFRX-68N32N0_WD-WCC7K5VY4XY7-20201122-1341.txtWDC_WD40EFRX-68N32N0_WD-WCC7K6SKLNHN-20201122-1349.txt

Ok, i'm running it on Disk 2, but DIsk 1 is also saying that there are some errors Could it be software related?

Hello Guys, Some time ago, i had read Errors on the array. But it was BTFRS errors and i removed the cache drive and it stopped spewing errors. But tonight, when i came home, it says it had found read errors. It it bad? Should i buy new drives? Thanks a lot .DS_Store domain.cfg go docker.cfg super.dat ident.cfg share.cfg network.cfg disk.cfg WDC_WD40EFRX-68N32N0_WD-WCC7K5VY42E9-20201121-1827 parity (sdd).txt SanDisk_Ultra_Fit_4C530001230713104105-0-0-20201121-1827 flash (sda).txt WDC_WD40EFRX-68N32N0_WD-WCC7K6SKLNHN-20201121-1827 disk2 (sdc).txt Samsung_SSD_860_EVO_1TB_S4FMNE0MB10644A-20201121-1827 cache (sdb).txt WDC_WD40EFRX-68N32N0_WD-WCC7K5VY4XY7-20201121-1827 disk1 (sde).txt Windows 10.xml cmdline.txt btrfs-usage.txt plugins.txt motherboard.txt iommu_groups.txt ethtool.txt folders.txt lsmod.txt lsscsi.txt loads.txt memory.txt lspci.txt meminfo.txt lsusb.txt top.txt ps.txt vars.txt lscpu.txt lsof.txt df.txt ifconfig.txt libvirt.txt docker.txt syslog.1.txt syslog.txt no qemu log files unraid-6.8.3.txt appdata.cfg domains.cfg M---a.cfg T----------e.cfg isos.cfg W----------s.cfg system.cfg D-------s.cfg D-------------o.cfg

Hi there, I have problem with my cache pool and want to remove the two SSDs i have right now in BTFRS (raid 1 i think) with only 1 big ssd. I read the faq and they talk about removing a drive from the cache pool but they say to not go below the requirement of the pool. In my case the requirement would be 2 drives minimum. So how do i do it? Would : 1. set All shares to "no" in use cache disk. 2. Activate the mover to remove the data from the cache disk. 3 stop the array. 4.pull the disks. 5 insert the new ssd. 6. Set the shares i want to 'yes' in use cache disk. 7. reactivate the mover? Btw in the faq it says for the 1 disk, remove or upgrade procedure, to set the shares to 'yes' in use cache disk , is it a typo? thanks a lot.

Hey, thanks for the answer, I ran a Smart extended test last night on one of the drive, and it says it was completed without error. Here is the file attached. i'm going to test the other one and see if the ram is overclocked today. thanks a lot. EDIT: the ram is not overclocked it was a 2133 WDC_WD40EFRX-68N32N0_WD-WCC7K6SKLNHN-20200113-2303.txt edit 2: I uploaded the second smart test it seems to spew errors especially on the cache drive that was dropping out, i'm planning to change it this week end WDC_WD40EFRX-68N32N0_WD-WCC7K5VY4XY7-20200115-0920.txt

Hi there, I've had a few issue for a few weeks, my docker were randomly crashing because one of the SSD in BTRFS Cache was sometimes dropping out. On Saturday, because of the crash it seemed to have corrupted the Plex docker and its metadata,. So i removed the docker (with krusader, because i could not do it without root privileges) and restarted from scratch. Yesterday, i also stopped the server and cleaned the NVME drive to make sure everything was ok and it would stop dropping out. And today i made a parity Check , and i found more than 500 errors on the array. I would normally conclude that both Drive are failing, but this seems weird. Is it possible that while removing the files, it would create the read errorrs? Should i order new drives and replace them, they are only 2 years old. What's the probability of them both failing on the same day? Thanks for the help unraidchoupi-diagnostics-20200113-0814.zip unraidchoupi-syslog-20200113-0814.zip

Hi there, Trying to mess with this docker for a few days, however i can't install node.js and get a react environnement working. The node.js install does not work. It seems i have to install the runtime environment OUTSIDE the docker. But i am not sure how. And when i get it working just a while (installing inside the docker, but does not stick when i restart it) and i npm create-react-app, i can't access the app page on my network, Have any of you guys made it work? cheers Edit 1: OK, i've figured out half my problem. You need to open port 3000 for the create react app to function. And after that it works great. However i still have a small problem, the terminal never access the bash profile of nvm so everytime i open a new terminal in vs code, i need to retype : export NVM_DIR="$HOME/.nvm" [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm [ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion" # This loads nvm bash_completion Do you guys know how to fix this?

Hey there, Trying to install my first Win 10 VM on unraid, i followed space invader video, i loaded the vnc and got to the installing part. But when i have to chose the driver to get the virtual drive to install win 10 on, i go in the E: drive>viostor>win10>amd64 and it shows nothing. It only shows when i uncheck "hide drivers that aren't compatible withis computer's hardware". I took the latest driver version in the unraid ui and downloaded the win iso today. Got a ryzen 5 1600, with 2070 RTX. Any of you guys have any idea why it is not working? thanks edit; fixed; i put the v primary disk under manual instead of auto. Works now with auto