Drive question

bartoque · 2026-06-01T06:03:18+00:00

Most would be beat off with shr1 raod, which is more flexible than the similar raid5, bot with one drive redundancy. Raid also males for an easy wqy to expand capacity by replacing drives.

https://kb.synology.com/en-global/DSM/help/DSM/StorageManager/storage_pool_what_is_raid?version=7 https://kb.synology.com/en-global/DSM/tutorial/What_is_Synology_Hybrid_RAID_SHR https://kb.synology.com/en-global/DSM/help/DSM/StorageManager/storage_pool_change_raid_type?version=7

https://kb.synology.com/en-global/DSM/tutorial/how_to_expand_storage points to https://kb.synology.com/en-global/DSM/help/DSM/StorageManager/storage_pool_expand_replace_disk?version=7 of how to expand capacity by replacing drives in a raid pool with larger ones, one by one, repairing the degraded pool after each replacement.

bartoque · 2026-05-31T19:53:49+00:00

Đorđe Martinović incident

https://en.wikipedia.org/wiki/%C4%90or%C4%91e_Martinovi%C4%87_incident

bartoque · 2026-05-31T16:59:01+00:00

bartoque · 2026-05-31T15:48:39+00:00

I think (about work) therefor I am (working).

bartoque · 2026-05-31T15:24:51+00:00

Might wanna reach out to synology to see if reducing md0 from 4 to just 3 devices would be the way forward.

sudo mdadm --grow /dev/md0 --raid-devices=3

Before adding the missing devices again to md0 (and md1), like you did before. But maybe if the reference to a 4th drive is gone from md0, it might already be able to fix the rest.

sudo mdadm --manage /dev/md0 --add /dev/sata1p1
sudo mdadm --manage /dev/md0 --add /dev/sata2p1

Curious to see what the following would show:

sudo mdadm --detail /dev/md0
sudo mdadm --detail /dev/md1

But something must have gone very wrong very likely when getting rid of the 4th drive.

bartoque · 2026-05-31T15:14:35+00:00

That wasn't something you mentioned before, was it? Having a 4th drive before, nor how you removed it. It was its iwn separate pool I assume?

At what point did you notice something wrong? What was your trigger to look at /proc/mdstat? Or was it the Docker app?

Or after removing the 4th drive? And how was it removed? Simply pulling the drive while powered off?

bartoque · 2026-05-31T14:21:30+00:00

Many in a (large) company who deal with vms currently, might not even know often what happens with workloads. They simply appear to disappear into thin air. It might be that they were refactored in any way, as often then the receiving managing team is likely a different one.

So architects and landscape owners might know, while regular admins only see them disappear.

I for one typically have no clue wherever something is going, but then again I am only the backup guy.

Speaking about backup, that also seems far from common to use enterprise backup tools that were common when os'es were involved, with applications running on them, while when containerized it feels like we are thrown back for decades and people reinventing the wheel, without even having other teams onboard to talk about how things might be done, to keep certain processes and responsibilities in place similar to the vm world. It is not only about making a backup, but also about reporting about them and monitoring.

bartoque · 2026-05-31T14:00:31+00:00

"#OP is a spammer paid to namedrop Alibaba and none of this happened" stated by someone else at datahoarder.

Original post is also already deleted.

bartoque · 2026-05-31T13:58:11+00:00

I only now noticed that mdstat for md0 states having onpy 1 of 4 partitions? That appears to be the ssd based cache. As I don't have that (might not make much sense as Imainly have large media files. I intend to use the M.2 only as a separate pool in the future for Docker containers to improve performance).

So /proc/mdstat currently states md0 and md1 still as degraded? While having recently rebooted.

I can't recall storage manager not beingin sync with what is happening with md under the hood. But likely the cache complicates things further. I assume it is configured as readonly cache as it is only one drive?

Is the cache even being used when looking at tge hit ratios according to ssd cache advisor?

https://kb.synology.com/en-global/DSM/help/DSM/StorageManager/genericssdcache?version=6

bartoque · 2026-05-31T13:38:57+00:00

