flyride

Members
  • Content Count

    1,928
  • Joined

  • Last visited

  • Days Won

    98

Everything posted by flyride

  1. 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.
  2. Xeon or Ryzen but on AMD it is supported by only a few motherboards. Personally I went the Xeon/SuperMicro route.
  3. Please note this: https://xpenology.com/forum/topic/9392-general-faq/?tab=comments#comment-82390 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.
  4. Using Jun's loaders and DSM 6.2.3: https://xpenology.com/forum/topic/13922-guide-to-native-drivers-dsm-617-and-621-on-ds3615/ https://xpenology.com/forum/topic/14127-guide-to-native-drivers-dsm-621-on-ds918/ You can search through the extra.lzma thread to see if any additional drivers have been compiled for your NIC: https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ And you can review whether folks have used the NIC before here: https://xpenology.com/forum/topic/12867-user-reported-compatibility-thre
  5. Prepare and burn new loader. Install again overwriting the existing disk. Optionally, delete all the partitions on the drives you were using beforehand.
  6. 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. https://xpenology.com/forum/topic/14337-volume-crash-after-4-months-of-stability/?do=findComment&comment=108021 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!
  7. 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.
  8. 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.
  9. 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: https://xpenology.com/forum/topic/14091-esxi-unable-to-expand-syno-volume-even-after-disk-space-increased/ You have an ext4 filesystem and you are not using lvm, and you have a one-disk
  10. Try the alternate tree roots, some information here: https://xpenology.com/forum/topic/48356-help-volume-crashed-shr-btrfs/?do=findComment&comment=217210
  11. You need to be more careful with the syntax. sudo mount -o recovery,ro /dev/vg1000/lv /volume1
  12. Try this one next: https://xpenology.com/forum/topic/14337-volume-crash-after-4-months-of-stability/?do=findComment&comment=107985
  13. 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.
  14. 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
  15. 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
  16. Jun/default drivers for DS918+ support I219-V on PCI ID's 1570 and 15B8 only (e1000e driver). Yours is 15FA (clearly newer) https://xpenology.com/forum/topic/14127-guide-to-native-drivers-dsm-621-on-ds918/ The DS918+ extra.lzma/extra2.lzma 0.13.3 driver compilation contains the following PCI ID's (latest 15E3, older than yours) https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ So unless someone has a newer compile of e1000e you are probably SOL...
  17. 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: https://kb.synology.com/en-us/DSM/help/DSM/StorageManager/volume_btrfs_dedup?version=7
  18. 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.
  19. Check for bad SATA cable or it is routed so that the connector is breaking contact.
  20. root is from md0. Did you try mdadm --scan --assemble? Try not to modify anything other than /dev/md0 from Linux.
  21. What does it say when access denied? Should be able to log in ssh if it was configured before. Alternative is to set up a linux boot environment and hten manually start /dev/md0 and mount the partition temporarily.
  22. Obviously we need to prove that you do not have a fs mounted on /volume1 per the previous post (incidentally, it looks like you have some jobs - ie Plex - that have written to /volume1 and in the absence of the mounted filesystem, those files are in the root filesystem. You should stop your Plex from running while this is going on) I would see if you can do a restore (copy out) using the alternate tree roots before you try and make corrections from the filesystem. http://www.infotinks.com/btrfs-restoring-a-corrupt-filesystem-from-another-tree-location/ If nothing
  23. I think perhaps you mean that you see a /volume1 folder. If the volume is not mounted, that folder will be blank. Check to see what volumes have been mounted with df -v at the command line. You should see a /volume1 entry connected to your /dev/lv device if it is mounted successfully. You can also sudo mount from the command line and any unmounted but valid volumes will be mounted (or you will receive an error message as to why they cannot be).