killseeker

@Peter Suh, if you need anyone to test any further improvements to the mpt3sas on DS918+ hit me up, I'm keen to help get them fixed If you need any info from my system let me know what I can share.

Thank you so much for sharing Peter Suh, this is awesome I think I might be doing something wrong, I cant seem to change the /sys/module/i915/parameters/enable_guc with vi or by echoing an update? Is there another way to correctly update it with a new value? using vi to update: "/sys/module/i915/parameters/enable_guc" "/sys/module/i915/parameters/enable_guc" E514: Write error (file system full?) WARNING: Original file may be lost or damaged don't quit the editor until the file is successfully written! trying to update with echo: root@slave:/# sudo echo 2 > /sys/module/i915/parameters/enable_guc -name: /sys/module/i915/parameters/enable_guc: Permission denied I can see the device in transcoder: As well as DRI in the system folders: Just everything is software transcoding:

Thanks Peter Suh, it is great that these do support transcoding. They still are having issues reading information from the disks. This means I can't see disk temperatures or smart information at all using this version. Mpt3sas does work correctly with ds3617xs (without these below errors), so is likely a driver issue with DS918+, DS1019+ etc? These messages are flooded in the /var/log/messages file. Do you know if support for 8th Gen or others is still being worked on for Kernel 5? Would be great to be able to move to the latest versions 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2611]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sda/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2611]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sda/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2614]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdb/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2614]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdb/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2617]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdc/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2617]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdc/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2620]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdd/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2620]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdd/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2623]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sde/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2623]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sde/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2626]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdf/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2626]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdf/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2629]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdg/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2629]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdg/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2632]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdh/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2632]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdh/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2629]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdg/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2629]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdg/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2620]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdd/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2620]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdd/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2611]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sda/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2611]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sda/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2623]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sde/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2623]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sde/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2617]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdc/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2617]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdc/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2626]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdf/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2626]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdf/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2632]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdh/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2632]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdh/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2614]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdb/device/../../scsi_host/host*/proc_name 2023-12-15T13:00:25+11:00 Beast synostgd-disk[2614]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdb/device/../../scsi_host/host*/proc_name

Hi Peter Suh, I'm running a 3617xs with mpt3sas drivers to support my raid card. Underneath its an 8700k CPU with 64GB RAM. Would the SA6400 be an appropriate upgrade pathway? Is there anything special required to enable fast transcoding for the CPU? I'm keen to upgrade as I'm still on an older version of your loader "0.9.5.0".

Thank you for all your continued work Peter Do these above fixes have any impact the issues with disk firmware messages for the 918+ or 920+ systems as shared from this post from last month? Many thanks again!

