pocopico

If i may ask, few things that come in mind, - What are the required NAS requirements in terms of availability, uptime, hardware redundancy etc ? - What is the budget ? - What is the workload you would like to host on the procured NAS ? SMB/CIFS, NFS, S3, structured or unstructured data ? - What other services you would like to host on the NAS device (Docker, Office, email, backup etc) ? - Are the above services critical for your bussiness needs ? Avoid DIY (Thats for non bussiness critical purposes). Dont just buy on features. Stick with the one that provides the best support, things CAN and WILL go wrong at some point ! You need to have a proper support organization structured to backup your business. Both Synology and QNAP don't offer 2 or 4 hours response time, spare part availability etc and i can guarantee that both will not engage fully to solve your issue. On the other hand, both are the titans of home to small/medium size business NAS devices. Syno is lacking some features that QNAP has BUT with Syno i've never lost data and I must say its rather difficult to do so, whereas with QNAP i've read and had some very dissapointing experiences. So if I were to prioritize my bussiness needs : 1st. Customer support with onsite presence and spare part availability 2nd. Design a backup solution in parallel with your NAS needs. 3rd. All other mentioned features I hope this helps a bit. And a small comment on " And of course, we need a solid backup system (RAID) 'cause those files are super important for our clients." RAID should NEVER be considered a backup. Its just a level of hardware failure redundancy and thats all. Plan for a proper offsite/offline backup solution as well. Backup to tape or S3, cloud or on premices targets. Ransomware and/or human mistakes can lead to loss of primary hosted data, you should be prepared for that possibility.

Testers , PM

Polling for modules request. Which modules would you like to be included ?

I would start with the RAM upgrade. Then use a new USB stick for the new loader and use the last known working settings from your 3615 loader (Sataportmap etc) and create a new loader. Also can you PM me the output of the command dmidecode ?

I will try x72 hero. x88 (1288) hero at least requires licence.

It would help i you could get the model.conf file that you've used, if of course you still have it

QuTS Hero is still an issue, the rest has been resolved more or less

Is this the image I’ve translated and created the automatic model.conf generation ? It still needs some work but I’ll release an alpha release soon. Afaik it looks that QuTS hero requires licence. It needs a lot of reverse engineering and I’m not that skilled. I’ll be calling soon for few physical system testers.

It’s about time to give some love to the Qnap community. Do we have any targeted models you would like to focus ? Eg TS-1655, TS-1273 etc

Use the html builder

Which loader are you using ? You can try DVA1622, with TCPR

You dont need redpill-load anymore, that is the most time consuming process.

The updates are handles by tcrpfriend so in tcrpfriend repo, i will try to update the info.

Yes you can, i have two of them.

I have seen no issues migrating from one model to another.

I'm not using bsp files at all in TCRP HTML Builder, its only rploader that has not been adjusted to that, but i plan to fix that soon

Yes you are right with the distrubution of bsp files and at some point i was also thinking about removing them as i now use Fabios patching method in HTML Builder. I just didnt have time to re-engineer the build process in rploader.sh. Having in mind that TTG was very cautious with the distribution of original Syno files, i would like to keep following their rules. It might be critical for us that we are testing many models to build in faster times but for the main user i think its OK to wait for 5 minutes once in a while. The stability plays a great role and i think at that we are all somehow in a very good place.

The whole Tinycore filesystem is on memory and being on RAM, there is no need to load anything to the RAMdisk. Setting the requirement for memory to 2GB to build the loader,. is one of the constraints that i decided is OK. If you have larger memory available you may speed up by writing more files to /tmp instead of the partition 3 of the loader. The whole process is based on the main constraint of not sharing anything (kernel, ramdisk binaries, update images, etc) that is copyrighted on any shared location. If you decide to do so, you are opening a posibility to be blaimed for distributing copyrighted material. Its you choice but you might have just opened a back door to be procecuted.

Correct, i think i've got this fixed after a version, didn't I ? 🤔🤔🤔🤔🤔

I've been away for some time. So i've somehow lost track of the progress of the loader. We were always using the same partition size for 1st and 2nd partitions as these are the syno defaults, actually the same ones that someone will find on an original syno device. We never know if thats checked somehow (now or in the future) so the recommendation from TTG was to keep it as is. I know we've changed a lot of things by introducing new method for modules etc, but we still have a lot of spare space in the third partition to store all the required files for the loader.

Hi, Please make sure you have C1E disabled in BIOS. This may have been reset for many reasons. (generic and not related to grub rescue issue) SD-Card will never work unless its on a USB reader. USB VID:PID should be set correctly otherwise DSM might think its a disk and will try to format it.

Hi, It doesnt sound so bad. Did you set the USB VID:PID and Serial Number & MAC Address, correctly on Juns restored loader ? Can you PM me your grub.cfg Data are always on the third disks partition and the installer usually does not mess with the hardware partitions unless it doesnt recognise the disks as DSM disks.

You do have the boot image on different SATA controller right ?

WoL is solved easily even without original interface. Look for the available addons

Hi, thanks for the message, I'm trying to identify the purpose for something like that. Why would you want to perform an XXmove command on Syno ? Can you please elaborate some more ?