Lygris

That did it, it's back online. will it remirror itself?

seems like one of my cache drives has died, the temp is showing * and i'm getting lots of errors in the logs, nothing popped up saying the drive has failed though. should i reboot to try and fix it or is there something else i can do? unraid-diagnostics-20240426-0831.zip

Went to check on my server today and couldn't load the webgui. attempted to restart nginx to fix it but that only got me to the login screen, after login it became unresponsive before loading the dashboard. unraid-diagnostics-20240227-1547.zip

Also having this issue, or at least something that is probably related. After the update to 6.12.6 my cpu was running around 20 degrees C hotter than before. Rolled back to 6.12.4 and it's back to sitting around 46 C.

Not sure where to start looking on this one, diagnostics attached. unraid-diagnostics-20231016-1908.zip

I keep getting spammed with warnings about my nvme drives getting hot because the disk temp thresholds are set for my HDD's. Can we get something to set a seperate threshold for SSD's or cache drives? EDIT: Nevermind found it down by smart settings in each cache drive. Could still be a useful feature under disk settings if SSD's could be auto seperated.

I'm still having the issue on 6.12.1 and i only have 1 ip assigned. diagnostics attached. It seems sort of random, sometimes it works sometimes it doesn't, usually starts to work after i goto my lan ip instead of the name but even that is hit or miss unraid-diagnostics-20230628-1703.zip

I can give it a shot, the cables are the SAS to SATA breakout style and i'm running all the disks off an hba card. The cables are only a month or 2 old but I'll replace it today and see if a rebuild completes.

About a week or so ago I noticed my parity disk was disabled so i unassigned it/reassigned and got parity to rebuild successfully. I logged in again today and noticed it is disabled again. Need help finding out what the cause is, I attached my diagnostics file. looks like i'm getting a high number of udma errors but it seems completely random when they happen and they happen in large groups. running 6.12.1 unraid-diagnostics-20230626-1321.zip

You will have to enable bridging on the network settings page for your interface and then set the "Ipv4 custom network on interface brX" in docker settings to your internal network space, then assign the ip to the container in your internal range. It will appear just like any other thing connected to your network at that point and you can use port 80 since it's on a different ip than unraid is using. another option would be to change the port unraid is using for the webgui to something else so the container can use 80, but the bridge network way is what i prefer

When you try and go to subdomain.duckdns.com that is pointing to your router on port 80 or 443, so you need to forward 80 and 443 from your router to your docker host at port 180 and 1443. From a quick google it doesnt look like your comcast router supports port forwarding to different destination ports, so you need to put the container on a custom network which it looks like you already did but didn't assign an ip. Once you assign an ip to the container you just forward 80 and 443 on the router to that ip address.

Did you forward port 80 and 443 in the router to your container?

Either the cert file doesn't exist or the permissions on it are incorrect.

I'm having a strange issue where SWAG stops working after seemingly random amounts of time. I will try and browse to a site fronted by swag and it seems like it just isnt responding. I then go and restart the docker and instantly the page loads once the reboot finishs. I don't see anything in the docker logs and have tried checking the nginx error.log in the container but it is usually just a single line unrelated to the incident.

Works much better on bare metal, back at ~100MB/s. Curious about the HBA & CPU issues. Where did you find those in the diag and are they still in this diag taken from bare metal? thanks! unraid-diagnostics-20210719-1408.zip

Working on getting the ip reassigned in bare metal right now. Had the same thought. I know it's not supported but i've run this as a vm on ESXI for years now and recently switched it to proxmox, but I don't think i've had to run a parity check with it running on proxmox yet. Would you know if there's anything special that needs to be done for a proxmox unraid vm? All the drives are being done with pci passthrough so I didnt think the parity speed would change.

overnight my parity disk disabled, I think because I had logs stating apparently 4 disks went unwritable for some amount of time. I checked the read/write speeds of all my disks and they all seem fine, however when i'm trying to resync parity it's incredibly slow at 25MB/s, normally I would see something around 100MB/s. Diags attached, not sure what to look for. unraid-diagnostics-20210719-1212.zip

With the nvidia version of the container, should I be seeing much cpu usage? With 8 cameras and a pci TPU i'm getting ~50% cpu usage on a 24 core machine, which seems odd. Also I cant seem to get anything other than person to show up as far as object detection goes? I set each camera to detect person, cat, dog, and car but it doesn't seem to take. config.yml

Having issues getting the my pci coral to show up correctly, /dev/apex_0 doesnt show up. I keep getting this in the logs and am lost. Any help would be greatly appreciated! Jul 12 16:31:03 unraid kernel: apex 0000:0d:00.0: Page table init timed out Jul 12 16:31:03 unraid kernel: apex 0000:0d:00.0: MSI-X table init timed out Jul 12 16:31:03 unraid kernel: apex: probe of 0000:0d:00.0 failed with error -110

Had a weird issue this morning after the upgrade to beta29 last night. Anything dockers using bridge connections wouldn't load from letsencrypt(which runs on br0.6) but dockers running on other br0.* networks worked fine through letsencrypt. Fix was putting any docker that i needed letsencrypt to load on a br0.* network and it resolved it. to be clear the bridge dockers loaded fine directly, just not from letsencrypt

So i had to do an unclean reboot last night because something was stopping the server from rebooting. I noticed this morning disk8 is unmountable. Is there any way to save the disk, it is btrfs and with some googling it looks like im screwed here, but i figured it was worth a shot. unraid-diagnostics-20200205-1727.zip

So this happened again, same disk is now showing 1 read error. It happened monday morning, not sure what else to try? i don't know where to pull the mcelog from either. I also got an email from the server with the following and i have no clue what this would be from subject: :cron for user root /usr/bin/run-parts /etc/cron.daily 1> /dev/null body: sh: -c: line 0: unexpected EOF while looking for matching ``' sh: -c: line 1: syntax error: unexpected end of file

I got some more errors today, along with some UDMA CRC counts going up. I've noticed those in the past but now they seem to be causing the machine check errors alert now as well, unless that's new in 6.5.3? I'm going to try another sata cable right now and see if it helps, but this will be the second time i've changed it.

Got this error in fix common problems this morning, not sure what to do about it. I installed the mcelog package but i have no clue how to check that. i've attached the diag bundle unraid-diagnostics-20180714-0708.zip