dv310p3r

So, after a second reboot everything seems to be working fine. Not sure what it is. I think the only thing I've changed prior to the problem was the Netdata app / container. I had it running for a few days no issues, so I'm not sure that's it. But I did remove it between freezes, and it's been up sicne then. Thanks for the help.

Attached. syslog

Yep, i can get that. Should I upload it here, or should I parse / clean out any identifiable information first? I would guess that's what the diagnostics command does, but don't know for sure.

Should the diagnostics collection take long? It's been running for about 10 minutes, and nothing has been created yet. I can access the logs myself and share if needed, I'd just need to know which ones to share.

I'm not sure what's happening. And I can't say what may have triggered it. Yesterday morning everything was fine and then in the evening my server wasn't working. I could still SSH into and I could still see the shares, but the WebUI wasn't working any longer. Oddly, some containerrs still seem to eb running while others are not, like plex for example. I'm at a loss for what to do next? Please help.

Ok, yeah. So, somehow what's being shown in the frontend, and what the config file are for the shares are different. When I make a slight change, like the description and then apply with it's current setting, the config file for the share then accurately reflects what's on the UI. So, i guess my next question would be, if the UI is not reflecting what's in the config file, which is reflecting how unraid behaves. Is it whatever is in the UI or is it whatever is in the config file for the share. My gut says config, but what would be odd about that is that I have seen files move onto the array and not into the cache. So I'm not sure.

Could there be some kind of issue with configs after upgrading? Or, am I missing something? When I go into the Shares, they are not configured to use a pool, as far as I can tell, below are some screenshots of some of the shares. Also, where can I find the flash drive to remove those files you mentioned? I do most of my file management via ssh and using midnight commander. Edited: found the /boot/ folder... Thanks,

Diags attached. unraid-server-diagnostics-20231023-1118.zip

So, I'm getting this error: Share books references non existent pool cache I followed the link to the forum where this error and a fix are explained. But, what I don't understand is that I've never had this share using any cache pool at all. What is true is that about a week ago I did update all the cache pools by adding an additional cache pool with a pair of nvme's. I'm curious as to what could be causing this because now ALL my shares are reporting the same error, and as with the share above... none of the others except appdata were using the cache. Thanks

With all the other stuff happening after getting the system back up, I haven't had a chance to thank JorgeB for his help. Thanks a million for this, I wouldn't have thought to try this or look at this as a problem and after the replacement of the PSU and adding some additonal SATA power cables, this did the trick. So, THANKS A MILLION!

Nope, no ability to SSH. So, I did a bit of searching and saw a random post somewhere on this forum where a person said this error was a generic error (he had basically the same one). He said his problem was a Docker container. So I restarted, quickly went into the docker tab and turned off all dockers and made sure they don't come back up on restart. Then I started them all one by one. Turns out my deluge container was causing the problem somehow. So I deleted it and now I'm all good... no issues all night. Not sure what that was all about.

Well, after a day of rebuilding in maintenance mode, I turned on the array in normal mode, and everything seemed fine, all the drives are reporting correctly, but after a minute or two, it stopped responding. I can't get diagnostics from the Command Line because when I plug in my monitor and keyboard, I see the following error. I haven't shut down in case someone can give me some directions to get the diagnostics from the system. Any help would be appreciated.

Look, I get it... I asked a question in a forum and got the classic, RTFM response. I should have known better. Either way, I think something that can be taken away here is that whatever UnRAID did to their manual, was kind of silly. As you scroll through past forum posts, and click on links to the manual, they don't take you, anymore, to where the poster thinks their link was taking people. UnRAID made a major change to the manuals online and it's caused a lot of confusion. As moderators maybe you can help them get that message.

Ok, so for anyone else out there looking for a simple answer to the question... how do I enable (re-enable) disks on my array that I think are fine but now have the Red X on them, here's what I found on Reddit where someone answered someone else's exact same question. Stop the array Unassign the disk Start the array in maintenance mode Now stop the array again Reassign the drive to the same slot Then start the array back up again in maintanence mode and it'll start to rebuild them I'd leave the rebuild to happen in maintenance mode, at least that's what worked for me (see edit note below) Image of the post on Reddit for reference. EDIT: I was having issues with the system freezing up after following the instructions above. I'm not sure what it was exactly, but I decided to start the array in maintenance mode to do the rebuild, and it seems to be working just fine now. So I edited the steps above to include that info.

You know, you could link me. Pointing me to the manual doesn't help very much considering that there's a lot of stuff there, and all i'm looking to do is know how to re-enable a drive. I've searched for that in the manual and I'm not easily able to find it. Now I remember why dislike using forums so much.

So, i'm thinking the drives are ok, but now they have red X's on them, and I can't figure out how to rebuild them. At least from my searching that's what it seems I have to do. Anyone got any advice?

So, should I get a bigger PSU?

