• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by flyride

  1. nVidia drivers are not included in any currently supported platforms. However, I believe there has been some progress to compile nVidia support and added it to DS918+. You'll have to search for that in the forums. Once it is working (nVidia device appears as /dev/dri) then it should be trivial to set up a Docker mining app.
  2. Based on this you would need to install DS3615xs or DS3617xs with loader 1.03b if you want the latest functioning version 6.2.3. Note you must download the exact 6.2.3-25426 version as the latest 6.2.4 and 7.0.1 builds do not work with the released loader. It's not difficult to install if you follow the FAQ and tutorials closely. But it can be a bit finicky as it is, at its core, a hack of a purpose-built software/hardware system.
  3. Just deleting the partition structures on the disks is adequate. No need for a full format.
  4. Moving shared folders from the control panel is a write operation. So that cannot be done on a read-only filesystem. btrfs attempts to fix itself in real-time. If it cannot due to corruption, it will mount read-only or fail to mount at all without external input. There is a filesystem check tool but it really isn't intended to return a filesystem to service if it has suffered unfixable corruption. The correct course of action is to COPY the files from the read-only filesystem, which you are supposedly doing. If Synology's implementation of docker is install
  5. You can convert a Basic Storage Pool to a RAID1 at any time by adding an appropriate disk. Understand the difference between the Storage Pool (where the array redundancy is) and the Volume (the filesystem, which has some corruption which is resulting in a read-only state). You are proposing to sacrifice your healthy array redundancy and create another Storage Pool and Volume. This will work logically, but this may be an inappropriate risk depending upon the value of the data and whether you have another copy somewhere else. As always, redundancy in the RAID array is n
  6. While e1000e does work (and was required with 6.2.2 when PCIe devices were borked by Synology) it is limited to 1Gbps. With 6.2.3 and VMXNET3, you can take advantage of >1Gbps adapter throughput.
  7. Xeon or Ryzen but on AMD it is supported by only a few motherboards. Personally I went the Xeon/SuperMicro route.
  8. Please note this: But if you were going to do it (for testing purposes of course), you would need to get ahold of a genuine failed DS3615xs, DS3617xs or DS918+ (depending on which platform you wanted to use) and copy the MAC and serial from that physical box.
  9. Using Jun's loaders and DSM 6.2.3: You can search through the extra.lzma thread to see if any additional drivers have been compiled for your NIC: And you can review whether folks have used the NIC before here:
  10. Prepare and burn new loader. Install again overwriting the existing disk. Optionally, delete all the partitions on the drives you were using beforehand.
  11. You're running low on options... please take a look at this post. If none of the information works for you, that is probably the extent of what I know to help you. There might be some btrfs experts out there in the ether but I don't think you'll get any other options here. Good luck and if something works, please report back!
  12. I'm sure that is to sell those silly overpriced branded SSDs and nothing else. Even if Syno tests for a device model or serial range, this should be defeatable much like the NVMe patch approach. Please consider a platform like this, with full RAIDF1 and decent CPU support.
  13. DS918+ has internal synoinfo.cfg parameter maxlanport which is defaulted to 2 ports. You can change it but it will get overwritten on DSM upgrade, so be careful it doesn't disable your LAN because you didn't think about it.
  14. Well, you can do what I suggested, which is copy off files, delete and remake your Storage Pool/Volume and it will use the size. Synology will automatically expand multi-drive arrays that are grown, but it has no provision for expanding a single drive. It can be done manually and is a basic procedure common to all Linux systems. You can follow this thread to get it done: You have an ext4 filesystem and you are not using lvm, and you have a one-disk
  15. Try the alternate tree roots, some information here:
  16. You need to be more careful with the syntax. sudo mount -o recovery,ro /dev/vg1000/lv /volume1
  17. Try this one next:
  18. You cannot make two volumes on the same physical disk. The "create" button in the UI is not available because the UI won't make two volumes on the same physical disk either. Offload your files, delete the volume you have, add it back in to use the balance of the disk space for /dev/sda3.
  19. Did you have btrfs checksum "on" for the affected volume? If so, btrfs would have told you if there was data corruption via pop-up in the UI. Normally it would also fix it, but you have no redundancy. Without the checksum, there is no way to determine corruption. If files were missing for some reason, that is also not really detectable. A good reason to have a real backup somewhere... I say this often: btrfs will fix itself if it can. If it cannot do that, there is underlying corruption that MAY be fixable via filesystem correction tools, but probably w
  20. Hello, Some of what you are reporting doesn't make sense. Maybe you have tried some recovery activity from the thread? The thread you cited is a pretty catastrophic failure recovery with multiple bad drives, and the procedures in it circumvent the protections inherent to the md system. Also, this post is in the Q&A session and you really need much more than a simple, single post response. Please repost in a support forum like The Noob Lounge or Post-Installation Questions as this will take many post iterations. And, use the first few posts
  21. Jun/default drivers for DS918+ support I219-V on PCI ID's 1570 and 15B8 only (e1000e driver). Yours is 15FA (clearly newer) The DS918+ extra.lzma/extra2.lzma 0.13.3 driver compilation contains the following PCI ID's (latest 15E3, older than yours) So unless someone has a newer compile of e1000e you are probably SOL...
  22. Redpill devs might want to consider one of the below listed models for support in order to enable this very useful and new feature. FMI:
  23. Check the PCI ID's, Intel revs with every chipset. The marketing device name remains the same, but the silicon and driver requirements differ. They have done this consistently for a long time.
  24. Check for bad SATA cable or it is routed so that the connector is breaking contact.