Hackaro

Members
  • Content Count

    24
  • Joined

  • Last visited

Community Reputation

5 Neutral

About Hackaro

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks for the reply, @pocopico. My primary intention is to go with bare metal machine, with the hardware you can see in my signature. Indeed I will make some tests before upgrading my RAID disks! Now, after creating the .img file, I've installed it onto an USB stick with this command: sudo dd if=redpill-DS918+_7.0.1-42218_b1637771683.img of=/dev/sdb where /sdb is my USB stick's dos partition. In this way I should create a bootable USB stick, shouldn't I? Second question: at the moment I've used the simplest apollo lake_user_config.json po
  2. Thanks for the reply. Yes, the rphelper, v 0.12 downloaded here somewhere in the forum. Basically I followed this video and I was able to have a working test machine under VW Fusion on MacOS BigSur. I built the .img file under another vm with Ubuntu installed on it.
  3. @pocopico I need a driver for a Realtek 8125 2,5gb ETH and I've noticed you have added... but ... sorry for the noob question... I don't know how to add the compiled module to the Apollolake build, could you be so kind to show how to do it? Thanks!
  4. @flyride so it's safe to use them? ... I' ve also tested TWO Samsung 970 EVO (instead of Plus version) and I got the same result in SSH and the same in DSM (they work like a charm) ... but isn't it very strange? Can be the standard Linux binary so firmware version dependant?
  5. @IG-88 I can confirm that RTL8125 works like a charm ... I have also update DSM to 6.2.3U3 without problems. I've change both the two NVMes from Crucial to Samsung 970 EVO PLUS to have better cache's performance as I've have said, but I've gotten in troubles as you can read here ... if you have any hint ... it's welcome!
  6. @flyride I have a strange behaviour since I have changed the NVMe disk's brand and updated to new Samsung 970 EVO+: thinks are working correctly in DSM as you can see https://www.dropbox.com/s/nwrfvwdss87zymj/Screenshot 2021-02-02 at 10.46.13.png?dl=0 https://www.dropbox.com/s/fcb8mlzeohwb4bf/Screenshot 2021-02-02 at 10.47.02.png?dl=0 but I don't have the correct list in Terminal: Root@NAS:~$ synonvme --is-nvme-ssd /dev/nvme0n1 It is a NVMe SSD Root@NAS:~$ nvme list Node SN Model Namespace
  7. I didn't opt for that convoluted and expensive solution: I just bought a QNAP switch 2,5Gbe e connected all my devices (two hackintoshes, and NAS) directly to it. All with 2,5Gb NIC on board. Write and read are consistent at full max speed if the storage source is an SSD/Nvme disk.
  8. Sorry for the late reply, and Happy New year! I had a lot of troubles with my 10Gbe ring (CRC errors) and after many tests I ended up discovering that my Asus 10Gbe switch was the culprit. Connecting NAS and Mac peer-to-peer made all the errors disappears. Now I sent back the switch and after thinking a bit about what we've discussed I've opted out for a 2,5Gbe ring instead of a 10Gbe, it's much more cheaper and it'll probably have performances that correctly match the Crucial NVMe disks I've bought. Maybe in the future I will consider selling my Crucial NVMe's and cha
  9. I made a recap post above ... and there is all the links you need ...
  10. I guess I have to study a bit more! ... that's the initial test' results: https://www.dropbox.com/s/d7hlhkae5lc9p7a/Screenshot 2020-12-20 at 12.59.06.png?dl=0 so the network is the bottleneck here... ny NAS has only 8GB RAM so I really don't know about the ram as cache ... maybe I should consider another type of NVMe ... mine are those one: https://www.anandtech.com/show/13512/the-crucial-p1-1tb-ssd-review and I read the following: too sad... I have to dig further on the NVMe technology, I guess. Thanks for now! I'll report back.
  11. @IG-88 Sorry for the late reply but I needed a second 10Gbe card to connect things properly. At the moment I'm still using an Asus switch XG-U2008, it was very cheap at half the price so I got it, and now I have my 10Gb ring between Mac (Hackintosh actually) and Nas Xpenology . Here are some speed tests: https://www.dropbox.com/s/db6h5xp9vpl24lj/Screenshot 2020-12-10 at 19.32.11.png?dl=0 considering that: I'm already using jumbo frames, SMB2/3 without signing and 7 cables' type (one 5meters, the other one 1,5 meters), I'm copying a single big file (around
  12. Uhm... why should it become slow? Maybe it needs a bit of time for the cache to just "caching" all your files . I suggest to use the NAS for some days and then decide. Problem is that as you copied the file, in case something is wrong if you haven't done a backup of it you cannot have it back.
  13. I'm setting up a connection between a Mac (Hackintosh) with 10GBe ethernet card, a Xpenology setup with Sonnet 10Gbe card and I'm waiting for a Netgear switch 10Gbe (2 ports 10Gbe), and then I will post the result. In the meanwhile I was noting that Synology DSM 6.2.3u2 is based on a very old Linux kernel: unmane -r 4.4.59+ and from version 4.15 the Linux kernel is supporting Thunderbolt devices, and networking over Thunderbolt too. I'm wondering if/whether Synology DSM 7.0 will have the right version of Linux kernel to add Thunderbolt support; if it will be th
  14. Just a recap for those who'll want to try NVMe cache because all the thread is quite messy imho. The above shell script with DSM 6.2.3-25426 Update 2 (on DS918+ , indeed) does not work anymore. At least in my experience it leads in an incorrect state where the two NVMe are not recognised as the same and therefore they cannot be used for a necessary RAID 1 in case of R/W cache. The only thing is really working at the moment is a copy of the libsynonvme.so.1 to the right path. So put this file in a public zone of your volume (this is my case) or wherever you like and th