Jump to content
XPEnology Community

dranivil

Member
  • Posts

    22
  • Joined

  • Last visited

Posts posted by dranivil

  1. 1 hour ago, mojojojotroi said:

    When you have this behaviour, it's probably bad setting(s) / option(s) chosen in the loader that conflict for DS model chosen, and this will bug / kernel panic the DSM (so you it won't boot and you can't acces it). Also ensure you didn't modify some BIOS settings, some are very important. Good luck !

    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.

  2. 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.

  3. 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).

  4. Nothing?

    On 7/21/2021 at 2:07 PM, Vortex said:

    - No, Just CSM  Boot Filter.

    - It is in the archive. Named ORIG.ROM.

    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.

  5. 1 minute ago, nurpur10 said:

    Thanks for reply. I use the first LAN. It works on the 1.02. Is it possible to let me have snapshot of your BIOS settings for the CSM and Boot menu as 

    I just cannot get 1.03 to be scanned in Find Synology. The Linux boot says that it is successful.

     

    Thank you

    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.

  6. 11 hours ago, nurpur10 said:

    I appreciate that this maybe a basic question  but could someone confirm the procedure 

    to load the extra.lzma & extra2.lzma. I know you have to mount the larger 30mb partition. 

    Do you then just copy past and over right the two existing files? or do I need to do anything else? 

    Do this makes no difference and I cannot load 1.04 as it appears some drives are missing.

     

    Thank you!

    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.

  7. On 7/17/2021 at 9:24 PM, nurpur10 said:

    Resolved thanks to VORTEX

    Everything works great after he supplied a BIOS mod:

     

     

    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.

  8. 17 hours ago, nurpur10 said:

    Would it be possible to replace the Bios by flashing with something that would give these options?

    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.

  9. 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?

    • Like 2
    • Haha 1
  10. 27 minutes ago, intrax said:

    Probably a driver problem. Check the nic specs of the F2-422 as it's realtek and what driver is in the extra.lzma. Weird booting uefi, would think you have to boot legacy ! Also check your dhcp for problems.

    Here I have opened a thread exposing everything. Apparently with 1.04b it gives stability and network problems, with 1.03b (+ extra.lzma) it works perfectly, but it forces me to boot into Legacy. If I have a power shutdown or reboot, I have to manually go into BIOS to boot from USB. No way to boot from HDD and redirect to USB?

  11. I have news!

     

    I have tested loader 1.03b with DS3617xs and this has happened:
    - The network works fine but ONLY one of the network connectors (the 1 Gbps one) works. The other 1Gbps connector and the 10Gbps connector are not working. With the 1.04b, 1 1Gbps connector and the 10Gbps connector worked.
    - The system works correctly, everything works smoothly.
    - It is impossible for me to leave it like that since I cannot leave the boot in legacy. This NAS has the boot priority blocked and the USB only starts me as the first option if I have set the UEFI mode.

    I think I'm close to fixing it, but I need some help.

     

    EDIT!

    I have managed to fix the problems with the network card by installing the extra.lzma, but I still have the problem that my BIOS boots by default from the hard disk and I cannot change the boot order!

     

    When boot normally...

    image.thumb.png.c72478a4317014e224680c1f86225b00.png

     

    My BIOS options:

     

    image.thumb.png.3dacf2e1a2a9c10434d9693808e3306a.png

     

     

  12. I am trying to get DSM running on this Terramaster NAS. I am using 1.04b 918+ with extra / extra2.
    The problem is that the network is unstable and I generally have problems with DSM. This NAS has 3 network connectors, 1 of 10Gb and 2 of 1Gb. I will explain the problems I have:
    - When I connect the cable the network is not recognized. It does not appear on the router and the light of the network connectors is not on. Sometimes I wait a while and it ends up working after several minutes, other times it is never recognized. In the grub.cfg I have the MAC address of the 3 connectors correctly set.
    - When the network finishes working, I can access DSM, but some things do not finish working well. For example, if I turn it off, it keeps turning off the device for several minutes and in the end it ends up being forced off. The Webdav protocol does not let me access my files (I have another NAS with xpenology next to it where I can access with the same configuration).
    - I've had crashes on some open windows.
    - The file transfer speed to / from the NAS is very slow (ranges from 1-20 Mb / s) when it should go faster

    I can't try another loader since 1.04b is the only one that lets me boot with UEFI, and I can't use Legacy.

    In the DSM system information it shows that I have an RTL8153 USB network card

    The truth is that I would like to use DSM, since the operating system that comes with this NAS is not very good and I have no other alternatives.

  13. 3 hours ago, intrax said:

    So you are booting from usb ! 

    Ok, I have news ...

    I have managed to always boot from USB change to "only UEFY". But now the problem is in the installation and recognition of DSM.
    The pendrive that I have prepared has been with the 1.04b and extra.lzma and extra2.lzma (I have tried several versions) emulating the 918+.
    I don't understand why but the network card works sometimes. It doesn't matter if you connect it to the 10G port (the connector lights glow only when working) or one of the 1GB ports (the connector lights always glow). In the grub.cfg I have put the MAC addresses of the 3 connectors (they come on a label attached to each connector), the generated serial number of a 916+ and the PID and VID of the USB flash drive. Once it is recognized, it works fine until I reboot or shut down. It is as if the network connection is unstable.

  14. 11 minutes ago, intrax said:

    Post a picture and try to reset bios. If not possible to boot legacy mode the bootloader must be installed on efi partition !

    There are 3 options that I can select:
    - uefi
    -legacy
    - uefi + legacy (default)

     

    I can only find DiskStation on the network if I boot from legacy mode. I don't know if that's what you mean.
    Resetting the bios does not change anything, the option to change the boot order is blocked by default.

  15. Hi, I just got a Terramaster F2-422 but the TOS OS does not have any of the features I need, so I have decided to install Xpenology. To my surprise, the BIOS is set by default to boot from the hard drive and I need to boot from USB, and the option to change the boot order is blocked (grayed out). I have seen in this thread (https://xpenology.com/forum/topic/36101-new-terramaster-f2-221-locked-bios/) that the same thing happened to someone with the F2-221 model, but in my BIOS does not show any CSM settings.

    I find it strange that it doesn't let me change the boot order. Some help?

×
×
  • Create New...