SLRist

Just thought I should update the status of this issue - it seems that saved Windows credentials were causing the issue. I deleted these using Control Panel / Credential Manager / Windows Credentials (Windows 10) and at the top, where server credentials are listed, simply clicked on the UNRAID server concerned and selected 'Remove' Once I had done this, all the shares under that server were once more browsable under Windows Explorer. This works even with NetBIOS disabled under SMB settings.

Yes, I know I have a UPS issue - it's an ancient APC with a network card in the back, and I think it's just responding too slowly across multiple unraid servers. Not really sure how to diagnose it. Other than that - yes, it's just basic NAS sharing - no containers or VMs or plugins installed. I did a memtest when I installed the RAM. No errors detected.

I've been waiting all day for a single 60GB file to copy over to my otherwise empty 2TB cache drive on my unRAID 6.11.5 server (8GB RAM installed - nothing but file sharing enabled). It's going at about 1MB/s (and it is going to the cache drive and not the array, as I can see it writing to the cache drive). Dashboard says that RAM is only about 23% used. However, the log is full of memory errors. Any idea what might be going on? Diagnostics file attached. Jan 15 21:37:48 UNRAID-02 nginx: 2023/01/15 21:37:48 [crit] 1250#1250: ngx_slab_alloc() failed: no memory Jan 15 21:37:48 UNRAID-02 nginx: 2023/01/15 21:37:48 [error] 1250#1250: shpool alloc failed Jan 15 21:37:48 UNRAID-02 nginx: 2023/01/15 21:37:48 [error] 1250#1250: nchan: Out of shared memory while allocating message of size 7997. Increase nchan_max_reserved_memory. Jan 15 21:37:48 UNRAID-02 nginx: 2023/01/15 21:37:48 [error] 1250#1250: *1052152 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" Jan 15 21:37:48 UNRAID-02 nginx: 2023/01/15 21:37:48 [error] 1250#1250: MEMSTORE:00: can't create shared message for channel /devices Jan 15 21:37:49 UNRAID-02 nginx: 2023/01/15 21:37:49 [crit] 1250#1250: ngx_slab_alloc() failed: no memory Jan 15 21:37:49 UNRAID-02 nginx: 2023/01/15 21:37:49 [error] 1250#1250: shpool alloc failed Jan 15 21:37:49 UNRAID-02 nginx: 2023/01/15 21:37:49 [error] 1250#1250: nchan: Out of shared memory while allocating message of size 7997. Increase nchan_max_reserved_memory. Jan 15 21:37:49 UNRAID-02 nginx: 2023/01/15 21:37:49 [error] 1250#1250: *1052158 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" Jan 15 21:37:49 UNRAID-02 nginx: 2023/01/15 21:37:49 [error] 1250#1250: MEMSTORE:00: can't create shared message for channel /devices Jan 15 21:37:50 UNRAID-02 nginx: 2023/01/15 21:37:50 [crit] 1250#1250: ngx_slab_alloc() failed: no memory Jan 15 21:37:50 UNRAID-02 nginx: 2023/01/15 21:37:50 [error] 1250#1250: shpool alloc failed Jan 15 21:37:50 UNRAID-02 nginx: 2023/01/15 21:37:50 [error] 1250#1250: nchan: Out of shared memory while allocating message of size 7997. Increase nchan_max_reserved_memory. Jan 15 21:37:50 UNRAID-02 nginx: 2023/01/15 21:37:50 [error] 1250#1250: *1052169 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" Jan 15 21:37:50 UNRAID-02 nginx: 2023/01/15 21:37:50 [error] 1250#1250: MEMSTORE:00: can't create shared message for channel /devices unraid-02-diagnostics-20230116-0251.zip

Many thanks. Actually, I do have an old Dune media streamer that still needs SMBv1, but I will take a look through your suggested post and see what I can do. I might need to just ditch that media player and replace it with another Zappiti.

I should say at the outset that I've already tried this fix, but it didn't fix my issue: All of my 5 unRAID servers are set up the same - just sharing video ISO files - no VMs or Dockers. All are running v6.11.5. All running on HP Proliant Microservers (N36L, N40L etc.) with 8GB RAM installed. I can see all servers listed in Windows (10) Explorer. Windows 10 has SMBv1 enabled. For three of them (UNRAID-02, UNRAID-03, UNRAID-04), I can click on that server and see and access all the shares - e.g: \\UNRAID-02 On the two problematic servers (UNRAID-01, UNRAID-05) - when I click on the server name in Windows Explorer, after some delay I get the following error message, and clicking [Diagnose] reveals no identification of the problem. These are some relevant settings I have on one of the problematic servers. As far as I can see, these settings are all the same as on the other machines whose shares work as expected. All shares have SMB security set to 'Public'. Any suggestions what might be wrong? Example share:

