pocopico Posted September 3, 2021 Share #901 Posted September 3, 2021 6 minutes ago, Orphée said: It seems loader consider "not a SATA disk" and then ignore it Did you try the supportsas in the synoinfo.conf ? Link to comment Share on other sites More sharing options...
pocopico Posted September 3, 2021 Share #902 Posted September 3, 2021 I have compiled and have tried some modules and it looks that they load and devices get discovered e.g vmxnet3, tg3, mptsas, etc. The problem though remains that during install we would need to find a way to load them and after install, keep/put them in place to be loaded consistently Link to comment Share on other sites More sharing options...
jumkey Posted September 3, 2021 Share #903 Posted September 3, 2021 3 hours ago, haydibe said: Oh boy🙄 This will leave plenty of fun for LSI9211 owner that want to migrate from (jun's) 6.2.3 to (redpill) 7.0. Must be a behavior of the mpt2sas driver itself - almost looks like they change from /dev/sd? to /dev/sas? at one point and the new drivers happen to be created from sources after that change? Afaik Bromolow DSM6.2.3 uses 3.10.105. and the change logs of https://mirrors.edge.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.106, https://mirrors.edge.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.107 or https://mirrors.edge.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.108 (which is what the bromolow DSM7.0 kernel sources base on) indicate nothing that would point to such a change (or anything helpfull).. But what caused the different detection then? I expect lvm/mdam raids to identify the drives belong to an array by device path (/dev/sd?) and not by the physical controller they are attached to - thus a switch from /dev/sd? to /dev/sas? will result in a broken array?! I hope I realy got this wrong and some sort of magic that relies on disk-uuid, serialnumber or whatever is used to self-heal the situation. change CONFIG_SYNO_SAS_DEVICE_PREFIX="sas" to CONFIG_SYNO_SAS_DEVICE_PREFIX="sd"? if you want? root@vultr:~/build/linux-4.4.x-apollolake-25426# grep -r 'SYNO_SAS_DEVICE_PREFIX' ./ ./synoconfigs/broadwellntbap:CONFIG_SYNO_SAS_DEVICE_PREFIX="sas" ./synoconfigs/Kconfig.devices:config SYNO_SAS_DEVICE_PREFIX ./synoconfigs/broadwellnk:CONFIG_SYNO_SAS_DEVICE_PREFIX="sas" ./synoconfigs/broadwellntb:CONFIG_SYNO_SAS_DEVICE_PREFIX="sas" ./synoconfigs/coffeelake:CONFIG_SYNO_SAS_DEVICE_PREFIX="sas" ./synoconfigs/purley:CONFIG_SYNO_SAS_DEVICE_PREFIX="sas" ./drivers/scsi/sd.c: error = syno_sd_format_numeric_disk_name(CONFIG_SYNO_SAS_DEVICE_PREFIX, synoidx, gd->disk_name, DISK_NAME_LEN); ./drivers/scsi/sd.c: error = syno_sd_format_numeric_disk_name(CONFIG_SYNO_SAS_DEVICE_PREFIX, synoidx, gd->disk_name, DISK_NAME_LEN); root@vultr:~/build/linux-4.4.x-apollolake-25426# 2 Link to comment Share on other sites More sharing options...
slte Posted September 4, 2021 Share #904 Posted September 4, 2021 On 9/1/2021 at 8:22 PM, jumkey said: with uefi support. redpill-load.win.zip.001 10 MB · 167 downloads redpill-load.win.zip.002 9.57 MB · 188 downloads it also can support dsm 7.0.1 How do I use it? Link to comment Share on other sites More sharing options...
mb0x Posted September 4, 2021 Share #905 Posted September 4, 2021 (edited) On 9/1/2021 at 3:22 AM, loomes said: The Loader can be build with 7.0.1 Images, the patches are ok, but when i boot up the created loader it jumps every time back to grub menu when it should load the kernel. I face this issue too. how do you solve it? Edited September 4, 2021 by mb0x Link to comment Share on other sites More sharing options...
pigr8 Posted September 4, 2021 Share #906 Posted September 4, 2021 11 hours ago, haydibe said: Oh boy🙄 This will leave plenty of fun for LSI9211 owner that want to migrate from (jun's) 6.2.3 to (redpill) 7.0. Must be a behavior of the mpt2sas driver itself - almost looks like they change from /dev/sd? to /dev/sas? at one point and the new drivers happen to be created from sources after that change? Afaik Bromolow DSM6.2.3 uses 3.10.105. and the change logs of https://mirrors.edge.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.106, https://mirrors.edge.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.107 or https://mirrors.edge.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.108 (which is what the bromolow DSM7.0 kernel sources base on) indicate nothing that would point to such a change (or anything helpfull).. But what caused the different detection then? I expect lvm/mdam raids to identify the drives belong to an array by device path (/dev/sd?) and not by the physical controller they are attached to - thus a switch from /dev/sd? to /dev/sas? will result in a broken array?! I hope I realy got this wrong and some sort of magic that relies on disk-uuid, serialnumber or whatever is used to self-heal the situation. i dont think it's a kernel issue related to the jump to 7.0, i think it's something related to the loader that does not do some kind of conversion like jun's did.. i tried to compile and boot redpill 6.2.4 (i'm now with jun's 6.2.3) and the /dev/sas* problem is there. 8 hours ago, jumkey said: change CONFIG_SYNO_SAS_DEVICE_PREFIX="sas" to CONFIG_SYNO_SAS_DEVICE_PREFIX="sd"? if you want? root@vultr:~/build/linux-4.4.x-apollolake-25426# grep -r 'SYNO_SAS_DEVICE_PREFIX' ./ ./synoconfigs/broadwellntbap:CONFIG_SYNO_SAS_DEVICE_PREFIX="sas" ./synoconfigs/Kconfig.devices:config SYNO_SAS_DEVICE_PREFIX ./synoconfigs/broadwellnk:CONFIG_SYNO_SAS_DEVICE_PREFIX="sas" ./synoconfigs/broadwellntb:CONFIG_SYNO_SAS_DEVICE_PREFIX="sas" ./synoconfigs/coffeelake:CONFIG_SYNO_SAS_DEVICE_PREFIX="sas" ./synoconfigs/purley:CONFIG_SYNO_SAS_DEVICE_PREFIX="sas" ./drivers/scsi/sd.c: error = syno_sd_format_numeric_disk_name(CONFIG_SYNO_SAS_DEVICE_PREFIX, synoidx, gd->disk_name, DISK_NAME_LEN); ./drivers/scsi/sd.c: error = syno_sd_format_numeric_disk_name(CONFIG_SYNO_SAS_DEVICE_PREFIX, synoidx, gd->disk_name, DISK_NAME_LEN); root@vultr:~/build/linux-4.4.x-apollolake-25426# won't work i'm afraid, sas devices have a different names for driver numbers, sata use /dev/sdA /dev/sdB /dev/sdX and so on while sas use /dev/sas1 /dev/sas2, even if the prefix is changed kernel side i don't think it would work. 1 1 Link to comment Share on other sites More sharing options...
haydibe Posted September 4, 2021 Share #907 Posted September 4, 2021 I am glad that I have been wrong about changes regarding /dev/sas vs. /dev/sd in the driver - it makes sense because there was no evidence in the change log. There must be some sort of config/flag that is responsible for this. Pitty that @jumkey's suggestion with CONFIG_SYNO_SAS_DEVICE_PREFIX didn't play out. Thanks for testing @pigr8! Link to comment Share on other sites More sharing options...
pocopico Posted September 4, 2021 Share #908 Posted September 4, 2021 8 minutes ago, haydibe said: I am glad that I have been wrong about changes regarding /dev/sas vs. /dev/sd in the driver - it makes sense because there was no evidence in the change log. There must be some sort of config/flag that is responsible for this. what if you create links of the eg /dev/sas1 to /dev/sda with # ln -s /dev/sas1 /dev/sda Link to comment Share on other sites More sharing options...
tocinillo2 Posted September 4, 2021 Share #909 Posted September 4, 2021 Sorry for the late reply: 6.2.4 with UEFI: https://drive.google.com/file/d/1N-edu-y_p6yE7bmRAY6sqgnzDaIagQqY/view?usp=sharing Works perfectly with 10 HDD SATA (2 sata pci-e controllers 4 port/each + 2 motherboard sata ports). Same img with 7.0 doesn't work ("error detected in sata port and disabled"). Baremetal with J4125M Link to comment Share on other sites More sharing options...
tocinillo2 Posted September 4, 2021 Share #910 Posted September 4, 2021 (edited) Compiled 7.0.1 with last BSP patch and works perfect https://drive.google.com/file/d/1CqqhO-TBdwOff0dH54iP-XPdrhzgvtNR/view?usp=sharing - Add UEFI support. - Deleted twice EFI folder. - Fixed SynoBoot_EFI place. - Compiled with last BSP Patch for 7.0.1. - Insmod efi_gop into EFI. - Tested with Baremetal and works fine (Astock 3455-ITX). - After installation (the reboot process can take 15-20 minutes) you have to install File Station manually: https://www.synology.com/en-us/support/download/DS918+#system (select DSM 7.0), find and download File Station SPK and install it in Package Center. Edited September 4, 2021 by tocinillo2 2 5 Link to comment Share on other sites More sharing options...
maxhartung Posted September 4, 2021 Share #911 Posted September 4, 2021 (edited) 2 hours ago, tocinillo2 said: Compiled 7.0.1 with last BSP patch and works perfect https://drive.google.com/file/d/1CqqhO-TBdwOff0dH54iP-XPdrhzgvtNR/view?usp=sharing - Add UEFI support. - Deleted twice EFI folder. - Fixed SynoBoot_EFI place. - Compiled with last BSP Patch for 7.0.1. - Insmod efi_gop into EFI. - Tested with Baremetal and works fine (Astock 3455-ITX). - After installation (the reboot process can take 15-20 minutes) you have to install File Station manually: https://www.synology.com/en-us/support/download/DS918+#system (select DSM 7.0), find and download File Station SPK and install it in Package Center. Thank you. I will try this version too on my HP EliteBook 840 G2. There is still hope. Same error on both EFI and legacy boot. I should mention that I only have USB 3.0 ports. Same with 6.2.4. So, I looked up in Linux and I only have one SATA Controller. Can anybody help me debug this issue ? Edited September 4, 2021 by maxhartung Link to comment Share on other sites More sharing options...
D.S Posted September 4, 2021 Share #912 Posted September 4, 2021 2 hours ago, tocinillo2 said: Sorry for the late reply: 6.2.4 with UEFI: https://drive.google.com/file/d/1N-edu-y_p6yE7bmRAY6sqgnzDaIagQqY/view?usp=sharing Works perfectly with 10 HDD SATA (2 sata pci-e controllers 4 port/each + 2 motherboard sata ports). Same img with 7.0 doesn't work ("error detected in sata port and disabled"). Baremetal with J4125M Just tested, it works! Thank you. Link to comment Share on other sites More sharing options...
D.S Posted September 4, 2021 Share #913 Posted September 4, 2021 1 hour ago, tocinillo2 said: Compiled 7.0.1 with last BSP patch and works perfect https://drive.google.com/file/d/1CqqhO-TBdwOff0dH54iP-XPdrhzgvtNR/view?usp=sharing - Add UEFI support. - Deleted twice EFI folder. - Fixed SynoBoot_EFI place. - Compiled with last BSP Patch for 7.0.1. - Insmod efi_gop into EFI. - Tested with Baremetal and works fine (Astock 3455-ITX). - After installation (the reboot process can take 15-20 minutes) you have to install File Station manually: https://www.synology.com/en-us/support/download/DS918+#system (select DSM 7.0), find and download File Station SPK and install it in Package Center. It works on my Baremetal with i7-6700 and no File Station issue. Everything looks good. Link to comment Share on other sites More sharing options...
kennysino Posted September 4, 2021 Share #914 Posted September 4, 2021 1 hour ago, tocinillo2 said: 使用最新的 BSP 补丁编译 7.0.1 并完美运行 https://drive.google.com/file/d/1CqqhO-TBdwOff0dH54iP-XPdrhzgvtNR/view?usp=sharing - 添加 UEFI 支持。 - 删除了两次 EFI 文件夹。 - 修正了 SynoBoot_EFI 的位置。 - 使用 7.0.1 的最新 BSP 补丁编译。 - Insmod efi_gop 进入 EFI。 - 使用 Baremetal 测试并正常工作(Astock 3455-ITX)。 - 安装后(重启过程可能需要 15-20 分钟)您必须手动安装 File Station:https : //www.synology.com/en-us/support/download/DS918+#system(选择 DSM 7.0),找到并下载 File Station SPK 并将其安装在套件中心。 there is an sata error and i don't know how to fix it Link to comment Share on other sites More sharing options...
yuuu Posted September 4, 2021 Share #915 Posted September 4, 2021 2 hours ago, tocinillo2 said: Compiled 7.0.1 with last BSP patch and works perfect https://drive.google.com/file/d/1CqqhO-TBdwOff0dH54iP-XPdrhzgvtNR/view?usp=sharing - Add UEFI support. - Deleted twice EFI folder. - Fixed SynoBoot_EFI place. - Compiled with last BSP Patch for 7.0.1. - Insmod efi_gop into EFI. - Tested with Baremetal and works fine (Astock 3455-ITX). - After installation (the reboot process can take 15-20 minutes) you have to install File Station manually: https://www.synology.com/en-us/support/download/DS918+#system (select DSM 7.0), find and download File Station SPK and install it in Package Center. It works on ASUS C246 Motherboard E2124 cpu. Link to comment Share on other sites More sharing options...
flyride Posted September 4, 2021 Share #916 Posted September 4, 2021 18 hours ago, haydibe said: I hope I realy got this wrong and some sort of magic that relies on disk-uuid, serialnumber or whatever is used to self-heal the situation. This is how it works. Device names can (and do) change and it has no impact on normal md services. 1 1 Link to comment Share on other sites More sharing options...
haydibe Posted September 4, 2021 Share #917 Posted September 4, 2021 (edited) 2 minutes ago, flyride said: UUID/superblock is how it works. Device names can (and do) change and it has no impact on normal md services. So it is not just the drive order that is irrelevant, but it's also the device path (and thus the controller type) that is irrevant. I was aware of the first part, but not of the second. Good to know Edited September 4, 2021 by haydibe Link to comment Share on other sites More sharing options...
pkdick1 Posted September 4, 2021 Share #918 Posted September 4, 2021 Il y a 4 heures, tocinillo2 a dit : Compiled 7.0.1 with last BSP patch and works perfect https://drive.google.com/file/d/1CqqhO-TBdwOff0dH54iP-XPdrhzgvtNR/view?usp=sharing - Add UEFI support. - Deleted twice EFI folder. - Fixed SynoBoot_EFI place. - Compiled with last BSP Patch for 7.0.1. - Insmod efi_gop into EFI. - Tested with Baremetal and works fine (Astock 3455-ITX). - After installation (the reboot process can take 15-20 minutes) you have to install File Station manually: https://www.synology.com/en-us/support/download/DS918+#system (select DSM 7.0), find and download File Station SPK and install it in Package Center. Hello, thank you very much for this file. May I ask you a question ?: I have myself an Asrock J4150-ITX, do you think that using you image, I will be able to migrate from DSM 6.23 to DSM 7.01 ? I also thought that it was also necessary to put a legit serial nember to make the baremetal XPENOLOGY device working: could you give me your point about this ? I admit that I start to long a bit about this wonderful development, so I am close to take the risk to use you image... Thank you in advance, Link to comment Share on other sites More sharing options...
taiziccf Posted September 4, 2021 Share #919 Posted September 4, 2021 In case any of you need 918+ 7.0.1 42214 https://github.com/RedPill-TTG/redpill-load/pull/21 i am using the docker 0.6 created by @haydibe i did only small modification so i take no credit for all hard work contributed by you kind people here. { "id": "apollolake-7.0.1-42214", "platform_version": "apollolake-7.0.1-42214", "user_config_json": "apollolake_user_config.json", "docker_base_image": "debian:10-slim", "compile_with": "toolkit_dev", "download_urls": { "kernel": "https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/25426branch/apollolake-source/linux-4.4.x.txz/download", "toolkit_dev": "https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.apollolake-7.0.dev.txz/download" }, "redpill_lkm": { "source_url": "https://github.com/RedPill-TTG/redpill-lkm.git", "branch": "master" }, "redpill_load": { "source_url": "https://github.com/chchia/redpill-load.git", "branch": "master" } } thanks a lot for all the great work! 2 Link to comment Share on other sites More sharing options...
maxhartung Posted September 4, 2021 Share #920 Posted September 4, 2021 In order to work on ESXI what changes are required ? Link to comment Share on other sites More sharing options...
snowfox Posted September 4, 2021 Share #921 Posted September 4, 2021 5 hours ago, tocinillo2 said: Compiled 7.0.1 with last BSP patch and works perfect https://drive.google.com/file/d/1CqqhO-TBdwOff0dH54iP-XPdrhzgvtNR/view?usp=sharing - Add UEFI support. - Deleted twice EFI folder. - Fixed SynoBoot_EFI place. - Compiled with last BSP Patch for 7.0.1. - Insmod efi_gop into EFI. - Tested with Baremetal and works fine (Astock 3455-ITX). - After installation (the reboot process can take 15-20 minutes) you have to install File Station manually: https://www.synology.com/en-us/support/download/DS918+#system (select DSM 7.0), find and download File Station SPK and install it in Package Center. Thank You ! It works on Astock J5005-ITX 1 Link to comment Share on other sites More sharing options...
Drones Posted September 4, 2021 Share #922 Posted September 4, 2021 (edited) My installation is stuck in 56%. Using 7.0.1 image on SanDisk flash drive. Trying to install on baremetal asrock 4105. Edited September 4, 2021 by Drones Link to comment Share on other sites More sharing options...
jforts Posted September 4, 2021 Share #923 Posted September 4, 2021 13 minutes ago, Drones said: My installation is stuck in 56%. Using 7.0.1 image on SanDisk flash drive. Trying to install on baremetal asrock 4105. Check the post that I posted earlier. Your problem could be resolved with that. At leat mine was... I am working to upgrade on my production 6.2.3 now. Link to comment Share on other sites More sharing options...
Drones Posted September 4, 2021 Share #924 Posted September 4, 2021 3 минуты назад, jforts сказал: Check the post that I posted earlier. Your problem could be resolved with that. At leat mine was... I am working to upgrade on my production 6.2.3 now. I'm trying this solution, but no luck. How i can change PID&VID on ready-made image (post tocinillo2)? I think my problem is with wrong PID&VID. Link to comment Share on other sites More sharing options...
haydibe Posted September 4, 2021 Share #925 Posted September 4, 2021 (edited) Incorporated the addition from @taiziccf for chchia's apollolake-7.0.1-42214, and added @jumkey's bromolow-7.0.1-42214 from his develop branch. You guys are moving at an incredible pace redpill-tool-chain_x86_64_v0.6.1.zip Edited September 4, 2021 by haydibe 5 1 Link to comment Share on other sites More sharing options...
Recommended Posts