After upgrade to 7.2.5 from 7.2.4, the first boot seemed to be taking forever. I mean after 30 minutes, not everything was running. SMB shares are not reachable. Any interactions with the Array just seems to hang. Even just running the 'reboot' command from the terminal just did nothing and sat there. I think it was stuck in 'mounting disks' for 15 minutes. Shares still have not returned. I am attaching the diagnostic zip which took 10 minutes to complete for some reason. UI also hangs every once and a while.

Greg

ur-diagnostics-20260502-2339.zip

Have you tried booting in Safe Mode as you have a deprecated [plugin that may be causing problems.

You also have a number of issues from Fix Common Problems that should be taken care of:

May 2 23:44:14 ur root: Fix Common Problems: Warning: Share appdata.2 is an implied array-only share, but files / folders exist on the cache

May 2 23:44:14 ur root: Fix Common Problems: Warning: Share etc is an implied array-only share, but files / folders exist on the cache

May 2 23:44:14 ur root: Fix Common Problems: Warning: Share mnt is an implied array-only share, but files / folders exist on the cache

May 2 23:44:14 ur root: Fix Common Problems: Warning: Share SyncThing set to cache-only, but files / folders exist on the array

May 2 23:44:14 ur root: Fix Common Problems: Warning: Share backups set to not use the cache, but files / folders exist on the cache drive

May 2 23:44:15 ur root: Fix Common Problems: Warning: Deprecated plugin folder.view2.plg

Well, this is getting really concerning.

It's been about 12 hours since I started a parity-check and it is only at 1.1% for 4x8TB array.

On a ZFS mirror of two 4TB drives, the scrub is only 18% done after 12 hours.

I decided to start a SMART test of /dev/sdd (parity drive) right now and the UI is unresponsive while the test was running.

WTF is happening?

Oh, and I see this in the log occasionally.

May  3 00:45:58 ur kernel: sd 8:0:0:0: [sdd] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s
May  3 00:45:58 ur kernel: sd 8:0:0:0: [sdd] tag#12 CDB: opcode=0x85 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00

Edited May 3May 3 by ggee

?? Why is there so many cores in wait?

Tasks: 536 total, 1 running, 525 sleep, 6 d-sleep, 0 stopped, 4 zombie
top - 13:30:15 up 14:02,  0 users,  load average: 10.30, 7.10, 6.31
Tasks: 537 total, 2 running, 519 sleep, 11 d-sleep, 0 stopped, 5 zombie
%Cpu0  :  0.3 us,  0.0 sy,  0.0 ni, 99.7 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
%Cpu1  :  1.0 us,  0.0 sy,  0.0 ni, 99.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
%Cpu2  :  0.0 us,  0.0 sy,  0.0 ni,  0.0 id,100.0 wa,  0.0 hi,  0.0 si,  0.0 st 
%Cpu3  :  0.0 us,  0.3 sy,  0.0 ni,  0.0 id, 99.7 wa,  0.0 hi,  0.0 si,  0.0 st 
%Cpu4  :  0.0 us,  0.0 sy,  0.0 ni,  0.0 id,100.0 wa,  0.0 hi,  0.0 si,  0.0 st 
%Cpu5  :  2.0 us,  0.0 sy,  0.0 ni, 98.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
%Cpu6  :  0.7 us,  0.0 sy,  0.0 ni,  0.0 id, 99.3 wa,  0.0 hi,  0.0 si,  0.0 st 
%Cpu7  :  0.3 us,  0.3 sy,  0.0 ni,  0.0 id, 99.3 wa,  0.0 hi,  0.0 si,  0.0 st 
%Cpu8  :  1.0 us,  0.0 sy,  0.0 ni, 99.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
%Cpu9  :  0.3 us,  0.0 sy,  0.0 ni,  0.0 id, 99.7 wa,  0.0 hi,  0.0 si,  0.0 st 
%Cpu10 :  0.7 us,  0.0 sy,  0.0 ni, 99.3 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
%Cpu11 :  0.0 us,  0.0 sy,  0.0 ni,  0.0 id,100.0 wa,  0.0 hi,  0.0 si,  0.0 st 
MiB Mem :  64087.3 total,  23608.2 free,  15193.5 used,  26280.9 buff/cache     
MiB Swap:      0.0 total,      0.0 free,      0.0 used.  48893.8 avail Mem 

OK. Did more looking around. I found that what I look at the drive "Attributes", the tabs open up instantly for all drives but 2 which take a long time. So decided to swap the drive cables for those two drives and all is back stable again.

I still find it odd that bad cables on the array can cause issues with the responsiveness of the Dashboard and also even performance of a other pools.

11 hours ago, itimpi said:

May 2 23:44:14 ur root: Fix Common Problems: Warning: Share appdata.2 is an implied array-only share, but files / folders exist on the cache

May 2 23:44:14 ur root: Fix Common Problems: Warning: Share etc is an implied array-only share, but files / folders exist on the cache

May 2 23:44:14 ur root: Fix Common Problems: Warning: Share mnt is an implied array-only share, but files / folders exist on the cache

May 2 23:44:14 ur root: Fix Common Problems: Warning: Share SyncThing set to cache-only, but files / folders exist on the array

May 2 23:44:14 ur root: Fix Common Problems: Warning: Share backups set to not use the cache, but files / folders exist on the cache drive

Do you know how to fix those?

Seems kind of strange to actually have user shares named mnt and etc. What are those for?