[Unassigned Devices Preclear - a utility to preclear disks before adding them to the array]

17 minutes ago, JonathanM said:

Do you have the disk location plugin installed?

Yep.  That was it.  Many thanks.  Problem solved. 

[Unassigned Devices Preclear - a utility to preclear disks before adding them to the array]

Anyone ever seen a blank dashboard page during preclear?  I started a preclear on a new 8TB drive two days ago.  When I login to the server the main Dashboard page is blank.  I can navigate to all other tabs just fine.  But the main Dashboard is blank.  The only thing that has changed on my server is starting the preclear.   

 

[[Plugin] NUT v2 - Network UPS Tools]

19 minutes ago, Rysz said:

 

pfSense NUT and NUT in general will by default shutdown when the UPS sends the low battery signal "LOWBATT" (usually happens around 20% charge). The runtime remaining or battery percentage remaining thresholds which trigger the low battery condition are often configurable on the UPS itself. I also happen to have an Eaton 5P and you can configure this on the UPS screen here:

So UNRAID also always does this as a last resort (shutting down on a low battery signal), but also has other additional shutdown conditions which act on top of that to ensure that UNRAID has sufficient time to shutdown before any such low battery signal. So setting a reasonable time for the additional shutdown condition (e.g. Time on Battery) on UNRAID while keeping the NUT defaults on the pfSense would ensure that UNRAID shuts down before the pfSense (and any other devices using basic NUT).

 

Perfect.  Thank you so much.  This is THE best explanation I have read so far.  Makes so much sense.

 

Thank you again for your help.  Hopefully others benefit from this.

[[Plugin] NUT v2 - Network UPS Tools]

21 minutes ago, Rysz said:

 

Indeed it seems like the pfSense is dropping the incoming packets to your NUT server's port on TCP 3493.

Please do report back if you managed to open the port and if it worked out for you eventually. 🙂

 

I figured it out by using some of the settings in this write-up.   I had to add additional configurations to ups.conf and upsd.conf.  The instant I hit SAVE on the pfSense box, UNRAID saw the info instantly.

 

EDIT: the ups.conf line is NOT needed.  Only upsd.conf setting.

 

 

 

One last remaining question if I may.  And understanding that this is a support thread for the UNRAID plugin, but figured it's worth asking.  How can I adjust the setting on the pfSense side so that my pfSense device does not shut down until the very last minutes of remaining battery life? 

 

Many thanks for the support today.

[[Plugin] NUT v2 - Network UPS Tools]

5 minutes ago, Rysz said:

That's weird, is there anything in the UNRAID logs indicating a problem?

 

Well how about that.  There sure is. 

 

 

I'll do some poking around in pfSense and see if it's being blocked somehow.  Good suggestion.

[[Plugin] NUT v2 - Network UPS Tools]

8 minutes ago, Rysz said:

 

