All Activity

Will do. To confirm, get the Diagnostics right after a reboot, or can I grab that anytime? I assume right after reboot, since that's when it fails to load.

I replaced the cpu and used the original ram. The server been stable for almost 15 hours now and I haven't had any of the error I was seeing before while using it.

Thanks, I'll just stick with the simple solution for now.

I assume this means the FS is fine? Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 1 - agno = 3 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting.

Btrfs usually work fine with good hardware, but try zfs, if you also have issues with that, there could be an underlying hardware problem.

Sounds perfectly reasonable for a core temp.

https://forums.unraid.net/topic/57181-docker-faq/page/2/#comment-566088

See if there's a support thread for that container:

You could change them, but probably best to just wait.

I bought 3-4 keys due to lack of help over the past 3 -4 years and i wouldnt even care if i would be recieving help but if i mess up in 365 days i wont pay another 300 for less drives.. no way. can you look up my old registrations so when and if power outage or surge or anything that happens more often then 365 days i could use one of my 3 other keys? or at least have them set up for in case i make more servers prob wont cuz lack of support. But i feel i should get the keys i paid for, and was basically told im shit outta luck buy more.

Thanks I should have tried that to be safe but bought a new set of ram and all good.

It can happen but shouldn‘t. Please try the slot that you used before.

Werde ich auch gleich mal machen, da ichdas sehr cool finde. Das schaue ich mir auch gleich mal an Wie hast du das hinbekommen. Nur mit installation von Memorys?

I wonder if it got fried. It showed up fine at first, then it ended up getting to around 96c and thats when i first saw the error. Does / can that happen?

Since only one of the drives is failing, can I just swap out that one drive and see if it rebuilds from the good drive to the new drive? I did do an rsync onto my array but it completed with some file errors so I'm not sure if I have a perfect copy. I do use CA backup, but I never realized that it was wiping all of the previous runs. So I only have a backup from this past Monday but I'm not sure when the corruption started so I'd like to resort to wiping and reformatting as the last result in the event my backup is corrupted. Will swapping out the bad drive with the new one and letting the system rebuild the pool work?

Got it solved,, but its a lil crazy the money i've got 3 keys before price rose just recently.. all pros. because the lack of help i get around here. So now if i have an issue in the next 365 day i have to spend 3 times what i origianlly spent..? for 1 key thats what for 6-12 drives when mine is max... like idk guys this doesnt seem right the lack of support even after you pay. if ur corrupt or key issues like i and what if i replace key and did it wrong.. with a sick kid that eat thru a gi tube and cant sit up at 2.5 years old my hard earn money cant keep going to support unsupportive community that now seems about money need to just figure out way to make back ups that you guys dont list. so i can have 200 then its only like 50 bucks a key /end rant

I'd like to see this too tbh.

Please see here: I think this is a pretty step by step tutorial.

sorry for the late reply, had to take a trip out of town and did not see this at all i have made some config changes, so hopefully it doesnt sully what you where looking for, please find the requested diag in our convo

The NginxProxyMaager has been running for over two years now without any problems, except that the automatic update of certificates does not work, but that is not so wild. I created a new ProxyHost today and then restarted Unraid. Since then, the proxy no longer works and I get an error message in the log: Does anyone have any tips on how I can rectify the error?

Ok I've got a data transfer going but once that's done I'll put the array in maintenance mode and check the filesystem on the cache disk. Are you saying that you disagree that it is a RAM issue? Or just that if I don't want to address the RAM issue simply recreating the docker.img file is easy? I do like my data uncorrupted so if it is a RAM issue I'll address it, doesn't mean I'm any less mad about having to do it in a server that's less than 2 years old. I've got someone who says the can memtest the sticks for me this weekend so I'll have them do that as well just to rule the RAM out.

I have a question on UPS for my unRAID. I have the CP1350PFCLCD from CyberPower. Today, we had a power outage for an extended period of about 15 to 20 minutes. It did go into shutdown mode and turned off my unRAID server. The only thing I disliked was that my UPS shut off also. If that happens when I'm gone, how will I get my UPS to turn back on without physically pushing the UPS power button?

Empfehle mit einen sicheren Stick und ich versuche es noch einmal. Das Image zu kopieren ist nicht das Problem.

Der 2te ist ein USB2 , hatte das mit dem USB3 zu spät gelesen. Der erste ist ein Intenso, der zweite ein noName.

Oh it'd sure be amazing to do that turn on -> backup -> turn back to off move. Is there a guide on that anywhere? Also what container update in regards to the root vs luckybackup directory? The container is running on my source machine. I dont have a LuckyBackup docker container running on my destination machine where the id_rsa is kept. I must be brain farting on this somewhere along the line. Here is a screencap of my docker container config