I had an array of 11 disks total, 1 parity and 10 disks. One of the drives failed on Sep 22, I didn't think much of it at the time and didn't even really troubleshoot it much. I had been runnng out of space so I decided to use this as an opportunity to upgrade to a bigger drive and while I'm at it, ad some more. So, I bought 3 14 tb drives (my parity is a 14 tb). I used the three drives to first, replace the bad drive, then I added one more drive as a parity so I'd have 2 parity drives, and then finally I added the third drive as an additional disk increasing my total drive space. Everything was fantastic till this Tuesday October 3, I had another drive reporting errors so the disks was taken off and data was being emulated. I figured, now I gotta start investigating. But, as life happens, I was a bit too busy. Anyway, I woke this morning and now I have a second drive failing. So, I'm here now, in desperate need of some guidance, because 1 drive failure can be expected, 2 can be a coincidence, 3 though... well that's a pattern, and likely a problem (or at leasts I thinks it is). I've attached the diagnostics effective this morning while the array was running, and I've attached a screenshot from how it was on Tuesday (10/03/23), and then one from this morning (10/05/23). I'm taking the array offline because well, I don't know I just feel safer that way, but of course, I'm here, so I'm not an expert. Any guidance would be helpful and if any additional logs / diagnostics, etc are needed, please let me know. server-name-diagnostics-20231005-0922.zip

Ok. So, it seems to be good now. I think it was a cloudflare thing. I had to turn on full end to end encryption in the cloudflare settings and then enable https in the nginxproxymanager, and it's working. So, thanks for the guidance.

Ah, yes, I understand what you mean now. And yes, if I have no Proxy Hosts configured in NPM and then try and go to mydomain.com, I get the congratulations page. DNS seems to be just fine.

Brave. Also the issue is that I do have to manually add www otherwise it doesn't work. There is an A record that points to my IP address. That's not an option. The host is a required field. Yes. If I go to the IP address shown in cloudflare it'll show the "Congratulations, You've successfully started the Nginx Proxy Manager." page. Also, if I go to www.mydomain.com, which is the host I configured in NPM, it takes me to the site no problem. So, I want to do a better job of explaining what's happening. In cloudflare right now, I have an A record that points to my IP, and a cname for www that targets the main domain. We'll say it's mydomain.com. In NPM on my unraid server, if I create a proxy host and put "mydomain.com" in the Domain Names input, the proxy doesn't work. Meaning, if I go to mydomain.com in a browser, I get a 500 error from cloudflare. At the same time I know NPM is running because I can go to the IP directly and see the congratulations page. Also, if I curl to the container from within the NPM console, it can communicate. Now, for the weird part. If I create a new Proxy Host and give it a domain name of www.mydomain.com OR... to clear up any confusion with WWW, it' has nothing to do with WWW, because if I put poop.mydomain.com or any other subdomain.mydomain.com... NPM works as expected. If I visit, poop.mydomain.com, or subdomain.mydomain.com, I see the properly served container (of course, as long as I created the correlating cname record in cloudflare). I hope that clarifies things.

I've been reading through all these posts, and not finding anything that'll fix my issue. And it doesn't seem to be nearly as complicated as all the stuff people here are having. I must be really missing something, but I cannot get Nginx Proxy manager to direct traffic to my main domain but it will work fine in sending traffic to containers or VM's if I use a subdomain. For example, if I make a proxy host sub.mydomain.com pointing to a container, it works. If however I make a proxy host mydomain.com pointing to a container. It does not work. I am not sure what I'm doing wrong.

ceres-station-diagnostics-20211227-1648.zip Attached.

I switched my AMD Ryzen 2700X to an Intel 10700 because I wanted to take advantage of QuickSync for my Plex Server. Since that switch I've been having serious issues. Here's my current hardware: Unraid Version - 6.9.2 Motherboard - MSI Z490-A PRO CPU - Core I7 10700K RAM - 32 GB Crucial Ballistix Sport LT 2666 MHz DDR4 DRAM DISKS - Unassigned Samsung SSD 860 Evo 1TB - used for downloads - Cache (two SSD 850 Evo 500 GB - Array (10 disks + 1 Parity total 11 disks) Parity is 14tb Disks are either 14tb, 8tb and 3 tb I've done no overclock, nor do I plan to. Issue #1: Since the switch over, after rebooting the system, sometimes it'll get an IP, and other times it'll get the auto assigned 169.... address. I have to restart it several times until it connects to the network. Issue #2: It's randomly freezing out of nowhere. The GUI won't load and after a restart it'll work again (unless it didn't get the right IP address). Sometimes it'll work for minutes, other times hours. Honestly, I have no idea what to do, or where to start. Any help would be greatly appreciated.

I've had unRAID since the end of 2016. My favorite aspect of it, is that in those 3 years, I've been running the same installation of it, without issue. I add new drives, no problem. Switch drives, no problem. I've changed my entire CPU / RAM / Motherboard 3 times, no problem. That damn thing just runs, and runs, and runs. I've done so much testing, creating VM's, Dockers, modifying, etc... and it keeps chugging along, letting me get my homelab kicks in, for very little time investment. Today I run my pfSense router on it, my HASS.io automation on it, and all my downloading, plex, etc. It just keeps running. I'm an evangelist of unRAID too. I've gotten at least 3 friends to use it. And they didn't believe it could do some of the things I said it could, like being a server and a gaming PC at the same time. I truly love my unRAID server. Thanks for it!