pocopico Posted June 7, 2023 Author Share #651 Posted June 7, 2023 (edited) 10 minutes ago, RedCat said: I did the usb loader. Now not restarted the VM, but the result is same: System boot, I see Login screen. Enter Username and passwd. "Booting up the system. Please login later!" I cant login. I waited 1 hour, but nothing changed. Please disregard my previous message, i'm in middble of something else and i didnt pay enough attention. Your system is always busy state, starting up, Thats something new, I dont know how to solve this. Something is holding the system from starting. Are your sataportmap and diskidxmap the same as before ? How are they set ? Edited June 7, 2023 by pocopico 1 Quote Link to comment Share on other sites More sharing options...
RedCat Posted June 7, 2023 Share #652 Posted June 7, 2023 (edited) 15 minutes ago, pocopico said: If you have a backup you can force reinstall of DSM. Also there is an option to block login from specific systems if you fail to login many times. Can you check from a different IP ? If you login, check that by clicking Allow/Block List you dont have anything under block list I know this IP block system, If there are too many login attemps. then it says too many login attempts, IP blocked. Here is another problem. Here it say: "Booting up the system. Please login later!" I cant login, I cant access the dsm.I tried another IP too. Same error. How can I reinstall the DSM? Edited June 7, 2023 by RedCat Quote Link to comment Share on other sites More sharing options...
nemesis122 Posted June 7, 2023 Share #653 Posted June 7, 2023 the login is admin pw: blank (nothing) 5 minutes ago, RedCat said: I know this IP block system, If there are too many login attemps. then it says too many login attempts, IP blocked. Here is another problem. Here it say: "Booting up the system. Please login later!" I cant login, I cant access the dsm.I tried another IP too. Same error. How can I reinstall the DSM? Quote Link to comment Share on other sites More sharing options...
RedCat Posted June 7, 2023 Share #654 Posted June 7, 2023 13 minutes ago, nemesis122 said: the login is admin pw: blank (nothing) Thx, I tried it, nothing changes. "Booting up the system. Please login later!" Quote Link to comment Share on other sites More sharing options...
pocopico Posted June 7, 2023 Author Share #655 Posted June 7, 2023 36 minutes ago, pocopico said: Are your sataportmap and diskidxmap the same as before ? How are they set ? Can you please specify the above ? Quote Link to comment Share on other sites More sharing options...
RedCat Posted June 7, 2023 Share #656 Posted June 7, 2023 (edited) 39 minutes ago, pocopico said: Please disregard my previous message, i'm in middble of something else and i didnt pay enough attention. Your system is always busy state, starting up, Thats something new, I dont know how to solve this. Something is holding the system from starting. Are your sataportmap and diskidxmap the same as before ? How are they set ? I dont remember the old 7.1 diskidxmap and sataport values. The CLI satamap now command gives back SataPortMap=1 and DiskIdxMap=10. The web version detect 0 and 8. I tried both, same result: "Booting up the system. Please login later!" Edited June 7, 2023 by RedCat Quote Link to comment Share on other sites More sharing options...
RedCat Posted June 7, 2023 Share #657 Posted June 7, 2023 1 minute ago, pocopico said: Can you please specify the above ? Sorry, I am slow See it above 1 Quote Link to comment Share on other sites More sharing options...
pocopico Posted June 7, 2023 Author Share #658 Posted June 7, 2023 8 minutes ago, RedCat said: I dont remember the old 7.1 diskidxmap and sataport values. The CLI satamap now command gives back SataPortMap=1 and DiskIdxMap=10. The web version detect 0 and 8. I tried both, same result: "Booting up the system. Please login later!" So the HTML Builder returned 0 ? Thats a value that DSM will not accept and in the past caused a KP. Thats good to know also. So since you've tried with the exact hardware configuration, Can you please change to SataPortMap=888 and DiskIdxMap=00 Quote Link to comment Share on other sites More sharing options...
RedCat Posted June 7, 2023 Share #659 Posted June 7, 2023 13 minutes ago, pocopico said: So the HTML Builder returned 0 ? Thats a value that DSM will not accept and in the past caused a KP. Thats good to know also. So since you've tried with the exact hardware configuration, Can you please change to SataPortMap=888 and DiskIdxMap=00 I did it, and recrated the loader. DSM boot, but nothing changed. Booting up the system. Please login later! Quote Link to comment Share on other sites More sharing options...
RedCat Posted June 7, 2023 Share #660 Posted June 7, 2023 What can I do now? How do I access my documents? DSM is dead. Even samba doesn't work. How can I downgrade the system? Or reinstall? If I change the serial number, will it reinstall the dsm? Quote Link to comment Share on other sites More sharing options...
pocopico Posted June 7, 2023 Author Share #661 Posted June 7, 2023 3 minutes ago, RedCat said: What can I do now? How do I access my documents? DSM is dead. Even samba doesn't work. How can I downgrade the system? Or reinstall? If I change the serial number, will it reinstall the dsm? No you can stop at count down of TCRP Friend by pressing <ctrl-c> Then you can type bfs and hit enter, this wil force DSM to boot in junior mode and you can re-install keeping configuration. Quote Link to comment Share on other sites More sharing options...
RedCat Posted June 7, 2023 Share #662 Posted June 7, 2023 55 minutes ago, pocopico said: No you can stop at count down of TCRP Friend by pressing <ctrl-c> Then you can type bfs and hit enter, this wil force DSM to boot in junior mode and you can re-install keeping configuration. Thank you! I reinstalled the dsm, now all work perfectly. You asked me, set SataPortMap=888 and DiskIdxMap=00. It is good for me? Or what is the correct numbers? 1 Quote Link to comment Share on other sites More sharing options...
pocopico Posted June 7, 2023 Author Share #663 Posted June 7, 2023 2 hours ago, RedCat said: Thank you! I reinstalled the dsm, now all work perfectly. You asked me, set SataPortMap=888 and DiskIdxMap=00. It is good for me? Or what is the correct numbers? Its a try and error situation. See what works for your case. Quote Link to comment Share on other sites More sharing options...
Blubster Posted June 8, 2023 Share #664 Posted June 8, 2023 Well it appears DSM 7.2.64561 was pulled be Synology, they just released today build 64570. Hopefully links to 64561 pat files are not broken... Quote Link to comment Share on other sites More sharing options...
Thesevenn Posted June 9, 2023 Share #665 Posted June 9, 2023 pocopico updated the configs to 64570, so no more broken links Quote Link to comment Share on other sites More sharing options...
Batmoine Posted June 9, 2023 Share #666 Posted June 9, 2023 (edited) Il y a 1 heure, Thesevenn a dit : pocopico updated the configs to 64570, so no more broken links Yes, but all the extensions point to the previous version of DSM, so the update can't take place until the repo is up to date 😔 Edited June 9, 2023 by Batmoine Quote Link to comment Share on other sites More sharing options...
renegadeBE Posted June 18, 2023 Share #667 Posted June 18, 2023 (edited) Hi @pocopico I come report a issue with TCRP : The update 6 for ds3622xs 7.1.1-42962 break the loader (generated with the last TCRP). It causes an infinite recovery cycle... The command postupdate don't résolve this issue. When in doubt, I reinstalled the server, to recover it, I had to perform a clean installation (keep just data, no configs)! Otherwise, the loop continued. Once on version 7.1.1-42962-1, reconfigure all the parameters. I applied update 6 again, I switched to TCRP and launched the postupdate procedure, on restart, same problem. Return to TCRP to apply the procedure, but on restart, the server is still in the recovery cycle... Any ideas for solutions? THX EDIT : My server uses an AMD platform, TCRP FRIEND does not work... Edited June 18, 2023 by renegadeBE Quote Link to comment Share on other sites More sharing options...
renegadeBE Posted June 18, 2023 Share #668 Posted June 18, 2023 Just tried again, reinstalling DS3622 server, DSM 7.1.1 u1. Configuration of basic parameters and installation of update 5 (to change... it worked before). On reboot, switch to TCRP to apply postupdate. The update is detected, I confirm and reboot again on DSM. Same issue, server in recovery loop. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted June 18, 2023 Share #669 Posted June 18, 2023 (edited) 1 hour ago, renegadeBE said: Just tried again, reinstalling DS3622 server, DSM 7.1.1 u1. Configuration of basic parameters and installation of update 5 (to change... it worked before). On reboot, switch to TCRP to apply postupdate. The update is detected, I confirm and reboot again on DSM. Same issue, server in recovery loop. There are 7 models that do not require PostUpdate. From the beginning, the full version of the DSM Pat file is compatible with Update 6. Models with a capacity of 300MB or more are applicable. https://archive.synology.com/download/Os/DSM/7.1.1-42962-6 Redpill corresponds to the following 7 models. DS723+ DS923+ DS1823xs+ RS3621xs+ RS4021xs+ RS3618xs SA6400 Although it is a Rackstation model among these models, the model most similar to DS3622xs+ is It is RS3621xs+. It has 12 bays and is the same Broadwell nk. We suggest temporarily migrating to this model until the issue with U6 is resolved in PostUpdate. M SHELL is currently working on a full version Update 6 and will be finished soon. Edited June 18, 2023 by Peter Suh 1 Quote Link to comment Share on other sites More sharing options...
MrHappy Posted June 18, 2023 Share #670 Posted June 18, 2023 (edited) I used 0.9.4.9b today to upgrade my 3622XS+ vm to 7.2. The vm runs on Proxmox and worked fine on 7.1U5. The boot disk is on sata, the storage-disks are on virtio scsi. After booting the last few lines showed: [ 94.678707] scsi 1:0:0:1: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5 [ 94.679627] sdh: sdh1 sdh2 sdh3 [ 94.680282] sd 1:0:0:2: [sdh] Attached SCSI disk [ 94.682593] want_idx 1 index 8. delay and reget [ 95.684099] want_idx 1 index 8 ..... [ 108.704116] want_idx 1 index 8. delay and reget [ 109.705114] want_idx 1 index 8 [ 109.706096] sd 1:0:0:1: Attached scsi generic sg8 type 0 [ 109.706247] sd 1:0:0:1: [sdi] 67108864 512-byte logical blocks: (34.4 GB/32.0 GiB) [ 109.706624] sd 1:0:0:1: [sdi] Write Protect is off [ 109.706626] sd 1:0:0:1: [sdi] Mode Sense: 63 00 00 08 [ 109.706716] sd 1:0:0:1: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 109.715812] sdi: sdi1 sdi2 sdi3 [ 109.717431] sd 1:0:0:1: [sdi] Attached SCSI disk [ 109.749675] udevd[4288]: failed to send result of seq 3047 to main daemon: Connection refused After a while the next message appears [ 140.441970] ext2: synoboot2 mounted, process=mantool [ 140.444151] vfat: synoboot2 mounted, process=mantool [ 140.452989] FAT-fs (synoboot2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 140.456348] synoboot2 unmounted, process=mantool This makes me think the OS sees the disks, but Syno says 'No drives detected in DS3622XS+'. Is this because the RedPill gui does not let me add virtio-drivers or is there something else the matter? Edited June 18, 2023 by MrHappy Quote Link to comment Share on other sites More sharing options...
pLastUn Posted June 18, 2023 Share #671 Posted June 18, 2023 (edited) Greetings, there is a problem with the latest version of tinycore-redpill.v0.9.4.9. Supermicro X7SPA-HF-D525 board, Intel Atom D525, 2x Intel 82574L Gigabit LAN, 6x SATA (3.0Gbps) Ports. The boot loader is built and written to flash drive well. When installing the DSM version: ds3617xs-7.1.0-42661 ds3617xs-7.1.1-42962 ds3617xs-7.2.0-64570 DSM installation error at 58% - file is corrupted. Tried both original PAT file and the one made by TC. During installation: ds3615xs-7.1.0-42661 ds3615xs-7.1.1-42962 No network when booting! Until 2 weeks ago, ds3615xs-7.1.1-42962 was installing fine (tinycore-redpill.v0.9.4.6) What needs to be done? Advice or fix TCRP! Thanks! Edited June 18, 2023 by pLastUn Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted June 19, 2023 Share #672 Posted June 19, 2023 5 hours ago, pLastUn said: Greetings, there is a problem with the latest version of tinycore-redpill.v0.9.4.9. Supermicro X7SPA-HF-D525 board, Intel Atom D525, 2x Intel 82574L Gigabit LAN, 6x SATA (3.0Gbps) Ports. The boot loader is built and written to flash drive well. When installing the DSM version: ds3617xs-7.1.0-42661 ds3617xs-7.1.1-42962 ds3617xs-7.2.0-64570 DSM installation error at 58% - file is corrupted. Tried both original PAT file and the one made by TC. During installation: ds3615xs-7.1.0-42661 ds3615xs-7.1.1-42962 No network when booting! Until 2 weeks ago, ds3615xs-7.1.1-42962 was installing fine (tinycore-redpill.v0.9.4.6) What needs to be done? Advice or fix TCRP! Thanks! Did you use WEBUI when building the loader? WEBUI is known to operate as withfriend by default. If you built the loader with a command using the console, try converting it to FRIEND by adding more withfriends as well. FRIEND is much less likely to encounter a 58% file corruption message than the conventional method without withfriend. Quote Link to comment Share on other sites More sharing options...
pocopico Posted June 19, 2023 Author Share #673 Posted June 19, 2023 SCSI/SAS issue has been resolved by adjucting the disks addon. You can rebuild and try again. Quote Link to comment Share on other sites More sharing options...
MrHappy Posted June 19, 2023 Share #674 Posted June 19, 2023 6 hours ago, pocopico said: SCSI/SAS issue has been resolved by adjucting the disks addon. You can rebuild and try again. Thank you for your great work. Working fine again! 1 Quote Link to comment Share on other sites More sharing options...
renegadeBE Posted June 19, 2023 Share #675 Posted June 19, 2023 On 6/18/2023 at 3:34 PM, Peter Suh said: There are 7 models that do not require PostUpdate. From the beginning, the full version of the DSM Pat file is compatible with Update 6. Models with a capacity of 300MB or more are applicable. https://archive.synology.com/download/Os/DSM/7.1.1-42962-6 Redpill corresponds to the following 7 models. DS723+ DS923+ DS1823xs+ RS3621xs+ RS4021xs+ RS3618xs SA6400 Although it is a Rackstation model among these models, the model most similar to DS3622xs+ is It is RS3621xs+. It has 12 bays and is the same Broadwell nk. We suggest temporarily migrating to this model until the issue with U6 is resolved in PostUpdate. M SHELL is currently working on a full version Update 6 and will be finished soon. Thx for your reply 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.