synoxpe
-
Posts
105 -
Joined
-
Last visited
Everything posted by synoxpe
-
RedPill - the new loader for 6.2.4 - Discussion
synoxpe replied to ThorGroup's topic in Developer Discussion Room
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 -
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).
-
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)
-
I gave up and went with Apollolake/DS918+ which is working great so far! Any particular reason you want the 3617?
-
Is the USB passthrough working for anybody on Proxmox? I've DSM 7 ds918+ (apollolake) running perfectly but as USB passthrough disk gets disconnected as soon as I start to copy stuff using Filestation. @haydibe @Dfds @pocopico
-
SMART isn't supported it seems. Is that planned as looks like a pretty important feature if we are to trust the setup? @pocopico
-
Thanks for the info @ngsupb. So you mean disconnect from internet after I upload the .Pat file and DSM installation starts?
-
Ouch. That sounds concerning ☹️
-
Did anyone succeed in installing broadwell? DSM installation gets stuck 10 min countdown timer. @Invaliduser
-
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.
-
@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?
-
Oh ok! I’ll need to rebuild then. Thanks for the tip.
-
Bromolow 7.0.1 ds3615xs
-
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)
-
Proxmox SATA HDD Passthrough to DSM 7. Anyone able to achieve this? I just added a few SATA Disks manually to the DSM VM with id 100: qm set 100 -sata1 /dev/disk/by-id/<id> but they're showing on DSM Storage Manager as QEMU Harddisks missing SMART info. @haydibe @pocopico
-
@haydibe got it working on Proxmox by following this video. Thanks much for helping out so far! Technology and talents keep amazing us @pocopico 🙏
-
I'm getting exactly the same error @killseeker @cris_t
-
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.
-
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".
-
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?
-
@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.
-
@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 🙏
-
Doesn't work unfortunately. DSM installation either says no devices found or the drive error as shown in the screenshot.
-
@haydibeno that's the only option that remained. Had to remove sata_remap to get back the RedPill boot from USB/SATA options.
-
After removing sata_remap and rebuilding, the tinycore image works as usual but the initial error as shown the screenshot remains.
