flyride

Not sure what else you are using the virtualized environment and storage for... but if it is intended mostly to run DSM, then yes, passthrough of physical drives is preferable. btrfs on DSM will provide RAID, RAIDF1 (if you are using SSD's), and SHR (for dissimilar drives). btrfs on DSM, combined with array duties will offer inline bitrot and file corruption repair, plus snapshots and snapshot replication. I have a very similar system to yours running ESXi. One NVMe SSD hosting the VM configurations and virtualized storage for non-DSM VM's. SATA controller and 10GBe passthrough for DSM full management since that's the primary workload.

This is not ideal. DSM is intended to have access to the physical disks for the features you mention. Why use DSM over a regular Linux server if you aren't going to take advantage of the disk optimizations? Storage pool should be Basic for a single virtual disk. btrfs is still superior if you intend to run the docker client in DSM. Otherwise the filesystem type doesn't really matter all that much in this neutered state.

You could have mentioned that you found, and are not able to use the Syno builds. "qemu guest agent bsd" https://github.com/aborche/qemu-guest-agent

https://www.synology.com/en-us/knowledgebase/DSM/tutorial/Virtualization/How_to_install_Synology_Guest_Agent_for_VMM_on_your_virtual_machine To find this, I put the following in this "Google" site: synology guest agent vmm

SHR is not a filesystem. It's an array. If you have only one drive, it can be called a JBOD, RAID0, SHR, Basic, they are all essentially the same thing. It doesn't matter. You have a one-disk SHR/Basic drive now (which is just a RAID0) applying to your HDD Partition #3. Depending on the version of DSM and hardware platform and the way you configured your original array, Synology may call an array a volume in a storage pool, or just a volume. Install SSD, create a NEW separate storage pool/volume. You don't need two drives, you can create a Basic or SHR with one drive. As soon as you do this, partitions #1 and #2 will be created and common across all devices. They ignore the layout of other arrays/storage pools/etc. Once you have two volumes (one on HDD and one on SSD), you can even move shares straight over using Control Panel. Again, packages may need to be uninstalled/reinstalled and data restored if applicable. There are lots of online resources on how to do that (move Synology packages from one volume to another). When all is complete, shutdown, remove HDD and done.

DSM has min three partitions as you see. #1 is DSM itself (i.e. Linux) #2 is swap #3 and additional are for volumes built on the storage pool As soon as you install a drive it is not Initialized. That means the above partition structure is not present. The first operation you do on the disk will cause it to create the DSM/swap partitions and it will be shown as Initialized. Partition #1 and #2 are now a RAID 1 with the existing disk(s) so no need to manually copy anything. Then all you have is your volume data. Generally there isn't anything at the root of volume partition #3 worth keeping (usually metadata only etc). However, you might have packages installed there, so just reinstall them to new volume. All your general file-based volume data is downstream of the mount /volumeX.

Sorry if this is is a dumb question, but why are you trying to do this? If there is only 22Gb of storage to migrate, install the SSD, create a new volume on it, copy files over, delete the original volume, done.

Mellanox cards work great, I use Connect X-3's on my systems, directly attached with DACs.

I don't know much about debugfs but it's really for kernel debugging and passing kernel parameters to userspace. And I am pretty sure you can't use it on a mounted ext4 filesystem. I know you are trying not to offload your files and rebuild with the hope of a quick easy fix. I don't mean to be preachy, but trying to edit your filesystem directly is a path that increasingly puts your data at risk. If fsck can't fix it, there is something significantly wrong.

It doesn't matter. You can upgrade a single disk to SHR or RAID at any time.

Install the new drive, create a new volume. You can actually move entire shares from the old volumes to the new one in one step, via the Control Panel | Shared Folder dialog. It will take awhile but no reconfiguration is required. When the old volumes are empty, just delete them and take the old drives out.

Yes, hardware transcoding support only exists in DS918+. However, if you read the post updates, 6.2.3 is preferred for that platform.

https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/

The FAQ addresses this directly: https://xpenology.com/forum/topic/9392-general-faq/?do=findComment&comment=82389

The activation file is for the Synology video app, nothing to do with Plex/Plex Pass.

Can you confirm your filesystem is on ext4? AFAIK Docker is not supported unless you are running on btrfs. Could be part of your problem. # cat /etc/fstab

I just use the edge of a razor blade and lift that pin clean off the PCB... no fuss no muss

No that will not work. You can leave the existing serial in the loader alone if you like.

Nope, the offending file is gone. Have you rebooted your NAS since completing the items in post #3? Is the issue still happening?

A drive that uses the 3.3V pin for reset control will just fail to spin up. You can't break it by plugging it in.

Probably one of your two NICs is not supported via the driverset you are running. This is fairly common with recent Intel motherboards. You may be able to get the second NIC working with IG-88's extra.lzma. No other configuration required for LAN2.

Did you look for it with "ls -la /.xpenoboot" The leading period is the syntax that hides the folder from a regular directory display.

Yes, they work. As far as modifying the third pin, you won't know until you try the drive. I've encountered two identical white label drives (same model #) where one required the mod, and the other did not.

I don't think anyone has ever posted a serial generator for DS918+

What loader? What DSM platform did you select?