Jump to content

plupien79

Members
  • Posts

    109
  • Joined

  • Last visited

Posts posted by plupien79

  1. Depending on what you need CPU wise.

     

    The 1037u Celeron is a great option. A board with that CPU is under $100 easy.

     

    My Network Setup...

    8 Disk Unraid - 1037u

    Kodi Box - 1037u

    Router 847

    HP Laptop - Domain Controller and PBX

    Plus switch and modem PoE for Voip Phone and WAP draws ~150w

     

    It all depends on if that can do the CPU lifting you need.

  2. Is it possible to keep your VMs up and running regardless of the state of the protected array? Assuming the VM is stored on the cache drive or a non-array drive.

     

    Here's my Use-Case Argument.

    A user is running a PBX as a VM.

    They want to put the array into maintenance mode to scan disks.

     

    However, they still want to be able to have their phone system up and running.

     

    Is this possible now, is it planned, if not is it worth suggesting?

  3. I am not copying directly to the cache drive. The speed differences are between 2 shares, one is cache only and the other is cached. That's why  I thought they should be similar performance. It seems I'm out of the comfort zone of many unraid users, I thought that stating I was getting 220-240MB/s would automatically answer the questions yes I'm using at least 10G Ethernet and its an SSD drive.

     

    So this is writing directly to the protected array. 80-90MBs is quite normal performance. This is due to the slower disks and the parity calculations. Hence the reason many people opt for a cache drive.

  4. This sounds a lot like the issues that I and some others are having.

     

    An attempt is made to write to the array, then for some currently unexplained reason, the write operation doesn't work, but also doesn't fail or create any errors. Then the SHFS process involved just sits using as much CPU as it can raising the load on the server until it becomes unresponsive. You then hard reset (a software reboot fails) do a parity check and find no errors.

     

    Are there any messages on the physical console?

  5. Ok...

    I've switched all my data drives from ReiserFS to XFS.

     

    This MAY have solved some things. Not 100% sure yet as only time will tell.

     

    I did see an odd Reiser error on my terminal when I had a crash:

                        "REISERFS error (device MD2): vs-4010 is_reusable block number is out of range"

     

    but running the scan in Maintenance mode found nothing, so I moved all my data disk by disk and changed to XFS. Ran a parity check and now everyone is humming along.

  6. I never used any of the beta's.

     

    I suspect it's something funky with the NM70 Chipset and the Linux kernel. I've had issues in the past with OpenELEC, but this is a different issue.

     

    But since nothing seems to show up with the logs and it seems that I'm the only person using this hardware it seems like a big hill to climb.

  7. root@InfoSphere:/usr/local/emhttp# lsof -p 21149

    COMMAND  PID USER  FD  TYPE DEVICE SIZE/OFF NODE NAME

    shfs    21149 root  cwd    DIR    0,2      380    2 /

    shfs    21149 root  rtd    DIR    0,2      380    2 /

    shfs    21149 root  txt    REG    0,2    83216 4568 /usr/local/sbin/shfs

    shfs    21149 root  mem    REG    0,2  171470 6323 /lib64/ld-2.17.so

    shfs    21149 root  mem    REG    0,2  134893 6252 /lib64/libpthread-2.17.so

    shfs    21149 root  mem    REG    0,2    48928 6341 /lib64/libcrypt-2.17.so

    shfs    21149 root  mem    REG    0,2  1944360 6269 /lib64/libcrypto.so.1.0.0

    shfs    21149 root  mem    REG    0,2  242840 6305 /lib64/libfuse.so.2.9.3

    shfs    21149 root  mem    REG    0,2  2102965 6246 /lib64/libc-2.17.so

    shfs    21149 root  mem    REG    0,2    18988 6296 /lib64/libdl-2.17.so

    shfs    21149 root    0u  CHR    1,3      0t0 1029 /dev/null

    shfs    21149 root    1u  CHR    1,3      0t0 1029 /dev/null

    shfs    21149 root    2u  CHR    1,3      0t0 1029 /dev/null

    shfs    21149 root    3u  CHR 10,229      0t0 5361 /dev/fuse

    shfs    21149 root    6r  REG    0,2      984 4588 /usr/local/emhttp/update.htm

     

×
×
  • Create New...