stealth82

I'm aware this is a very old thread but to date I'm experiencing the same problem. Normal read speeds - above 100MB/s - but disappointing write speeds - 25/40MB per second. I can't move the controller to any other slot because the 4x is the only one I have and I'm not sure the cables are the problem at this point, otherwise why would the read speed be OK? Anyone?

OK, sorry for that. I misunderstood you.

I don't find this intuitive user experience. Either you make the checkboxes behave the same or one has to "figure out" that one of them works the opposite respecting the others. And that's what I'm saying. You have to click 5 checkboxes to highlight the errors only. If you trap the double click or think of something else with a quick double click I would like to immediately filter for the errors. I'm just suggesting since you asked for feedback.

I would anyway change the behaviour of the checkboxes. "hide text|default unchecked" to "text|default checked" checkbox. I would also love to see a sort of quick behaviour where you double click the checkbox and all the other ones get automatically unchecked instead of unchecking them manually to narrow the filter to one category only. In addition an All checkbox to selected them all back

Dec 22 19:09:23 Tower sshd[22152]: Received disconnect from : 11: disconnected by user Dec 22 19:19:52 Tower sshd[12117]: Received disconnect from : 11: disconnected by user Dec 22 19:57:17 Tower sshd[20064]: Accepted publickey for root from port 52621 ssh2: RSA Dec 22 22:01:03 Tower sshd[20064]: Received disconnect from : 11: disconnected by user The above messages get red color coded but they are not errors BTW, I love the new log! Thumbs up! EDIT: sorry, my bad the color is orange and looks very close to red. They're not errors. Can the login color be changed to something more neutral?

I did. It's just a little bit obsessive-compulsive disorder: I want to run only the necessary and therefore I want understand what is going on. I saw your plugin before. I will give it a try but, still, my point remains

It's good now! Thanks!

I added and then removed some repositories to the docker repository list. I thought the dockers belonging to the removed repositories would go away automatically but instead it seems they keep on sticking around. I then manually removed the repositories folders under boot/config/plugins/dockerMan/templates and they finally disappeared. Problem is, when the server is rebooted they get recreated and show up again. I tried to look for places where they might still be referenced but I found none. Ideas?

I installed the very first version of your plugin and the icons was under tools. I just updated the plugin but, apart from the new settings > syslog configuration, I can't find access to the colored log anymore... System Information is simply not there.

I checked but there are no firmware upgrades for it. Yours might be a lucky hardware combination then, but I totally see the problem and I don't wanna deal with it any longer. Since I bought it a few weeks ago I'm still eligible to send it back and be refunded, I will buy a different disk and see what happens.

I think any Samsung 840/850 is not safe choice for unRAID, let alone for any Linux distribution...

Here, I think I nailed it https://bugzilla.kernel.org/show_bug.cgi?id=72341

