flyride

Members
  • Content Count

    384
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by flyride

  1. Yes, your J3455 supports the instruction set needed. When you install the new loader, your system will boot to a migration install since you are changing DSM platforms. So download the 6.2.1-23824 PAT file in advance.
  2. Please see this for loaders vs. versions. 6.2.x has a number of hardware constraints on it, so you may need to pick your loader and platform carefully, referencing your hardware.
  3. Well, you need a certain minimum level of tech expertise to run XPEnology. If you aren't comfortable with that then you might be better off with a real Synology unit. There isn't a turnkey backup methodology to restore a broken XPEnology/DSM system. But there are a number of ways to back up various parts of it, here are some: 1. Keep a backup image of your loader on your PC hard drive so it can be rebuilt exactly every time 2. Save your system settings from DSM 3. If you are using ESXi, you can snapshot your VM prior to upgrade and roll it back if there is a problem 4. If you are using ESXi, you can backup your VM and scratch resources using any number of ESXi backup tools 5. If you want an separate copy of your data, build up another XPEnology NAS environment and use BTRFS replication 5a. If you are using Docker, you can replicate your whole Docker environment using BTRFS replication Backing up DSM itself to something like an image backup isn't the easiest thing to do, and generally isn't necessary.
  4. Install an Intel NIC (see here) and disable your on-board NIC in the BIOS. Intel CT works, as do others that are specifically supported by e1000e driver (see here)
  5. When you try it, we will know... The spreadsheet doesn't tell you whether particular hardware will work. For example, we have had some difficulties with booting network drivers in loaders after 1.02. So even if the NIC is supported (meaning, there is a driver installed that is compatible with the card), there have been kernel panics and other failures. I have not seen evidence of similarly supported (driver installed in image) disk drivers with problems, but there are no guarantees unless someone else has proven it out with the hardware you are considering. I will say that some implementations of embedded third-party controllers behave differently than the native PCI cards which can cause problems. The spreadsheet shows exactly which device drivers exist and the PCI device ID's supported by those specific drivers... nothing more or less. If I were in your shoes, I would be very certain that the PCI device ID of the LSI controller embedded on the SuperMicro board is represented in the image you want to use.
  6. Actually it's Intel that says the processor only supports 8GB but it actually works fine up to 32GB.
  7. That board is having problems with 6.2.2 and we haven't figured out why yet. It works with 6.2.1 okay.
  8. Yes that card works great with 1.02b and DS3615 on all DSM 6.1.x
  9. That is what I would attempt. Be prepared for suboptimal SATA controller mappings. Can you grab a few small drives and build up a parallel test environment to try it? In any case, don't try to repair anything that doesn't come up clean and you can always go back.
  10. I'm not sure why the i3-4150 would not have FMA3 like other Haswells, but if it is true the Linux kernel will stop the boot. So you will know immediately.
  11. Just curious, what is Portainer doing for you that the native Syno docker manager doesn't? I use Portainer on non-DSM Docker hosts, but never thought to load it up on DSM.
  12. 1.02b loader supports all 6.1.x builds released thus far. No package limitations, with the exception of those requiring a legitimate Synology serial number.
  13. Aside from courteous language, no. As of 12 Jan that appeared to be true. Everything you see in that post comes from community experience and reports. I'll remove that statement based on your note.
  14. What BIOS version and how much RAM do you have?
  15. This is what is happening to me as well. J4105-ITX. With or without a CT card, same results. Still investigating.
  16. Glad you got your stuff back. There isn't much information out there to support btrfs recovery, so this was a useful exercise.
  17. Use AHCI mode if you can. Discrete LSI controllers work with the 3615 image but I don't know if ESRT2 is supported differently.
  18. Try loader 1.02b, DSM 3615 6.1.7 update 3 (15284), no extra.lzma
  19. I get this too. Keep refreshing the page and it will eventually go through.
  20. Boot device must be a USB flash.
  21. - Outcome of the update: SUCCESSFUL - DSM version prior to update: DSM 6.2.1-23824U6 - Loader version and model: Jun v1.03b - DS3615 - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.7 - Outcome of the update: SUCCESSFUL - DSM version prior to update: DSM 6.2.1-23824U6 - Loader version and model: Jun v1.04b - DS918 - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.7 - Outcome of the update: FAILED - DSM version prior to update: DSM 6.2.1-23824U6 - Loader version and model: Jun v1.04b - DS918 - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock J4105-ITX Failure notes - no network on Realtek, installed an Intel CT card and this doesn't work either. Tested a clean install using both NICs and encountered the same failure. BIOS version? Certain USB key device ID's? Need more information from anyone who is successfully installing 6.2.2 on 1.04b on an ASRock J-series device.
  22. This Intel website shows device ID's vs product names. The DSM 918 supported e1000e devices are visible in the spreadsheet here - just match them up. If you are just looking for something inexpensive for a PCIe x1 slot (most everybody has at least one of those), the Intel Gigabit CT is a good bet. 82574 chipset, device ID 10D3 and is current product, new for about $33 USD
  23. flyride

    Question on disks

    DSM is installed on all your drives, unless you do something heroic with mdadm to disable updates to the system partitions. Reinstalling DSM doesn't impact any of your pools unless you choose to overwrite them.
  24. You've hit the nail on the head. Intel is notorious for releasing silicon updates with different PCI device IDs and keeping the marketing designation the same. I looked at that website and while it asserts your card is supported, I can find plenty of other sources that say it isn't. e1000e v3.2.6k is what is in the 4.4 kernel tree and Synology did not update that driver for 918. 3.2.6k does not support your 15BC card. The DSM 918 image should support i219 devices with the id's 15B7, 156F, 1570, 15B8.
  25. DSM is stable with one CPU. Throughput may suffer if you are using it for a production load. I routinely use 1 CPU for test systems.