• Content Count

  • Joined

  • Last visited

  • Days Won


flyride last won the day on May 15

flyride had the most liked content!

Community Reputation

722 Excellent

About flyride

  • Rank
    Guru Master

Recent Profile Visitors

10,272 profile views
  1. Mis-mapping of USB drives interacting with the intended HDD pool may be an inadvertent consequence of leaving the SataPortMap value blank. You may have to make a decision between using the 16-port card for all 16 ports (which is working as we intended now) and having USB drives mapped correctly. Alternatively, a device-tree based solution (DS1621+) will probably work for both, but it would be a complicated manual configuration at the moment.
  2. Check and make sure that AHCI mode is selected for both SATA drives in the BIOS.
  3. Well you could have started with that. But I'm not going to copy it from the image. You'll need to translate or switch your install to English.
  4. It's behaving as if maxdisks = 20 Any thoughts? @pocopico @jumkey @IG-88
  5. You will need to post more information. What is the SATA error?
  6. A couple of questions: Why are you using DS3615xs? See here for preferences: Are you trying to use SATA boot? That is not the right option for a baremetal NUC install. You need a USB key and choose USB boot.
  7. @-iliya- Please check grep -i maxdisks /etc/synoinfo.conf grep -i maxdisks /etc.defaults/synoinfo.conf
  8. I'm not sure what you are asking. Jun "ESXi" option = SATA Redpill and TinyCore (actually "TinyCore RedPill" = TCRP) are the same loader code, just delivered differently.
  9. If you are running baremetal you should use USB. SATA is for VMware although it may be usable on other hypervisors.
  10. That is odd. Is the Sandisk your loader device or another USB key? Can you run: ls /sys/block sudo lsusb
  11. Not sure, but there is a lot of information suggesting MaxDisks >24 is problematic. Also do you need 14 USB ports? Not sure how many Syno actually supports, but I have never seen someone try to use 14 of them at once. Why don't you try MaxDisks=24, internalportcfg = 0xFFFFFF, usbportcfg = 0xF000000 and see if you get a different result
  12. Looks like TCRP is using something from @jumkeythat has been updated? @pocopico need forking?
  13. Yes this is working exactly as desired. It is telling you 1) you are assigning ports that are more than maxdisks and 2) sataportmap cannot specify >9 disks so it is setting it to the max of 9. Manually edit user_config.json with new maxdisks and delete the "9" from "SataPortMap=689" and I think you will be ok
  14. I have 10Gbe LAN and all-SSD array. Four SATA SSD's will max out the 10Gbe link so it makes no sense to use cache in that case. Additionally all DSMs use whatever RAM is free to cache recently used files, so if you have a heavy multi-user workload that all refer to a small dataset, it already is cached. Personally I think it's a bit of a gimmick/product differentiation. Not too much value if you ask me, other than to stress test the cache device.
  15. I'm not seeing those errors. Maybe your image is corrupted, consider reburning it. tc@box:~$ ./ update now Checking Internet Access -> OK Checking if a newer version exists on the repo -> There is a newer version of the script on the repo should we use that ? [yY/nN]y OK, updating, please re-run after updating Updating tinycore loader with latest updates Backing up files to /mnt/sda3//mydata.tgz Done.