[Bug 218731] FREEBSD 11 SCSI drive issue with all 11.xxxx versions running under HYPER-V as a VM

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218731

--- Comment #9 from ds <mx5arbc at hotmail.com> ---
Some additional info that might be useful:
-----------------------------------------------------------------------
I'm using a SEAGATE 1 TB standalone hard drive as a test drive attached using
SCSI definition via HYPER-V.  It is invisible when I run Clear Config and
Import Disks after bootup in NAS4FREE 11.1.  

This is what I get when I run RESCAN BUSSES after the O/S is running this is
what shows up on the console and log file as well (device da1 would normally be
what I should see as available for this hard drive):

kernel: (da1:storvsc2:0:0:0): Periph destroyed
Aug 24 13:56:45 nas4free        kernel: da1 at storvsc2 bus 0 scbus4 target 0
lun 0
Aug 24 13:56:45 nas4free        kernel: da1: < ST1000DM003-1SB1 CC43> Fixed
Direct Access SCSI device
Aug 24 13:56:45 nas4free        kernel: da1: Serial Number Z9A4S5TQ
Aug 24 13:56:45 nas4free        kernel: da1: 300.000MB/s transfers
Aug 24 13:56:45 nas4free        kernel: da1: Command Queueing enabled
Aug 24 13:56:45 nas4free        kernel: da1: 953869MB (1953525168 512 byte
sectors)
Aug 24 13:56:45 nas4free        kernel: da1 at storvsc2 bus 0 scbus4 target 0
lun 0
Aug 24 13:56:45 nas4free        kernel: da1: < ST1000DM003-1SB1 CC43> s/n
Z9A4S5TQ detached
Aug 24 13:56:45 nas4free        kernel: g_access(918): provider da1 has error
Aug 24 13:56:45 nas4free        last message repeated 8 times

This tells me that the disk is being seen at start but something is causing it
to detach.  The drive itself is healthy.  If I define the drive in HYPER-V as
an IDE drive (similar to the O/S virtual disk), then it is seen successfully.  

If I were to guess there is a flaw in the integration between Microsoft's
provided integration software embedded into FREEBSD 11 as it relates to SCSI
only.   Microsoft site indicates that FREEBSD 11.1 is fully supported in
HYPER-V as it was with 10.X which previously worked well.

   See link:
https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/supported-freebsd-virtual-machines-on-hyper-v

-- 
You are receiving this mail because:
You are the assignee for the bug.