I'm still waiting for the cables, but I plugged the disk back to the mb controller, reformatted the disk to xfs and.... Dec 21 21:36:52 Tower emhttp: shcmd (203): set -o pipefail ; mkfs.xfs -m crc=1,finobt=1 -f /dev/sdb1 |& logger Dec 21 21:36:52 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x480100 action 0x6 frozen Dec 21 21:36:52 Tower kernel: ata1.00: irq_stat 0x08000000, interface fatal error Dec 21 21:36:52 Tower kernel: ata1: SError: { UnrecovData 10B8B Handshk } Dec 21 21:36:52 Tower kernel: ata1.00: failed command: DATA SET MANAGEMENT Dec 21 21:36:52 Tower kernel: ata1.00: cmd 06/01:01:00:00:00/00:00:00:00:00/a0 tag 16 dma 512 out Dec 21 21:36:52 Tower kernel: res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error) Dec 21 21:36:52 Tower kernel: ata1.00: status: { DRDY } Dec 21 21:36:52 Tower kernel: ata1: hard resetting link Dec 21 21:36:53 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 21 21:36:53 Tower kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Dec 21 21:36:53 Tower kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Dec 21 21:36:53 Tower kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Dec 21 21:36:53 Tower kernel: ata1.00: supports DRM functions and may not be fully accessible Dec 21 21:36:53 Tower kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 Dec 21 21:36:53 Tower kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Dec 21 21:36:53 Tower kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Dec 21 21:36:53 Tower kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Dec 21 21:36:53 Tower kernel: ata1.00: supports DRM functions and may not be fully accessible Dec 21 21:36:53 Tower kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 Dec 21 21:36:53 Tower kernel: ata1.00: configured for UDMA/133 Dec 21 21:36:53 Tower kernel: ata1.00: device reported invalid CHS sector 0 Dec 21 21:36:53 Tower kernel: ata1: EH complete Dec 21 21:36:53 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen Dec 21 21:36:53 Tower kernel: ata1.00: irq_stat 0x08000000, interface fatal error Dec 21 21:36:53 Tower kernel: ata1: SError: { UnrecovData Handshk } Dec 21 21:36:53 Tower kernel: ata1.00: failed command: DATA SET MANAGEMENT Dec 21 21:36:53 Tower kernel: ata1.00: cmd 06/01:01:00:00:00/00:00:00:00:00/a0 tag 5 dma 512 out Dec 21 21:36:53 Tower kernel: res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error) Dec 21 21:36:53 Tower kernel: ata1.00: status: { DRDY } Dec 21 21:36:53 Tower kernel: ata1: hard resetting link Dec 21 21:36:53 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 21 21:36:53 Tower kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Dec 21 21:36:53 Tower kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Dec 21 21:36:53 Tower kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Dec 21 21:36:53 Tower kernel: ata1.00: supports DRM functions and may not be fully accessible Dec 21 21:36:53 Tower kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 Dec 21 21:36:53 Tower kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Dec 21 21:36:53 Tower kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Dec 21 21:36:53 Tower kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Dec 21 21:36:53 Tower kernel: ata1.00: supports DRM functions and may not be fully accessible Dec 21 21:36:53 Tower kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 Dec 21 21:36:53 Tower kernel: ata1.00: configured for UDMA/133 Dec 21 21:36:53 Tower kernel: ata1.00: device reported invalid CHS sector 0 Dec 21 21:36:53 Tower kernel: ata1: EH complete Dec 21 21:36:53 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x800 SErr 0x400100 action 0x6 frozen Dec 21 21:36:53 Tower kernel: ata1.00: irq_stat 0x08000000, interface fatal error Dec 21 21:36:53 Tower kernel: ata1: SError: { UnrecovData Handshk } Dec 21 21:36:53 Tower kernel: ata1.00: failed command: WRITE FPDMA QUEUED Dec 21 21:36:53 Tower kernel: ata1.00: cmd 61/00:58:40:00:00/01:00:00:00:00/40 tag 11 ncq 131072 out Dec 21 21:36:53 Tower kernel: res 40/00:58:40:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Dec 21 21:36:53 Tower kernel: ata1.00: status: { DRDY } Dec 21 21:36:53 Tower kernel: ata1: hard resetting link Dec 21 21:36:53 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 21 21:36:53 Tower kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Dec 21 21:36:53 Tower kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Dec 21 21:36:53 Tower kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Dec 21 21:36:53 Tower kernel: ata1.00: supports DRM functions and may not be fully accessible Dec 21 21:36:53 Tower kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 Dec 21 21:36:53 Tower kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Dec 21 21:36:53 Tower kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Dec 21 21:36:53 Tower kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Dec 21 21:36:53 Tower kernel: ata1.00: supports DRM functions and may not be fully accessible Dec 21 21:36:53 Tower kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 Dec 21 21:36:53 Tower kernel: ata1.00: configured for UDMA/133 Dec 21 21:36:53 Tower kernel: ata1: EH complete Dec 21 21:36:53 Tower kernel: ata1: limiting SATA link speed to 3.0 Gbps Dec 21 21:36:53 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x4000 SErr 0x400100 action 0x6 frozen Dec 21 21:36:53 Tower kernel: ata1.00: irq_stat 0x08000000, interface fatal error Dec 21 21:36:53 Tower kernel: ata1: SError: { UnrecovData Handshk } Dec 21 21:36:53 Tower kernel: ata1.00: failed command: WRITE FPDMA QUEUED Dec 21 21:36:53 Tower kernel: ata1.00: cmd 61/00:70:40:00:00/01:00:00:00:00/40 tag 14 ncq 131072 out Dec 21 21:36:53 Tower kernel: res 40/00:70:40:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Dec 21 21:36:53 Tower kernel: ata1.00: status: { DRDY } Dec 21 21:36:53 Tower kernel: ata1: hard resetting link Dec 21 21:36:54 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Dec 21 21:36:54 Tower kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Dec 21 21:36:54 Tower kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Dec 21 21:36:54 Tower kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Dec 21 21:36:54 Tower kernel: ata1.00: supports DRM functions and may not be fully accessible Dec 21 21:36:54 Tower kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 Dec 21 21:36:54 Tower kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Dec 21 21:36:54 Tower kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Dec 21 21:36:54 Tower kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Dec 21 21:36:54 Tower kernel: ata1.00: supports DRM functions and may not be fully accessible Dec 21 21:36:54 Tower kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 Dec 21 21:36:54 Tower kernel: ata1.00: configured for UDMA/133 Dec 21 21:36:54 Tower kernel: ata1: EH complete Dec 21 21:36:54 Tower logger: meta-data=/dev/sdb1 isize=512 agcount=4, agsize=15262410 blks ... set the NCQ disabled to yes again - because I also noticed that makes unRAID throw errors like crazy and rsync'ed the data back, at the magical speed of 13MB/s (woot... just joking...) The VM is running at the moment, trying to "stress" it the same way I was doing earlier today. But theres's something hitching me. The SSD, although on a 6Gb channel port is operating at 3Gb...

