3blackdots

Members
  • Posts

    8
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

3blackdots's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I was not having any luck with a Marvel based expander (SAS2LP-MV8) with IOMMU enabled in the BIOS but since I swapped to an IBM ServeRAID M1015 I have been having a much better time all round as I also run it with a HP SAS Expander for an extra 24 ports (The SAS2LP-MV8 didnt like the dual link connection to the HP card, but the M1015 worked fine). The only thing with the IBM card is that you will want to flash it to IT mode which is fairly straightforward but I did have to muck around with making a UEFI bootable USB to do the flash as it kept throwing an error when doing it via a DOS based USB, but there was a post on the forum or externally somewhere for doing either method. I used the following page as a guide for choosing my card at the time, but I dont know when it was last updated. The M1015 seemed to be a popular choice with other users though: http://lime-technology.com/wiki/index.php/Hardware_Compatibility#PCI_SATA_Controllers Since then I have been able to run VM's, the only thing you may want to check beforehand is if you want to pass through PCI devices to the VM as that caught me out. All my PCIe slots were in the same IOMMU group so you have to pass them all through to the VM which was obviously no good to me as I want my SATA controllers to stay in unRAID. You could use ACS override but it would not be a good idea to do it on the same group as your SATA controllers due to the possibility of the other device writing to the memory space of your controller, which would not be good for your data integrity. Hope that helps.
  2. Hi, I am currently running 6.2rc2 and have a problem with my NFS shares. I realise that the initial post for 6.2beta18 indicated there was a problem with NFS and I can't say I have seen an updated post that says the problem has been fixed, however it works, but has some issues. I have Kodi setup to access my media shares over NFS and for items already existing in the library it works fine, files are able to be played without issues. The problem lies with Kodi reporting folders as non-existent which means I can no longer scan new files into the library. This only occurs when accessing a user share, I can see and open the /mnt/user/Movies share but it is empty, but I tested exporting a disk share and then I am able to see all the sub-folders. Kodi Log: 17:10:20 T:15600 DEBUG: NFS: Context for 192.168.1.54/mnt/user/Movies not open - get a new context. 17:10:20 T:15600 DEBUG: NFS: Connected to server 192.168.1.54 and export /mnt/user/Movies 17:10:20 T:15600 DEBUG: NFS: chunks: r/w 1048576/32768 17:10:20 T:15600 DEBUG: VideoInfoScanner: Scanning dir 'nfs://192.168.1.54/mnt/user/Movies/' as not in the database 17:10:20 T:15600 DEBUG: VideoInfoScanner: No (new) information was found in dir nfs://192.168.1.54/mnt/user/Movies/ 17:10:20 T:15600 WARNING: VIDEO::CVideoInfoScanner::Process directory 'nfs://192.168.1.54/mnt/user/Movies/10,000 BC (2008)/' does not exist - skipping scan. 17:10:20 T:15600 WARNING: VIDEO::CVideoInfoScanner::Process directory 'nfs://192.168.1.54/mnt/user/Movies/12 Years a Slave (2013)/' does not exist - skipping scan. ... I found a post in the past about possibly using NFSv4 for user shares and staying with NFSv3 for disk shares but that was about 2 years ago and I don't see any further posts to say this was actually implemented. I bring it up because the Kodi devs have indicated no plans to move to v4 support and wondering if this may be the cause of the issue? I have gone and checked permissions on the folders and on the NFS shares but I can't see any problems: cat /etc/exports "/mnt/user/Movies" -async,no_subtree_check,fsid=101 *(sec=sys,ro,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/TV Shows" -async,no_subtree_check,fsid=100 *(sec=sys,ro,insecure,anongid=100,anonuid=99,all_squash) ls -l /mnt/user/Movies/ drwxrwxrwx 1 tony users 44 Jan 23 16:03 007\ -\ Spectre\ (2015)/ drwxrwxrwx 1 tony users 37 Jul 11 15:32 10\ Cloverfield\ Lane\ (2016)/ dr-xr-xr-x 1 nobody users 44 Mar 27 2015 10,000\ BC\ (2008)/ drwxrwxrwx 1 nobody users 34 Mar 27 2015 12\ Years\ a\ Slave\ (2013)/ ... I have tried changing various NFS parameters around, tried from windows, docker and raspberry pi versions of Kodi but all have the same issue and since they are able to access the server over NFS and can see folders on disk shares it makes me think it is something in unRAID stopping user shares exporting properly. I have used the Movies share as an example here but it also happens on the TV Shows share as well (or whatever other share I try). Has anyone else had the same problem or does anyone know what is going on here? Thanks tower-diagnostics-20160719-1655.zip
  3. This bug does not apply to you. I don't know of any reports concerning the 9480, just the ones listed in the first post. And if it did apply, you wouldn't be complaining about parity, you wouldn't see any of the attached drives at all. Hi RobJ, I have one of the Supermicro SAS2LP-MV8 cards with the 9480 chipset and i am getting this issue when i have IOMMU enabled. I have been running ok with IOMMU disabled while on the betas since getting the card but I just upgraded to 6.0.1 and re-tested and I am still getting the problem. I seem to recall there was meant to be a patch for this problem introduced into kernel 3.17 (based on this post: http://lime-technology.com/forum/index.php?topic=35190.0) any updates on this or workaround for this problem on the horizon? Thanks syslog.txt lspci.txt
  4. The plot thickens... I downloaded the latest Ubuntu image and booted that up from my usb and I end up getting the exact same error messages, so the problem appears to be related to the current hardware I have installed, possibly the A88X chipset? Anyway, thanks for your help so far but it looks like I will have to continue searching for an answer... If anyone has any further suggestions they would be most appreciated. Thanks.
  5. I noticed in your (bkastner) signature that you have an Intel based system. After a bit of checking I worked out that another of my PC's has an Intel based processor/motherboard capable of Vt-d/IOMMU. When I put the Supermicro card into that PC and booted up unRAID the hard drive was detected both times (normal and Xen/unRAID - its the 80GB drive in the logs) but I still had a problem with the on-board Marvel adapter in Xen/unRAID only, to which my 60GB SSD was attached. At this stage it seems like the problem is linked to the AMD visualization technology as the Intel one seems to work fine. The only other thing I can think to test would be a pre 6b7 version of unRAID as, if I remember correctly, a lot of problems with Marvel based chips had problems from that point on. Unfortunately I don't have a copy to test. I also tried a fresh unRAID USB but that didn't make any difference. syslog_intel.txt syslog_intel_xen.txt
  6. Motherboard BIOS has been updated again, still having the same issue. Re-flashed the expander to the latest 1812 firmware and still getting the same issue. Does anyone else have a working SAS2LP card in this latest beta? If not I'm wondering if its just a problem with my motherboard.
  7. It was on the latest BIOS, but checking again there was an updated version just released on the 5th Feb. Its description is for improving stability with a particular CPU. I'll try updating to this latest version and see how things go, though i wont hold my breath...
  8. Hi All, I have recently added a Supermicro AOC-SAS2LP-MV8 SATA expander card but I have been having problems with the connected hard drives which show up in the boot/BIOS screen for the expander card but have issues showing up in unRAID. Based on this post (http://lime-technology.com/forum/index.php?topic=35190.0) it appears the problem should have been resolved with kernel version 3.17 which is included as of 6b11h but I'm still having problems. I can workaround the problem by disabling IOMMU in the BIOS and then everything is fine but the main goal of this current build was to get Xen working, which I did prior to installing the expander. I get the following error for all disks connected to the expander when IOMMU is enabled (the first line only appears for normal unRAID but is missing in Xen/unRAID, the next 2 lines appear in both): Feb 7 10:44:36 Tower2 kernel: AMD-Vi: Event logged [iNVALID_DEVICE_REQUEST device=00:00.1 address=0x000000fdf8040020 flags=0x0a00] Feb 7 10:44:36 Tower2 kernel: ata9.00: qc timeout (cmd 0xec) Feb 7 10:44:36 Tower2 kernel: ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4) I have tried both the latest firmware for the expander (1812) and the previous version (1808) but the problem exists using both. I tried unRAID 5.0.6 and that worked without issue. Is anyone else having similar issues or knows why this is still happening? Any help would be appreciated. Syslogs have been attached. unRAID Version: 6b12 CPU: AMD A8-7600 Motherboard: Asus A88X-PRO Expander: AOC-SAS2LP-MV8 - currently on 1808 firmware Thanks syslogs.zip lspci.txt