Checking one of the disks - /dev/sdo, i see the following details: root@Beast:/# cd /sys/block/sdo/device root@Beast:/sys/block/sdo/device# ls -la total 0 drwxr-xr-x 8 root root 0 Sep 2 23:39 . drwxr-xr-x 4 root root 0 Sep 2 23:39 .. drwxr-xr-x 3 root root 0 Sep 2 23:39 block drwxr-xr-x 3 root root 0 Sep 2 23:39 bsg --w------- 1 root root 4096 Sep 3 00:07 delete -r--r--r-- 1 root root 4096 Sep 3 00:07 device_blocked -r--r--r-- 1 root root 4096 Sep 3 00:07 device_busy lrwxrwxrwx 1 root root 0 Sep 3 00:07 driver -> ../../../../../../../../../bus/scsi/drivers/sd -rw-r--r-- 1 root root 4096 Sep 3 00:07 eh_timeout -r--r--r-- 1 root root 4096 Sep 3 00:07 evt_capacity_change_reported -r--r--r-- 1 root root 4096 Sep 3 00:07 evt_inquiry_change_reported -r--r--r-- 1 root root 4096 Sep 3 00:07 evt_lun_change_reported -r--r--r-- 1 root root 4096 Sep 3 00:07 evt_media_change -r--r--r-- 1 root root 4096 Sep 3 00:07 evt_mode_parameter_change_reported -r--r--r-- 1 root root 4096 Sep 3 00:07 evt_soft_threshold_reached lrwxrwxrwx 1 root root 0 Sep 3 00:07 generic -> scsi_generic/sg8 -r--r--r-- 1 root root 0 Sep 3 00:07 inquiry -r--r--r-- 1 root root 4096 Sep 3 00:07 iocounterbits -r--r--r-- 1 root root 4096 Sep 3 00:07 iodone_cnt -r--r--r-- 1 root root 4096 Sep 3 00:07 ioerr_cnt -r--r--r-- 1 root root 4096 Sep 3 00:07 iorequest_cnt -r--r--r-- 1 root root 4096 Sep 3 00:07 modalias -r--r--r-- 1 root root 4096 Sep 3 00:07 model drwxr-xr-x 2 root root 0 Sep 3 00:02 power -rw-r--r-- 1 root root 4096 Sep 3 00:07 queue_depth -rw-r--r-- 1 root root 4096 Sep 3 00:07 queue_ramp_up_period -rw-r--r-- 1 root root 4096 Sep 3 00:07 queue_type --w------- 1 root root 4096 Sep 3 00:07 rescan -r--r--r-- 1 root root 4096 Sep 3 00:07 rev -r--r--r-- 1 root root 4096 Sep 3 00:07 sas_address -r--r--r-- 1 root root 4096 Sep 3 00:07 sas_device_handle drwxr-xr-x 3 root root 0 Sep 2 23:39 scsi_device drwxr-xr-x 3 root root 0 Sep 2 23:39 scsi_disk drwxr-xr-x 3 root root 0 Sep 2 23:39 scsi_generic -r--r--r-- 1 root root 4096 Sep 3 00:07 scsi_level -rw-r--r-- 1 root root 4096 Sep 3 00:07 state lrwxrwxrwx 1 root root 0 Sep 2 23:39 subsystem -> ../../../../../../../../../bus/scsi -r--r--r-- 1 root root 4096 Sep 3 00:07 syno_disk_serial -rw-r--r-- 1 root root 4096 Sep 3 00:07 syno_idle_time -rw-r--r-- 1 root root 4096 Sep 3 00:07 syno_scmd_min_timeout -r--r--r-- 1 root root 4096 Sep 3 00:07 syno_spindown -rw-r--r-- 1 root root 4096 Sep 3 00:07 syno_standby_syncing -rw-r--r-- 1 root root 4096 Sep 3 00:07 timeout -r--r--r-- 1 root root 4096 Sep 3 00:07 type -rw-r--r-- 1 root root 4096 Sep 3 00:07 uevent -r--r--r-- 1 root root 4096 Sep 3 00:07 vendor -r--r--r-- 1 root root 0 Sep 3 00:07 vpd_pg80 -r--r--r-- 1 root root 0 Sep 3 00:07 vpd_pg83