MB: Intel DZ77SL-50K CPU: Intel® Core™ i5-3570T Memory: 8192 MB GeForce GTX 750 pass-thru AOC-SASLP-MV8 Asus Xonar ST 2 pass-thru Cache: Samsung EVO 850 btrfs Windows 10, SeaBIOS, 440fx 2.3, qcow2 Details 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.7 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 8 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation Z77 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04) 01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750] (rev a2) 01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1) 02:00.0 RAID bus controller: Marvell Technology Group Ltd. MV64460/64461/64462 System Controller, Revision B (rev 01) 03:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 30) 04:00.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio] [0:0:0:0] disk SanDisk Cruzer Fit 1.22 /dev/sda [1:0:0:0] disk ATA WDC WD20EZRX-00D 0A80 /dev/sdd [1:0:1:0] disk ATA WDC WD20EARS-00M AB51 /dev/sde [1:0:2:0] disk ATA WDC WD20EARS-00M AB51 /dev/sdf [1:0:3:0] disk ATA SAMSUNG HD204UI 0001 /dev/sdg [1:0:4:0] disk ATA SAMSUNG HD204UI 0001 /dev/sdh [1:0:5:0] disk ATA Samsung SSD 850 1B6Q /dev/sdi [2:0:0:0] disk ATA ST2000DM001-1CH1 CC29 /dev/sdb [3:0:0:0] disk ATA TOSHIBA MD04ACA4 FP2A /dev/sdc vm settings <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>HTPC</name> <uuid>03647809-f67f-a683-a756-9b1522e620f2</uuid> <description>Virtual Home Theater PC</description> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='1'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/cache/vm/htpc/vdisk1.qcow2'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/software/iso/SW_DVD5_WIN_ENT_10_64BIT_English_MLF_X20-26061.ISO'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/software/iso/virtio-win-0.1.110.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:cc:18:9c'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/HTPC.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> </source> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> </qemu:commandline> </domain> My early posts: SSD cache disk throwing lots of errors: disk or cabling issue? I also have write performance issues, 25-30MB transfer speed between cache to/from array or array disk to/from array disk. If I'm lucky it is the supermicro controller possessing the whole server...

I don't even want to mention the huge amount of time I'm wasting down the toilet trying this new fancy virtualization but I'm very close to give up entirely. What I experienced so far is not what I had in mind. Is it possible that a VM can completely freeze and make unRAID go totally unresponsive for the second time in a few days?? Now a new parity check is waiting for me as soon as I hard reset the server. And I won't have any syslog to inspect in order to understand what went wrong again. This time it happened 20/30 mins after I started playing a movie and just like that the VM and and, what is worse, the server are dead.

