Syneon

Are you signed into your account in the top right corner?

In my post up above that one I did test the backplane connected to another motherboard and it was detecting the drives in the bios. So definitely something with that SM model not cooperating with SAS backplane to SATA ports. But yes, I am picking up another x99 extreme4 mobo from microcenter tonight and swapping it out just to confirm. Then going to replace the norco case with a new one from newegg since 3 out of 5 of the backplanes were having issues.

Got a not very helpful email from SuperMicro: "Our LAB have not tested 3rd party Norco 4220 chassis or Reverse breakout cable C-SFF8087-4S. Since Direct SATA to SATA connection to drives functions properly, issue lies with 3rd party items, not BIOS. For compatible chassis, please refer to MB webpage." I guess this model isn't compatible with SAS backplanes for whatever reason. Will be flipping it on ebay and picking up another X99 or similar mobo I guess.

Sorry for the delay guys! I was on a trip and away from my poor server for way too long. I was able to do more testing and I think ended up with some answers, but more questions. I hooked up the SAS backplane on the norco case to another mobo (X99 Extreme4) and I was able to see some of the hard drives display over there. Full testing revealed top SAS backplane doesnt show any drives, 2nd and 3rd SAS plane show 3 out of 4, and bottom 2 show all 4 drives. So with this new info from the thorough testing on all backplanes I plugged them back into the supermicro board, but nothing is showing in the BIOS there even from ones that worked on the X99 mobo. I noticed my bios revision 1.0c is older than the current one on the supermicro page of 2.0a. I have logged a ticket with supermicro for any input on if the newest revision has anything to assist with connecting drives via the SAS > SATA reverse breakout cable, but it seems like a very strange thing for them to not have in the bios already as this stuff has been around for awhile. Anyone have new thoughts based on that scenario? I emailed norco, but I am also within neweggs holiday return window. When this happens does norco send replacement backplanes? or should I arrange an exchange for the whole case directly with newegg?

Hard to hear if the drives are spinning or not with the louder norco fans. The blue lights on the front do come on in front of each drive though. I will try swapping out some cabling when I get to the server later to see if its an issue with the cable not providing enough power.

Hello everyone! I've done some googling and limetech forum reading the past couple hours and I cannot figure out what is going on. I am assuming some hardware incompatibility or cabling.. just missing it. I had an existing array running in my previous tower and decided to make the migration to Norco. Norco 4220 SUPERMICRO MBD-X10SRL-F Server Motherboard LGA 2011 R3 Intel Xeon E5-1650 v3 Mini-SAS to 4x SATA Reverse Breakout Cable Assorted 4, 6, 8tb WD Reds 500gb Evo SSD Cache Got all of my components moved over to the norco case and UnRaid will boot up and get back to my old dashboard. I see my 11 drives all showing up as missing. None of my drives are showing up in the drive drop downs, unassigned, etc. Also they do not display in the bios. The one thing that does display is my cache drive, but that is just using a regular sata cable direct to mobo and is not on the sas backplane the norco has. I have tried multiple reverse breakout cables, each backplane, multiple drives, and multiple sata ports but nothing is getting detected. The fact I cannot see them in the bios means it isn't an unraid issue, but with the massive norco following here I am hoping someone knows what is going on! I also have a PCI-E (4 port sata) card that doesnt detect anything either. I am thinking either the cable is wrong.. The one I got: http://a.co/dWC8i75 or some other factor I am not seeing. Any incompatibilities in my list that could be causing an issue? Thanks!

Hey I dont have the Rift (htc vive here) When I was passing through the USB functions from the headset some things would work and some wouldnt. Seems like there were like 13 usb devices showing up in that single usb port making it quite difficult to get to work. The only way I was able to get my vr to work properly was to get a PCI-E card with USB ports. I had to pass through the whole card to the VM then having the headset gear plugged into that card to get it to work properly. Definitely was a difficult process to get set up, but it is possible! (for vive at least, I assume the rift works similarly)

Disabled Hyper Threading and all performance and sound issues are gone in the gaming VM. So weird

Very strange.. I've been reading threads all over the place on my symptoms and this one was by far the most informative. Seems like there is a scarcity of information. I recently built my unraid server to take advantage of the NAS + VM functionality for gaming. Got a 6 core E5 1650 xeon, 980 ti, and 32gb ddr4 ram and I boot up the VM and total crap performance. Stuttering, audio feedback, mouse jumping, choppy gaming, etc.. I've tried a few things in here, but not the disabling of HT. I guess I will try that tonight. It's really a shame we have to give up one of the big perks of the intel processor, but if disabling that part makes it functional I guess it is worth it. Will definitely have to keep a close eye on developments to find if a better fix is discovered.

I have been at this all morning and I cannot figure out what is going on. I current have 1 drive added to the array (4tb) and a 500gb cache drive. I have a drive that is from a Windows 10 machine that I want to copy the contents to the drive already in the array. I am having great difficultly getting that drive to mount. I have been all up and down any forum thread I could find and it seems ntfs-3g is needed for drives >2tb, but it is still not cooperating with my drive. Here is the output from some various commands I have seen mentioned in other threads. Anything jumping out to anyone? mount -t ntfs-3g /dev/sdc1 /mnt/dataimport -o umask=111,dmask=000 -v NTFS signature is missing. Failed to mount '/dev/sdc1': Invalid argument The device '/dev/sdc1' doesn't seem to have a valid NTFS. Maybe the wrong device is used? Or the whole disk instead of a partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around? gdisk -l /dev/sdc GPT fdisk (gdisk) version 0.8.7 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sdc: 7814037168 sectors, 3.6 TiB Logical sector size: 512 bytes Disk identifier (GUID): 6B562ADC-663B-4069-9182-C40D75D9DFB9 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 7814037134 Partitions will be aligned on 64-sector boundaries Total free space is 30 sectors (15.0 KiB) fdisk -l|grep NTFS WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted. sdc is the drive I want to mount outside the array. sdd is the one currently mounted. cat /proc/partitions major minor #blocks name 7 0 52428800 loop0 8 0 30031250 sda 8 1 30031234 sda1 8 16 488386584 sdb 8 17 488386552 sdb1 8 32 3907018584 sdc 8 33 3907018535 sdc1 8 48 3907018584 sdd 8 49 3907018535 sdd1 9 1 3907018532 md1 I also attempted to install the unassigned devices plugin, but the mount button is dithered. Hopefully this is enough information. I am missing a key piece here and I cannot figure out what it is. Let me know if anything else is needed.