@Peter Suh I've tried to find some more information about what is happening under the hood in Synology regarding these messages: 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9340]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdl/device/../../scsi_host/host*/proc_name 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9340]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdl/device/../../scsi_host/host*/proc_name 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9335]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdk/device/../../scsi_host/host*/proc_name 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9335]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdk/device/../../scsi_host/host*/proc_name 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9348]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdm/device/../../scsi_host/host*/proc_name 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9348]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdm/device/../../scsi_host/host*/proc_name 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9354]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdn/device/../../scsi_host/host*/proc_name 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9354]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdn/device/../../scsi_host/host*/proc_name 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9357]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdo/device/../../scsi_host/host*/proc_name 2023-09-03T00:06:32+10:00 Beast synostgd-disk[9357]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdo/device/../../scsi_host/host*/proc_name I've tracked them to the "systemctl status synostoraged.service": ● synostoraged.service - Synology daemon for monitoring space/disk/cache status Loaded: loaded (/usr/lib/systemd/system/synostoraged.service; static; vendor preset: disabled) Active: active (running) since Sat 2023-09-02 23:39:31 AEST; 33min ago Main PID: 16670 (synostoraged) CGroup: /syno_dsm_storage_manager.slice/synostoraged.service ├─16670 synostoraged ├─16673 synostgd-disk ├─16675 synostgd-space ├─16677 synostgd-cache ├─16678 synostgd-volume └─16680 synostgd-external-volume Sep 03 00:12:32 Beast [3825]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdk/device/../../scsi_host/host*/proc_name Sep 03 00:12:32 Beast [3825]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdk/device/../../scsi_host/host*/proc_name Sep 03 00:12:32 Beast [3828]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdl/device/../../scsi_host/host*/proc_name Sep 03 00:12:32 Beast [3828]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdl/device/../../scsi_host/host*/proc_name Sep 03 00:12:32 Beast [3831]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdm/device/../../scsi_host/host*/proc_name Sep 03 00:12:32 Beast [3831]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdm/device/../../scsi_host/host*/proc_name Sep 03 00:12:32 Beast [3834]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdn/device/../../scsi_host/host*/proc_name Sep 03 00:12:32 Beast [3834]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdn/device/../../scsi_host/host*/proc_name Sep 03 00:12:32 Beast [3836]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdo/device/../../scsi_host/host*/proc_name Sep 03 00:12:32 Beast [3836]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdo/device/../../scsi_host/host*/proc_name It would be specifically coming from this process: synostgd-disk which seems to run every minute in the background. I am kind of at a loss of where else to check. My unix knowledge and troubleshooting skills are not that advanced, so I am unsure how else to help out here sorry. Do you think we need to modify the synostgd-disk service and the tell it to use the mtp3sas driver to do its queries and checks as opposed to the mv1475_driver or mv_soc_driver? Or is this not how it works or not possible? Even though I see these messages, my Storage manager appears healthy and happy: Disks are also all visible, and shows serial numbers and all SMART information:

Thank you for taking the time to post this information Peter Suh, I will review and see if anything comes back. Nothing appears to be having problems, all data is accessible and DSM appears to be working without any issues at all. Its purely these messages in the /var/log/messages file. Will see where this goes over the next while. Cheers, KS

Sorry post removed.

Thank you for the response Peter Suh, so not much I can really do but wait for better drivers / combability with HBAs, if I want to use 918+? 2023-08-31T18:39:35+10:00 Beast synostgd-disk[12352]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdn/device/../../scsi_host/host*/proc_name 2023-08-31T18:39:35+10:00 Beast synostgd-disk[12352]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdn/device/../../scsi_host/host*/proc_name 2023-08-31T18:39:35+10:00 Beast synostgd-disk[12354]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdo/device/../../scsi_host/host*/proc_name 2023-08-31T18:39:35+10:00 Beast synostgd-disk[12354]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdo/device/../../scsi_host/host*/proc_name 2023-08-31T18:39:36+10:00 Beast synostgd-disk[12334]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdh/device/../../scsi_host/host*/proc_name Otherwise go back to 3617xs but give up QVS working? Do you think those above errors are anything to really worry about? I'm not seeing anything bad within DSM. only in /var/log/messages.

Has anyone ever encountered this continuously appearing in their /var/log/messages? 2023-08-31T18:04:33+10:00 Beast disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdj/device/../../scsi_host/host*/proc_name 2023-08-31T18:04:33+10:00 Beast disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdj/device/../../scsi_host/host*/proc_name 2023-08-31T18:04:33+10:00 Beast synostgd-disk[19287]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdh/device/../../scsi_host/host*/proc_name 2023-08-31T18:04:33+10:00 Beast disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdh/device/../../scsi_host/host*/proc_name 2023-08-31T18:04:33+10:00 Beast synostgd-disk[19290]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdi/device/../../scsi_host/host*/proc_name 2023-08-31T18:04:33+10:00 Beast synostgd-disk[19290]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdi/device/../../scsi_host/host*/proc_name 2023-08-31T18:04:33+10:00 Beast synostgd-disk[19296]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdk/device/../../scsi_host/host*/proc_name 2023-08-31T18:04:33+10:00 Beast synostgd-disk[19296]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdk/device/../../scsi_host/host*/proc_name 2023-08-31T18:04:33+10:00 Beast synostgd-disk[19304]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdn/device/../../scsi_host/host*/proc_name 2023-08-31T18:04:33+10:00 Beast synostgd-disk[19304]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdn/device/../../scsi_host/host*/proc_name 2023-08-31T18:04:33+10:00 Beast synostgd-disk[19299]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdl/device/../../scsi_host/host*/proc_name 2023-08-31T18:04:33+10:00 Beast synostgd-disk[19299]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdl/device/../../scsi_host/host*/proc_name 2023-08-31T18:04:33+10:00 Beast synostgd-disk[19306]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdo/device/../../scsi_host/host*/proc_name 2023-08-31T18:04:33+10:00 Beast synostgd-disk[19306]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdo/device/../../scsi_host/host*/proc_name 2023-08-31T18:04:33+10:00 Beast synostgd-disk[19301]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdm/device/../../scsi_host/host*/proc_name 2023-08-31T18:04:33+10:00 Beast synostgd-disk[19301]: disk/disk_is_mv1475_driver.c:66 Can't get sata chip name from pattern /sys/block/sdm/device/../../scsi_host/host*/proc_name Seem to continuously occur every time the synostgd service runs every minute. My install is using a mpt3sas driver on DS918+ install. 7.2.0-64570 Update 1

