Randomized
-
Posts
10 -
Joined
-
Last visited
Posts posted by Randomized
-
-
15 hours ago, dejimmy said:
Should it be the same sn?
Only if you had AME and want it to keep it working. Otherwise no.
-
14 hours ago, dejimmy said:
I've already tried. But I got this. I believe "recover" will only recover files and that I have to get message "migrate"?
You are good to go, i had to do a 'recover' too.
Just make sure you're using the same model (ds920+), sn and mac, and just press recover.
-
3 hours ago, dejimmy said:
I would like to replace loader arpl 1.1beta2 with arpl ln18. I'm on dsm 7.1.1-42962 update 6. I don't like to reinstall dsm and lose data,sertings and packages. If I create loader to new usb and choose same model and build number will I be able to direct boot to same dsm with same settings and packages as before?
Yes, just make a new disk with aARPL-18n, build loader, boot loader and you are good to go.
I just did it, it had to 'migrate' upon booting 7.2.2 though, everything went fine.
Tbh I was just so angry I had to make a new bootloader again, because I thought the arpl 1.1beta2 was going to manage it well, unfortunately it doesn't work with the new DSM versions.
-
4 minutes ago, fbelavenuto said:
You're not wrong, I did a wrong thing to take advantage of the same release number, that's all.
The most correct would be to have me launched with another number (in this case 8 )
Thanks for the clarification, that's exactly the point I tried to make before somebody told me what I did was not possible..... (SWAGG3R)
And thanks again for your work, because it's a very nice and easy menu added on the loader
-
1 hour ago, fbelavenuto said:
I uploaded and tested the alpha7 48 minutes from now.
That's my point, you have reused the alpha7 version nr with 2 different releases.
I downloaded and installed alpha 7 today on 10:10 AM (CEST).
SHA1 hash of downloaded file:
C:\Users\<omitted>\Downloads>certutil -hashfile arpl-0.4-alpha7.vmdk.zip
SHA1 hash of arpl-0.4-alpha7.vmdk.zip:
f487b25411f6c5cfe335c92461430efc2f52d965
CertUtil: -hashfile command completed successfully.
In other words, watch out because there are 2 releases with the same version nr.
Tell me i'm wrong and I admit it, but I have used alpha 7 already this morning.
I download the 'new' alpha 7 and it has indeed changed, now it has the following SHA1 hash:
f53dbe699e880c40122905fb2375866d934a6d33
-
11 minutes ago, SWAGG3R said:
its alpha7 with the correction of errors in it, because alpha7 was not loaded by anyone
How do you know?
I loaded it 3 hours ago, check
-
25 minutes ago, fbelavenuto said:
Hi guys, there were some bugs in the latest versions.
Please redownload the latest v0.4-alpha7, I recreated it with the bugs fixed.I appreciate your work and I like the loader very much. But....
If I understand correctly, you had alpha7 online, changed the release and it's still alpha7 ? That's wrong, it should be alpha8 then.
-
Is it still required to add a second SATA controller in ESX for data disks besides the system disk? Or can all the disks be on 1 controller in ESX?
My install is on a 100gb vmdk while all the data is on a much larger vmdk on another datastore.
-
- Outcome of the update: SUCCESSFUL
- DSM version prior update: DSM 7.1.0-42661 Update 4
- Loader version and model: Automated Redpill Loader 0.4 alpha7 DS3622xs+
- Using custom extra.lzma: NO
- Installation type: VM on ESXi-7.0U3f- Additional comments: Migrated to arpl 0.4 alpha 7 from tcrp. I didn't even try it with tcrp, arpl works excellent, after migration I added the disks and performed a recover procedure.
AME 3.0 patcher
in Developer Discussion Room
Posted · Edited by Randomized
I can also confirm, worked like a charm.