UnluckyTech

You ever figure this out? Having the issue myself. Seems to work with no issue when accessed locally but when accessed through my domain it states the maintenance error.

Issue keeps happening with me every few months. Things will work for a few minutes. Stop working for another few minutes. Does this for a day or two and then back to normal.

Almost 3 years now. Thanks for showing how you resolved those issues. Helped me out alot!!!

Honestly, I kept convincing myself for whatever reason that it wasnt a fan issue but once you pointed it out, I took another look. The cpu fan wasnt spinning. Guess one of the wires was caught in it making it not move. Greatly appreciate it.

About a month ago, I did a full teardown of my server, including reapplying thermal paste and thoroughly cleaning all its components. I have a 3700x and after doing this the temps averaged between 40c-50c depending on the load. Also just to note this was on 6.12.1. During this time, I noticed that my 1TB NVMe SSD was reaching temperatures of 46-48°C without a heatsink, leading to frequent notifications. To address this issue, I decided to invest in a heatsink for the NVMe SSD. Additionally, I purchased two 2TB SATA SSDs with the intention of experimenting with ZFS pools. I don't know much about ZFS but have heard positive things about it and wanted to give it a try. Yesterday, I installed the new drives, updated the Unraid OS to version 6.12.3, and set up a RAIDZ pool. To optimize performance, I moved all my appdata and Nextcloud data onto the cache. Following Spaceinvaderone's guide, I converted appdata to a dataset without compression. After verifying that everything seemed in order, I reactivated Docker and started up around 40 containers. The CPU temperature spiked significantly this time, reaching 95-99°C, which I attributed to launching multiple containers simultaneously. However, even during idle periods, the CPU temperature remains at a concerning 80°C-90°C. I use glances to see what could be causing it but none of the containers are using much resources to begin with. I assume it has to do with zfs in some way but have no idea how to approach this and get the temps back down now. Any help would be appreciated! Here is everything in the server. Also attached diagnostics. unluckyserver-diagnostics-20230720-1217.zip

Would be awesome to see!!!

NEVERMIND. I will be judged. Restarting the hub and router fixed the issue. I shall go hide in a corner now...

I just upgraded my internet through att and they swapped out the hub previously used BGW210 to the BGW320. I set the new hub like I have done previously to IP passthrough and disabled the firewall/ packet filtering on the hub. I then have my RAX120 that has all the same preconfigured settings for the firewall local IPs and whatnot. The network itself runs great and my unraid server is accessable locally with the same local ip and everything like before BUT I cant get any of my subdomains now to work. Now I do have a new public IP address and I set everything to be ipv4 only. I have duckdns configured and that detects the new ip address and I can even ping to the address with no issues. I have the domain all routed through cloudflare but for whatever reason none of them will connect. Letsencrypt shows all the certs go through with no issues and I can run a speedtest through unraid showing it still can connect to the internet. Overall just confused now why I cant seem to access anything outside the network. I can still somehow connect to plex but stuff like heimdall, radarr, code-server dont load anymore outside the network. Whenever I do heimdall.mydomain.com Just prompts cloudflare saying something is wrong with my server. unluckyserver-diagnostics-20220131-1848.zip

