HellDiverUK

Members
  • Posts

    1296
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by HellDiverUK

  1. UnRAID is using a paltry 110MB of my 8GB USB stick. Removing python and perl isn't really a deal breaker as far as size goes is it? The 8GB stick is new, and it was literally the smallest brand name stick I could get.
  2. So, I created a folder called "docker" on my cache, put the docker.img inside it, set up all my dockers. Forgot to tell UnRAID that the folder was cache only. Mover moved it to the array. I used mc to move it back to the cache. Now Docker Settings says I have to recreate the image due to the previous beta bug (I assume moving it broke the COW?). Can I recreate the image without blowing away all the settings on my Dockers?
  3. Idling with the drive spun down it uses 24W. That's a few watts more than the i3 at idle, but under load it uses 40W compared to nearly 80W of the i3.
  4. I had exactly the same with the two brand-new, just out of the box Crucial BX100 drives, so there was nothing on those drives before.
  5. I find turning the screen off is the easiest way of doing that.
  6. I've also got a pair of these drives running in UnRAID and I've had no problems at all so far. Speed is just fine.
  7. All my stuff is now copied over to the pair of Archive v2 drives. Took about 8 hours to copy ~3.8TB across gigabit. I did notice the drives slowing up a little at various points, I assume while doing the shingling on parts of the drives formerly written to. Once it got past that area (up to about 100GB) they ran just fine at ~100MB/s for big files. I'm surprised how noisy the drives are on read/write, they rattle away like my HGST Deskstar NAS units, which are 7200rpm. I've also witnessed them rattling away for several (up to 30) seconds after drive access has apparently finished by the host. I assume it's SMR housekeeping in action. Platter whine on the Seagates is totally absent, as quiet as a WD Red. Lots quieter than the Hitachis, and quieter than the Seagate Desktop.15 by a little margin. The D.15 units I have are shucked, so park their heads every few seconds, giving a wheeze-ka-boing-clunk! noise which gets pretty irritating pretty quick. I'm 48 hours in with these drives and I've no regrets, other than the fact they're almost 50% full already.
  8. No, it's UnRAID. We've discussed this before. Happened first with 14b. Still happens with 15. It's an easy fix, you just have to run "sensors-detect" from the local console or ssh, and then modprobe the resulting driver in the go file. See: http://lime-technology.com/forum/index.php?topic=39244.0
  9. I have the board up and running. The AM1M-A is surprisingly small, it's about 1" shorter than a normal uATX board, and much narrower. There's basically only four chips on the board, Asus' EPU, the Realtek NIC and Realtek audio chip, and the SuperI/O chip to run the serial and parallel ports. I'm still building parity, and currently it's using 41W. I should see sub-30W when the drives spin down. Currently running off a 150W 1U PSU.
  10. I have a thing about power consumption. We have a 5kW PV array on the roof, so every watt saved when it's dark is bringing the break-even date closer. I already have all I can running during the day while it's sunny. I'm currently looking at a 225W night-time power use, but I'm hoping to cut that down below 200W with the server doing it's nightly downloading. I'd aim for less than 190W total idle, which means the server needs to use about 20W. The current machine is rarely below 50W, usually more towards 70W. Everything else is turned off apart from the PVRs, fridge and electric clocks/timers. I already have the server doing it's housekeeping during the day. Unfortunately the PVRs are hard-coded to housekeep at 3am, which tends to be the time my downloads happen, so I can already see the spike in power consumption at that time.
  11. OK, just for a giggle I've ordered some odds and sods to see if I can build an UnRAID box that uses less power then my current rig, but can still run Plex Server acceptably. Spec as follows: Asus AM1M-A motherboard (£33) Athlon APU 5350 (4x2.05GHz) (£42) 2x2GB DDR3L-1600 (recycled), 2x SSD (recycled), 2x HDD (recycled), Startech PEXSAT34SFF PCI-E SATA card with SFF8087, (£49) SFF8087 to 4x SATA cable (torn down backplane out of an old HP Microserver). 300W PSU. I'm hoping this will use half the power of my current UnRAID box, and be fast enough to do the limited transcoding I do (720p content transcoded down to 480p). It should be as the APU is faster than the Celeron J1900 which I know works fine for my uses. Current rig running idle: 49W. The new parts are due tomorrow, so I'll update as I go along. Edit: For posterity and completeness, at the time of writing my "current rig" was as follows: i5-3570S, 2x8GB Kingston DDR3L-1600, AsRock C216WS.
  12. I'll be using the super-high quality and ultra-stable Broadcom NICs on my board (sarcasm overload there).
  13. Parity build ended in a little under 12 hours 30 minutes. Copying stuff over at the moment at 100MB/s more or less...
  14. OK, cheers, will try it when I'm at home - don't want to futz with it when connecting remotely from work.
  15. Just a quick question. I have two NICs in my server, can I use one for UnRAID file operations, and one for the KVM VMs?
  16. What does SMART say about the drive? In other words is it a btrfs issue, or is the drive throwing bad sectors?
  17. Absolutely it's more than good enough for v6. Only thing I'd be wanting to do is a bigger cache device, but even that is likely to be unnecessary. Definitely move to Dockers, they really are the way forward. Even MS is working with Docker for Windows 10, so Dockers are going to become very, very popular which is nothing but a good thing.
  18. Darksurf, I'd think about trying BTRFS on native SATA before dismissing it as disastrous. The chipset used in those IcyBox RAID enclosures is a bit...well, cheap and rubbish. What you've done is like taking a Ferrari out on the track fitted with LingLong Ditchfinder tyres, and saying that Ferraris are rubbish because they go off the track on the first corner.
  19. 34% done, 4 hours 12 minutes done, 8 hours 4 mins to go. 179.9MB/s at the moment.
  20. MicroATX is shortened to mATX. Micro (symbol µ) is a unit prefix in the metric system denoting a factor of 10?6 (one millionth). The prefix comes from the Greek (mikrós), meaning "small". So, microATX ends up bastardized to uATX.
  21. If you've got phpmyadmin or other SQL admin program (HeidiSQL?), just pull down a backup of the DB and restore if required.
  22. Are these the only two drives in your new array? Correct. For now, anyway. The two 4TB drives will go in later.
  23. pras1011, I got them from Lambdatek, they were about £230 each. Similar price to a 6TB Red. http://www.lambda-tek.com/Seagate-ST8000AS0002~sh/B1999368
  24. They're in. I've blown away my old array and started again with the two 8TB drives. Parity is building at 189MB/s, expected to finish in just under 12 hours.