lousek
-
Posts
6 -
Joined
-
Last visited
Posts posted by lousek
-
-
you shoud try carefull if this works reliable, the mvsas driver seems to be used but thats for marvell chips, maybe there ist a marvell chip under the hood?
edit: according to https://cateee.net/lkddb/web-lkddb/SCSI_MVSAS.html some of this rocket raid controllers use the same chip from marvell so i added HighPoint RocketRAID 2710/2720/2721/2722/2740/2744/2760 to the mvsas section under storage drivers
thanks for reporting back
Will keep an eye on it.
Maybe the original RocketRAID 2720SGL driver could still be added to a future release?
Thanks for your help! -
try a
lspci -k | grep 'Kernel driver'
to see what drivers are used, maybe in non raid mode the ahci driver does the job?
admin@nas01:/$ lspci -k | grep 'Kernel driver' Kernel driver in use: pcieport Kernel driver in use: xhci_hcd Kernel driver in use: ahci Kernel driver in use: pcieport Kernel driver in use: pcieport Kernel driver in use: pcieport Kernel driver in use: mvsas Kernel driver in use: r8168
-
are you shure? my list contains only RocketRAID 3xxx/4xxx, the 271x/272x need a different driver (rr272x_1x.ko)
I can see & access my two disks connected to the RocketRAID 2720SGL, so I think the driver is included (or another driver is used instead).
-
Sorry if wrongly double posted ("Driver extension jun 1.02b/DSM6.1.x for 3615xs / 3617xs / 916+" thread).
Please add the driver for RocketRaid 2720SGL HBA, Linux drivers can be found here: http://www.highpoint-tech.com/USA_new/series_rr272x_configuration.htm
Many thanks for your good work!
[VMM] BSOD on install
in Synology Packages
Posted
It seems this issue is related to the CPU mode with Win2016 and Win10 on KVM. (Synology uses KVM underneath).
You can check the current CPU config when you login e.g. via SSH, then identify a (running) VM with virsh list and virsh dumpxml <ID>.
My vCPU were on "passthrough". I temporarily solved this issue by joining the VMM Pro Beta Program (under License) and then activating the CPU Compatibility Mode (VMM Pro only) for this VM - this sets the CPU Fallback to core2duo, which works fine for me (Win2016 and Win10).
KR,
lousek