Ah, my bad, in that case you'll put the pfSense's configured Slave username and password (that'd be monslave and yourpassword in the original screenshot) into the respective NUT Monitor username and password fields on the UNRAID server. NUT Mode would be Slave on the UNRAID server. 🙂

The second credential fields were recently hidden because they were unused in NUT Mode Slave.

 

Yep, that is exactly what I did. 

 

  

 

However, the UNRAID server does not display any UPS information.  it just sits there and "spins".  Then evetually indicates that there "no information available".

 

  

[[Plugin] NUT v2 - Network UPS Tools]

1 minute ago, Rysz said:

 

You need to set NUT Mode to Netserver.

On the Unraid side or pfSense side?  Just to clarify, I am using (or attempting to use) pfSense as the master and Unraid as the slave.

 

Thank you for the amazingly fast reply by the way. 

[[Plugin] NUT v2 - Network UPS Tools]

On 9/4/2023 at 7:44 PM, DataBitz said:

Just wanted to share my working configuration where Unraid is a Slave and pfsense is the Master, for anyone else looking.

Eaton 3S 850 connected via USB to pfsense (192.168.1.1)

 

pfsense config

 

 

Unraid NUT v2 config.

 

 

I am curious to know if you had to make any changes to this configuration recently?  I tried applying the same settings (I am also using an Eaton UPS unit [5P 1500]) but am not able to get Unraid to grab info from the pfSense gateway.  Also, I do not have a UPS Slave Username or UPS Slave Password on the Unraid settings.   This is all that is available to me.

 

 

[Unassigned Devices Preclear - a utility to preclear disks before adding them to the array]

1 minute ago, dlandon said:

That older server needs it enabled so UD can resolve the IP address.

 

Did the USB2.0 port change let the 'df /' work?

Replying in/switching to DM.  Apologies.

[Unassigned Devices Preclear - a utility to preclear disks before adding them to the array]

2 minutes ago, dlandon said:

Give me a new diagnostics in that condition.

Many thanks for the continued help.  Sent you a DM.

server-nas-diagnostics-20231101-1220.zip

[Unassigned Devices Preclear - a utility to preclear disks before adding them to the array]

23 minutes ago, dlandon said:

Reboot with docker set to not start.  I suspect you have a docker container mapping issue.

Yep.  That's the condition I am currently sitting in.  Rebooted to a normal boot, but both Docker and VM services are turned off.  Plugins are all loaded and active.  Same rootfs condition.

 

Filesystem     1K-blocks  Used Available Use% Mounted on
rootfs                 0     0         0    - /

 

[Unassigned Devices Preclear - a utility to preclear disks before adding them to the array]

3 minutes ago, dlandon said:

Just go to the apps and add them back.

So this is interesting.  I just booted back up under normal mode, but prior to doing so I removed .plg files from the \flash\config\plugins folder.  So no plugins are currently installed/running.  Docker is shut down and VM is shut down.  I am back to:

 

Filesystem     1K-blocks  Used Available Use% Mounted on
rootfs                 0     0         0    - /

 

[Unassigned Devices Preclear - a utility to preclear disks before adding them to the array]

1 minute ago, dlandon said:

I was going to ask you to do that next.  That's what it should look like.  A plugin or docker is causing an issue.  Add them back one at a time until you see the issue.  Let me know what you find.

I verified it was not a docker or VM.  Same results with all dockers and VM running.  No issues. 

 

How does one go about adding plugins one at a time? 

[Unassigned Devices Preclear - a utility to preclear disks before adding them to the array]

2 hours ago, dlandon said:

Go to a command line and show the output of this command:

df /

 

By the way, when I boot in safe mode I get this:

 

Filesystem     1K-blocks    Used Available Use% Mounted on
rootfs          16404780 1090788  15313992   7% /

 

And this:

rootfs on / type rootfs (rw,size=16404780k,nr_inodes=4101195,inode64)
rootfs on /mnt type rootfs (rw,size=16404780k,nr_inodes=4101195,inode64)

 

[Unassigned Devices Preclear - a utility to preclear disks before adding them to the array]

2 minutes ago, dlandon said:

Give me the output of this command:

mount | grep rootfs

 

 

rootfs on / type rootfs (rw)
rootfs on /mnt type rootfs (rw)

 

[Unassigned Devices Preclear - a utility to preclear disks before adding them to the array]

7 minutes ago, dlandon said:

Go to a command line and show the output of this command:

df /

 

df / output:

Filesystem     1K-blocks  Used Available Use% Mounted on
rootfs                 0     0         0    - /

 Did you mean just:

df

 

 

[Unassigned Devices Preclear - a utility to preclear disks before adding them to the array]

On 10/27/2023 at 11:16 AM, dlandon said:

Maybe, but the error was a memory issue.  That's why I had you check the cache_dirs setup.  At this point I would run a memory test.

So I ran a memory test on both the old memory I was using and the new memory I just installed during the switchover (back) to an Intel setup.  All momory checked out fine; no errors.

 

But on the "new" setup, once I got everything up and running I attempted to preclear some discs.  Four discs to be exact.  They all failed and produced the same low memory error.  So I'm now using a new mobo, new processor, and new memory and am still getting the same error.  Also, during these new attempts to preclear, I stopped all dockers and VMs and shut down both services.  As you can see in the stats screenshot the system has plenty of available memory.

 

I'm at a loss.

[Unassigned Devices Preclear - a utility to preclear disks before adding them to the array]

2 hours ago, dlandon said:

Maybe, but the error was a memory issue.  That's why I had you check the cache_dirs setup.  At this point I would run a memory test.

Thank you for the responses and attempts to help.  I'm switching my setup back over to an Intel board in a few days.  Seeing some other wonkiness since switching to AMD.   Will wait until I make that change and run a preclear again; see what happens.  Thanks again.

[Unassigned Devices Preclear - a utility to preclear disks before adding them to the array]

13 hours ago, dlandon said:

I actually prefer the opposite.  Only include the shares you want cached.  If I remember correctly, cache_dirs will cache remote shares and that is not necessry and is wasteful of memory.

Made the changes.  Still same error.  Is it possible it's a hardware issue?  Not the drive, but the mobo or sata ports?

[Unassigned Devices Preclear - a utility to preclear disks before adding them to the array]

1 hour ago, dlandon said:

Start by going to the cache_dirs settings and only inculding shares that need to be cached.  Normally any share on an SSD pool device doesn't need to be cached by cache_dirs.  Shares like 'isos' don't need to be cached.  Cache_dirs by default will cache everything it finds.  It can be a real memory hog.

Thank you for the replay.

 

I don't have any shares on the SSD Pool.  At least not intentionally.  And I wasn't quite sure how to do this, but I went into the settings and excluded every folder that IS NOT a normal media folder.  Hopefully this is what you were suggesting?

 

If I did do it properly, it did not fix it.  Same error on preclear attempt.

[Unassigned Devices Preclear - a utility to preclear disks before adding them to the array]

33 minutes ago, dlandon said:

Post diagnostics.

Apologies.  Forgot to do that. 

diagnostics-20231026-1730.zip

[Unassigned Devices Preclear - a utility to preclear disks before adding them to the array]

I have never been able to get Preclear to work.  It fails every time regardless of the disc.  I have never bothered to seek help and finally decided to as I am in the process of replacing my parity drives.  Would like to preclear them first.

 

This is the second drive I tried today.  Error as follows.  Any help would be much appreciated.  Unraid Version: 6.12.4

many thanks in advance.

 

Oct 26 16:26:57 preclear_disk_70015084_17575: Preclear Disk Version: 1.0.29
Oct 26 16:26:57 preclear_disk_70015084_17575: Disk size: 8001563222016
Oct 26 16:26:57 preclear_disk_70015084_17575: Disk blocks: 1953506646
Oct 26 16:26:57 preclear_disk_70015084_17575: Blocks (512 bytes): 15628053168
Oct 26 16:26:57 preclear_disk_70015084_17575: Block size: 4096
Oct 26 16:26:57 preclear_disk_70015084_17575: Start sector: 0
Oct 26 16:27:00 preclear_disk_70015084_17575: Pre-read: pre-read verification started 1 of 5 retries...
Oct 26 16:27:04 preclear_disk_70015084_17575: size:         0, available:     0, free: 0%
Oct 26 16:27:04 preclear_disk_70015084_17575: Filesystem     1K-blocks    Used Available Use% Mounted on
Oct 26 16:27:04 preclear_disk_70015084_17575: tmpfs              32768     408     32360   2% /run
Oct 26 16:27:04 preclear_disk_70015084_17575: /dev/sda1       30028448 1238544  28789904   5% /boot
Oct 26 16:27:04 preclear_disk_70015084_17575: devtmpfs            8192       0      8192   0% /dev
Oct 26 16:27:04 preclear_disk_70015084_17575: tmpfs           16392372       0  16392372   0% /dev/shm
Oct 26 16:27:04 preclear_disk_70015084_17575: tmpfs             131072    9764    121308   8% /var/log
Oct 26 16:27:04 preclear_disk_70015084_17575: tmpfs               1024       0      1024   0% /mnt/disks
Oct 26 16:27:04 preclear_disk_70015084_17575: tmpfs               1024       0      1024   0% /mnt/remotes
Oct 26 16:27:04 preclear_disk_70015084_17575: tmpfs               1024       0      1024   0% /mnt/addons
Oct 26 16:27:04 preclear_disk_70015084_17575: tmpfs               1024       0      1024   0% /mnt/rootshare
Oct 26 16:27:04 preclear_disk_70015084_17575: Low memory detected, aborting ...
Oct 26 16:27:04 preclear_disk_70015084_17575: Pre-read: pre-read verification failed!
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: Error:
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.:
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: ATTRIBUTE              	INITIAL	NOW	STATUS
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: Reallocated_Sector_Ct  	0      	0  	-
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: Power_On_Hours         	1      	1  	-
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: Reported_Uncorrect     	0      	0  	-
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: Airflow_Temperature_Cel	38     	38 	-
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: Current_Pending_Sector 	0      	0  	-
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: Offline_Uncorrectable  	0      	0  	-
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: UDMA_CRC_Error_Count   	0      	0  	-
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: 
Oct 26 16:27:07 preclear_disk_70015084_17575: error encountered, exiting ...

 

 

[Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array]

16 minutes ago, Kilrah said:

Did you try removing the $ from the mount point?

Man, do I feel like a dumb a$$ now.  Thank you very much. 

[Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array]

I updated most of my hardware today (mobo, CPU, memory).  Everything is working fine, however; I can no longer mount my Remote SMB share that resides on a Windows Server 2016 machine.  I can successfully set up the share with username, password, domain, etc. It shows up on the MAIN tab and indicates that it is "online.  But when I click MOUNT, it tries and then just goes back to saying MOUNT again.  I did try replacing the share using the static IP address rather than the name of the server.  No luck. 

 

Many thanks in advance.

[Linking unRaid with Tresorit]

I too would like to know the answer to this question.  Any chance you figured it out?