ivanavich

When either starting or stopping the array, the unraid host becomes unresponsive to pings for up to 30 seconds. Diagnostics attached. nas-diagnostics-20231009-1133.zip

I transitioned all array disks to ZFS and am seeing parity check crawling along at 28MB/sec. Previously with XFS it was over 100 MB/sec with 10TB parity. Stopped docker services - no change to parity speed. Started docker services - docker tab showed as not running, no start stop would make a difference. Reboot Partity sync restarted and back to over 100 MB/sec. Docker containers all running fine. strange. diagnostics-20231001-0055.zip

Some interesting info here regarding compression from @SpaceInvaderOne https://unraid.net/blog/zfs-guide

Just for shz and giggles I rebuilt parity and part the way through parity rebuild.. Unraid StatusNotice [ODIN] - array health report [FAIL]Array has 18 disks (including parity & pools)alert Parity - ST10000NM017B-2TL103_WP00QECY (sdr) - active 54 C [DISK INVALID] Disk 1 - ST10000NM017B-2TL103_WP00TPD4 (sdc) - active 54 C [OK] Disk 2 - ST10000NM017B-2TL103_WP00QEVX (sde) - active 56 C (disk is hot) [NOK] Disk 3 - HGST_HDN726060ALE614_K1HK1RVB (sdh) - active 47 C [OK] Disk 4 - HGST_HDN726060ALE614_K1HJ91ZB (sdk) - active 50 C [OK] Disk 5 - HGST_HDN726060ALE614_K1HJ9AUB (sdm) - active 42 C [OK] Disk 6 - HGST_HDN726040ALE614_K4JWVZ0B (sdf) - active 55 C (disk is hot) [NOK] Disk 7 - WDC_WD40EFRX-68N32N0_WD-WCC7K0EHKAF1 (sdp) - active 41 C [OK] Disk 8 - WDC_WD40EFRX-68N32N0_WD-WCC7K2UVS4TD (sdb) - active 49 C [OK] Disk 9 - WDC_WD40EFRX-68WT0N0_WD-WCC4E2XDVZE4 (sdd) - active 46 C [OK] Disk 10 - WDC_WD40EFRX-68WT0N0_WD-WCC4E4TX8D6R (sdj) - active 46 C [OK] Disk 11 - WDC_WD30EZRX-00DC0B0_WD-WCC1T1410174 (sdg) - active 46 C [OK] Disk 12 - WDC_WD30EZRX-00DC0B0_WD-WCC1T1348759 (sdt) - active 44 C [OK] Disk 13 - WDC_WD30EZRX-00SPEB0_WD-WCC4E0501415 (sdl) - active 42 C [OK] Disk 14 - WDC_WD30EZRX-00DC0B0_WD-WMC1T0290168 (sdq) - active 41 C [OK] Disk 15 - WDC_WD30EZRX-00DC0B0_WD-WMC1T2397360 (sdn) - active 40 C [OK] Nvme-cache-one - Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M917665F (nvme0n1) - active 45 C [OK] Nvme-cache-two - Samsung_SSD_960_EVO_500GB_S3EUNX0J304522K (nvme1n1) - active 37 C [OK] Parity-Sync in progress. Total size: 10 TB Elapsed time: 4 hours, 18 minutes Current position: 1.67 TB (16.7 %) Estimated speed: 109.8 MB/sec Estimated finish: 21 hours, 4 minutes Sync errors corrected: 0 Seems like a check is out of order. Not bothered by it, perhaps something untoward.

Unraid 6.12.4 Rebuilding parity with a new 10TB drive which had been successfully precleared to avoid infant mortality. Largest drive in the array is 6TB at time of rebuild. Received email notification (Odin Home unRAID Status: Notice [ODIN] - Parity-Sync finished (0 errors)): Link: https://Odin.local/Main Event: Unraid Parity-Sync Subject: Notice [UNRAID] - Parity-Sync finished (0 errors) Description: Canceled Importance: warning In Unraid server warning log is one entry- all drives showing as [OK] except the parity drive which shows as: Parity - ST10000NM017B-2TL103_WP00QECY (sdt) - active 44 C [DISK INVALID] At the bottom of the log: Parity-Sync in progress. Total size: 10 TB Elapsed time: 22 hours, 49 minutes Current position: 9.87 TB (98.7 %) Estimated speed: 140.8 MB/sec Estimated finish: 16 minutes Sync errors corrected: 0 Array Operation shows 'Parity is valid.' Last check completed on Tuesday, 05-09-2023, 12:36 am (today). Duration: 23 hours, 6 minutes, 4 seconds. Average speed: 120.3 MB/s. Finding 0 errors Any ideas what happened? Thank you! unraid-diagnostics-20230905-1405.zip

Hi SRB Stopping the array should not force a parity-check. I have seen your issue on one of my unRAID instances running 6.4.1. Stopping the array causes "Unclean shutdown detected." You should be safe in cancelling the parity-check and formatting the drive you set to XFS-Encrypted.

unRAID is a NAS you store (via dedicated parity drive/s) protected files over the network. Is is not a SAN product that you can access directly and treat as secondary storage for your Windows client. I think that is what you mean? If you want to install a Windows client for gaming (installed on an SSD) and unRAID for network storage (installed on a USB flash drive), then you can switch between them using your BIOS boot options at startup.

<Edited after further troubleshooting> unRAID 6.2.4 on ESX 6.5 using Plop Boot Loader. Symptoms: - unRAID would boot however no response from HTTP port 80, can get to Flash share through SMB however - Removed Pro.key from config directory and rebooted, unRAID works fine - Added Pro.key into config directory and reboot, again no response from HTTP port 80 - Removed all config files and loaded stock unRAID 6.2.4 with Pro.key and loads fine So what's the config file that's malfunctioning here?

I had similar problems with OS/Hypervisors detecting USB drive when the bare metal server restarted. The only solution was to remove the USB, replug and boot again. Always had this issue with Kingston USB flash drives. Since switching to Sandisk (Ultra & Ultra Fit) I haven't had any issues. Try recreating another UNRAID USB using the same method and boot up. Try restarting a few times to see if it is that particular issue. If in the end it works, then restore your config directory and use the GUI to request a new registration key for that particular USB flash drive. https://lime-technology.com/replace-key/

No sure if this helps however console shows: Unraid login: /bin/bash: line 3: /usr/local/emhttp/pluginsunbalance/scripts/stop: No such file or directory

Hi jbrod The page is blank in all browsers [ie/chrome] Preclear Disks/Community Applications work fine

I have installed the unBALANCE plugin from: https://raw.githubusercontent.com/jbrodriguez/unraid/master/plugins/unbalance.plg Once installed it shows in Plugins list as up-to-date (version 1.4.0) When I click on the logo it takes me to http://<unraidIP>/Settings/unbalance which is blank except the unRAID menu up the top. I tried http://<unraidIP>:6237 and that port doesn't seem to be open either. Tried both of the above after a reboot to no avail. I am running two unRAID 6.1.9 boxes and the same is happening on both. Files: * boot\config\plugins\unbalance\unbalance.cfg >SERVICE="disable" >PORT="6237" >RUNAS="nobody" * boot\config\plugins\unbalance\unbalance-1.4.0.tgz Any ideas jbrodriguez?