shibby Posted July 25 Share #1276 Posted July 25 (edited) another try with and result so it`s almost correct. Edited July 25 by shibby Quote Link to comment Share on other sites More sharing options...
Trabalhador Anonimo Posted August 10 Share #1277 Posted August 10 On 7/22/2024 at 11:53 AM, Peter Suh said: Can I see the sata_remap option you used? I used yout m-shell menu to auto remap as i´m not a linux friend. 1 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted August 11 Author Share #1278 Posted August 11 (edited) [Notice] The storagepanel addon included in mshell did not work properly, so I completed the fix distribution today. And here's a tip related to the storagepanel addon. root@DS918p:/usr/sbin# /usr/sbin/storagepanel.sh TOWER_5_Bay 1X2 storagepanel set to TOWER_5_Bay 1X2 There are two ways to check the changed appearance after changing the panel size using /usr/sbin/storagepanel.sh in the scheduler or ssh. 1. Reboot DSM. 2. Log out of DSM in your web browser and then log in again. When changing the panel size, the JavaScript file below is modified, /usr/local/packages/@appstore/StorageManager/ui/storage_panel.js In order to reflect this file in real time, the web browser must notice the change. Edited August 11 by Peter Suh 1 Quote Link to comment Share on other sites More sharing options...
kevwiener Posted August 14 Share #1279 Posted August 14 is this a full build or a set of tools to run once you have redpill installed ? Quote Link to comment Share on other sites More sharing options...
smileyworld Posted August 20 Share #1280 Posted August 20 On 6/25/2024 at 10:40 PM, Hackaro1 said: @Peter Suh and all, I ask the community about what is the general consensus about high-speed NIC cards working with TCRP: what are the best 10Gbe NICs both RJ45 and/or SFP? what are the best 25Gbe NICs both RJ45 and/or SFP? and also what are the best SAS controllers that are compatible with TCRP? Thanks! I personally use an Intel X540-T2 and can't complain. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted August 22 Author Share #1281 Posted August 22 On 8/14/2024 at 11:51 AM, kevwiener said: is this a full build or a set of tools to run once you have redpill installed ? There are two full builds using Redpill: TCRP and RR (ARPL FORK), and this MSHELL is a FORK derived from TCRP. It is a tool for full builds, so you can choose whichever you want to use. 1 Quote Link to comment Share on other sites More sharing options...
foxbat Posted August 27 Share #1282 Posted August 27 Hello, Thank you for your work! Any news for 7.2.2-72803 update? Quote Link to comment Share on other sites More sharing options...
ct85msi Posted August 27 Share #1283 Posted August 27 it works, booted 7.2.2 Quote Link to comment Share on other sites More sharing options...
foxbat Posted August 27 Share #1284 Posted August 27 Thank you. What were the steps please? my dsm not booting after update (manual update) Quote Link to comment Share on other sites More sharing options...
foxbat Posted August 27 Share #1285 Posted August 27 After update (1.0.4.2) it's working. Thank you! Quote Link to comment Share on other sites More sharing options...
djvas335 Posted August 27 Share #1286 Posted August 27 Hi Peter, I have updated and rebuilt the loader however I am getting Failed to Install DSM, Failed to install the file, the file is probably corrupt when trying to install latest 1 Quote Link to comment Share on other sites More sharing options...
gericb Posted August 27 Share #1287 Posted August 27 19 minutes ago, djvas335 said: Hi Peter, I have updated and rebuilt the loader however I am getting Failed to Install DSM, Failed to install the file, the file is probably corrupt when trying to install latest Ditto. I posted in the "DSM Updates Reporting". I'm sure the file itself is not corrupted, guessing not enough space on the USB or some other minor glitch gumming up the works. Sadly, now the system is "up", just waiting to be "Migrated" and I'm sure @Peter Suh will vanquish those tiny pesky bugs before you know it.🪳 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted August 28 Author Share #1288 Posted August 28 (edited) 17 hours ago, djvas335 said: Hi Peter, I have updated and rebuilt the loader however I am getting Failed to Install DSM, Failed to install the file, the file is probably corrupt when trying to install latest Sorry for the late notice version 1.0.4.2. This is the official version corresponding to the 7.2.2-72803 revision. However, in the case of bare metal, the errors you reported above have been confirmed on some platforms. The message that appears on the screen is the 56% stop and file corruption message during DSM installation that we have seen so far, but in fact, the internal content seems to be a different pattern than now. I am currently experiencing the same error as rr and am checking what the error code 21 is. https://github.com/RROrg/rr/issues/2607 The platforms that are causing error code 21 on bare metal are as follows. Apollolake (DS918+) Broadwell (DS3617xs) Broadwellnk (DS3622xs+) Denverton (DVA3221) The commonality is that they are all Non-DT-based platforms that do not use Device-Tree. If it is a DT platform, there is no problem with all types of bootloaders (USB, SATA). Edited August 28 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted August 28 Author Share #1289 Posted August 28 17 hours ago, gericb said: Ditto. I posted in the "DSM Updates Reporting". I'm sure the file itself is not corrupted, guessing not enough space on the USB or some other minor glitch gumming up the works. Sadly, now the system is "up", just waiting to be "Migrated" and I'm sure @Peter Suh will vanquish those tiny pesky bugs before you know it.🪳 Quote Link to comment Share on other sites More sharing options...
gericb Posted August 28 Share #1290 Posted August 28 1 hour ago, Peter Suh said: Sorry for the late notice version 1.0.4.2. This is the official version corresponding to the 7.2.2-72803 revision. However, in the case of bare metal, the errors you reported above have been confirmed on some platforms. The message that appears on the screen is the 56% stop and file corruption message during DSM installation that we have seen so far, but in fact, the internal content seems to be a different pattern than now. I am currently experiencing the same error as rr and am checking what the error code 21 is. https://github.com/RROrg/rr/issues/2607 The platforms that are causing error code 21 on bare metal are as follows. Apollolake (DS918+) Broadwell (DS3617xs) Broadwellnk (DS3622xs+) Denverton (DVA3221) The commonality is that they are all Non-DT-based platforms that do not use Device-Tree. If it is a DT platform, there is no problem with all types of bootloaders (USB, SATA). It's interesting...just in case something changed from yesterday to today, I rebuilt the loader again a few minutes ago, and still running into the same error. Oddly, when allowing the migration/upgrade to download the DSM from Synology, it failed around 55/56% if I point to the file already downloaded, it fails around 41/42%. Are there any logs being stored somewhere I can get you to help? I saw you were able to do a "NEW INSTALL" of a 920+ with success. Do you think it might help if I totally re-create the USB from scratch? Not getting any error number, just the "probably corrupted" in both upgrade option instances. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted August 28 Author Share #1291 Posted August 28 (edited) 3 minutes ago, gericb said: It's interesting...just in case something changed from yesterday to today, I rebuilt the loader again a few minutes ago, and still running into the same error. Oddly, when allowing the migration/upgrade to download the DSM from Synology, it failed around 55/56% if I point to the file already downloaded, it fails around 41/42%. Are there any logs being stored somewhere I can get you to help? I saw you were able to do a "NEW INSTALL" of a 920+ with success. Do you think it might help if I totally re-create the USB from scratch? Not getting any error number, just the "probably corrupted" in both upgrade option instances. It's also possible that the /home/tc/redpill-load/ directory that you reference when building the loader is not completely CLONE'd from GitHub. When you see the mshell bootloader build menu, try this command first to clean it up. sudo rm -rf /home/tc/redpill-load/ Edited August 28 by Peter Suh Quote Link to comment Share on other sites More sharing options...
gericb Posted August 28 Share #1292 Posted August 28 34 minutes ago, Peter Suh said: It's also possible that the /home/tc/redpill-load/ directory that you reference when building the loader is not completely CLONE'd from GitHub. When you see the mshell bootloader build menu, try this command first to clean it up. sudo rm -rf /home/tc/redpill-load/ Hehehe, from bad to worse it seems. After executing the above command, and then rebuilding the loader for the new DSM, now getting a new error condition. I've no issue in rebuilding the USB from scratch, but just wanting to be sure I can help out, however possible. 🤠. Regardless of automatically downloading or manual selection, never gets past 0%. Quote Link to comment Share on other sites More sharing options...
djvas335 Posted August 28 Share #1293 Posted August 28 I had this issue it seems that the system partition fills up with failed updates, I had to rebuild the last working version of the loader to be able to boot the system and cleanup the system partition 12 minutes ago, gericb said: Hehehe, from bad to worse it seems. After executing the above command, and then rebuilding the loader for the new DSM, now getting a new error condition. I've no issue in rebuilding the USB from scratch, but just wanting to be sure I can help out, however possible. 🤠. Regardless of automatically downloading or manual selection, never gets past 0%. Quote Link to comment Share on other sites More sharing options...
gericb Posted August 28 Share #1294 Posted August 28 2 hours ago, djvas335 said: I had this issue it seems that the system partition fills up with failed updates, I had to rebuild the last working version of the loader to be able to boot the system and cleanup the system partition So you rebuilt the USB loader, but back on 7.2.1-69057 Update 5, got the system to come up normally, and then cleaned where on the system partition? I'll totally try it! Thank You Quote Link to comment Share on other sites More sharing options...
djvas335 Posted August 28 Share #1295 Posted August 28 Yes, I did just that, my control panel is broken and doesn't start but I can live with that for now, to clean the system partition you need to ssh to your device as root and then mount the system partition by creating an empty folder anywhere and then just do mount /dev/md0 /youreemptyfolder, after that go to that folder folder and delete files inside autoupdate and update folders Quote Link to comment Share on other sites More sharing options...
gericb Posted August 28 Share #1296 Posted August 28 1 hour ago, djvas335 said: Yes, I did just that, my control panel is broken and doesn't start but I can live with that for now, to clean the system partition you need to ssh to your device as root and then mount the system partition by creating an empty folder anywhere and then just do mount /dev/md0 /youreemptyfolder, after that go to that folder folder and delete files inside autoupdate and update folders Curious? Is there no way to mount/access this /dev/md0 location from the Bootloader configuration tools, and delete all the files, like a Terminal? 🤔 Quote Link to comment Share on other sites More sharing options...
djvas335 Posted August 28 Share #1297 Posted August 28 From the bootloader configuration tools I dont think so as md0 is a type of raid so it needs to assemble before mounting 6 minutes ago, gericb said: Curious? Is there no way to mount/access this /dev/md0 location from the Bootloader configuration tools, and delete all the files, like a Terminal? 🤔 Quote Link to comment Share on other sites More sharing options...
gericb Posted August 28 Share #1298 Posted August 28 21 minutes ago, djvas335 said: From the bootloader configuration tools I dont think so as md0 is a type of raid so it needs to assemble before mounting More fun than humans are allowed to have! I'm assuming something still needs to be tweaked by @Peter Suh to get his whole wonderful loader with this 7.2.2-72803 and the "corruption" error, thankfully I'm not the only one. If your control panel isn't working, how did you enable the Telnet/SSH? Seems like the Upgrade/Migration process would automatically purge failed/leftovers /dev/md0 to avoid this other error, at least in the background or prompt if it should. I guess the Synology folks assume such a condition would never exist. Quote Link to comment Share on other sites More sharing options...
djvas335 Posted August 28 Share #1299 Posted August 28 SSH was already enabled before this update so no need to change anything for now. 33 minutes ago, gericb said: More fun than humans are allowed to have! I'm assuming something still needs to be tweaked by @Peter Suh to get his whole wonderful loader with this 7.2.2-72803 and the "corruption" error, thankfully I'm not the only one. If your control panel isn't working, how did you enable the Telnet/SSH? Seems like the Upgrade/Migration process would automatically purge failed/leftovers /dev/md0 to avoid this other error, at least in the background or prompt if it should. I guess the Synology folks assume such a condition would never exist. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted August 29 Author Share #1300 Posted August 29 [NOTICE] DSM 7.2.2 DS918+ Installation Issues Resolved (MSHELL lkm 24.8.29 Distribution Completed) I think I have a good friend. ^^ I gave @wjz304 the key points that I suspected in the junior detailed log /var/log/messages regarding error code 21 that occurred when installing DS918+, and at first he said it didn't seem to be the case, but then he looked into it again at dawn and said that it was the problem and fixed the problem. rr The DS918+ 7.2.2 installation failure and 56% file corruption issue during DSM installation have been resolved. I modified the lkm for mshell exactly as wjz304 modified it and just finished reflecting it. If you rebuild the loader and the prod-24.8.29 LKM version is confirmed on the screen, it will be installed normally. In addition, the issue of not being able to install natively on NON-DT models such as DS3622xs+ / DS3617xs (probably due to checking Synology's incompatible disk firmware database) is still being considered a separate issue. I think it's another issue with this lkm fix, so I'm checking it out. 2 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.