So to start here is my server and also I attached the diagnostics for the drives. Now I had purchased several 10tb wd red drives and initially had no issues with the drives. I did a preclear on each one and then distributed some of my data over the drives using "unBALANCE". Again everything was normal for the first week but then my second parity went down. Initially thought it was odd but removed it off the array. Ran a preclear to see if it was still good and then put the parity back up. I had dealt with this three times now and each time the parity drive would die every 3 days or so. I then came to terms that maybe this drive is just dying so I purchased another drive to replace it. Then one of my wd red drives went down with the second parity drive. I then went about how I usually add the drives back onto the array but this resulted in about 3tb's of data being lost. Essentially everything I moved onto the wd red drive. Thankfully though I had another drive with all the data saved lying around for situations like this and got all the data back. Thing is though as I began moving data back onto the drives I noticed ALOT of errors begin appearing on all the wd red drives. I attached a screenshot of it but basically showed 344 million errors on two of the drives. Seeing all these errors made me to think that it may not be the drives so I began looking around and many began to say how cheap SATA cards can cause these types of things to happen. I have this in my server. Sooo, got me thinking I need to replace the sata card with an HBA card. I have no idea what they are but understand they are alot better then the sata cards and have considered getting an 8 port one. Moreover just trying to figure out whats up with the sudden problems ive been having to deal with and if getting an hba card would fix it. WDC_WD101EFBX-68B0AN0_VCJBBRRP-20211223-2223 disk4 (sde).txt WDC_WD101EFBX-68B0AN0_VCJAHAHP-20211223-2223 disk3 (sdb).txt ST10000VN0004-1ZD101_ZA2BN4ZH-20211223-2223 disk1 (sdg).txt SHGP31-1000GM-2_AJ0BN90921170C35J-20211223-2223 cache (nvme0).txt WDC_WD101EFBX-68B0AN0_VCJB7V8P-20211223-2223 disk2 (sdc).txt ST10000NE0008-2JM101_ZPW0N3TK-20211223-2223 parity (sdf).txt ST10000NE0008-2JM101_ZPW0K8YX-20211223-2223 parity2 (sdd) - DISK_DSBL.txt SanDisk_Cruzer_Glide_4C530001240112105053-0-0-20211223-2223 flash (sda).txt unluckyserver-diagnostics-20211223-2223.zip

Yeah looked like I just had bad luck. I ordered instead this drive by Western Digital and worked the moment I plugged it in. Started the preclear and everything is running like it should.

Good to know for future reference, thx.

Ok, I was presuming so. I'm just surprised then that I got now two drives in a row that arent working.

I have recently purchased a new Seagate IronWolf 10TB drive due to my server running low on storage. I presumed the next steps to adding the drive onto unraid would be to install the drive, format the drive, and preclear the drive. Anytime I would attempt to preclear (gfjardim - 1.0.22) the drive it'll show "Pre-Read: 0% @ 0 MB/s" and this is what shows in the logs... Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0 bytes copied, 181.749 s, 0.0 kB/s Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: dd: error reading '/dev/sdb': Input/output error Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0+0 records in Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0+0 records out Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0 bytes copied, 181.835 s, 0.0 kB/s Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: dd: error reading '/dev/sdb': Input/output error Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0+0 records in Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0+0 records out Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0 bytes copied, 181.962 s, 0.0 kB/s Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: dd: error reading '/dev/sdb': Input/output error Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0+0 records in Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0+0 records out Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0 bytes copied, 182.037 s, 0.0 kB/s Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: dd: error reading '/dev/sdb': Input/output error Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0+0 records in Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0+0 records out Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0 bytes copied, 182.113 s, 0.0 kB/s Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: dd: error reading '/dev/sdb': Input/output error Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0+0 records in Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0+0 records out Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0 bytes copied, 182.191 s, 0.0 kB/s Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: dd: error reading '/dev/sdb': Input/output error Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0+0 records in Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0+0 records out Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0 bytes copied, 182.278 s, 0.0 kB/s Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: dd: error reading '/dev/sdb': Input/output error Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0+0 records in Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-Read: dd output: 0+0 records out Nov 20 21:53:14 preclear_disk_ZS512YZW_19855: Pre-read: pre-read verification failed! Nov 20 21:53:15 preclear_disk_ZS512YZW_19855: error encountered, exiting... Also when I do the Script "Joe L. -1.20' it states... "Sorry: Device /dev/sdb is not responding to an fdisk -l /dev/sdb command. You might try power-cycling it to see if it will start responding." I initially thought it was a bad drive since I couldnt even load the drive when installed into my pc but this is the second drive now having the same issue. Model Family:n/a Device Model:ST10000VN0008 Serial Number:ZS512YZW Firmware Version:SC61 Size:10 TB This is my server ST10000VN0008_ZS512YZW-20211121-2248 (sdb).txt

Jesus. That's really all it was. Was having the same issue and tried troubleshooting every little detail. Saw this and looked at what I was on. Noticed it was on dev and not latest...