Itay1778
-
Posts
13 -
Joined
-
Last visited
Posts posted by Itay1778
-
-
On 9/9/2022 at 1:28 PM, pocopico said:
you should now be able to also create a new loader for 42962 as well.
How? I don't see an update...
And is it possible to update from DSM 7 7.1.0-42661 U1 to 42962? What is the process?
DS918+
and DS3622xs+-
1
-
-
On 9/6/2022 at 10:15 PM, apriliars3 said:
./rploader.sh update now
./rploader.sh fullupgrade now./rploader.sh serialgen DS918+
./rploader.sh identifyusb now #only baremetal
./rploader.sh satamap now #optional./rploader.sh build apollolake-7.0.1-42218-JUN
sudo reboot
Fresh install to DSM 7.1.0-42661 and then update to DSM 7.1.1-42962. Works perfectly.
I tried to do it exactly according to what you wrote here, and it doesn't work for me. DSM failed to install.
I also re-burned the USB device and formatted the drives.
Just to be clear, I'm trying to upload: DSM_DS918+_42661.pat file
to apollolake-7.0.1-42218-JUN
Do you have any idea what to do?
Because if it doesn't work I'll just wait for TCRP to update...
-
15 minutes ago, flyride said:
We don't actually know the answer to this question. The issue is some sort of instruction requirement compiled into the Linux kernel for this (and several other) platforms. If your CPU doesn't work, it crashes very early in the boot process. This has been the case since DSM 6.1 and DS916+ and generally correlates to Intel QuickSync support starting with the Haswell microarchitecture. There is a strong crowdsourced correlation to the presence/absence of the FMA3 architecture and this has been a good rule of thumb, but it could be something more obscure like SSSE3.
To confuse the issue, it appears that some Intel chips support some FMA3 instructions even when not explicitly branded or flagged to do so. And it is possible for a new build or DSM version to remove whatever compile-time requirement is in play. For example, it seems that DS920+ (which is the refresh of the DS918+) runs on any x86-64 platform, even while supporting QuickSync.
Occasionally there are reports such as yours that say things are working on X or Y CPU. Great! Post your results on the upgrade threads. Better yet, figure out what is really going on and advise!
Oh ok, thanks for the explanation.
-
Why does the DS918+ need FMA3 support? The processor that comes with it does not support it...
INTEL Celeron J3455
Does not support FMA3.
And I was also able to install it on a Pentium G3220 which also doesn't support it. -
1 hour ago, apriliars3 said:
./rploader.sh update now
./rploader.sh fullupgrade now./rploader.sh serialgen DS918+
./rploader.sh identifyusb now #only baremetal
./rploader.sh satamap now #optional./rploader.sh build apollolake-7.0.1-42218-JUN
sudo reboot
Fresh install to DSM 7.1.0-42661 and then update to DSM 7.1.1-42962. Works perfectly.
I am testing with Redpill with DSM 7.1.1-42962 and recovery loop, not works postupdate. @pocopico any solution with recovery loop?
./rploader postupdate apollolake-7.1.0-42661 #not works with DSM 7.1.1-42962
I didn't quite understand.
Do you have to do the same as the initial installation process and then upload the updated file (7.1.1-42962)?
If that's the way I think I'll have a problem updating... because for me during the installation I had to set "satamap=2" and after the installation of DSM finished installing then I changed it to "satamap=6" otherwise I would have errors. And if I do it again I will have problems in the raid and I will lose data.Can I just upload the file (of the 7.1.1-42962) to "Manual DSM Update" in the DSM settings? it won't work?
-
Hi, I noticed that the update to DSM 7.1.1-42962 is out.
How do you update it?
Currently running DSM 7.1-42661 Update 1.
Of course without losing data and without resetting the settings. Is it possible to update directly? what is the process?I have a DSM built on the DS918+ models
And another one of DS3622xs+ -
13 hours ago, pocopico said:
They will accept the disks but you will need to reinstall. The application, application data and volume data will remain intact.
Thanks for the answer, so when I rebuild the loader it will ask me for the pat file of the model I switched to and will not format the disks?
-
Hi, so after I successfully installed DSM 7.1 with help from here, I have some questions.
1. If I want to change the model from 1918 to 3622 is this possible to do that without installing DSM from scratch? Can I just re-build the loader and change the serial number and Mac address? Or do I have to format and install everything and set everything up from scratch?
2. Is it possible to disconnect the disk-on-key after the DSM is booted?
3. Is it reliable? - Yes I know no one here can guarantee me that it will work 100 % and I will not lose data. But I'm sure there are many here who have been running this way for months and using DSM this way every day, so is it reliable enough to use it? -
33 minutes ago, facelessone said:
Exactly. If you manage to install it with one drive, when you build loader again again with sataportmap 4 it will still boot from 1st drive into DSM, but you will see other drives. Make sure the other data in user_config.json stay the same.
That's how I got it to work, hope you will to
Thank you!! I succeeded! Everything works, all disks are recognized.
I need to set sataportmap to 6 because this motherboard defines disks 0,1,4,5 so in DSM it shows me Disk 1, DIsk 2, Disk 5, Disk 6
But it doesn't matter to me because I still know who is what. -
1 minute ago, facelessone said:
Try This. Build a loader with SataPortMap 1, install with only one hdd on port0, When you install build loader again with sataportmap 4 and connect other drives.
Ok, I'll try but just to be sure what to do:
I do the build loader with SataPortMap 1 if it works then continue installing DSM with only one drive then after installation and everything works with one drive then to try to build again with SataPortMap 4? And if I build again then it will not ask me to install DSM again? -
Hi, everyone.
I am trying to install DSM 7.1 on bare metal with the help of this guide:
But I seem to be stuck on this screen:
Don't really know what to do... I tried to figure out how to maybe fix it through the previous pages here, but without success
Motherboard model: asrock h91m-plus
The SATA controller supports up to 6 ports but the board has 4 ports and all ports are connected with HDDs
What to do?
And another question when I make a change in user_config.json I need to do build again to save it? -
Hey, I'm new here until a day ago I didn't know there was such a thing.
I'm trying to install on Proxmox 6.1-8
DS3615sx
Loader v1.03b
I was finally able to move on to something only when converting the synoboot.img into qcow2. otherwise it didn't work
But now that I'm trying to install the pat file it says "Failed to format the disk (53)"
The VM configbios: seabios cores: 2 cpu: kvm64 machine: q35 memory: 2048 name: synologytest net0: e1000e=9E:55:42:1F:CB:60,bridge=vmbr0,firewall=1 numa: 0 ostype: l26 sata0: NFS1:201/synoboot.qcow2,size=50M smbios1: uuid=9d6a9bd1-5af2-40e5-b988-XXXXXXXXX sockets: 1 virtio0: G500:vm-201-disk-0,size=64G virtio1: G500:vm-201-disk-1,size=64G vmgenid: 79acaa43-5f89-4c2f-b06e-XXXXXXXXXWhat to do?
UPDATE: I managed to install !!
I had to add another disk and it installed it!
TinyCore RedPill Loader (TCRP)
in Loaders
Posted
Is there an ETA when v9 is out? Or the possibility to update properly from 7.1-42661 Update 4 to 7.1.1-42962 update 1?
On DS1918+ and DS3622xs+