Jump to content

something fishy

  • Posts

  • Joined

  • Last visited


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

something fishy's Achievements


Noob (1/14)



  1. It doesn't have files on the array according to the "compute" button in the shares tab and verified with Midnight Commander. I used to have some orphan appdata files and I forced them off under 6.10.2. As I've said, all was normal with the cache directories plugin operating in 6.10.2 and all seems normal in 6.10.3 without the plugin. Thanks
  2. This is for me? Yes I'm sure. Appdata is cache only and my sageTV recording directory is on a pool drive not on the array. These shares were excluded from cache directories and were working as expected in 6.10.3: asleep when not used. With the plug in removed, expected behaviour has returned to all disks. The only disks spun up are those that have current file activity. For eg, at time of writing I have a scheduled windows disk image running so one array drive and parity are spun up, plus cache (an SSD). The remaining 6 array drives are asleep. SageTV has just started recording so its dedicated pool drive spun up around 3 minutes ago. Thanks
  3. I appreciate that. Thank you. I've removed for the moment. It was working as designed on 6.10.2 (no impact on disk sleep that I could see or any other negative side effects) and with the same settings carried over appeared not to work as designed on 6.10.3.
  4. Removing Dynamix cache directories and rebooting appears to have sorted it. Smart requests in the log no longer spin up the disk and unused disks spin down on schedule. Thanks, this is mostly static, infrequently accessed data so spindown is important on heat and power grounds. Cheers Eric
  5. Is there reason that array disks won't spin down after this upgrade. After upgrade (smooth, no problems) to 6.10.3 all but one of my array disks are staying spinning with no file access. If i spin the array down manually (using the little down arrow button under the disk listing) they almost immediately spin up in response to a smart request. This is copy and past from the live log: Jun 17 15:03:43 shortie emhttpd: spinning down /dev/sdj Jun 17 15:03:43 shortie emhttpd: spinning down /dev/sdk Jun 17 15:03:44 shortie emhttpd: spinning down /dev/sdh Jun 17 15:03:45 shortie emhttpd: spinning down /dev/sdi Jun 17 15:03:46 shortie emhttpd: spinning down /dev/sdf Jun 17 15:03:46 shortie emhttpd: spinning down /dev/sdg Jun 17 15:03:47 shortie emhttpd: spinning down /dev/sdd Jun 17 15:03:49 shortie emhttpd: read SMART /dev/sdj Jun 17 15:03:49 shortie emhttpd: read SMART /dev/sdg Jun 17 15:03:49 shortie emhttpd: read SMART /dev/sdf Jun 17 15:03:58 shortie emhttpd: read SMART /dev/sdk Jun 17 15:04:08 shortie emhttpd: read SMART /dev/sdh Jun 17 15:04:08 shortie emhttpd: read SMART /dev/sdd Jun 17 15:04:08 shortie emhttpd: read SMART /dev/sdi With 6.10.2 the array was spun down as expected. I have Dynamix cache directories installed and one disk is reporting as over temperature (server in marginally cooled location and its hot, ironically, because the array is spun up). Thanks Eric
  6. I bought an old QNAP 1079 Pro on ebay https://www.qnap.com/en-uk/product/ts-1079 pro for the express purpose of running unraid. It was the cheapest way that I could get a compact 10 bay hotswap enclosure. Its serving well and appears to have great cooling. I doubt that I could have built better for twice the second hand price I paid. This is an i3 machine and mine came with 16Gb of RAM. It has 2x onboard NICs and mine came with an extra dual NIC card (removed see below). A few observations - I had to load the QNAP OS and switch off "environmental energy management" (or something like that) to enable boot on power restore (for a UPS). The setting is not exposed in the BIOS. Power cycle it a few times to make sure its working - sometimes the setting did not stick for me. This was maybe a flat cmos battery - To change the cmos battery requires the mainboard being removed. This needs six screws removing (4x ordinary and both the locking screws on the vga port) the SATA backplane removing (do this without disks present!) and pretty much all mainboard cables pulling. It's not hard but it is very fiddly and the chassis edges are sharp. - I couldn't get the front LED working either, I unplugged it. - CPU cooling looked marginal to me (slowing the case fans down caused a kernel panic before HDD temps became a problem). I wedged a noctua fan on top of the CPU heatsink (there are spare fan headers). Switch the fan control for the case fans to fixed speed in the BIOS and Dynamix fan control plugin seems to work. - I stuck a cheap sata card into the spare pcie slot (designed for a second NIC card) for a SSD cache drive. A 2.5 inch HDD/SSD can sit loose above the drive bay (where the PSU lives). You will need a special card backplate (one came with the NAS in my case) as standard low profile backplates don't work. This done all ten drive bays are free for the array. - I'm only using one of its two onboard NICs but as far as I can tell unraid is perfectly happy in this hardware and I can see no reason why it wouldn't work - Started off by pulling the QNAP DOM module. But there is a second on board USB header (presumably for a redundant DOM?) and I fashioned a short flying lead so that my unraid flash drive is stored internally (attached to the base of the case behind the drive bay). Just select the correct boot order in the BIOS. - It seems to reboot once during a start up sequence for reasons I don't understand. But I think using the QNAP OS it does this several times. The unraid webui is available about 90 seconds after boot which is 3-4 minutes quicker than the QNAP web UI. - Its as quiet as the N54L HP microserver that preceded it. The HDDs seem happier spinning down than they did in the microserver. The unraid system info reports the NAS as: Model: N/A M/B: ICP/iEi QA61 Version V1.0 - s/n: To be filled by O.E.M. BIOS: American Megatrends Inc. Version 4.6.4. Dated: 01/19/2012 CPU: Intel® Core™ i3-2120 CPU @ 3.30GHz HVM: Not Available IOMMU: Not Available Cache: 128 KiB, 512 KiB, 3 MB Memory: 16 GiB DDR3 Multi-bit ECC (max. installable capacity 32 GiB) Network: eth0: 1000 Mbps, full duplex, mtu 1500 eth1: interface down Kernel: Linux 5.10.28-Unraid x86_64 OpenSSL: 1.1.1j Uptime: 0 days, 04:09:09
  • Create New...