Many thanks - made a backup of the USB drive before copying over the bz* files (including the .SHA256 files - which it actually requires) as recommended, and re-booted. As simple as that. Worked like a charm.

I have 4 machines which need upgrading - two are on 6.3.2 and two are on 6.3.5 None are running anything but the basic unRAID drive array - no dockers or VMs. No plugins other than the Dynamix webGui 2017.02.16 (6.3.2) and 2017.05.26 (6.3.5). Tried following these instructions for v 6.3.x upgrade: https://wiki.unraid.net/Manual/Upgrade_Instructions Under Plugins, when I [Check for Updates] it finds an update to 6.3.5 Unfortunately, when I try to [update] it tells me: plugin: updating: unRAIDServer.plg plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.5.3-x86_64.zip ... failed (Invalid URL / Server error response) plugin: wget: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.5.3-x86_64.zip download failure (Invalid URL / Server error response) That update file is no longer on S3 🤨 So I figure I need to upgrade manually - probably to a later version? Then I see this guidance: https://unraid.net/blog/6-11-1 So I decide I should run the Update Assistant - and I go to Tools to find it - except there is no update assistant! 🤔 So then it says I need to install the Fix Common Problems plugin. And I read this article: Which tells me to go to the Apps tab and search for Fix Common Problems Except that I don't have an Apps tab! 😟 I have: Dashboard / Main / Shares / Users / Settings / Plugins / Tools And at this point I am forced to admit defeat. Any idea what I need to do to get to the point where I can actually upgrade unRAID OS?

Perfect - thanks. Maybe I should enable it on all my 4 other unRAID servers too

OK - I temporarily borrowed 8GB of RAM from one of my other servers and enabled write caching in BIOS - now parity sync speed has gone from about 4MB/s to 100MB/s! Estimated completion of sync is 22 hours rather than closer to 22 days! Thanks for the help. Problem (apparently) solved! Is it a good idea to leave write cache enabled permanently - or is it better to disable it? All my servers are connected to a UPS.

Many thanks. To be honest, I think I'll just let it start from the beginning. Hopefully it will run a lost faster after the RAM is upgraded and maybe write cache is BIOS enabled (if it isn't).

Thanks for your suggestions. Is it OK for me to pause the parity sync, shut down the server and upgrade the RAM before re-starting and continuing the parity sync, or would I be better to scrub the array and start from scratch?

Hi - just built a brand new unRAID server in a HP Proliant N40L 2GB server chassis (I already have 4 other unRAID servers in similar hardware - except they have 6TB drives or smaller) 4 data drives + 1 parity. These are shucked 8TB Seagate desktop 5400rpm drives which have been extensively tested for errors (over several days) before installing. I also ran a memory test of the 2GB single memory card on the motherboard before starting. Running initial parity sync on the empty array. It's running *very* slowly (1MB - 6MB per second) - sync is only at 6.2% after 34 hours. Estimate at this rate is another 20 days to complete! I have attached a Diagnostics export. I see lots of repeated mention of: Dec 7 02:17:20 UNRAID-05 nginx: 2022/12/07 02:17:20 [error] 1353#1353: *390296 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" Dec 7 02:17:20 UNRAID-05 nginx: 2022/12/07 02:17:20 [error] 1353#1353: MEMSTORE:00: can't create shared message for channel /devices Dec 7 02:17:21 UNRAID-05 nginx: 2022/12/07 02:17:21 [crit] 1353#1353: ngx_slab_alloc() failed: no memory Dec 7 02:17:21 UNRAID-05 nginx: 2022/12/07 02:17:21 [error] 1353#1353: shpool alloc failed Dec 7 02:17:21 UNRAID-05 nginx: 2022/12/07 02:17:21 [error] 1353#1353: nchan: Out of shared memory while allocating message of size 7993. Increase nchan_max_reserved_memory. Any suggestions please? unraid-05-diagnostics-20221208-0759.zip

Aha! Genius - many thanks, you are correct.

