Model Name TS-451+
BIOS Version QW37AR41
Total RAM 8 GB (7 GB usable)
Memory Slots 2 (4 GB / 4 GB)
Firmware Version QTS 5.2.9.3499 Build 20260514
Hello Community,
Here’s the setup:
3x HDD in RAID 5 [DATA] (Seagate - ST4000VN008-2DR166 - 3.64 TB (4 TB))
- sda (bay 1)
- sdb (bay 2)
- sdd (bay 3) No idea why this became sdD…
1x SSD in RAID 1 [SYSTEM] (Samsung - 870 QVO 1TB - 931.51 GB (1 TB))
- sdc (bay 4)
The SSD (sdc) was previously a Crucial 250GB, which was full, and I cloned it to the 1TB SSD using DD.
Now, 750 GB is just hanging in limbo and I can’t expand the SSD with the usual methods.
When setting up, I didn’t do anything fancy.
RAID 5 = 8 TB, no partitions, data / videos / photos, etc.
The SSD was forced to RAID 1 = also no partitions, apps
What the wizard made out of this is a mystery to me.
If I’m interpreting the mdstat output correctly, I would need to expand the partition md1 / sdc3. But sdc5, sdc4, and sdc3 are in the way:
md1 : active raid1 sdc3[0] - 227216384 blocks
md321 : active raid1 sdc5[0] - 6702656 blocks
md13 : active raid1 sdb4[0] sdc4[32] sdd4[2] sda4[1] - 458880 blocks
md9 : active raid1 sdb1[0] sdc1[3] sdd1[2] sda1[1] - 530048 blocks
Losing data on md321, md13, and md9 would be acceptable for me.
But md1 contains the Multimedia Console data (thumbnails, face recognition) which I’d prefer not to have to regenerate.
On a Celeron, that takes weeks or months, and since the NAS is in the living room, there would be constant HDD noise.
For md13 and md9, it should be enough if I temporarily remove them from RAID1 and then add them back. (RAID across ALL drives)
I have no idea where md321 points to, maybe overprovisioning.
But now there’s also vg., lv., drbd., mapper, and cachedev. coming into play, which is where I’m pretty lost.
Can anyone offer some help with this issue?
Maybe some alternative approaches?
Thanks and regards,
Alexander


