miniwalks

Happy to help mate! Sent from my iPhone using Tapatalk

Dunno if it helps you or not, I'm running the M1015 (LSI same as H310) with seagate 8tb's and I parity check at 125MB/s? Not sure if that's good or not? Sent from my iPhone using Tapatalk

Those errors generally indicate controller failure; Can you please try the following and report back? 1) 8tb in other PC 2) 8tb in unraid - different port 3) other drive in same port as current 8tb Cheers Sent from my iPhone using Tapatalk

I'd still recommend a high endurance ssd for cache Mines a Micron/Dell Enterprise NVMe SSD Sent from my iPhone using Tapatalk

SSD cache only serves writes on configured shares, and reads only before the mover shifts it down to array. 10GBE in my Unraid is only really helpful to assist with multi stream, and for some reason seems to help inter-docker transactions Sent from my iPhone using Tapatalk

Quite right, however provided that you either have a large SSD and utilise TRIM etc you wont run into an issue for years, or have an enterprise SSD which is designed for endurance, as i listed with mine, it is entirely SLC over NVMe U.2 Nothing should be long-term kept on the cache that you cant live without. Dockers can be rebuilt, i run the mover once a week, anything in that week can be easily redone. Configurations and things that are important are backed up to the UnRaid array itself and a secondary NAS which is offsite.

I'm using an SSD with an endurance rated to 25PB @4K, or 50PB @128k So I think I'll be sweet Sent from my iPhone using Tapatalk

Close any browser sessions that were open prior to upgrade, this is part of the CSRF protection The CSRF is generated each time unraid boots to stop previous sessions from carrying out unwanted actions Sent from my iPhone using Tapatalk

Thanks guys I disabled docker, rebooted, and renabled with the existing image (have a backup of it anyways) Seems to be stable again, not sure what happened

Sorry, Tapatalk had a fit Diags attached miniraid-diagnostics-20170226-1511 (1).zip

Hmm For whatever reason, now my docker has screwed up.... Been running 6.3.2 since release, and now I can't update any dockers, start ones that are stopped etx. I've tried disabling and reenabling docker - now won't start Tried deleting the image and starting again - doesn't work. Just sits in a loop trying to start the docker process Ideas? Sent from my iPhone using Tapatalk

At a terminal command prompt, use the following command to obtain the actual spin state of the drive: hdparm -C /dev/sdX (replace sdX with the correct drive symbol from the Main screen) If it returns "active/idle", then it's spinning. If it returns "standby", then it's spun down. I'm sure someone has a little script that reports the spin states for all attached drives. Thanks for that RobJ, Unfortunately all the drives are reporting as active/idle when this is occuring. I have tried using ionotifywait -mr on /mnt/user/ and get nothing back except for sickrage touching its DB which is on the cache drive only. Ideas?

Are you absolutely positive the disks are still physically spinning? I suspect there is a disconnect between the display and reality. Can you hear the drives spinning? Im thinking the disks are actually spun up, given they are reporting their temps etc Other than physically inspecting the drives, is there any other way to confirm? Otherwise I'll inspect the drives physically tonight, but based on UPS draw I'd say they're spinning Sent from my iPhone using Tapatalk

Are you absolutely positive the disks are still physically spinning? I suspect there is a disconnect between the display and reality. Can you hear the drives spinning? Other than physically inspecting the drives, is there any other way to confirm? Otherwise I'll inspect the drives physically tonight, but based on UPS draw I'd say they're spinning Sent from my iPhone using Tapatalk

Perhaps I spoke too soon; Feb 19 03:25:35 MiniRAID kernel: mdcmd (62): spindown 1 Feb 19 03:25:36 MiniRAID kernel: mdcmd (63): spindown 2 Feb 19 03:25:37 MiniRAID kernel: mdcmd (64): spindown 3 Feb 19 03:25:38 MiniRAID kernel: mdcmd (65): spindown 4 Feb 19 03:25:39 MiniRAID kernel: mdcmd (66): spindown 5 Feb 19 03:25:47 MiniRAID kernel: mdcmd (67): spindown 6 Feb 19 03:25:49 MiniRAID kernel: mdcmd (68): spindown 7 Feb 19 05:26:35 MiniRAID kernel: mdcmd (69): spindown 4 Feb 19 05:56:08 MiniRAID kernel: mdcmd (70): spindown 6 Feb 19 06:59:01 MiniRAID kernel: mdcmd (71): spindown 2 Feb 19 07:16:41 MiniRAID kernel: mdcmd (72): spindown 3 Disks are being told to spin down but don't do it, only when the "spin down" button is used do they do it. Has happened in all 6.3.x releases but not 6.2.4 Help? Sent from my iPhone using Tapatalk

Hey guys, Updated from 6.3.1 to 6.3.2 successfully So far so mostly good; Goods; Disk spinup seems to be back to normal Other; Ram usage has jumped to 50% from averaging 34% on a 16GB System

I seem to be having some issues with my Kodi connecting to NFS and seeing file/folder structures correctly

Looks like it might be a GUI graphic bug on my end Still not sure on the drive not spinning down, will keep investigating Sent from my iPhone using Tapatalk

Kinda silly if you ask me, my docker is on cache so I don't want it spun down. Normally I wouldn't use the button, but since 6.3.0 and 6.3.1 my drives aren't spinning down at all. Only when forced, and that takes down my docker and VM Sent from my iPhone using Tapatalk

Still waiting to see if anyone else's spin down button is. Ow trying to spin down their cache drive? Sent from my iPhone using Tapatalk

Just noticed that my spin-down button on the main screen now tries to spin down the cache drive? whereas this used to only do up-to but not including cache drive assignment. Cheers,

Hey guys, Not sure if its cosmetic or not, but it seems like my drives arent spinning down once theyre spun up since updating to 6.3.0? Cheers

Fwiw I have 8 of these drives in an unraid (7D+1P) setup for 56TB Protected. They're a solid drive, which is designed towards WORM workloads, hence why I chose them as I do singular writes of data and rarely delete. Haven't had any issues with them and they hold up well with 500GB Cache SSD in front of them. Sent from my iPhone using Tapatalk

Hey guys, I had to remove and re-install the plugin for some unknown reason it wasnt detecting the update being available. anyways, now im seeing the below in the "/var/log/preclear.disk.log" Tue Dec 20 23:32:37 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:32:47 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:32:57 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:33:07 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:33:17 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:33:27 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:33:37 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:33:47 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:33:57 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:34:08 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:34:18 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:34:28 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:34:38 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:34:48 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:34:58 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:35:08 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:35:18 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:35:28 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:35:38 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:35:48 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:35:58 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:36:08 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:36:18 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:36:28 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Tue Dec 20 23:36:38 AEDT 2016: PHP Warning: mkdir(): Invalid path in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 30 Thoughts?

Just disable jumbo frames. Even using 10gbps and 40gbps NICs there is little difference in "real world" throughputs. 1gbps NIC, you'll see 115mbyte/sec (125max - overheads) 10gbps NIC, 1.125 gbyte/sec Jumbo frames are a bit of a misnomer unless you 300% know what you're doing, what the workload is, and what the hardware/software in the path is Sent from my iPhone using Tapatalk