Well I have resolved my issue another way, I found that PeterSuh's loader had an mpt3sas support with DS918+ so I've installed that and migrated successfully. With Transcoding working straight away with the 918+ is there any reason to go 920+ now?

Hi All, I'm struggling to install DS920p and load the MPT3SAS Driver. I'm running the command to add it: ./rploader.sh ext ds920p-7.2.0-64570 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt3sas/rpext-index.json This appears to work correctly and pull the drivers. I see the following: tc@box:~$ ./rploader.sh ext ds920p-7.2.0-64570 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt3sas/rpext-index.json Rploader Version : 0.9.4.9 Loader source : https://github.com/pocopico/redpill-load.git Loader Branch : develop Redpill module source : https://github.com/pocopico/redpill-lkm.git : Redpill module branch : master Extensions : all-modules eudev disks misc Extensions URL : "https://github.com/pocopico/tcrp-addons/raw/main/all-modules/rpext-index.json", "https://github.com/pocopico/tcrp-addons/raw/main/eudev/rpext-index.json", "https://github.com/pocopico/tcrp-addons/raw/main/disks/rpext-index.json", "https://github.com/pocopico/tcrp-addons/raw/main/misc/rpext-index.json" TOOLKIT_URL : https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.bromolow-7.0.dev.txz/download TOOLKIT_SHA : a5fbc3019ae8787988c2e64191549bfc665a5a9a4cdddb5ee44c10a48ff96cdd SYNOKERNEL_URL : https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/25426branch/bromolow-source/linux-3.10.x.txz/download SYNOKERNEL_SHA : 18aecead760526d652a731121d5b8eae5d6e45087efede0da057413af0b489ed COMPILE_METHOD : toolkit_dev TARGET_PLATFORM : ds920p TARGET_VERSION : 7.2.0 TARGET_REVISION : 64570 REDPILL_LKM_MAKE_TARGET : dev-v7 KERNEL_MAJOR : 4 MODULE_ALIAS_FILE : modules.alias.4.json SYNOMODEL : ds920p_64570 MODEL : DS920+ Local Cache Folder : /mnt/sda3/auxfiles DATE Internet : 30082023 Local : 30082023 Checking Internet Access -> OK Cloning into 'redpill-lkm'... remote: Enumerating objects: 1715, done. remote: Counting objects: 100% (483/483), done. remote: Compressing objects: 100% (95/95), done. remote: Total 1715 (delta 415), reused 395 (delta 388), pack-reused 1232 Receiving objects: 100% (1715/1715), 5.84 MiB | 11.44 MiB/s, done. Resolving deltas: 100% (1049/1049), done. Cloning into 'redpill-load'... remote: Enumerating objects: 5098, done. remote: Counting objects: 100% (5098/5098), done. remote: Compressing objects: 100% (2251/2251), done. remote: Total 5098 (delta 2703), reused 4983 (delta 2644), pack-reused 0 Receiving objects: 100% (5098/5098), 125.90 MiB | 11.84 MiB/s, done. Resolving deltas: 100% (2703/2703), done. [#] Checking runtime for required tools... [OK] [#] Adding new extension from https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt3sas/rpext-index.json... [#] Downloading remote file https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt3sas/rpext-index.json to /home/tc/redpill-load/custom/extensions/_new_ext_index.tmp_json ################################################################################################################################################### 100.0% [OK] [#] ========================================== pocopico.mpt3sas ========================================== [#] Extension name: mpt3sas [#] Description: Adds LSI MPT Fusion SAS 3.0 Device Driver Support [#] To get help visit: <todo> [#] Extension preparer/packer: https://github.com/pocopico/rp-ext/tree/main/mpt3sas [#] Software author: https://github.com/pocopico [#] Update URL: https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt3sas/rpext-index.json [#] Platforms supported: ds1621p_42218 ds1621p_42951 ds918p_41890 dva3221_42661 ds3617xs_42621 ds3617xs_42218 ds920p_42661 dva3221_42962 ds918p_42661 ds3622xsp_42962 ds3617xs_42951 dva1622_42218 dva1622_42621 ds920p_42962 ds1621p_42661 dva1622_42951 ds918p_25556 dva3221_42218 ds3615xs_42661 dva3221_42951 ds3622xsp_42661 ds2422p_42661 ds3622xsp_42218 ds2422p_42962 rs4021xsp_42621 dva1622_42962 ds2422p_42218 rs4021xsp_42962 dva3221_42621 ds3615xs_42962 ds3617xs_42962 ds3615xs_41222 ds920p_42951 rs4021xsp_42218 ds2422p_42951 ds918p_42621 ds3617xs_42661 ds3615xs_25556 ds920p_42218 rs4021xsp_42951 ds920p_42621 ds918p_42962 ds3615xs_42951 ds3622xsp_42951 dva1622_42661 ds918p_42218 ds2422p_42621 ds1621p_42621 ds3615xs_42621 ds3615xs_42218 ds1621p_42962 ds3622xsp_42621 rs4021xsp_42661 [#] ======================================================================================= However when I do a build ./rploader.sh build ds920p-7.2.0-64570 I get the following: [-] The extension pocopico.mpt3sas was found. However, the extension index has no recipe for ds920p_64570 platform. It may not be [-] supported on that platform, or author didn't updated it for that platform yet. You can try running [-] "ext-manager.sh update" to refresh indexes for all extensions manually. Is there any know version of MPT3SAS that will work with the DS920P? I was keen to use it for the Intel Quick Shift transcoding options. My current install is ds3617xs however it doesn't support transcoding at all. Thanks, KS

