Orphée Posted January 2 Share #951 Posted January 2 May I suggest an easier ssh password or backup/restore .ssh/authorized_keys with loader backup ? I did not try recently maybe it is already the case. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 2 Author Share #952 Posted January 2 3 minutes ago, Orphée said: May I suggest an easier ssh password or backup/restore .ssh/authorized_keys with loader backup ? I did not try recently maybe it is already the case. P@ssw0rd is already announced in many guides and texts. Changing this part now will cause confusion to users. If you want to change the settings personally, I can guide you on how to change and fix them within tc. Do you want it this way? Quote Link to comment Share on other sites More sharing options...
Orphée Posted January 2 Share #953 Posted January 2 No don't worry not a big deal, thanks 😘 Quote Link to comment Share on other sites More sharing options...
wjz304 Posted January 2 Share #954 Posted January 2 3 hours ago, Peter Suh said: If so, I will no longer try to access the Tcrp loader build menu from the serial port console. Instead, I will finish implementing the DSM Force re-install function. Regarding the console, the base system tc of tcrp has a desktop, so the console is not turned on by default. The base system of RR does not have a desktop environment, so the default is console. You can search for articles related to opening the console in ubuntu for reference. 2 1 Quote Link to comment Share on other sites More sharing options...
wjz304 Posted January 2 Share #955 Posted January 2 On 1/1/2024 at 8:20 PM, Peter Suh said: To me, it sounds like they are asking for M-SHELL to have features like ARPL.^^ LOL Let's consider adding features. First I have to solve the MAC-SPOOF issue. Questions about mac, DSM will read the mac set in cmdline after startup and set it to eth in sequence. So I blocked this process of DSM in RR 23.9.7. In this way, eth maintains its own mac, and syno's app will read the mac in cmdline for verification. They do not affect each other, because eth has a real mac, so wake-up and other functions are also normal. I think there is no need to modify the Mac. If you need to modify the Mac, the virtual environment can be modified directly on the upper virtual platform. The physical environment is best modified through official software and hardware. 1 Quote Link to comment Share on other sites More sharing options...
Orphée Posted January 2 Share #956 Posted January 2 I did not really remember, so I did not want to say something false, but I just tested again. And yes, console port access works too even in loader configuration with RR : Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 3 Author Share #957 Posted January 3 15 hours ago, Orphée said: I did not really remember, so I did not want to say something false, but I just tested again. And yes, console port access works too even in loader configuration with RR : That's strange. I also tested it with the same RR v23.11.10 USB stick. Is the situation different between baremetal and VM? I will try it again. Quote Link to comment Share on other sites More sharing options...
Biocef Posted January 3 Share #958 Posted January 3 Hi, I still have the mac address issue 😕 I tried to rebuild the loader, I also made a new usb key with the latest release but DSM still use the real mac. Is there anything else to do? Thanks for your help ! Quote Link to comment Share on other sites More sharing options...
Orphée Posted January 3 Share #959 Posted January 3 (edited) 46 minutes ago, Biocef said: Hi, I still have the mac address issue 😕 I tried to rebuild the loader, I also made a new usb key with the latest release but DSM still use the real mac. Is there anything else to do? Thanks for your help ! On 1/2/2024 at 5:11 AM, Peter Suh said: [NOTICE] I found out what was causing the SAN MANAGER package repair. It has been confirmed that mac-spoof addon has a direct effect. Currently, the mac-spoof addon has been removed so that it cannot be used. Maybe this is related. Edited January 3 by Orphée 1 Quote Link to comment Share on other sites More sharing options...
Tibag Posted January 10 Share #960 Posted January 10 Hi @Peter Suh I've been trying your build for the first time, using ESXI, with the latest version (v1.0.1.0.m-shell) and when building ds3622xsp_64570 (or later) I get: Quote [#] Downloading remote file https://raw.githubusercontent.com/PeterSuh-Q3/tcrp-modules/master/ddsml/releases/modules.alias.3.json.tgz to /home/tc/redpill-load/custom/extensions/ddsml/broadwellnk_44302/modules.alias.3.json.tgz [#] Verifying /home/tc/redpill-load/custom/extensions/ddsml/broadwellnk_44302/modules.alias.3.json.tgz file... [ERR] [!] Checksum mismatch - expected c70ada1247849d67bbb4face71e456c074f73511c0c3bae09ee1f479ffbeafa4 but computed ed263ba26e53869597b682a9fa9703a26b872e40e32658a8aae0d33e9772f389 *** Process will exit *** [!] Failed to update all extensions for ds3622xsp_64570 platform - see errors above *** Process will exit *** I couldn't find someone else with the same issue... any idea? 1 Quote Link to comment Share on other sites More sharing options...
Trabalhador Anonimo Posted January 10 Share #961 Posted January 10 1 hour ago, Tibag said: Hi @Peter Suh I've been trying your build for the first time, using ESXI, with the latest version (v1.0.1.0.m-shell) and when building ds3622xsp_64570 (or later) I get: I couldn't find someone else with the same issue... any idea? I´m having the same problem. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 10 Author Share #962 Posted January 10 1 hour ago, Tibag said: Hi @Peter Suh I've been trying your build for the first time, using ESXI, with the latest version (v1.0.1.0.m-shell) and when building ds3622xsp_64570 (or later) I get: I couldn't find someone else with the same issue... any idea? Do not use the build command directly. The menu method below corresponds to the above error. Please use the menu. ./menu.sh Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 10 Author Share #963 Posted January 10 6 minutes ago, Trabalhador Anonimo said: I´m having the same problem. Do not use the build command directly. The menu method below corresponds to the above error. Please use the menu. ./menu.sh Quote Link to comment Share on other sites More sharing options...
Tibag Posted January 10 Share #964 Posted January 10 (edited) 1 hour ago, Peter Suh said: Do not use the build command directly. The menu method below corresponds to the above error. Please use the menu. ./menu.sh Thanks for helping! The error is from the menu: I suspect this may be related to your latest commit @Peter Suh? https://github.com/PeterSuh-Q3/tinycore-redpill/commit/708116888de6d9bb08b5b2fc1850c22fbba2011a I can see the file was changed so the md5 must have too. I am just not sure what is used to compare the md5s. Edit: nevermind, the issus is with the gz file which didn't change in 2 years... Edited January 10 by Tibag 1 Quote Link to comment Share on other sites More sharing options...
Tibag Posted January 10 Share #965 Posted January 10 (edited) 3 hours ago, Tibag said: Thanks for helping! The error is from the menu: I suspect this may be related to your latest commit @Peter Suh? https://github.com/PeterSuh-Q3/tinycore-redpill/commit/708116888de6d9bb08b5b2fc1850c22fbba2011a I can see the file was changed so the md5 must have too. I am just not sure what is used to compare the md5s. Edit: nevermind, the issus is with the gz file which didn't change in 2 years... Actually there was a commit after which changed the gz file - I suspect this is our culprit! https://github.com/PeterSuh-Q3/tinycore-redpill/commit/a97eb8527c416dfd17cb7f788f5245936ae03e41 @Peter Suh I created a PR for your repo: https://github.com/PeterSuh-Q3/tcrp-modules/pull/1 Edited January 10 by Tibag 1 Quote Link to comment Share on other sites More sharing options...
waspsoton Posted January 10 Share #966 Posted January 10 i am getting the same problem, thought it was just me Quote Link to comment Share on other sites More sharing options...
Trabalhador Anonimo Posted January 10 Share #967 Posted January 10 (edited) I used a second terminal screen, type ./menu.sh, but get the same error. Edited January 10 by Trabalhador Anonimo Quote Link to comment Share on other sites More sharing options...
Tibag Posted January 10 Share #968 Posted January 10 So I forked the repo and managed to build - the above PR will fix it. So I am now on my next challenge. After the build it starts and suggests to migrate my disks. I upload my pat and during the process it fails with a corruption message. I check my logs and see: Quote Detected data partition on sdag. Must not be fresh installation. ForceNewestLayout: Skipped Mounting /dev/md0 /tmpRoot ------------upgrade Begin upgrade procedure Failed to found any patch No upgrade file found End upgrade procedure ============upgrade ------------bootup-smallupdate Failed to AssertFileKeyValueEqual value1: /etc.defaults/VERSION:buildnumber -> 69057 value2: /tmpRoot/etc.defaults/VERSION:buildnumber => 64570 Skip bootup smallupdate, because root is not matched to junior ============bootup-smallupdate Failed to AssertFileKeyValueEqual value1: /etc.defaults/VERSION:buildnumber -> 69057 value2: /tmpRoot/etc.defaults/VERSION:buildnumber => 64570 Exit on error [7] root not matched with junior... Wed Jan 10 21:24:03 UTC 2024 /dev/md0 /tmpRoot ext4 rw,noatime,data=ordered 0 0 none /sys/kernel/debug debugfs rw,relatime 0 There is a few posts about that but none makes sense. Any idea? Quote Link to comment Share on other sites More sharing options...
Trabalhador Anonimo Posted January 10 Share #969 Posted January 10 35 minutes ago, Tibag said: So I forked the repo and managed to build - the above PR will fix it. So I am now on my next challenge. After the build it starts and suggests to migrate my disks. I upload my pat and during the process it fails with a corruption message. I check my logs and see: There is a few posts about that but none makes sense. Any idea? I´m not linux expert. How can I forked? Quote Link to comment Share on other sites More sharing options...
Tibag Posted January 10 Share #970 Posted January 10 8 minutes ago, Trabalhador Anonimo said: I´m not linux expert. How can I forked? Pretty sure Peter will fix it once he is back online - I wouldn't bother if you can wait. Once the repo is forked you need to manually fudge the various scripts and it's a PITA. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 11 Author Share #971 Posted January 11 I'm sorry. I found the cause of the error and took action. Please try again. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 11 Author Share #972 Posted January 11 8 hours ago, Tibag said: Actually there was a commit after which changed the gz file - I suspect this is our culprit! https://github.com/PeterSuh-Q3/tinycore-redpill/commit/a97eb8527c416dfd17cb7f788f5245936ae03e41 @Peter Suh I created a PR for your repo: https://github.com/PeterSuh-Q3/tcrp-modules/pull/1 I was mistaken. A tgz file should have been used here, not a gz file. Only the sha256 content should not be changed. The tgz file must have been recompressed and uploaded with new content. The content has already been taken action. Please withdraw your Pull Request. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted January 11 Author Share #973 Posted January 11 (edited) 2 hours ago, Tibag said: So I forked the repo and managed to build - the above PR will fix it. So I am now on my next challenge. After the build it starts and suggests to migrate my disks. I upload my pat and during the process it fails with a corruption message. I check my logs and see: There is a few posts about that but none makes sense. Any idea? Are you by any chance building a loader on a VM like Proxmox? The Pat file corruption message is directly related to the failure to mount three partitions on the loader disk. This occurs especially frequently in SATA mode used by VMs. If it is Proxmox, there is also a way to convert it to USB mode instead of SATA mode. Please tell me exactly what your situation is. Edited January 11 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Tibag Posted January 11 Share #974 Posted January 11 6 hours ago, Peter Suh said: I was mistaken. A tgz file should have been used here, not a gz file. Only the sha256 content should not be changed. The tgz file must have been recompressed and uploaded with new content. The content has already been taken action. Please withdraw your Pull Request. Thanks, I closed the PR. 6 hours ago, Peter Suh said: Are you by any chance building a loader on a VM like Proxmox? The Pat file corruption message is directly related to the failure to mount three partitions on the loader disk. This occurs especially frequently in SATA mode used by VMs. If it is Proxmox, there is also a way to convert it to USB mode instead of SATA mode. Please tell me exactly what your situation is. Yeah I am on ESXI using SATA controller... I can't really move to Proxmox as I have various other VMs running on my ESXI. Do you know any workaround? Quote Link to comment Share on other sites More sharing options...
waspsoton Posted January 11 Share #975 Posted January 11 8 hours ago, Peter Suh said: I'm sorry. I found the cause of the error and took action. Please try again. thank u, its now running again. 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.