dranivil

On the setup screen, the arc script recognizes my original Macs (of all the network cards, I have 2 and one of them with 2 connectors). I have checked and they are correct. After starting the loader, the script itself tells me to access an ip x.x.x.x:5000 but that ip does not lead anywhere. In the BIOS I have observed everything. Tested UEFI and Legacy. CSM enabled and disabled. Really everything is as I have always had it. In fact, I saw that I had an old DSM 6 synoboot.img saved on my PC and I was able to use it and now the NAS recognizes me on the network. It has to be something in the loader configuration... I haven't really selected any modules, only those that are selected by default. Tested with Fake mac and real mac.

I need help. I don't know what happened but I can't regain access to my nas. I have a Terramaster f2-422 that had DSM 6 (Jun Loader), it worked fine if I put the extra file in the partition. I updated to arpl (DSM 7) with a loader that I don't remember (I think arc loader) in the summer and everything worked correctly. Today I went to update the loader. I have pressed the update option within the loader and apparently it has updated, but I have lost access to the NAS. I have tried to reinstall the USB with arpc from 0 and I have tried several loaders (rr, fbelavenuto loader, arc loader...) but none of them recognize the NAS on the network. Everything is installed correctly, from the menu it recognizes my network cards (it has 2), and I have access to the NAS, but when the network card starts up it keeps flashing but without being able to access the NAS. I have also tried the "Force DSM installation" option but the same thing. I have very important data on the NAS and I don't know how I can recover it.

solved. The problem was a enclosure usb...

I don't know why, but since I upgraded to DSM 7 from 6.2 I can't change the permissions of the files and folders. It doesn't matter if I change the permissions from shared folders, from an FTP client or from SSH with chmod, the permissions are always 777 (some are not 777, because they are created by packages or they are system). Also, if I connect an external device and format it to EXT4, it doesn't have permissions and I can't change them in any way (it fails when I try).

Nothing? It is strange but the "RTC Alarm" option is always enabled even if you disable it if WOL is enabled. And even if the date and time change, it is always active at the same time (00:00 every day). I have tried modifying the BIOS with AMIBCP and disabling the "RTC Alarm" option but it still wakes up. I'm very lost and I don't know what to do anymore.

There is a bug in this BIOS. It always wakes up at 00:00 when the WOL option is activated !!

I haven't installed the bios mod yet. But all I had to do is change the boot mode to legacy (but it should work on uefy + legacy). Then I suppose that you have to change the options in CSM Options so that the usb starts automatically. But I don't know yet, I have to do the tests yet. I have to say that in the multiple tests I did, it has sometimes started me with the 1.04 bootloader, but the system was unstable.

I did manage to load DSM with 1.03b, but I had to use the extra files. And yes, to put them it is necessary to mount the unit and copy / replace the files. Make sure to try the 3 network connectors, you may have tried one that is not functional.

What bootloader did you use in the end? I was doing tests and only 1.03b (+extra) worked but there are certain things that did not work correctly with DSM. - disk hibernation does not work. - When using that bootloader, the transcoding doesn't work. - Fan speed does not change automatically - Network speed using different protocols is low (I have tried FTP, WebDAV, and SMB). According to my tests, with TOS I reach the maximum that the ethernet cable can give (approximately 115Mb / s). With DSM, it reaches about 30-40 Mb / s, or even less depending on the protocol you use.

Oh! Thanks! Does this allow to change the boot order? On the other hand, do you have the original BIOS file in case I had to reinstall it?

Yes you can. You have to use the extra bootloader 1.03b + extra but you will have to boot from the usb manually every time you boot.

You can not. Unless someone updates the bootloaders.

From the official Terramaster forums they do not give much hope of it. It is easier to launch a UEFI compliant bootloader that is compatible with new hardware.

Seeing that new hardware is coming to the market, the compatibility problems with the 1.04b loader, not being able to use the 1.03b with UEFI and not being able to update to 6.2.4 ... Do you think that a future 1.05 loader will come out that will solve these problems or is it something that is not expected?

I've already tried, but that doesn't work. And even if it did, it would have to do it manually every time it reboots.