What happened in my case is that I wanted to mount a disk to make it visible to the system and put it as second cache drive. I didn't read any wiki before doing this test and so I noticed that the cache pool concept was applied. I stopped the array, unassigned the second cache disk and started it again. Everything seemed fine at first. Then I decided to mount that drive that I wanted to make visible manually. I formatted it to btrfs. After the format the cache folder disappeared and the disk showed up as unmountable and couldn't retrieve any data with any btrfs restore command. I think the 2 disks were still connected somehow. That was my bad but and I think nobody would do what I did. Nevertheless if there's a way to correctly handle a cache disk removal it should be stated more clearly.

I just want to chip in by saying that I have the same SSD disk as cache drive and experiencing 25-30MB/s when moving files to the array. Apart from the parity disk - attached directory to the mb controller, 6Gb - all of the disks in the array are attached to a SASLP-MV8 controller (.21 firmware version).

OK, I bought new cables and I will test everything again. If it is still unstable I will try xfs as my last attempt, after which I will keep the SSD on the 3Gb controller and wait for better times, sigh

Agreed.

It happened the same to me lately with a Seagate Drive (2 years) and a WD drive (4 years old). My server underwent some major changes but I never had so many strange problems all at once. I reaseated drive cables and everything and the drives went back to normal but I don't feel too confident about my hardware configuration at the moment.

Are you using a cache disk? If yes, what model?

I swapped the cable, I did every possible test. As I wrote what I know is that a drive platter has no problem using the same channel and cable. Could it really be that a cable makes the difference when it comes to SSD, despite the use of a cables tested and used for years?

I don't know why but it turns out the SSD is unstable when attached to the 6Gb primary mobo sata controller. If I move the SSD on one of the 8 ports of my Supermicro 3Gb controller it works OK. If I move a regular HD on the same channel the SSD was throwing a gazillion errors before, the HD works just fine. So, I can't use my SSD at its full speed with unRAID. Why? It makes me lose confidence in the overall stability of the system. I'm too old for this crap.

I have a Samsung 850 EVO and the same message is reported in my syslog.

My server underwent lots of changes lately, mostly due to the virtualization opportunity. I got myself a SSD cache disk and for the first days everything went well. It was directly attached to the mb controller. Then I decided to make it hot-swappable, by using a SSD converter and slapped eveything into my trayless HDD 5x3 cage where the array disks have been for some time now. When I assembled everything back and started the server again the cache disk was detected, the array could start and everything seemed well. I tinkered with my virtual machine, installed software and everything till the day before yesterday. Yesterday I wanted to use my vm and although the windows desktop was visible I could not interact with anything. The vm seemed half frozen. I decided to take a look at the syslog and found it flooded with error messages regarding my cache disk. I decided to turn the vm off and try to understand what went wrong (see diag1.zip). After many minutes the vm would not shut down gracefully so I killed it. I stopped the array and turned the server off. I thought the problem was the SSD converter the cache disk was in. I removed the disk and reattached it directly to the motherboard. I started the server again. The SSD disk was there, but the fs was now corrupt... I imagined that. I removed it as cache drive since it said unmountable and presented me with the option of formatting it... I was able to get it back with btrfschk , I then mounted it manually and copied everything to my array (it worked and the data seemed OK to me). I unmounted the disk and the ran btrfs check --repair. It worked again. Therefore I set the disk as cache drive again. unRAID read it correctly. At this point I really wanted to make sure it was the SSD converter, so I stopped the server and put the disk in the converter and again in the cage. I booted up the server, unRAID was OK with it. I decided to test the cache disk by converting a raw image file to qcow2 from the array to it. It wrote 3.5GB and then froze: errors again... I thought it definitively was the SSD converter. I stopped everything again and attached the disk back directly to the mb and tried the image conversion copy again. This time it didn't even start... errors again (see diag2.zip). So, now I don't know what to think. Is it the file system? Has the disk gone bad? The SATA cable? The mb port? Can you tell from the logs? I attached 2 sets of logs. diag1.zip diag2.zip