amikot

Members
  • Content Count

    54
  • Joined

  • Last visited

Community Reputation

10 Good

About amikot

  • Rank
    Regular Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Before everything else you should test your HDD - if there are bad sectors it may explain installation issues. I made that mistake and was trying to fix USB stick, configuration, BIOS version, but real reason of installation failure was HDD with bad sectors.
  2. You can always block address of update server on the router. What is that address - I don't know. Hopefully it's not the same as for packages centre - otherwise you would have no ability to install any synology software.
  3. WebDAV is secure if you use HTTPS. Over HTTP it may be not so secure, but I think in another area than it's with SMB. Mounting FTP in Windows - I may be wrong, but I think it's possible if you use just raw FTP. If you want to use SFTP (FTP in SSH session) and FTPS (FTP over SSL) Windows can't do it. There was one project made by someone in the past for that (mounting FTPS/SFTP as drive in Windows), but it's abandoned and it doesn't work well with Windows10.
  4. Exposing SMB to the internet is like invitation for hackers. Never ever do that. There are other ways to share data over internet: 1. SFTP + DDNS - simple and secure, supported by Linux, simple clients needed for other operating systems. 2. WebDav + DDNS - as others described. Easy setup on DSM, client app needed. 3. SMB or AFP or NFS over VPN + DDNS- Rather complicated setup on both server and client machines. 4. SMB or AFP or NFS over VirtualLAN (ZerotierOne) - Apps needed on both - server and clients ends + free management account on zerotier-one.com (where you create your virtu
  5. SHR is for Synology Hybrid Raid, so yes it's only for Synology (and Xpenology of course). I don't know anything about QNAP - my suggestion is to google it. SHR is nothing about stability or self healing. SHR lets to use full disks capacity for different size disks. If you have all disks of the same capacity SHR is pointless. Synology or QNAP? Qnap has it's features as well - for sure you can install additional software as well (Entware?). Biggest benefit of DSM (Synology/Xpenology) is number of android/ios apps to access data remotely. Everything else can be achieved on any PC setup w
  6. @xReppa: you opened samba port to the world and you're surprised with the attack? Only safe way to share samba over internet is through Virtual LAN like ZerotierOne. There is Zerotier client for most of devices including DSM and any linux/android/windows etc. So you just need to register on their webpage, create virtual network, share network ID with clients and when they join you just accept them in your admin console. All traffic is encrypted and safe. Apart of that, it's good to separate upload section from download section. All downloads should be read-only for all external clien
  7. @Steveyg777: if you're update freak then you should go with Synology and actually you always may consider some older models . As from observations, Synology supports their devices with DSM updates for 6-7 years, so even with models from 2017-2018 you would have better guarantee of future updates then with Xpenology. With Synology you also have easy access to your NAS with Quick Connect which is not supported on Xpenology and on Xpenology you have to use DDNS or Virtual LAN (like ZerotierOne). Sometimes also you may experience hardware compatibility issues, installation issues etc. To
  8. If you want to CHANGE disks for bigger it will work only if you have SHR volume and you can change at once only your redundancy number of disks, but I wouldn't suggest that. If you have just RAID5 or RAID6 disk change for bigger ones wont add any capacity to the volume because of RAID limitations. Another situation is when you're ADDING disks as merve04, then if you have SHR you will add full capacity of the drives. In case of RAID5/6, for each added disk you will get additionally capacity of smallest unit in the raid (or nothing if you added drive for additional redundancy).
  9. Really ? could you share the link, please? I'm googling, duckduckgoing and binging and nothing found
  10. On AmigaOS there was something called "buffers" that was basically ram allocated space that user could set for disk. In those days hard drives had very limited cache and adding buffers did speed up HDD access. To be honest I don't know how it's organised in modern OSes since HDDs has their own cache now. But here we have situation where actually we need kind of additional cache, so maybe it would be good idea to go back to that old solution? You could create ram disk and maybe you could allocate it as SSD cache? Actually Synology DSM may not permit to use something that's not
  11. @unmesh: according to installation guide I've linked earlier you don't need to edit grub.cfg to get DSM booted. To achieve that you have to enter grub console (press "c" when you see grub menu). In grub console you use following commands to enter your data (enter each line separately): vid 0xYOUR 4 DIGITS USB DRIVE VID pid 0xYOUR 4 DIGITS USB DRIVE PID sn YOUR NAS SERIAL NUMBER mac1 YOUR NAS MAC1 ADDRESS Then, you press ESC to return to menu and you can boot DSM with adequate grub menu option. Of course entered data will be gone after reboot.
  12. It must be image and even more ... your changes of grub.cfg doesn't matter, because as I understand your problem is that grub is not starting. So it must be one of: 1. grub.cfg access error. 2 grub.cfg syntax error (this can be probably caused if for editing you used wrong editor - I suggest to use Notepad++) 3. faulty or incorrect synoboot.img (I'm using this one) I would do fresh start - from scratch as described in the guide with taking care about details.
  13. Actually it is pretty easy to determine. It can't be Microserver itself nor BIOS settings because USB stick taken from N54L works in N40L. It must be something with USB dongle or with image written on it. If you're sure image is prepared correctly, then only possibility is that your USB stick is rubbish. Just try another USB dongle.
  14. For SN I used that -> generator In case of the rest I'm completely confused. I have N54L as well, but I don't know what FixSynoBoot.sh is. Only what I did to get Xpenology working on my N54L was: 1. Flashed in modified BIOS version to N54L. 2. Switched C1E off in the BIOS and generally prepared all settings in the BIOS. 3. Flashed USB stick with synoboot.img with prepared grub.cfg with USB stick VID, PID, Serial Number (generated on the web) and MAC address taken from BIOS and PCIE card. 4. Booted bootloader with no problems. I had issues on next steps, but caused by fa