gadreel
-
Posts
317 -
Joined
-
Last visited
-
Days Won
5
Everything posted by gadreel
-
The visualisation wrapper I think is the one I have now. Because in DSM the Disks appear as QEMU HARD DISK... and not the actual hard disk names. Unless this not what you mean. Now if I pass the physical SATA controller I should see the actual HD names. Thank you @flyride for the helpful information.
-
@flyride Apologies. It's 1TB 870 QVO Neither do I understand how KVM works all I know is that with the KVM virtual SATA Controller and passing-trough the drives they are slow. The way it works now is that the drives are visible in Unraid OS and I am passing through individual drives to DSM. If I pass-through the Motherboard SATA controller then the drives wont be visible in Unraid ('it's not a problem). The SMART values etc will be handled by DSM. In theory since I am passing-through the SATA controller not a Virtio SATA controller the speeds should be the rated one. Well I can give it a go later tonight... for me it's important to know how the DSM will react with the new SATA Controller? It will boot up and report both volumes as corrupted? For example if you had a DS918+ with 4 drives inside and you moved the drives to another DS918+ or DS3622xs+ how the DSM handle them? They will appear as corrupted? It will ask you to migrate or if the array is valid they will just work?
-
@flyride@Peter Suh Hi, I have Unraid which comes with KVM. I have an HBA with 8 SATA ports and the motherboard has 4 additional SATA ports. At the moment I do not pass-through either the HBA nor the Motherboard SATA Controller. I have a DS918+ with 2x 6TB WD Red and 2x 1TB 970 EVO SSDs and I am passing-through the entire drives to a virtual SATA controller(s). Recently I came to the possession of a X550 10Gbe and I realize that the SATA paravirtualization is rubbish. The write speeds especially for the SSDs are very slow 130/150 MB/s. 1) I was wondering if I pass-through the Motherboard SATA controller will I get better write speeds? 2) If the above is correct, when I build a new loader with the MB SATA Controller the DSM will ask me to reformat the drives or continue as it was? (I know always keep backup but in theory will it work?) 3) I am missing something else?
-
No. I have Unraid. It's KVM... When I tried iperf3 with vmxnet I was getting 2.5Gigabit that is just iperf3 has nothing to do with the disks. I thought maybe the 10G nic might help. iperf3 now I am getting 5Gigabit but still the write speeds are the same. I do not know if that will help in anyway. Maybe is the way the KVM SATA controller works...
-
@Peter Suh Update: I did as you said. I recreated the loader with the extensions that I needed. I had to fork redpill-virtio and redpill-acpid to my own repos in order to add support for DS918p-42661. I had a mini heart-attack because after the build I stuck in a recovery loop but going back to tiny core and run the postupdate command it detected update 2 and now everything is back to normal. But unfortunately it seems that even if I connect a 10Gbe post when I am passing-through my drives I only get 130Mbytes write speeds. I guess is a waste. I should go back to virtio-net. Thank you for the support.
-
@Peter SuhIndeed, I built the loader only once and my image file is "tinycore-redpill.v0.4.4.img" ofcourse during the course of DSM updates I run the commands to update the rploader.sh and fullupgrade but I never run the "build" command again. I open the loader img with OSFMount and I found in partition 1(0) the "custom.gz" which contains the existing .ko of my loader. But that file contains a ReadMe file saying that you should NOT temper with that file, do not add, remove or edit any extensions. Unless this is not how you add an extension manually. What I am worrying is that when building the loader again it will try and take the extensions from the sources that I used at my 1st build, as said, for example the ACPID for some reason Jumkey removed DS918+, I have no idea why but I know that during build if an extensions is not found for the model and version you are building it, it will not build the loader. It will cause an error. Correct me if I am wrong. Yes I will pass a single port. I created another TEST VM with the DS918+ and I pass-through a single port and it works just fine. DS3622xs+ nope, I do not want to migrate...
-
@flyride Since the first TinyCore release I have my DS918+ up and running. Recently I came into the possession of a X550-T2 (2 ports) and I would like to use it. My DS918+ it's not a baremetal but a VM. I know how to pass-through 1 of the ports. The question here is how do add the ixbe driver to loader in order to identify the new network card without messing everything up. Any particular commands that I need to run? I prefer not to rebuild the loader because a lot of stuff have change in TCRP since then... for example Jumkey's ACPI used to work on DS918+ not it does not. Any advice is much appreciated...
-
No additional benefits if you jump from DS918+ to DS920+. Just keep in mind that DS920+ uses that Device Tree Structure (DTS) in order to identify your disks. If you want to take easy road just stay on the DS918+... And yes, your DS918+ serial number will NOT work on the DS920+.
- 1 reply
-
- 1
-
-
It was told before that developing tcrp (TinyCore RedPill) to support other models it can be troublesome and requires a lot of effort to do so. Why do you want that specific model? The other models like DS918+ and DS3622xs+ do not offer the same stuff as your DS1815+?
-
Read IG-88 post...
-
Yes. Upto 10gen with a lot of mods. No. There is no workaround.
-
Real SN/MAC request
gadreel replied to yanjun's topic in General Installation Questions/Discussions (non-hardware specific)
@yanjun using a valid sn/mac on a non synology device it's not ethically correct, we will be abusing Synology's services and that might give another reason to Synology to shutdown this community if we start passing valid sn/mac around... I remember when ThorGroup was developing the RedPill loader they made a lot of comments that they did not want to make any changes/hacks on the source code that is not covered by that GNU license... This is the same license Synology has to respect also and release the DSM code to the public. I understand that your intentions is to assist and help the community with an issue but again ethically I am also against it. If somebody wants to pass that boundary he/she knows what to do... -
Hi Ed, for DSM 7.1 you need to use a different loader (RedPill). The procedure might be a bit different from Jun's Loader, maybe have a look at the tutorials IG-88 linked in his post how to install DSM 7.
-
The Synology account is one and you can assign multiple devices to that account... Then each device must have different quick connect id... The DDNS totally misunderstood what your are trying to achieve.
-
I do not think somebody will help you with this. The QuickConnect ID you have is linked with your DS220 serial. Your XPEnology has a different serial number therefore requires a different QuickConnect ID and valid serial number. When it comes to serials and quick connect id stuff the policy in this forum is "no one will assist in any way to abuse Synology's services using an XPEnology machine". Alternative you can use DDNS to achieve a similar goal. Just search the forum for more information.
-
LSI SAS2008 - Make disk order follow enclosure places
gadreel replied to exodius's topic in Developer Discussion Room
I am just using common sense here. Correct me if I am wrong. Passing individual drives is possible but you will loose SMART on those disks. This is what I do on my Unraid. I think if you pass through the HBA as a whole you will be able to monitor the SMART values in the DSM. -
I am pretty sure this is not possible. The XPEnology loaders only work on x86 processors (Intel/AMD) and not on any ARM or Realtek processors.
-
Seems so...
-
I am not an ESXI user therefore I cannot assist further other than telling you that you need to find a way to access the boot sequence using a serial port. With that you can see what is failing during booting but you need to search the forum how you can do that.
-
What is your Core i5 generation? Above (Haswell 4th gen) you can install DS918+... As for guide if you want to instal DSM 6 you can follow this guide: If you want to install DSM7 you can follow this guide:
-
Limitations are listed here...
-
Indeed all points are valid but there is no going back now. Whether Jun's loader was more stable or not, we are comparing apples with oranges and that ship already sailed. Since ThorGroup loader is open source I want to believe when the time comes hopefully somebody will rise from the community with the necessary skills to take over...
-
RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal
gadreel replied to Peter Suh's topic in Tutorials and Guides
DS920+ does not even work for me due to that DTS thingy... DS918+ will not work on your system. It requires 4th Gen Intel and above. You have 2nd Gen. I think is best if you start with DS3615xs or DS3617xs... -
RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal
gadreel replied to Peter Suh's topic in Tutorials and Guides
@nabito You need to provide more information in order for the community to assist you. Is it Baremetal, is it a VM? Are you using an integrated ethernet card or not? -
I do not know if this is the same: https://github.com/pocopico/redpill-load/blob/master/redpill-virtio/rpext-index.json