I got it sorted. I found HyperV wouldn't redirect USB though. So I installed USBIP on my WIndows PC and the Ubuntu VM. Got the USB updated to UEFI Correctly. After that, I found it still didn't help my disk detection process for upgrading to DSM 7.0 - From all my previous messages in this thread. TLDR, I was struggling to get my DSM 7.0 Install to give me a migratable option. MPT3SAS and Disks were being detected correctly, just no option to Migrate only fresh install. After I disabled motherboard SATA controller (which only has 1 drive connected to it), leaving only my MPT3SAS Raid card (with 8 drives connected). I was presented with a migratable option!! YAY! So now, I have DSM 7.0 installed and working beautifully as it was in all my previous testing I can only assume that my disk on my SATA controller did not have any of the DSM6.2 OS install on the disk and the DSM7.0 install was looking there as it was included. I may end up changing my SATAPortMAPs again later on to put the Onboard Sata Controller and Disk back online. But for now its not important!. Man, what a ******* Plex Media Server was for DSM7 though, I didn't realise it creates a whole new user account and needs to migrate the configuration / metadata. Took some googling but worked through it also I really appreciate you efforts here @pocopico, you've really made an awesome tool here. Major props to so many of our awesome contributors to this thread and the forums!!! Go Xpenology

Thx for responding, I was trying from a LIVE Ubuntu IMG I'm installing Ubuntu on a HyperV machine, so give it another try from within the VM and I'll see how that goes