mathgoy

Hi everyone, Gridrunner videos convinced me to switch from Ubuntu Server to Unraid. I followed all his tutorial to setup my server and it was incredibly easy and well documented. This was logic for me to follow his tutorial to setup a High Sierra VM on my server. Unfortunately, I am currently facing an issue that I couldn't solve with any of the fix proposed in the thread. I must be missing something! When I boot on the freshly created VM, the progress bar won't go further than 5 or 7% and then the machine will reboot. I used several tweaks I could read on the forum and it's the best scenario I can have so far (ther worst scenario being the machine rebooting on apple's logo without showing the progress bar). After several tweaks here and there here is the XML I have at the minute. I also tried to create a new install disk with no success. Thanks for the help! <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>OSX</name> <uuid>1d2e866e-e08b-0f09-d351-e30bf9de8391</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='6'/> <vcpupin vcpu='1' cpuset='14'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-2.9'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/1d2e866e-e08b-0f09-d351-e30bf9de8391_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='custom' match='exact' check='partial'> <model fallback='allow'>core2duo</model> <vendor>Intel</vendor> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/isos/highsierra2.img'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Linux/vdisk2.img'/> <target dev='hdd' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:e7:8b:6f'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='fr'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=xxxxxxxxOSK_KEY_xxxxxxxxxxxxxxxxxxxxxx'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,vendor=GenuineIntel,kvm=on,+invtsc,vmware-cpuid-freq=on,'/> </qemu:commandline> </domain>

Thanks for your reply mate. I will stick to the plan as I don't have docker containers with CPU pin. Will let you know about how it will go!

Hi all, My unraid is running on a Supermicro X9SRE and a Xeon E5-2650 @ 2.00GHz with 8 cores I purchased a E5-2670 v2 which has 10 cores @ 2.5GHz for 120 USD (this looked like a good deal) The bios is up to date and and the motherboard is compatible with that CPU. I was wondering if there is any precaution to take in unraid when I swap the CPU since the new one has more cores. Especially on VMs because of the thread pairing. I was planning to update the CPU allocation on each VM but maybe there is something else to take care about. Thanks for your help.

I did reinstall it once and it didn't work. I did reinstall it another time after rebooting my server and it did worK Thanks !

Hi, Thanks for the prompt reply. First here is the log I could get from the docker: Mar 25 14:12:36 f4b5626ab1b7 syslog-ng[12]: EOF on control channel, closing connection; *** Running /etc/my_init.d/20_apt_update.sh... Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease Get:2 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Get:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] Get:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB] Get:5 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [962 kB] Get:6 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [780 kB] Fetched 2048 kB in 2s (749 kB/s) Reading package lists... E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. *** /etc/my_init.d/20_apt_update.sh failed with status 100 And the Run command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='LogitechMediaServer' --net='bridge' -e TZ="Europe/Paris" -e HOST_OS="unRAID" -e 'PUID'='99' -e 'PGID'='100' -p '9000:9000/tcp' -p '3483:3483/tcp' -p '3483:3483/udp' -p '9090:9090/tcp' -v '/mnt/user/media/Musique/':'/music':'rw' -v '/mnt/user/appdata/LogitechMediaServer':'/config':'rw' --log-opt max-size=50m --log-opt max-file=1 'dlandon/logitechmediaserver' 9df8876117ca2622f9f41b87ad77db02ad80d0d4231af7d37ff27edeff38c0b5 The command finished successfully! Then I didn't modify any port (using the 9000 one) and I am trying to get in to the GUI via a left click on the docker icon in Unraid

Hi there first of all, thanks for the great work done on that Docker. However, I couldn't use it yet since I can't access the GUI. The installation of the docker was flawless but when I try to connect to the GUI, the address is unknown. I'll be happy to provide all the information required to solve that issue. Cheers

Well, since nobody could help me so far, I went back to 6.3.5 which runs smoothly. Any ideas why 6.4.0 bugs like that on my system? Cheers

