synoxpe
-
Posts
105 -
Joined
-
Last visited
Posts posted by synoxpe
-
-
3 hours ago, renxpe said:
Hi Synoxpe, I am using newer hardware mainly the cpu is 10thgen i7 - my understanding is 3617 can fully utilize all the cores with hyperthreading - is this the case for DS918+ as well? Also, i'm using 10 drives 6 spinning and 4 ssd's - the 918 has 4 drive limit - can this be increased through configuration file?
appreciate the suggestion!
Ren
Yes! All loaders are set to 16 drives by default so that shouldn’t be a problem.
I too have a i7 10th gen and the 918+ is a quadcore device (just like the 3617).
-
9 hours ago, synoxpe said:
Never mind! I went the NFS route. Seems like the network doesn’t go through the full stack between the Proxmox host and the DSM VM as confirmed by iperf (I’m getting ~350MB/s network throughout which is way more than the reading speed of the USB disk)
-
20 hours ago, renxpe said:
@gorski I've spent the last day or so trying to get a baremetal (even tried a vm in proxmox) install for 3617xs using tinycore. It comes up in syno assistant, you can push the pat file, and it appears to complete the install and reboot, however when it comes back up, you go through the same install loop ( syno assistant indicates status as not installed) another member here advised it might be updating during the initial install, to latest version of 7.0.1 which appears to break the install. I tried blocking the machine from going out to the network, at the router level a few times, and then by disconnecting the ethernet cable, just after it begins the pat file install, but no joy - still getting the install loop. I'd be more than happy to try anything else to get a 3617 working - open to any suggestions!
Ren
I gave up and went with Apollolake/DS918+ which is working great so far!
Any particular reason you want the 3617?
-
-
SMART isn't supported it seems. Is that planned as looks like a pretty important feature if we are to trust the setup? @pocopico
-
5 hours ago, ngsupb said:
Had same, so I did a fresh install but turned off internet access, it does some updates during the first run to update 2 version which seems breaks the install
Thanks for the info @ngsupb. So you mean disconnect from internet after I upload the .Pat file and DSM installation starts?
-
6 minutes ago, Invaliduser said:
But a stuck install seems to be fairly common right now
Ouch. That sounds concerning ☹️
-
1 hour ago, synoxpe said:
Got stuck in the migration loop
Did anyone succeed in installing broadwell? DSM installation gets stuck 10 min countdown timer. @Invaliduser
-
31 minutes ago, synoxpe said:
@Invaliduser Oops build fails:
[!] There doesn't seem to be a config for DS3617xs platform running 7.0.1-42218 (checked /home/tc/redpill-load/config/DS3617xs/7.0.1-42218/config.json) *** Process will exit ***Perhaps I'm missing something?
Ok had to clean the cache. Build went fine! Got stuck in the migration loop (from 3615 to 3617. Guess I need to provide fresh disks.
-
34 minutes ago, synoxpe said:
You need broadwell-7.0.1-42218 that the DS3617 uses
@Invaliduser Oops build fails:
[!] There doesn't seem to be a config for DS3617xs platform running 7.0.1-42218 (checked /home/tc/redpill-load/config/DS3617xs/7.0.1-42218/config.json) *** Process will exit ***Perhaps I'm missing something?
-
2 minutes ago, Invaliduser said:
That uses a dual core architecture. You need broadwell-7.0.1-42218 that the DS3617 uses
Oh ok! I’ll need to rebuild then. Thanks for the tip.
-
Just now, Invaliduser said:
Which build did you use?
Bromolow 7.0.1 ds3615xs
-
1 hour ago, Smartpol said:
Redpill is not passtrough SMART to DSM
Good to know. Also I’ve allocated 4 cores DSM is showing 2 with wrong processor type (Intel i7 on host being shown as i3)
-
-
-
3 minutes ago, killseeker said:
I get
Loading Linux...
error: kernel doesn't support EFI handover
loading initramfs...
error you need to load the kernel first
starting kernel with USB boot
I am looking it it now. But did you encounter this?
I'm getting exactly the same error @killseeker @cris_t
-
8 minutes ago, Unregistrado said:
The other drives are just in the right place. It is just to make sure that drives are following up and you don’t have any gaps between your harddrive connected to different controllers. This was done in older versions also but syntax is different now. So you can see and read more in following link.
Thanks for the link. That explains it. But I guess in my case I won't need sata_remap to start with as I was trying with just two drives.
-
6 hours ago, cris_t said:
it worked at first try. no need to edit any other file.
Great post and thanks a lot for sharing! The boot option "Tiny Core Image Build" is now coming up with UEFI but when I select it, it fails with error message: "error: you need to load the kernel first".
-
9 hours ago, ikky_phoenix said:
"sata_remap": "24\\>2:25\\>3:26\\>10:27\\>11:28\\>12:29\\>13"
Thanks for sharing. Help me please with the logic (newbie alert!). I see 24, 25 mapped to 2,3 and 26~29 to 10~13. What about the other drives?
Say I've 6 drives. How to construct the mapping?
-
On 1/25/2022 at 9:42 PM, haydibe said:
Worst case put Proxmox on your NUC and install it as Proxmox-VM
@haydibe That seems to be the only route as UEFI boot isn't supported by the loader. I had switched to legacy boot on the NUC but my HBA isn't recognized so had to revert to UEFI.
-
On 1/24/2022 at 8:31 AM, haydibe said:
Appart of beeing an anoying error message, does it actualy prevent you from using rp?
@haydibeHow do I proceed past that error message screen? Guess DSM needs to recognize the hardware and then ask to upload the .pat file for starting the installation?
@pocopico please help 🙏
-
11 hours ago, chickey said:
Try SataPortMap 1 and drop the sataremap
Doesn't work unfortunately. DSM installation either says no devices found or the drive error as shown in the screenshot.
-
9 hours ago, haydibe said:
so the tinycore bootloader entry disapeared as well?
@haydibeno that's the only option that remained. Had to remove sata_remap to get back the RedPill boot from USB/SATA options.
-
9 hours ago, haydibe said:
What error does it give you when you try to build after sata_remap is removed?
After removing sata_remap and rebuilding, the tinycore image works as usual but the initial error as shown the screenshot remains.
RedPill - the new loader for 6.2.4 - Discussion
in Developer Discussion Room
Posted
Apologies for resurrecting an old thread. I've 918+ running (4 HDDs as SATA passthrough) successfully on proxmox, only gripe being fake SMART info. Keen to discuss how to fix SYNO_DEV_DISKPORTTYPE=UNKNOWN:
root@ds918p:~# udevadm info /dev/md0 P: /devices/virtual/block/md0 N: md0 E: DEVNAME=/dev/md0 E: DEVPATH=/devices/virtual/block/md0 E: DEVTYPE=disk E: MAJOR=9 E: MINOR=0 E: SUBSYSTEM=block E: SYNO_DEV_DISKPORTTYPE=UNKNOWN E: SYNO_INFO_PLATFORM_NAME=apollolake E: SYNO_KERNEL_VERSION=4.4 E: SYNO_SUPPORT_XA=no E: TAGS=:systemd: E: USEC_INITIALIZED=685493