What's strange is that, once the parity drive re-built, the shares all disappeared from the GUI. I know they're there, because I can connect to them all remotely. I can also add new shares, but once they're added, they don't appear in the GUI either. I'm guessing there's some error which is stopping the GUI from pulling a list of them. Which is a bit annoying.

Fantastic - super helpful, thanks!

Once I backed up the files to my NAS, I formatted the Flash drive and installed version 6.2.4 from scratch with default settings, and copied over my v5.x license file. Booting up as a default, blank install, it listed all my existing drives from the v5.x array. I selected the drives into the array in the same order they were before, and the parity drive started to rebuild (this is taking a long time, as there is 14TB of files across the 4 disks). The original shares appear to be intact, and I can see all the files. All that is missing are the original user accounts. So it appears at this time that all I need to do is re-name the server, create the old accounts, set up the UPS settings and I'm finished. No need to copy all the files back over. Unless I'm missing something... I had custom split levels set for each share on v5.x - I'm not sure how the automatic split method is going to work on v6.x, but I guess I'll see...

Indeed, I had no trouble with the Ubuntu server reading the drives. Still copying files off them, and will rebuild as v6 before coping them back over. Many thanks.

Hello. Many thanks for your assistance so far. I ran a CHKDSK on the Flash drive, and it came up as OK - no issues. The log I posted before was actually covering the whole incident from boot to freeze to shutdown. I can get it to stop responding almost instantly. ---- As an aside, I was wondering whether I can copy my files off the array using another machine rather than trying to repair it in-situ. I have a laptop running Ubuntu 16.04, and a USB SATA dock plugged into it. If I pull one of the 4 drives from my unRAID array and connect it up to my Ubuntu machine using the USB SATA dock, will I be able to read the files? Will doing so stuff up the drive so that the array will no longer work? (Even if I don't write to it)? Many thanks.

It's very basic: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & The server is almost a default config - no packages running except APCUPSD. I hadn't made any changes to it for months. It just started playing up out of the blue. I was wondering whether maybe one of the drives was on the way out, or maybe the network card was about to blow up. Unfortunately my Linux knowledge is very basic, so I don't know how to test these things. I would be quite prepared to trash the server and install v6.x from scratch as long as I could re-mount the existing drive array. The only other option would be to buy a new set of drives, install those, and copy the contents of the old drives over one by one, by mounting them on my Windows PC. I'd rather not do that if I don't have to though, it's quite a costly option.

I couldn't get FTP to work, but I finally realised that the latest logs were getting written to /logs, so I pulled out the Flash drive and stuck it in my PC to get the log file off. This is one which covers a frozen session (attached) - hopefully there is something useful in it, but I couldn't see anything obvious... You can see halfway down where I initiated a 'powerdown' at the command line following the freeze. I had to ZIP it, as it was too big to attach as a TXT file. syslog-20170127-203425.zip

Unfortunately not. I just tried booting into safe mode for the second time, and I immediately get the web GUI stop working on me.

Thanks. I had to restart the server again to get access to the GUI to grab the Syslog from Utils. I've attached it as a TXT file, as it was apparently too big to cut & paste into the forum. unraidsyslog01.txt

I have three unRAID Plus servers running v5.0.5 One of the servers (which has been running fine for months) has just started being rather unstable. After a restart, it appears to run fine. However, the web GUI and shares will, after a couple of minutes, stop responding with the following message in Chrome: This site can’t be reached unraid-03 refused to connect. Search Google for unraid Main ERR_CONNECTION_REFUSED I also am unable to connect to shares via my Windows PC. I can ping it, and access it via the command line with a keyboard and screen attached. If I re-start it, I can again access the GUI, but again, after a very short period, it stops responding. Shares also. I was wondering whether an upgrade to v6.x would be wise, or whether I should perform some more diagnosis beforehand. I have a backup of the Flash drive, but only since the problem started occurring. I am not sure the file system is 100% clean, as I have had to power it down (reasonably gracefully) by using the power button to initiate a shutdown several times. It has not been written to recently, On booting the server, the web GUI looks like this: Once the server becomes unresponsive, after very many attempts to refresh it, I may be able to get the homepage to respond, at which time, the array appears to be offline: Many thanks in advance.

I reverted the 'go' file back to its default, and now the server shuts down on power failure. Can anyone tell me which file I need to edit to add some unmount statements to allow shutdown to complete successfully?

I'm not sure I am! When I run a manual shutdown I go through the following on the GUI: Which shuts the server down fine. I don't need to unmount any shares or remotely mounted shares beforehand. I haven't put any special share unmount provision in place.