beefyjoe

hello, I wanted to report that after upgrading ARPL to latest version and also being on latest dsm for ds918+, running baremetal on lenovo y410p laptop with usb 3 4bay mediasonic probox as the drive enclosure. was working fine until I lost power, now I have tried reinstalling, DSM with arpl so many times I am the point of giving up since there doesnt seem to be many people who are having this issue. Previously was able to set to these last known working values during dsm 7.0.1 lkm: dev model: "DS918+" build: "42218" sn: "serialnumber" maxdisks: "24" layout: qwerty keymap: "" zimage-hash: "e3f8367fd662d9f0a93a2fa579e37fc915695324cb0a3a98f0edf68045071f8a" ramdisk-hash: "ea49dd27e810222cbaa1aa643e45883c2c92daa3882e498c47ae6d1e0bd36513" cmdline: netif_num: "1" mac1: 28d24428d8d3 synoinfo: support_disk_compatibility: no support_memory_compatibility: no esataportcfg: "0" support_led_brightness_adjustment: "" support_leds_lp3943: "" internalportcfg: "0xfffff" usbportcfg: "0" buzzeroffen: "0xffff" rss_server: https://raw.githubusercontent.com/fbelavenuto/arpl/main/rss.xml rss_server_ssl: https://raw.githubusercontent.com/fbelavenuto/arpl/main/rss.xml rss_server_v2: https://raw.githubusercontent.com/fbelavenuto/arpl/main/rss.json small_info_path: https://example.com/null security_version_server: https://example.com/smallupdate addons: misc: "" acpid: "" i915: "" lsiutil: "" dbgutils: "" 9p: "" original-mac: macaddress vid: "0x18a5" pid: "0x0250" Since losing power and then updating arpl, I have not been able to restore my Volume 1 Raid 5 volume. I have set this in /etc/ /etc.defaults/ and in the arpl user_config.yml, but everytime I boot into DSM drives show as external and my RAID 5 Volume 1 is not accessible at all. Looking for assistance, I have tried so many things and at this point am looking into other solutions over xpenolgy... its been rough when the system goes down... I only store backups with active backup but its still very time consuming and super annoying when this shiz happens.

These links work for the latest version of DSM on Xpenology using TCRP ARPL 7.1.1 Thank you!

I was able to get around 2fa by creating a new account with synouser and adding them to administrator's group, per this guide, https://global.download.synology.com/download/Document/Software/DeveloperGuide/Firmware/DSM/All/enu/Synology_DiskStation_Administration_CLI_Guide.pdf For others to reference if they get locked out

Ok so I am recovered... but now my 2FA doesnt work at all... for any of my accounts. I am unable to sign in to the web portal to manage the system, but I can still SSH in, I am currently researching how to go about getting around 2FA and get back into the web interface... If anyone has experience with this and is kind enough to donate their knowledge, I would be happy to take your advice.

Hi fbelavenuto, thanks for taking the time to reply. So I did have to reflash the flash drive with the latest ARPL. Before I did that, i copied my user-config.yml to my personal computer. While I was setting up ARPL fresh, I editing the user-config/yml manually in ARPL configuration, and after rebooting, it seems that my DSM is detectable, its showing "Recoverable" as the state in Synology assistant. I am currently going through the Recovery with DSM via the web interface for Synology Asistant/Finds Synology. I hope this works, fingers crossed. (It gave me a warning about my DSM being older than the one on the disks, and said this common after RMA). I am glad i chose the same build that I started with. Also, is DSM 7.1 working on ARPL for DS918+ appololake? Just curious, as I would like to update for security.

Hello, I recently updated from ARPL alpha 4 to arpl 1 beta 6, and now its saying that the kernal could not load and i cant boot into DSM, The ARPL configuration, or anything, i just keep getting stuck because there is no kernal to boot off anymore.... what should I do to fix this? I dont really know what I can do here to fix since I can't do or access anything on the machine now... do I need to reflash the flash drive with latest ARPL? Please help, thanks

Thank you, changing the url for step 1 to include the "version=3" and "format=cookie" fixed the problem where i was getting failed activation. I was then able to use step 2 and 3 url from original solution to activate and verify, no more activation prompt. Thanks!

Howdy, I just found this tool today and thought that it was my saving grace, had Jun's loader setup as DS3617xs on a Lenovo y410p laptop witha mediasonic probox 4 bay the new 2022 version as an external USB enclosure for the drives, since they obviously wont fit in the laptop. This was rock solid. had going for 2 weeks uptime after initial install. Was trying to get DSM 7.1 installed with regular TCRP but ran into the Bad Ports issue, so I found the automated loader since it resolves that for me. I was able to get it setup and working no problems, I switched my build to a DS918+ since it seems a better match for my hardware (i7-4800mq 4core core 8 thread, 8GB RAM, Haswell, which should support apollolake according to sheet) Everything also seemed fine after install, it migrated my RAID 5 Array of 3 14TB drives in the MediaSonic USb enclosure, and I was also able to setup SSD cache as well with 2 internal 120GB SATA SSDs. I was able to get all these listed and identified by the computer by modifying the user config json so that everything was an internal port Internalportcfg: "0xffffffffff" esataportcfg: "0" usbportcfg: "0" This is also what i had to do on the DS3617xs build with jun's loader to get it to work with the usb drive enclosure. The problem happened after I rebooted. The system did not go back to DSM... i had no idea what was going on and thought to open the Synology assistant app. Lo and behlod, there is the DSM 7.1 machine now saying that DSM is not installed, and going to find.synology.com starts the installation process all over again. Looking for some help in getting this fixed... I have tried rebuilding the loader with arcl but it seems that now every DSM release from Synology that I am trying to install is corrupted. Should I update to 7.1.1 ? This seems like a bad idea considering its still only RC and arcl itself is in alpha... I tried looking through the forums and google already but there were only a couple of mentions of this problem with other users and they did not receive answers.