phone guy Posted July 4, 2022 Share #3951 Posted July 4, 2022 1 hour ago, gadreel said: @pocopico I have Unraid which is using KVM for Virtual Machines. With Unraid's version 6.9.2 the virtual SATA controller which I passthrough my drives has the PCI address 00.1f.2 it was working fine to me. I updated to Unraid 6.10.3 recently and now when I use the satamap command I am getting the message "Mapping KVM q35 bogus controller after maxdisks". I do not know why this check does not fire when I am on 6.9.2 but is there a specific reason why we flag the 1st controller as bogus? 56 minutes ago, pocopico said: Well actually if i remember correctly the first controller is not the one that KVM is attaching the drives. During tests with proxmox, and q35 based vms, the first controller was a ghost controller with no drives, the 2nd sata controller is the one it starts mapping from. The solution was to switch to i440fx system, or always accept drives 1 and 2 will never technically be populated. I have done both. 1 Quote Link to comment Share on other sites More sharing options...
gadreel Posted July 4, 2022 Share #3952 Posted July 4, 2022 (edited) 1 hour ago, pocopico said: Well actually if i remember correctly the first controller is not the one that KVM is attaching the drives. Not for Unraid guys. At least for version 6.9.2. Pocopico's if statement does not fire up. I do not know why the if statement is true on 6.10.3 <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> I do not know if this change is causing kernel panics on 6.10.3. So what should I do? For now on I should skip the 1st controller and create a 2nd controller to map my drives? Edited July 4, 2022 by gadreel Quote Link to comment Share on other sites More sharing options...
pocopico Posted July 4, 2022 Author Share #3953 Posted July 4, 2022 11 minutes ago, gadreel said: Not for Unraid guys. At least for version 6.9.2. Pocopico's if statement does not fire up. I do not know why the if statement is true on 6.10.3 <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> I do not know if this change is causing kernel panics on 6.10.3. So what should I do? For now on I should skip the 1st controller and create a 2nd controller to map my drives? Wrong SataPortMap will not cause KP. Can you capture the KP ? The most common issue would be the cpu emulation. Q35 was/is the right one. Quote Link to comment Share on other sites More sharing options...
gadreel Posted July 4, 2022 Share #3954 Posted July 4, 2022 Just now, pocopico said: Wrong SataPortMap will not cause KP. Can you capture the KP ? The most common issue would be the cpu emulation. Q35 was/is the right one. I have been using TC RedPill since day one with q35 and never had an issue. I do not thing is the issue unless something changed in new versions of libvirt. I will update Unraid to 6.10.3 again and try and this time map all 6 drives to the 2nd controller. Quote Link to comment Share on other sites More sharing options...
flaky Posted July 4, 2022 Share #3955 Posted July 4, 2022 Hi, I did a baremetal install with RedPill TinyCore loader. The installation finishes smoothly, DSM prompted reboots. Upon reboots, RPTC boots from usb, then after a while, the machine automatically shutdown. Any idea? I suspects it's a crash/kernel panic? Any log that I can look into? Thanks. Quote Link to comment Share on other sites More sharing options...
pocopico Posted July 4, 2022 Author Share #3956 Posted July 4, 2022 2 hours ago, flaky said: Hi, I did a baremetal install with RedPill TinyCore loader. The installation finishes smoothly, DSM prompted reboots. Upon reboots, RPTC boots from usb, then after a while, the machine automatically shutdown. Any idea? I suspects it's a crash/kernel panic? Any log that I can look into? Thanks. Which platform are you building ? Quote Link to comment Share on other sites More sharing options...
z1022 Posted July 4, 2022 Share #3957 Posted July 4, 2022 On 7/2/2022 at 8:01 PM, z1022 said: Hi Pocopico, I create two VM, VM1 and VM2 VM1 run TCRP to build image and extract for VM2 After setup in VM2. downloaded from synology the 7.1.0-42661 update 2 then do manual update inside DSM After the next reboot I got the page "Welcome back: Click here to migrate your diskstation". I shutdown VM2 And then use VM1 boot into TCRP and run ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh backup ./rploader.sh postupdate apollolake-7.1.0-42661 extract image and replace the image in VM2 Reboot VM2 After the next reboot I got the page "Welcome back: Click here to migrate your diskstation". confirm migration and reboot. I got the page "Welcome back: Click here to migrate your diskstation". again. What step is wrong ? Thanks Anyone can help? Thanks Quote Link to comment Share on other sites More sharing options...
flaky Posted July 5, 2022 Share #3958 Posted July 5, 2022 5 hours ago, pocopico said: Which platform are you building ? DS3622xs+ Motherboard: Supermicro X11SRM-VF CPU: 8core/8thread RAM: 128GB ECC HBA: LSI SAS3224 Network: connectx-3 I also tried ESXI with this guide VM boots and can install DSM with one virtual disk, but as soon as I add either one of the PCIE passthrough device (SAS3224 or connectx-3), it automatically shutdown. I see that during builds the ./rploader found driver for both devices. Here is my config: { "extra_cmdline": { "pid": "removed", "vid": "removed", "sn": "removed", "netif_num": "2", "mac1": "removed", "mac2": "removed", "SataPortMap": "11", "DiskIdxMap": "1000" }, "synoinfo": { "internalportcfg": "0xffff", "maxdisks": "16", "support_bde_internal_10g": "no", "support_disk_compatibility": "no", "support_memory_compatibility": "no" }, "ramdisk_copy": {} } Quote Link to comment Share on other sites More sharing options...
pocopico Posted July 5, 2022 Author Share #3959 Posted July 5, 2022 1 hour ago, flaky said: VM boots and can install DSM with one virtual disk, but as soon as I add either one of the PCIE passthrough device (SAS3224 or connectx-3), it automatically shutdown. You need to login though serial and check your systemctl failing depending services. I was certain that redpill-misc has solved this issue but maybe not all cases. Quote Link to comment Share on other sites More sharing options...
loveburn Posted July 5, 2022 Share #3960 Posted July 5, 2022 (edited) What does that mean? What the required tools?) Edited July 5, 2022 by loveburn Quote Link to comment Share on other sites More sharing options...
pocopico Posted July 5, 2022 Author Share #3961 Posted July 5, 2022 bspatch is missing, you can do wget https://github.com/pocopico/tinycore-redpill/blob/main/bspatch?raw=true sudo cp bspatch /bin/ 1 Quote Link to comment Share on other sites More sharing options...
loveburn Posted July 5, 2022 Share #3962 Posted July 5, 2022 7 минут назад, pocopico сказал: bspatch is missing, you can do wget https://github.com/pocopico/tinycore-redpill/blob/main/bspatch?raw=true sudo cp bspatch /bin/ Thanks for helping) Quote Link to comment Share on other sites More sharing options...
a29psx Posted July 5, 2022 Share #3963 Posted July 5, 2022 (edited) On 5/12/2022 at 6:49 PM, pocopico said: Change both to ./rploader.sh ext broadwellnk-7.1.0-42661 add https://github.com/pocopico/redpill-load/raw/develop/redpill-virtio/rpext-index.json ./rploader.sh ext broadwellnk-7.1.0-42661 add https://github.com/pocopico/redpill-load/raw/develop/redpill-acpid/rpext-index.json does these develop package work with broadwellnk-7.1.0-42661 update 2 and update 3 Edited July 5, 2022 by a29psx Quote Link to comment Share on other sites More sharing options...
gadreel Posted July 5, 2022 Share #3964 Posted July 5, 2022 @pocopico for Update 3 we need to wait for something or we just update it as normal and run the postupdate command as on Update 2? Quote Link to comment Share on other sites More sharing options...
pocopico Posted July 5, 2022 Author Share #3965 Posted July 5, 2022 Tested the manual update to 7.1 update3, followed by the postupdate process and all work as expected. 2 Quote Link to comment Share on other sites More sharing options...
gadreel Posted July 5, 2022 Share #3966 Posted July 5, 2022 (edited) I confirm for DS918+. Manual update to 7.1 U3 followed by the postupdate command. Edited July 5, 2022 by gadreel Quote Link to comment Share on other sites More sharing options...
sam juan Posted July 5, 2022 Share #3967 Posted July 5, 2022 how to update to 7.1 U3 without attaching monitor to the box? thanks. Quote Link to comment Share on other sites More sharing options...
drobik Posted July 6, 2022 Share #3968 Posted July 6, 2022 Hello, @pocopico First of all, many tanks to you for work! I have installed DSM 7.1 DS3622+ on my PC, everything works fine, but I have the error in update section (see attached file). The same situation when i try to log into advanced media extension. Looks like this is not connection to synology servers, but i have the real s\n and quickconnect is working. I think somewhere in bootloader it is blocked, but for example for DS918+ no this problem. Can you please help and give a right direction to make some change and get it working. Thank you in advance. Quote Link to comment Share on other sites More sharing options...
pocopico Posted July 6, 2022 Author Share #3969 Posted July 6, 2022 1 hour ago, drobik said: Hello, @pocopico First of all, many tanks to you for work! I have installed DSM 7.1 DS3622+ on my PC, everything works fine, but I have the error in update section (see attached file). The same situation when i try to log into advanced media extension. Looks like this is not connection to synology servers, but i have the real s\n and quickconnect is working. I think somewhere in bootloader it is blocked, but for example for DS918+ no this problem. Can you please help and give a right direction to make some change and get it working. Thank you in advance. Update servers are masked. SSH into DSM and check your /etc/hosts for records. Quote Link to comment Share on other sites More sharing options...
drobik Posted July 6, 2022 Share #3970 Posted July 6, 2022 46 минут назад, pocopico сказал: Update servers are masked. SSH into DSM and check your /etc/hosts for records. Hosts file is clean, I've checked it first. Quote Link to comment Share on other sites More sharing options...
vikikang Posted July 6, 2022 Share #3971 Posted July 6, 2022 1 hour ago, pocopico said: Update servers are masked. SSH into DSM and check your /etc/hosts for records. 14 minutes ago, drobik said: Hosts file is clean, I've checked it first. Hey, pocopico Thanks for the previous help. Yup, I am also wondering how can I get update server back to function. Checked hosts file, same as drobik's. How dose the update server been blocked though? Thanks for your time. Quote Link to comment Share on other sites More sharing options...
mmkt Posted July 6, 2022 Share #3972 Posted July 6, 2022 Hi, The updateserver links are blocked in the model config.json from redpill load. (redpill-load/config/DS3622xs+/7.1.0-42661/) "rss_server": "http://example.com/null.xml", "rss_server_ssl": "https://example.com/null.xml", "small_info_path": "https://example.com/null", "rss_server_v2": "https://example.com/autoupdate/v2/getList", "security_version_server": "https://example.com/smallupdate", "updateurl": "http://example.com/", "update_server": "http://example.com/", "update_server_ssl": "https//example.com/", "myds_region_api_base_url": "https://example.com" Why it is done , you have to ask pocopico. 1 Quote Link to comment Share on other sites More sharing options...
vikikang Posted July 6, 2022 Share #3973 Posted July 6, 2022 5 hours ago, mmkt said: Hi, The updateserver links are blocked in the model config.json from redpill load. (redpill-load/config/DS3622xs+/7.1.0-42661/) "rss_server": "http://example.com/null.xml", "rss_server_ssl": "https://example.com/null.xml", "small_info_path": "https://example.com/null", "rss_server_v2": "https://example.com/autoupdate/v2/getList", "security_version_server": "https://example.com/smallupdate", "updateurl": "http://example.com/", "update_server": "http://example.com/", "update_server_ssl": "https//example.com/", "myds_region_api_base_url": "https://example.com" Why it is done , you have to ask pocopico. Aha, I see. Thanks man🤝 Quote Link to comment Share on other sites More sharing options...
drobik Posted July 7, 2022 Share #3974 Posted July 7, 2022 @vikikang Thanks. I compared config for 3622 with 918 , remove extra lines (for 918 5 lines, for 3622 9 lines), build new loader and the error is gone. And next question is how we can change this links on working xpenology? Because I have already used postupdate function and I am not sure that I can just rebuild loader and get all is working after. Quote Link to comment Share on other sites More sharing options...
pocopico Posted July 7, 2022 Author Share #3975 Posted July 7, 2022 5 hours ago, drobik said: @vikikang Thanks. I compared config for 3622 with 918 , remove extra lines (for 918 5 lines, for 3622 9 lines), build new loader and the error is gone. And next question is how we can change this links on working xpenology? Because I have already used postupdate function and I am not sure that I can just rebuild loader and get all is working after. updates are blocked cause TTG thought that it should at that point of time. Currently, I think we have a better knowledge of how to handle the updates and either with Jumkey solution or postupdate or arpl we can manage. We never know though what the future might bring so it’s better to always have control over the updates. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.