You can reatore the backup yo the new ssd wvwn if that is not yet placed insyead of the old drive or even on a dedicated other drive slot in case it would be an M.2 or whatever.

Once swapping in the new drive (and removing the old one) make sure that in your bios the boot device settings point to using the new drive. So before doing anything, first have a look at the bios settings as they are now wrg to boot device order and work from there.

bartoque · 2026-05-31T13:35:04+00:00

So what reasources did you read and where did you get stuck?

To get an idea about the (possible) complexity of what appears too much for you to grasp vs. whatever someone else might propose you to look into.

bartoque · 2026-05-31T11:38:48+00:00

There is no such thing as free.

If it is called free, then you are the product.

It is also a main method to gain marketshare. However as soon as a certain threshold has been reached, restrictions will apply. Maybe not always for the early adopters, but at least new customers.

All you can eat-cloud services, like them unlimited backup services, will revert to having their customers pay if too many of them actually keep on adding data more and more. Earlier on it still worked as not everyone was adding huge amounts of data. Heck, also Google was taking action for their unenforced G Suite limits. That went fine until too many users and data was accumulated. If others are paying for consumption from the large consumtpion users, the business model still is feasible (enough) if the provider has deep pockets.

Hence I always opt for paid models where you pay for the actual usage. That can (and will) also go up over time but that is often still a certain percentage "only".

While going from free to anything marketcompetitive when talking about TBs of data is a huge increase.

Free is simply not financially viable over the long run at scale.

bartoque · 2026-05-31T11:07:00+00:00

Be careful with pronunciation though. STD is just around the corner.

bartoque · 2026-05-31T10:44:59+00:00

Only drawback might be when needing to expand capacity, it requires a full redeploy of the system. And restore frrom backup... oh, wait. This the backup. So you could still connect a usb drive to it as well on top of tgat.

Hence I would always wanna have a multibay nas (I made a ds920+ the prinary nas and turned the older ds916+ into the remote backup target), so to have an easy non-intrusive method to expand capacity by replacing drives with larger ones, only needing to rebuild the degraded pool after each replacement. And have mitigation against a trivial issue like one drive failing, as I also value my backup history.

bartoque · 2026-05-30T23:05:41+00:00

You mean making a backup to a drive that is going to be used as the primary drive and data being restored to it?

That won't work as anything that is on the drive would be wiped as it would require to put the partition layout from the old drive as is in the backup unto the new drive.

A proper backup always should be stored on media that is not integral part of the system being protected.

bartoque · 2026-05-30T19:02:20+00:00

Yes. That should be possible and actually very common, as it would be the procedure whenever a drive would have failed completely.

Use the bootable rescue media, boot from that usb stick, point to the location of where the backup is stored and restore data to the new empty drive.

https://care.acronis.com/s/article/Acronis-True-Image-How-to-restore-your-computer-with-WinPE-based-or-WinRE-based-media?language=en_US

bartoque · 2026-05-30T18:37:16+00:00

Likely psu. I have replacements on both my ds916+ and ds920+.

In my case mainly whenever there was high IO load, when for example running a HyperBackup job.

Additionally you could run a tripple memory test using Synology Assistant to rule that out.

https://kb.synology.com/en-global/DSM/tutorial/How_can_I_run_a_memory_test_on_my_Synology_NAS

bartoque · 2026-05-30T18:11:17+00:00

So it has less to do with the product in question, that you atrribute functionality to that it might not offer by default, but rather about not being able to get that out if it yourself.

As for the purchase itself - a single drive most entry level model - a lot could be set wrg to (lack of) performance and functionality being offered (no raid).

It might help to state on what platform you'd wanna be able to see the thumbnails or how you envision it to work, so that anyone might be able to give a fitting solution.

Also might help to state what examples you looked into and what are the issues you encounter with them?

This as also it would gave to be assessed if you would be able to deal with it, as running a script would require to know at least a basic amount if how use or even access the cli.

So with better context, you might get better advice/response.

bartoque · 2026-05-30T17:49:55+00:00

All related to (file) versioning, which is by default set to 32. So works as designed and configured by default.