Hi Gents, Since I updated my server to 6.4.0, I keep having those errors in the log when I boot in normal mode I did uninstall a whole bunch of plugins (preclear, unassigned devices, user's scripts...) but won't fix anything. Jan 15 23:33:01 MAXIMUS kernel: CPU: 3 PID: 21564 Comm: kworker/u32:6 Not tainted 4.14.13-unRAID #1 Jan 15 23:33:01 MAXIMUS kernel: Hardware name: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F/X9SRE/X9SRE-3F/X9SRi/X9SRi-3F, BIOS 3.2 01/16/2015 Jan 15 23:33:01 MAXIMUS kernel: Workqueue: scsi_tmf_7 scmd_eh_abort_handler Jan 15 23:33:01 MAXIMUS kernel: task: ffff880807380000 task.stack: ffffc90007840000 Jan 15 23:33:01 MAXIMUS kernel: RIP: 0010:isci_task_abort_task+0x18/0x334 [isci] Jan 15 23:33:01 MAXIMUS kernel: RSP: 0018:ffffc90007843ce8 EFLAGS: 00010296 Jan 15 23:33:01 MAXIMUS kernel: RAX: ffffffffa01d6cbb RBX: ffff880818fef1a8 RCX: 0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: RDX: ffff88085ec18020 RSI: 0000000000000400 RDI: 0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: RBP: 0000000000000000 R08: 00000000000000d2 R09: 0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: R10: ffffc90007843e58 R11: ffff8808073800c0 R12: ffff8808562d6800 Jan 15 23:33:01 MAXIMUS kernel: R13: 0000000000000000 R14: 0000000000000008 R15: 0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: FS: 0000000000000000(0000) GS:ffff88085f2c0000(0000) knlGS:0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 15 23:33:01 MAXIMUS kernel: CR2: 0000000000000000 CR3: 0000000001c0a003 CR4: 00000000000626e0 Jan 15 23:33:01 MAXIMUS kernel: Call Trace: Jan 15 23:33:01 MAXIMUS kernel: ? __freed_request+0x34/0x86 Jan 15 23:33:01 MAXIMUS kernel: ? freed_request+0x31/0x4b Jan 15 23:33:01 MAXIMUS kernel: ? __blk_put_request+0xed/0x131 Jan 15 23:33:01 MAXIMUS kernel: ? blk_put_request+0x38/0x4b Jan 15 23:33:01 MAXIMUS kernel: ? scsi_execute+0x168/0x177 Jan 15 23:33:01 MAXIMUS kernel: ? scsi_test_unit_ready+0x45/0x99 Jan 15 23:33:01 MAXIMUS kernel: ? cpuacct_charge+0x2c/0x6b Jan 15 23:33:01 MAXIMUS kernel: sas_eh_abort_handler+0x2a/0x3c [libsas] Jan 15 23:33:01 MAXIMUS kernel: scmd_eh_abort_handler+0x35/0x8f Jan 15 23:33:01 MAXIMUS kernel: process_one_work+0x146/0x239 Jan 15 23:33:01 MAXIMUS kernel: ? rescuer_thread+0x258/0x258 Jan 15 23:33:01 MAXIMUS kernel: worker_thread+0x1c3/0x292 Jan 15 23:33:01 MAXIMUS kernel: kthread+0x10f/0x117 Jan 15 23:33:01 MAXIMUS kernel: ? kthread_create_on_node+0x3a/0x3a I also include the diagnostics that I downloaded by booting in safe mode. Safe mode is 100% functionnal but in normal mode, even if the array starts and runs smoothly, after 10mins, I can't access to any of my shares (except on cache disk) from the server itself (by using Dolphin browser) or from PC on the network. All the dockers and VMs are running smoothly. Of course, Plex works but can't play anything since it can't get access to the data. Any idea? Cheers! maximus-diagnostics-20180118-1727.zip

Hi bonienl and thanks for your feedback. Preclear and SE sleep are not installed. I started the machine in safemode and it looks like it works. Only Plex docker and a VM are currently running. Since it works in Safe mode do you still need diagnostics? Cheers

Hi Gents, Since the update, my array won't work at all. When I reboot the server, it will work for about 10min and then, I can't browse my shares on the hard drives neither from a machine on the same network nor from the server itself. However, cache drive still runs smoothly. I can browse it and all my dockers and VM are still working. I tried to uninstall most of the plugins but it won't fix the issue. Here is an extract from the log where we can see on the first line the main errors (kworker/u32:6 Not tainted and Call Trace) Jan 15 23:33:01 MAXIMUS kernel: CPU: 3 PID: 21564 Comm: kworker/u32:6 Not tainted 4.14.13-unRAID #1 Jan 15 23:33:01 MAXIMUS kernel: Hardware name: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F/X9SRE/X9SRE-3F/X9SRi/X9SRi-3F, BIOS 3.2 01/16/2015 Jan 15 23:33:01 MAXIMUS kernel: Workqueue: scsi_tmf_7 scmd_eh_abort_handler Jan 15 23:33:01 MAXIMUS kernel: task: ffff880807380000 task.stack: ffffc90007840000 Jan 15 23:33:01 MAXIMUS kernel: RIP: 0010:isci_task_abort_task+0x18/0x334 [isci] Jan 15 23:33:01 MAXIMUS kernel: RSP: 0018:ffffc90007843ce8 EFLAGS: 00010296 Jan 15 23:33:01 MAXIMUS kernel: RAX: ffffffffa01d6cbb RBX: ffff880818fef1a8 RCX: 0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: RDX: ffff88085ec18020 RSI: 0000000000000400 RDI: 0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: RBP: 0000000000000000 R08: 00000000000000d2 R09: 0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: R10: ffffc90007843e58 R11: ffff8808073800c0 R12: ffff8808562d6800 Jan 15 23:33:01 MAXIMUS kernel: R13: 0000000000000000 R14: 0000000000000008 R15: 0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: FS: 0000000000000000(0000) GS:ffff88085f2c0000(0000) knlGS:0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 15 23:33:01 MAXIMUS kernel: CR2: 0000000000000000 CR3: 0000000001c0a003 CR4: 00000000000626e0 Jan 15 23:33:01 MAXIMUS kernel: Call Trace: Jan 15 23:33:01 MAXIMUS kernel: ? __freed_request+0x34/0x86 Jan 15 23:33:01 MAXIMUS kernel: ? freed_request+0x31/0x4b Jan 15 23:33:01 MAXIMUS kernel: ? __blk_put_request+0xed/0x131 Jan 15 23:33:01 MAXIMUS kernel: ? blk_put_request+0x38/0x4b Jan 15 23:33:01 MAXIMUS kernel: ? scsi_execute+0x168/0x177 Jan 15 23:33:01 MAXIMUS kernel: ? scsi_test_unit_ready+0x45/0x99 Jan 15 23:33:01 MAXIMUS kernel: ? cpuacct_charge+0x2c/0x6b Jan 15 23:33:01 MAXIMUS kernel: sas_eh_abort_handler+0x2a/0x3c [libsas] Jan 15 23:33:01 MAXIMUS kernel: scmd_eh_abort_handler+0x35/0x8f Jan 15 23:33:01 MAXIMUS kernel: process_one_work+0x146/0x239 Jan 15 23:33:01 MAXIMUS kernel: ? rescuer_thread+0x258/0x258 Jan 15 23:33:01 MAXIMUS kernel: worker_thread+0x1c3/0x292 Jan 15 23:33:01 MAXIMUS kernel: kthread+0x10f/0x117 Jan 15 23:33:01 MAXIMUS kernel: ? kthread_create_on_node+0x3a/0x3a Thanks you all for your help!

Well didn't reboot yet in safe mode but here is the log: Jan 15 23:33:01 MAXIMUS kernel: CPU: 3 PID: 21564 Comm: kworker/u32:6 Not tainted 4.14.13-unRAID #1 Jan 15 23:33:01 MAXIMUS kernel: Hardware name: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F/X9SRE/X9SRE-3F/X9SRi/X9SRi-3F, BIOS 3.2 01/16/2015 Jan 15 23:33:01 MAXIMUS kernel: Workqueue: scsi_tmf_7 scmd_eh_abort_handler Jan 15 23:33:01 MAXIMUS kernel: task: ffff880807380000 task.stack: ffffc90007840000 Jan 15 23:33:01 MAXIMUS kernel: RIP: 0010:isci_task_abort_task+0x18/0x334 [isci] Jan 15 23:33:01 MAXIMUS kernel: RSP: 0018:ffffc90007843ce8 EFLAGS: 00010296 Jan 15 23:33:01 MAXIMUS kernel: RAX: ffffffffa01d6cbb RBX: ffff880818fef1a8 RCX: 0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: RDX: ffff88085ec18020 RSI: 0000000000000400 RDI: 0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: RBP: 0000000000000000 R08: 00000000000000d2 R09: 0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: R10: ffffc90007843e58 R11: ffff8808073800c0 R12: ffff8808562d6800 Jan 15 23:33:01 MAXIMUS kernel: R13: 0000000000000000 R14: 0000000000000008 R15: 0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: FS: 0000000000000000(0000) GS:ffff88085f2c0000(0000) knlGS:0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 15 23:33:01 MAXIMUS kernel: CR2: 0000000000000000 CR3: 0000000001c0a003 CR4: 00000000000626e0 Jan 15 23:33:01 MAXIMUS kernel: Call Trace: Jan 15 23:33:01 MAXIMUS kernel: ? __freed_request+0x34/0x86 Jan 15 23:33:01 MAXIMUS kernel: ? freed_request+0x31/0x4b Jan 15 23:33:01 MAXIMUS kernel: ? __blk_put_request+0xed/0x131 Jan 15 23:33:01 MAXIMUS kernel: ? blk_put_request+0x38/0x4b Jan 15 23:33:01 MAXIMUS kernel: ? scsi_execute+0x168/0x177 Jan 15 23:33:01 MAXIMUS kernel: ? scsi_test_unit_ready+0x45/0x99 Jan 15 23:33:01 MAXIMUS kernel: ? cpuacct_charge+0x2c/0x6b Jan 15 23:33:01 MAXIMUS kernel: sas_eh_abort_handler+0x2a/0x3c [libsas] Jan 15 23:33:01 MAXIMUS kernel: scmd_eh_abort_handler+0x35/0x8f Jan 15 23:33:01 MAXIMUS kernel: process_one_work+0x146/0x239 Jan 15 23:33:01 MAXIMUS kernel: ? rescuer_thread+0x258/0x258 Jan 15 23:33:01 MAXIMUS kernel: worker_thread+0x1c3/0x292 Jan 15 23:33:01 MAXIMUS kernel: kthread+0x10f/0x117 Jan 15 23:33:01 MAXIMUS kernel: ? kthread_create_on_node+0x3a/0x3a

Well, I spoke too fast. This happened again. Right after a system reboot, all the server's services (shares, dockers, VM) will work but after some few minutes, the array will stop working (Can't access to shares through the netwrok and also can'et access to folders even locally). Cache drive still works, VMs and dockers too. This is really a huge issue, someone can help plz thanks

Hi Mate, I had the very same issue here. Had to reboot the machine to get things back. Hope it won't happen again

That's interesting; thanks for your feedback. I have absolutely no idea why it didn't work on your server. 16GB of ram seem enough for that. I could read from here and their that transcoding from the SSD could wear it quite quickly. That's why I use ram transcoding. To be honnest, it doesn't seem to improve the user experience but at least, it will significantly reduce the I/O on my ssd. One subsidary question, I can read that you use kodi and I was used to use it as well but honnestly, I couldn't find a reliable way to make it work with plex. plexkodiconnect is struggling so hard when it comes to sync the large libraries and the plex app for Kodi is just not that great. Can I ask you what is your solution because I would love using Kodi again (because of its decoding capabilities!) thanks

Well if you want to enable the ram transcoding, you need to use /tmp as a host path in your floder mapping. Then, with an ssh connection, you can check that plex uses the /tmp folder with ls /tmp/transcode (you should see a session folder and in that session folder one folder per active stream). Anyway, I ran some test using my SSD for transcoding and the performance are still the same. Also, even if all the cores are used, none of them will go higher than 50% when encoding a file

When you made that test did you make sure to specify the tarsncode folder (the one you mapped to /tmp) in the plex server settings (within the webgui)?

I am using ram to transcode (mapped the /transcode folder to /tmp) so I don't think it is the issue here

HI again, So I ran a test again once the parity check was over and the results are the same. Running conversion at 5x speed maximum, all my cores are used but only at 30 to 50% Any idea? THanks

Actually, you might be right. I am running several tasks in parallel and one of them is a parity check. I will make a new converting test once it's done and will let you know. Anyway, thanks a lot for the quick reply wgstarks

Hi all, I just migrated from an ubuntu server to unraid and am pretty happy so far. I installed the linuxserver.io-docker container, setup my complete library pretty smoothly and started streaming some media over my network. The streaming works great, and my sever (Xeon e-2650 + 32GB ECC ram + 250GB cache drive + 16TB array) can handle 7 to 8 streams in parallel. However, I noticed that converting some medias (not transcoding on the fly) was pretty slow. It will convert at 4.8x and will never use more than 40% of my CPU. So my question is, how can I get the best out of my CPU so I can transcode faster than that? Thanks for your reply, cheers.

OK sounds clear. Thanks a lot

Hi Johnnie.black Thanks for your quick reply. That was it indeed. It's now fixed. However, how is that possible that I had a "media" folder on cache when it's been set to "not use cache"' since the very beginning?

Hi all, I switched from ubuntu server to unraid last week and I am having a little issue with my shares. I am running unraid on a server with 5TB drives (4 data drives+1parity drive) and an SSD as cache drive. My main shared folder is my media folder which doesn't use my cache drive. However, when we have a look on that screenshot we can see that: Unraid tells me that some of my data are not protected in that share Unraid tells me that the the remaining space available in that share is 1.79TB when there is only 1.55TB available. Those 1.79TB includ the Cache but it shouldn't. As a comparison, the share named "Data" has the exact same setup as "media" and works well. Any Idea? Cheers