flyride

Do you have multiple volumes in the storage pool? If so, it won't know which one to expand. Once your expansion is complete and are absolutely certain no restripe/resync/other activities are occurring on your system, and you still don't see all the usable space in the storage pool allocated to a volume, you can manually grow it in this way (assuming btrfs and example of volume1): $ sudo btrfs filesystem resize max /volume1

Did you change your BIOS to boot in Legacy mode? ACPI boot is not supported on 1.03b.

Lots of people are using 6.2.2. But you haven't posted enough information for anyone to provide advice. Perhaps you should research compatibility with your hardware platform, just a little... maybe? Try reviewing: https://xpenology.com/forum/topic/9392-general-faq/?tab=comments#comment-113011 https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ https://xpenology.com/forum/forum/78-dsm-updates-reporting/(specifically the 6.2.2 threads) https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/

AS3104T uses a Broadcom 57781 NIC. https://www.kitguru.net/professional/networking/simon-crisp/asustor-as3104t-4-bay-nas-review/3/

https://xpenology.com/forum/forum/91-additional-compiled-modules/

You can try and update the SMART database. In Storage Manager, go to HDD/SDD, General, then scroll to the bottom and click Update Now. If that doesn't work, you can turn off the lifespan warning with the adjacent checkbox.

That particular server has been up on 6.1.x since October 2017. It's a pretty complicated build, so I haven't rushed to upgrade it, although I think all its services are now supportable on 1.03b and DSM 6.2.2. The only inbound services on my network are IP and port firewalled VPN termination points and a guacamole (remote access proxy) server. Personally, I wouldn't ever expose a Synology server directly to the Internet for any reason. Therefore, I don't have too much heartburn about the latest security patches not being available. Even on 6.2.2, Synology lags so far behind core OS support, I'm not sure it matters all that much.

A clean install only requires a single write of the array, so it will be the same as a RAID5 or RAID1 using the same size member devices.

If the stream does not require transcoding then your CPU usage will be negligible.

On a separate note, why do you need to transcode at all with the iPad Mini, it's got better than 1080p resolution so it should not need to. Are your client settings correct to not force transcoding unless required? Also, you might be transcoding audio which does not use Quicksync hardware?

You would be unable to check the box for hardware transcoding on Plex if it was not working in some capacity. Plex does not use the syno codec activation (you bought Plex Pass to unlock the hardware transcoding support for that product). To clarify, the existence of /dev/dri lets you know that an Intel i915 driver has initialized the hardware. "ls /dev/dri" The driver may not be working well with the version of QuickSync embedded your J4105 silicon, or Plex itself may not like the J4105 hardware or driver. You can try and change the i915 driver by modifying extra.lzma Or, take it up with Plex. It's their software.

Virtualization is always an option.

No, that will not work.

https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ Please read at least a few of the posts in the thread!

These are all settings in DSM.

Here are three topics from the very prominently featured FAQs that may be considered as such a warning: https://xpenology.com/forum/topic/9392-general-faq/?tab=comments#comment-95507 https://xpenology.com/forum/topic/9392-general-faq/?tab=comments#comment-113011 https://xpenology.com/forum/topic/9394-installation-faq/?tab=comments#comment-81100

The purpose of this thread is to help with the selection of a loader (based on its supported DSM versions) and a DSM platform (based on its feature and hardware support). Can you give an explanation or example of what could be communicated by your request? I'm not sure what to report. ESXi is just a hardware spec like the many bare metal choices. All the 6.x loaders support baremetal or ESXi boot menu option. AFAIK the only difference between selecting a baremetal or ESXi option is to affect how the loader tries to hide the VID/PID of the boot device, which is cosmetic only.

Core support is a kernel compile parameter, and we have no ability to rebuild the Synology kernel. Based on this additional feedback, I think your motherboard isn't actually booting in Legacy mode. Some BIOSes are not entirely obvious in how this is done. Sometimes you need to turn on or off a "CSM" (compatibility) mode in addition to setting the Legacy boot device type.

Generally modern Intel hardware should be compatible. Since you have a CT card, try BIOS disabling your on-board LAN. Also, Sometimes DS3617xs has problems, try DS3615xs and see if it works. I realize you want all 12 threads to work, but you will lose very little if you turn off Hyperthreading.

Did you change to Legacy (non-EFI) boot?

um, This link from the FAQ: https://xpenology.com/forum/topic/9394-installation-faq/?do=findComment&comment=81092 And this link from the Guide section: https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ Both of these discuss the relative merits of each bootloader and platform and some discussion of compatible hardware.

with this line: support_syno_hybrid_raid = "yes" above supportphoto="yes" ? Cool! Thanks for this supercool hint! That's the one. I think you also must comment out #supportraidgroup="yes"

At some point you have to make some decisions on which features you want to support. NVMe direct support is only in DS918. RAIDF1 support (if you ever need it) is only in 3615/3617. 10Gbe and SAS support is better in 3615/3617 but somewhat mitigated if you experiment with add-in drivers from IG-88. My main system is similar to yours - 10Gbe, and I use enterprise SATA SSD drives now so RAIDF1 is important. I also have two U.2 NVMe drives, and the only way I found to get everything to work was to use ESXi to run DS3615 (for RAID F1 and 10Gbe support) and present the NVMe devices via RDM.

You can turn on SHR with 3615/3617 by changing two lines in /etc.defaults/synoinfo.conf

DSM installs OS and data to the same devices. This is intrinsic to the system and not really negotiable. The USB key is not a boot drive, it's a bootloader that stages the OS to be loaded from the partitions on the disk devices. I think it is "possible" to use the ESXi version of the bootloader and install it to a generic boot device in lieu of the USB key, but it's not straightforward. It's also "possible" to use the USB devices in DSM but only after modifying the disk bitmask, which you can't easily do until after you've installed (which you can't do because there is no addressable disk in the system). Bottom line, everything you are trying to do will be a lot of trouble and will probably break your system on every update. With all candor, the Brix platform really isn't suitable for DSM and you should find something else.