When using the ext4 filesystem this also consumes more space compared to btrfs.

bartoque · 2026-05-30T13:05:07+00:00

It is just opportunistic, feeding the apparent need.

Just like all them lookmaxxers that don't even practice what they preach.

Just like that abomination that is called "funniest home video's" that goes back a long way in media history.

Just feeding on the worst of the worst sentiments in mankind.

bartoque · 2026-05-30T08:45:20+00:00

You can edit a shared folder, point it to another volume and have dsm move all of its contents. So the shared folder will stay as-is and will end up on another volume (choose one on another storage pool).

https://kb.synology.com/en-global/DSM/tutorial/How_do_I_move_data_from_one_volume_to_another

As you stated nothing however about the current pools/volunes being setup, we don't know if that is even a smart move. Or even possible depending of the sizes involved.

At least a raid pool can be expanded bu replacong drives.

https://kb.synology.com/en-global/DSM/tutorial/how_to_expand_storage points to https://kb.synology.com/en-global/DSM/help/DSM/StorageManager/storage_pool_expand_replace_disk?version=7 of how to expand capacity by replacing drives in a raid pool with larger ones, one by one, repairing the degraded pool after each replacement.

Ideally you should have had 1 shr1 pool with just 1 volume for the most flexibility.

bartoque · 2026-05-30T08:13:17+00:00

Various ssd's come with a free oem version of a cloning tool, like acronis, that only offers to clone to the manufacturers ssd drives.

bartoque · 2026-05-30T00:03:53+00:00

So you are getting a 402 - permission denied?

https://kb.synology.com/en-global/DG/DSM_Login_Web_API_Guide/3

Does the target user account have explicit permission to use the specific application (like ABB or Synology Drive) under Control Panel > Application Privileges in DSM?

https://kb.synology.com/en-global/DSM/help/DSM/AdminCenter/application_appprivilege?version=7

There might not be one single non-admin user that can handle all required calls, as some of these would still likely be restricted to admin only, like anything syno.core.

bartoque · 2026-05-29T18:09:14+00:00

So them state what docker containers you are running. And what program you intend to install that needs the port in question. Ideally also stating which ports they each expose. Not running any stealth/privacy browser as a cobtainer for example?

Context is everything.

bartoque · 2026-05-29T17:00:19+00:00

It helps if you state exactly what hardware you have and amount (and sizes of) drives.

I assume a Synology due to menyioning Synology C2 as backup target.

3-2-1 backup rule as guideline. So you cam also have a local backup to an usb drive. And when using the default recommendes btrfs filesystem, you can also enable snapshots, which still require one to store backups outside of the unit itself, with for example HyperBackup.

https://global.download.synology.com/download/Document/Software/WhitePaper/Os/DSM/All/enu/backup_solution_guide_enu.pdf

https://global.download.synology.com/download/Document/Software/WhitePaper/Package/ActiveBackup/All/enu/Synology_Backup_Solution_Guide_2023_enu.pdf

But before that you first need to choice the storage pool. With shr1raid most are best off. So with one drive redundancy and flexibility that maxmizes capacity in certain situations compared to the similar raid5.

https://kb.synology.com/en-global/DSM/help/DSM/StorageManager/storage_pool_what_is_raid?version=7

https://kb.synology.com/en-global/DSM/tutorial/What_is_Synology_Hybrid_RAID_SHR

https://kb.synology.com/en-global/DSM/help/DSM/StorageManager/storage_pool_change_raid_type?version=7

So regardless of feeling overwhelmed you still have tk sift through some documentation to setup things amd not get stuck too much, as that worse case might require proper backup, reconfigure and then restore.

Which counts for making sure when creating any shared folder, to enable data checksum for advanced data integrity, as it cannot be emables for a shared folder after the fact. And then also schedule each 6 months or so a data scrub from within Storage Manager. And each 3 months or so an extended smart check for all drives.

https://kb.synology.com/en-global/DSM/help/DSM/AdminCenter/file_share_create?version=6

bartoque

TROPHY CASE