Jump to content
XPEnology Community

namvan

Member
  • Posts

    43
  • Joined

  • Last visited

Everything posted by namvan

  1. I think you should go baremetal first. DSM can do VM and also Docker.
  2. The goal you would want as above is nothing (much) to do with the boot device which is the USB/SSD. If speeding up boot process, faster app response time is something you are after then the SSD would play a role in your set up. There are a few things you need to consider 1. Boot loader: the USB. Nothing much you can do for this. 2. DiskStation Manager installation (DSM): this is the bare minimum, think of it as Windows or Linux, to control your devices such as disks, networks.. And some skeleton apps. This part can be speeded up with SSD. 3. The individual app: such as Photos, Office etc. This part can be speeded up with SSD too. 4. The data for the app: most of the apps will need some kind of storage and would provide an option to specify the location for the storage outside of the app at installation time. If this is the case, you can choose to put the apps to the SSD storage and store the data to the spinning disks. 4a. Some apps won't provide an option at installation time but will create a share folder instead. You should pick the SSD at installation time so that everything would set up there and then move the share folder to the spinning disks later. Hope this helps.
  3. I've just checked my set up and it does not give the current IP. You can set your IP to a static in DSM as an option or type this into your web browser https://finds.synology.com
  4. By managing in VMM, did you mean shutdown/restart of the VM? If yes then the addon acpid would help you.
  5. Content extracted from https://kb.synology.com/en-global/DSM/tutorial/which_synology_nas_models_support_WriteOnce_and_secure_snapshots The ones in blue are supported by ARPL and TCRP. The ones in purple are supported as beta in ARPL. WriteOnce and immutable snapshots are both based on the WORM (Write Once, Read Many) technology. These two features offer your data further protection within a specified period. The following table lists the Synology NAS models that support WriteOnce and immutable snapshots. Series Models HD-series HD6500 FS-series FS6400, FS3600, FS3410, FS3400, FS2500, FS2017, FS1018 SA-series SA6400, SA3610, SA3600, SA3410, SA3400, SA3400D, SA3200D 23-series RS2423RP+, RS2423+, DS1823xs+, DS923+, DS723+, DS423+ 22-series RS822+, RS822RP+, RS422+, DS3622xs+, DS2422+, DS1522+ 21-series RS4021xs+, RS3621xs+, RS3621RPxs, RS2821RP+, RS2421+, RS2421RP+, RS1221+, RS1221RP+, DS1821+, DS1621xs+, DS1621+ 20-series RS820+, RS820RP+, DS1520+, DS920+, DS720+, DS620slim, DS420+, DS220+
  6. i do now. It's basically the same for ARPL I would say.
  7. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42962 - Loader version and model: arpl-arc 23.6.22_vmdk-dyn DS918+ - Using custom extra.lzma: NO - Installation type: QEMU/KVM with disks passthrough - Additional comments: + built new loader + upgrade existing DSM via Synology Assistant
  8. And a follow up with the links to the mentioned loaders ARPL - ARC https://github.com/AuxXxilium/arc ARPL - i18n https://github.com/wjz304/arpl-i18n Thanks heap to the 2 authors/maintainers. P.S. to @Orphée I ran a test with ARPL i18n and can do 7.2 now with virtio NIC and SAS disks although it was less fun with only hitting ENTER, no typing from console haha. Thanks for the reference info.
  9. This is something that might be useful to you @ed_co when I was wandering in the forums or a snap of it. By the way, thanks to @ozef. Disclaimer: as everything else in life, use this at your own risk and I hope you would have some fun.
  10. Hey @Orphée it is a general comment in a form of a question As for my case, I am using a VM so just the loader alone is not enough. And this set up does not allow me to add a second SATA controller soI would need at least virtio. apcid is another minor thing but would be better to have it.
  11. Extracted from Synology KC https://kb.synology.com/en-au/DSM/tutorial/Which_models_support_M_2_SSD_storage_pool 23-series: DS1823xs+, DS923+, DS723+, DS423+ 22-series: DS1522+. Available on DSM 7.2 and later. 21-series: DS1821+, DS1621xs+, DS1621+. Available on DSM 7.2 and later. There are some interesting notes The DSM operating system cannot be installed on M.2 SSDs. For DSM installation to be successful, your Synology NAS must contain at least one drive that is not an M.2 SSD. Synology High Availability (SHA) does not support storage pools created using M.2 SSDs. Have fun.
  12. When there is no info, can I (we) assume it is not yet supported? 7.2 is officially release recently so I am patiently waiting for updated information across loaders as well.
  13. Maybe stay with v0.9.4.4 for a little longer. Don't update it and don't do a fullupgrade, just build your loader from the stuff in the image. I am doing that in the serious setup. As of yesterday, I had similar issues with the latest v0.9.4.7 however v0.9.4.8 which was out a little after is alright.
  14. Well said @Orphée. To @ed_co I might misread your requests in the thread but I can tell you that I had fun clicking around the web interface of TCRP. More to that, I also can tell you it is a lot more fun typing into the console over SSH to build the loader or even inside the Redpill itself. As you never know when you mistyped some letters and got a bad result. It is about playing and learning at the same time with xpenology for me. Reading the README.md is also very fun and feeling the effort from the dear developers like pocopico or those from the thorgroup. I am forever grateful to the work they were/are doing. My take from last night as an example when trying to get some fun with the latest tcrp with all the errors. I reported it to pocopico github repo and could see he was working on other tickets there a couple of minutes ago. He even fixed the issue I reported after that so I can see it this morning. Had felt even more grateful Now back to your point, if you feel like creating a step by step doco or something like that, I would suggest you to create a github repo to shape your initial findings and others can also contribute to it as you go. I might be better that way when the forum is scattered with info. It might sound crazy to some but losing time in the forum for stuff you can play with is part of the fun as well.😁
  15. a quick search pointed to this link https://diktiosolutions.eu/en/synology/synology-reset-two-factor-authentication/ Please try and report back.
  16. Hi, I think he meant the below Boot up TCRP up to the point where you can see it prints out the IP Address. For example 192.168.1.15 From a different computer within the same network, such as a laptop or another desktop. Open up a browser: Firefox, Chrome, Edge etc Type in the IP address from point 1. You might have to type in the protocol as http, i.e http://192.168.1.15 TCRP Web will greet you and you go from there. Hope this helps.
  17. From the code here https://github.com/pocopico/tinycore-redpill/blob/main/rploader.sh withfriend is an option/mode when doing a build. As you can see from the sample command below ./rploader.sh build <model> withfriend In short, when building a loader for your setup you can tell the build to include that option for you. It is the default option anyway so you won't likely have to type it. bringfriend is however a command. You can think of it in the similar way as build. The use case is explained in the code and also from help command as below. The context if it might help, is to bring it into your existing loader setup instead of rebuilding a new one. - bringfriend Downloads TCRP friend and makes it the default boot option. TCRP Friend is here to assist with automated patching after an upgrade. No postupgrade actions will be required anymore, if TCRP friend is left as the default boot option. I in fact have my own question about that "assisit with automated patching after an upgrade". It is not very clear on what sort of patching is required and that kind of "an upgrade" is that 😁 I can only guess: patching is for tcrp and upgrade is for DSM. So the docs could be clearer as - bringfriend Downloads TCRP friend and makes it the default boot option. TCRP Friend is here to assist with automated patching TCRP after an DSM upgrade. No postupgrade actions will be required anymore, if TCRP friend is left as the default boot option.
  18. This is from reddit. Have you got more than 1GB of RAM? I think they dropped the support with latest due to that condition to ensure a good performance at peak.
  19. Thanks for the info. It's a large reduction to celebrate. Do you have good transfer speed using the USB Dock? Copying large files, like 5-20GB would be at > 100 MB/s?
  20. I know for sure I got issue with the latest v0.9.4.5 and reported it. Hence I think it would be better to stick with v0.9.4.4.
  21. Did you get any errors when building the loader with TCRP v0.9.4.4? Can you post the commands you executed and the logs if you can collect them?
  22. Then I am pretty sure you got a kernel panic with the SATA card. Would you have time to try with bare minimum as below 1. Remove all hard drives and also the SATA card 1.a If you can find hot plug option in your BIOS, turn on for all SATA ports. 2. Add only 1 hard drive or SSD to your onboard SATA 3. Rebuild your loader from scratch 4. Try find.synology.com or with Synology Assistant if good, try to take off 1.a and redo if you don't like it. Good luck mate.
  23. This link should help you. Thanks to flyride. You can find more links within the top menu section "MUST READ" https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/
  24. Interested to know whether you have measured the power again from both that M910q and the USB 3.0 dock.
×
×
  • Create New...