Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

8.1 SATA Controller passthrough help

Featured Replies

Whenever I attempt to passthrough a SATA controller to 8.1 I can VNC and see the Xen Boot screen come up, followed by the SATA controller, then the screen no longer progresses.

 

I NEED a SATA controller passed through for my Bluray burner.

 

I have installed a Syba Sil3132 PCIe x1 card (first tried stock, then nonraid bios & driver b7703.bin bios & 3132_x64_1.0.15.6 & 3132_x86_1.0.22.4 drivers)

 

I also attempted to a Sil3114 PCI card (first tried stock, then nonraid bios & driver b5500.bin bios & 3114_x64_W7_1.2.9.0 & 3114_x86_w7_1.3.11.0 drivers)

 

As soon as I disable SATA passthrough my 8.1 VM works fine (I have a USB PCI card and a GPU passed through fine).

 

Any help is GREATLY appreciated!

  • Author

I just finished trying to passthrough a Asmedia / PEXESAT322I PCIe card.

 

Using VNC I see:

Asmedia 106X SATA Controller Ver 0.95 AHCI Mode
Copyright (C) Asmedia Technologies, Inc. ALL Right Reserved.
SMART Supported
Using PCIE Gen2
Cant Find any device

No bootable device
Powering off in 30 seconds

 

Even by trying to passthrough ONLY a single SATA controller to the Win 8.1 VM, the system does not boot past ANY Sata Controller - like it is looking for the operating system ON the SATA controller?

 

Any help would be VERY Much appreciated.

 

This is to Passthrough a Blu-Ray burner to Windows - a requirement for this setup to be usable.

 

Thank you.

  • Author

http://lime-technology.com/forum/index.php?topic=32344.msg297285#msg297285

 

@itimpi, your advise sounds similar to what I read in a german forum: http://www.nickles.de/forum/linux-contra-monopole/2014/xen-4-1-und-bluray-dvd-laufwerk-539048804.html

The issue that the guy had was that he had to always restart the VM in order to change a DVD/CD/Bluray. He was using the following commands:

phy:/dev/sr0,hdc:cdrom,w
xm block-attach VM phy:/dev/sr0 cdrom r

I searched through the whole /dev directory and wasn't able to identify the drive.  :(

 

@ironicbadger, you are correct, with the actual setup I haven't passedthrough anything (I passed through the AOC-SAS2LP-MV8 before when I was using ESXi 5.1). What do you mean with "PCI line" ?

 

OK my RDM(ESXi term) pass through of a CDROM does not appear to work.

 

 

I can get a physical drive to pass through but you have to restart the VM every time you want to change the disk in the CDROM so probably not a desirable feature.  Since I know little about Xen I don't know if it will work or not but I will post the settings I used to get this far.

 

 

I went ahead and used by-id to mount it as using sr0 didn't appear to work at first.  I believe however it didn't work because at the time I started the VM the DVD drive was empty so for as long as the VM was active it would only see it as empty.  Anyway the post below is after I decided to switch to by-id.  It will become more obvious when I post the settings I used for my HDDs passed through individually later on.

 

 

Anyway here is how I passed through the DVDR in my Xen WHS2011.cfg file:

'phy:/dev/disk/by-id/ata-HP_DVD_Writer_1260t_3743524275_328041500,hdc:cdrom,r'

 

 

The three HDDs I passed through to my WHS2011 VM were done like this:

'phy:/dev/disk/by-id/ata-WDC_WD30EZRS-00J99B0_WD-WCAWZ2011608,hdb,w',
'phy:/dev/disk/by-id/ata-WDC_WD30EZRS-55J99B0_WD-WCAWZ0764007,hdc,w',
'phy:/dev/disk/by-id/ata-WDC_WD30EZRS-55J99B0_WD-WCAWZ0771695,hdd,w'

 

 

So by using this method I could be assured that the disks were always mounted correctly every time the WHS2011 VM was started.  I didn't like it this way for the reasons in my prior posts in this thread.

 

 

Hope this info is useful.

 

Done - it was a drive issue within Windows. I installed the ADAPTEC driver and I can see (and use) the drive now.

 

I'm a lucky camper now  :D

 

{EDIT} One more thing. I temporarely removed pci = ['03:00.0'] from my windows.cfg file. I used the following command instead:

xl pci-attach windows 0000:03:00.0

. This is the result of "xl pci-assignable-list" by the way.

 

HOWEVER, using pci = ['0000:03:00.0'] within windows.cfg isn't working either, I have to manually send the 'xl pci-attach windows 0000:03:00.0' command after the VM was started

 

 

 

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.