teknas Posted June 1, 2022 #1 Posted June 1, 2022 Hello, I installed RedPill TinyCore DSM 7.1, everything works well but DSM is not able to log into Synology account. I do not see any error even. Same with 7.0. How can i resolve this? Thanks Quote
phone guy Posted June 1, 2022 #2 Posted June 1, 2022 Try in Chrome. I tried to use firefox with my genuine synology nas and had issues, when you click synology account in control panel in chrome. the page loads correctly. That fixed it for me. [rant] honestly, while I do not like chrome, I prefer firefox, chrome seems to get along better with DSM. Thats been my experience, maybe my firefox is messed up? I dunno [/rant] Quote
teknas Posted June 2, 2022 Author #3 Posted June 2, 2022 I was already trying in Chrome. I tried in Firefox. I created new account on synology, but none are working. Quote
pocopico Posted June 2, 2022 #4 Posted June 2, 2022 On 6/1/2022 at 2:12 PM, teknas said: Hello, I installed RedPill TinyCore DSM 7.1, everything works well but DSM is not able to log into Synology account. I do not see any error even. Same with 7.0. How can i resolve this? Thanks could you please explain a bit more ? can you please post a screenshot of the message ? Quote
teknas Posted June 2, 2022 Author #5 Posted June 2, 2022 Ok, so following is the screenshot. On this DSM Page (Synology Account, Left Panel), i get an option to sign in to synology account. When I click, new form Popups for sign in. I type in my username and password so that this DSM gets registered to Synology account. But it never gets there. Once I enter signing details and hit submit, Poped up form gets closed, and it come back to below shown same page. ========= Quote
flyride Posted June 2, 2022 #6 Posted June 2, 2022 Please keep in mind this FAQ entry when discussing Synology Accounts. You should not be surprised if serial numbers are blacklisted or other methods are used to deny your XPEnology installation access to Synology server services. Quote
teknas Posted June 3, 2022 Author #7 Posted June 3, 2022 i tried with many installations, none of them was able to sign in to synology accunt. Quote
pocopico Posted June 3, 2022 #8 Posted June 3, 2022 6 hours ago, teknas said: i tried with many installations, none of them was able to sign in to synology accunt. You cannot login to syno account unless you have a legit - original - syno box or a valid non banned serial number. May i ask though, why would you like to login to syno account ? Quote
NooL Posted June 3, 2022 #9 Posted June 3, 2022 13 minutes ago, pocopico said: You cannot login to syno account unless you have a legit - original - syno box or a valid non banned serial number. May i ask though, why would you like to login to syno account ? I believe you need to login if you want to use quickconnect and/or synologys own dyndns. But yes, in order for this to work you need a genuine sn/mac i believe. teknas: Check /var/log/messages via ssh when you try to login - that might provide you with some information Quote
phone guy Posted June 4, 2022 #10 Posted June 4, 2022 A synology acct is required for some of the apps to activate too, like advanced media extension, active backup for business and others. There are some work arounds to activate some apps like ABB for example, theres a thread here somewhere. Sorry chrome didnt work, thats how I got mine working. Quote
canserman Posted June 4, 2022 #11 Posted June 4, 2022 how can I change the SN and mac after the installation is successful? Do I have to rebuild the whole thing? Quote
pocopico Posted June 4, 2022 #12 Posted June 4, 2022 (edited) 1 hour ago, canserman said: how can I change the SN and mac after the installation is successful? Do I have to rebuild the whole thing? You can edit the linux line on grub.cfg but I’m not 100% sure that it’s not kept somewhere else inside DSM root after install. EDIT : Well after doing a search on my test system, i've found that the serial number is indeed contained in some files sudo find / -type f -exec grep -iH YOURSERIAL {} \; /volume1/@appstore/MediaServer/etc/initall.xml: <serialNumber>YOURSERIAL</serialNumber> But, you can uninstall and install these package(s) again. To mount the synoboot1 so you can edit the grub.cfg file, on DSM execute : cd /dev/ sudo mount synoboot1 /mnt sudo vi /mnt/boot/grub/grub.cfg EDIT2 : Please bear in mind , though that replacing the serial number might trigger a migration Edited June 4, 2022 by pocopico 1 Quote
Peter Suh Posted June 4, 2022 #13 Posted June 4, 2022 (edited) @pocopico To solve the update 2 recovery loop issue of DS918+ in baremetal. There was a report that the recovery loop was repeated even though postupdate was used, so I tried to trigger the same. If you look at the log below, the /etc.defaults/VERSION file is I thought smallfixnumber was pointing to 2, It is still 0. It seems that the recovery loop continues because of this problem. I obviously used update 2 pat file through manual DSM update. Should this smallfixnumber not change from 0 to 2 as a bug in Synology itself? Inevitably, I plan to edit this /etc.defaults/VERSION file directly. Is my method right? Spoiler DiskStation> cat linuxrc.syno.log START /linuxrc.syno.impl Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module xhci-pci ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "e1000e.ko" for pocopico.e1000e (args: ) Loading kmod #0 "mii.ko" for pocopico.r8169 (args: ) Loading kmod #1 "r8169.ko" for pocopico.r8169 (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000e.sh" for pocopico.e1000e->on_boot Loading module e1000e -> Module e1000e loaded succesfully Ran "check-e1000e.sh" for pocopico.e1000e->on_boot - exit=0 Running "check-r8169.sh" for pocopico.r8169->on_boot Loading module r8169 -> Module r8169 loaded succesfully Ran "check-r8169.sh" for pocopico.r8169->on_boot - exit=0 Running "boot-wait.sh" for redpill-boot-wait->on_boot Still waiting for boot device (waited 1 of 30 seconds) Still waiting for boot device (waited 2 of 30 seconds) Still waiting for boot device (waited 3 of 30 seconds) Still waiting for boot device (waited 4 of 30 seconds) Still waiting for boot device (waited 5 of 30 seconds) Still waiting for boot device (waited 6 of 30 seconds) Still waiting for boot device (waited 7 of 30 seconds) Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=0 Running "install_rd.sh" for redpill-misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for redpill-misc->on_boot - exit=0 :: Executing "on_boot" custom scripts ... [ OK ] Extensions processed Insert net driver(Mindspeed only)... Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 0 Insert synorbd kernel module Insert synofsbd kernel module Insert sha256 kernel module Assemble args: -u 7bc9a5b2:f4ff55c4:3017a5a8:c86610be /dev/sda1 mdadm: /dev/md0 has been started with 1 drive (out of 16). Partition Version=9 /sbin/e2fsck exists, checking /dev/md0... e2fsck 1.44.1 (24-Mar-2018) /sbin/e2fsck -yvf returns 0 Mounting /dev/md0 /tmpRoot ------------upgrade Begin upgrade procedure Failed to found any patch No upgrade file found ============upgrade ------------bootup-smallupdate Failed to AssertFileKeyValueEqual value1: /etc.defaults/VERSION:smallfixnumber -> 0 value2: /tmpRoot/.syno/patch/VERSION:smallfixnumber => 2 Skip bootup smallupdate, because root is not matched to junior ============bootup-smallupdate Failed to AssertFileKeyValueEqual value1: /etc.defaults/VERSION:smallfixnumber -> 0 value2: /tmpRoot/.syno/patch/VERSION:smallfixnumber => 2 Exit on error [7] root not matched with junior... Sat Jun 4 12:52:55 UTC 2022 /dev/md0 /tmpRoot ext4 rw,relatime,prjquota,rootprjquota,data=ordered 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0 DiskStation> Edited June 4, 2022 by Peter Suh Quote
Peter Suh Posted June 4, 2022 #14 Posted June 4, 2022 6 minutes ago, Peter Suh said: @pocopico To solve the update 2 recovery loop issue of DS918+ in baremetal. There was a report that the recovery loop was repeated even though postupdate was used, so I tried to trigger the same. If you look at the log below, the /etc.defaults/VERSION file is I thought smallfixnumber was pointing to 2, It is still 0. It seems that the recovery loop continues because of this problem. I obviously used update 2 pat file through manual DSM update. Should this smallfixnumber not change from 0 to 2 as a bug in Synology itself? Inevitably, I plan to edit this /etc.defaults/VERSION file directly. Is my method right? DS918+ after postupdate (Reveal hidden contents) DiskStation> cat linuxrc.syno.log START /linuxrc.syno.impl Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module xhci-pci ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "e1000e.ko" for pocopico.e1000e (args: ) Loading kmod #0 "mii.ko" for pocopico.r8169 (args: ) Loading kmod #1 "r8169.ko" for pocopico.r8169 (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000e.sh" for pocopico.e1000e->on_boot Loading module e1000e -> Module e1000e loaded succesfully Ran "check-e1000e.sh" for pocopico.e1000e->on_boot - exit=0 Running "check-r8169.sh" for pocopico.r8169->on_boot Loading module r8169 -> Module r8169 loaded succesfully Ran "check-r8169.sh" for pocopico.r8169->on_boot - exit=0 Running "boot-wait.sh" for redpill-boot-wait->on_boot Still waiting for boot device (waited 1 of 30 seconds) Still waiting for boot device (waited 2 of 30 seconds) Still waiting for boot device (waited 3 of 30 seconds) Still waiting for boot device (waited 4 of 30 seconds) Still waiting for boot device (waited 5 of 30 seconds) Still waiting for boot device (waited 6 of 30 seconds) Still waiting for boot device (waited 7 of 30 seconds) Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=0 Running "install_rd.sh" for redpill-misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for redpill-misc->on_boot - exit=0 :: Executing "on_boot" custom scripts ... [ OK ] Extensions processed Insert net driver(Mindspeed only)... Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 0 Insert synorbd kernel module Insert synofsbd kernel module Insert sha256 kernel module Assemble args: -u 7bc9a5b2:f4ff55c4:3017a5a8:c86610be /dev/sda1 mdadm: /dev/md0 has been started with 1 drive (out of 16). Partition Version=9 /sbin/e2fsck exists, checking /dev/md0... e2fsck 1.44.1 (24-Mar-2018) /sbin/e2fsck -yvf returns 0 Mounting /dev/md0 /tmpRoot ------------upgrade Begin upgrade procedure Failed to found any patch No upgrade file found ============upgrade ------------bootup-smallupdate Failed to AssertFileKeyValueEqual value1: /etc.defaults/VERSION:smallfixnumber -> 0 value2: /tmpRoot/.syno/patch/VERSION:smallfixnumber => 2 Skip bootup smallupdate, because root is not matched to junior ============bootup-smallupdate Failed to AssertFileKeyValueEqual value1: /etc.defaults/VERSION:smallfixnumber -> 0 value2: /tmpRoot/.syno/patch/VERSION:smallfixnumber => 2 Exit on error [7] root not matched with junior... Sat Jun 4 12:52:55 UTC 2022 /dev/md0 /tmpRoot ext4 rw,relatime,prjquota,rootprjquota,data=ordered 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0 DiskStation> I modified the smallfixnumber of the VERSION file to 2 and rebooted, but it returns to 0 again. Is there no way? DiskStation> cat VERSION majorversion="7" minorversion="1" major="7" minor="1" micro="0" productversion="7.1" buildphase="GM" buildnumber="42661" smallfixnumber="0" nano="0" base="42661" builddate="2022/04/01" buildtime="17:49:46" unique="synology_apollolake_918+" extractsize=841916 partitionversionlimit=0 Quote
Peter Suh Posted June 4, 2022 #15 Posted June 4, 2022 5 minutes ago, Peter Suh said: I modified the smallfixnumber of the VERSION file to 2 and rebooted, but it returns to 0 again. Is there no way? DiskStation> cat VERSION majorversion="7" minorversion="1" major="7" minor="1" micro="0" productversion="7.1" buildphase="GM" buildnumber="42661" smallfixnumber="0" nano="0" base="42661" builddate="2022/04/01" buildtime="17:49:46" unique="synology_apollolake_918+" extractsize=841916 partitionversionlimit=0 Sorry, I wrote without checking the title of the topic. I thought it was a RedPill Tinycore loader topic, but it was written in the wrong place. Since it is impossible to delete it, I will keep it. Quote
canserman Posted June 5, 2022 #16 Posted June 5, 2022 15 hours ago, pocopico said: You can edit the linux line on grub.cfg but I’m not 100% sure that it’s not kept somewhere else inside DSM root after install. EDIT : Well after doing a search on my test system, i've found that the serial number is indeed contained in some files sudo find / -type f -exec grep -iH YOURSERIAL {} \; /volume1/@appstore/MediaServer/etc/initall.xml: <serialNumber>YOURSERIAL</serialNumber> But, you can uninstall and install these package(s) again. To mount the synoboot1 so you can edit the grub.cfg file, on DSM execute : cd /dev/ sudo mount synoboot1 /mnt sudo vi /mnt/boot/grub/grub.cfg EDIT2 : Please bear in mind , though that replacing the serial number might trigger a migration Thank you for your help. I managed to change the SN and mac address Quote
goodone007 Posted July 31, 2022 #17 Posted July 31, 2022 (edited) @canserman I am having the same problem. Changing SN and Mac after installation fixed your login issue? How do I generate new SN and Mac again for adding this modification? Did you had to create a new account in synology for this or previous one worked? I used a google sign on account. I don't have a synology original mac or sn, will this method work for me? Someone please help. Edited July 31, 2022 by goodone007 1 Quote
songhanpoo Posted February 6, 2024 #18 Posted February 6, 2024 (edited) On 7/31/2022 at 10:48 PM, goodone007 said: @canserman I am having the same problem. Changing SN and Mac after installation fixed your login issue? How do I generate new SN and Mac again for adding this modification? Did you had to create a new account in synology for this or previous one worked? I used a google sign on account. I don't have a synology original mac or sn, will this method work for me? Someone please help. +1 the same my case. Does anyone has solution on that ? Edited February 6, 2024 by songhanpoo Quote
gericb Posted February 11, 2024 #19 Posted February 11, 2024 On 2/6/2024 at 9:45 AM, songhanpoo said: +1 the same my case. Does anyone has solution on that ? Yes me too. I am on a 920+ using TCRP w/Friend. Since I have a real SN/MAC's it's not a worry and in fact has been working perfectly (AME) since first release of DSM 7.1. I was able to login via "External Access" and "Synology Account" @ Control Panel until just recently, thinking about 3 weeks ago, something changed in the loader. It accepts my credentials, spins for a bit like it's going to login, but never successfully does in either sub-section. Prior to this stop working, there were a couple of glitches with the loader and it's reliability, both with the SN and MAC addresses, and though visually it appears to be resolved, there is this last glitch, which has me thinking something might be embedded still in the DSM on the HDD. Quote
GreNoxX Posted February 12, 2024 #20 Posted February 12, 2024 On 6/5/2022 at 5:44 AM, canserman said: I have same problem. Any idea? Quote
gericb Posted February 15, 2024 #21 Posted February 15, 2024 On 2/12/2024 at 11:34 AM, GreNoxX said: I have same problem. Any idea? Nothing at all, this is really outside of my knowledge of this process of booting and installing DSM. I thinking....hoping...that maybe something got corrupted within DSM, that we can fix. I think there might be an option to re-intall DSM, but I have to check on that, hopefully without effecting the other softwares installed and their respective configuration. All I did was re-boot and let it do it's thing, and it was a series of loader failures and glitches, and given nothing changed on my platform and not even a DSM incremental update, I'd venture to say it's all loader/friend generated glitches, and they were numerous. I'm sure the root cause will be determined and we'll get it resolved! 🤠 Quote
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.