flyride

Members
  • Content Count

    1,429
  • Joined

  • Last visited

  • Days Won

    78

Everything posted by flyride

  1. @bateau please post your question in the questions forum, and please include details of your system - what loader and software versions you were running before, etc.
  2. I'm using the U-NAS 4-bay and 8-bay cases. They are very compact but hard to build.
  3. I was under the impression that this message was part of Synology's hardware validation feature and if it failed (meaning that the loader hack did not work), this message was the result. I don't believe that it means there is a data integrity problem. However, I would start with looking at your arrays and see if they are damaged, then start documenting the system. OP seems to be wandering around with online tutorials (already tried a filesystem check for ext4 and btrfs, there is only one or the other) and that will only result in damage. If arrays look intact, I'd consider regen
  4. It is not required. But it often is helpful for troubleshooting as there is little to go wrong with configuration. If you haven't done XPe with ESXi before, configure with a virtual disk, don't provision a Storage Pool on it and then delete it when your RDM drives are up and running and working correctly.
  5. Not sure what to say here, friend. You are literally posting on the thread that intends to inform you on your options. If you have some specific questions about your specific hardware, post a new question thread with enough information about your setup such that a meaningful answer can be provided.
  6. See this: https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ You did not specify exactly which DSM version you are trying to install. You should be attempting 6.2.3. There are some earlier 6.2 versions that have driver compatibility issues. Also, 1.03b only can be used to support 3615 and 3617. And your BIOS MUST be in CSM/Legacy boot mode to use this loader/DSM version. For 918, you must use loader 1.04b. I don't know if you have run foul of these stipulations but it can be implied from what you posted.
  7. A quick search for "DS918+ network" turned up this post which is exactly your situation. https://xpenology.com/forum/topic/39583-intel-x540-t2-nic-not-obtaining-ip-address-stays-disconnected/?tab=comments#comment-186615 Remember that the onboard (RealTek) NIC uses a port even if you are not using it, unless you disable in the BIOS.
  8. As long as the card has driver support, either from the loader or extra.lzma, 10Gbe works fine.
  9. Well, you need to use an editor, such as vi. Perhaps you should try editing on a non-critical file if you have never done this before.
  10. If the Axagon works with both drives when the other external is left out, change the bitmaps that allocate slots to device types. SSH into the system, become root, and edit two lines in /etc.defaults/synoinfo.conf Change: usbportcfg="0x300000" to usbportcfg="0x380000" and esataportcfg="0xff000" to esataportcfg="0x7F000" When you are finished, reboot and then you should be able to use three USB devices at a time. Note that this setting may revert after a DSM update. If that happens you will have to apply the changes again.
  11. That's functionally backward. The LAN network addressing cannot be shared; the VPN network addressing must be shared.
  12. There is not very much technical information about how the Axagon device interacts with the system, other than to say it does not require a special device driver. If you remove the drive listed above, and then unplug and replug the Axagon, do both Axagon drives appear? I believe that the default settings for the device bitmaps only support two USB devices.
  13. If you configure grub by modifying the loader, no keyboard or monitor is needed on the DSM device (which is what the directions state, and most people do). Optionally you may interact with grub at boot time, and in that case, you will need a keyboard and monitor.
  14. Snapshot Replication. I do this over a Wireguard VPN terminating on my firewalls. But it can also be done with the VPN termination within DSM (works on both Synology and XPEnology). https://xpenology.com/forum/topic/30678-using-docker-wireguard-vpn-on-xpenologydsm
  15. Please do us a favor and explain what you know about the drives and devices you have. You say you have a dual dock, but I see two drives. What's the third drive? How is it connected? What are the drive sizes? !!!
  16. There is no monitor or keyboard on Synology units. They are not required for DSM. You know this already from DSM 5.
  17. How are we supposed to know which ones are the dock? I see /dev/sdv and /dev/sdw, are those the disks?
  18. Migration upgrade with new bootloader == in-place upgrade, boot failure, then boot with new bootloader Bootloader must be configured either way. Not sure how that is simpler than the tutorial procedure. You will have xpenoboot file problem however that will need a quick fix.
  19. Here is your issue. You have your boot loader set to slot 2 when the tutorials indicate that it must be SATA (0:0). Because your SataPortMap=1 that means the first controller (SATA 0) is only mapped for one drive, so this device is not assigned a /dev/sd slot. Therefore, the loader and script cannot find the device to remap for the synoboot devices. Change this to SATA (0:0) and you should find your upgrade works properly.
  20. What are the controller/slot assignments on the four drives? I assume HD4 is the loader, what is HD1?
  21. As long as the array was healthy when it was shut down, they should be recognized out of order when they come back up. If you do know the order that is best however.
  22. Since your disks do not start with sda, and you have no isolated disk device, I believe you have modified DiskIdxMap and inadvertently made the loader device inaccessible to DSM, so therefore it cannot remap/create synoboot. Post the relevant lines from grub.cfg for more advice.