[Guide] How to expand the volume if DSM doesn't want to

[Sandstorm]

I confirm. Solution 2 works. This issue has been resolved in DSM 5.1-5022 Update 3.

 

Update your DSM, and Manage your Volume. It will be expanded.

 

Just wanted to say that I am having this problem and I am on DSM 5.1-5022 Update 3 so I don't think that is the case.

 

Added a 5th Western Digital Red 3TB and I get the option to expand, but it just fails and goes back to saying "You can expand size to about 11160".

 

I will be trying the guide in this article in the next couple days but figured I would post some screencaps if anyone cares to take a look.

 

https://www.dropbox.com/s/b7ofykw9k3f4eli/Volume.JPG?dl=0

 

https://www.dropbox.com/s/nmb5nezkxuj566r/DiskGroup.JPG?dl=0

 

https://www.dropbox.com/s/kv9pmfq7ze73ewa/HDD_SSD.JPG?dl=0

 

https://www.dropbox.com/s/btnpehk4vr82wyi/log.JPG?dl=0

[Sandstorm]

Just to follow up...I followed the guide and ran into only one problem along that way. Specifically where the guide says:

 

"Run a file system check. This may take some time":

 

sudo fsck.ext4 -fvp /dev/vg1000/lv

 

I had to use

 

sudo fsck.ext4 -fvp /dev/vg1/volume_1

 

I am guessing everyone's disk groups and volumes will be named differently but I didn't see in the guide how to verify the names of these.

 

Just wanted to say thank you for helping me get all the disk's recognized!

[clipto]

Let me first say I am a noob at Linux, the link in the first post wasnt working for me, so I did this:

 

I run Xpenology, latest version on a HP DL380G6 with the latest VMWare HP custom 6 version (the one of jan. 2016).

Installed it on a 200Gb disk, but need it to be 300Gb now.

 

It is in Dutch:

 

I followed this link with the following commands:

http://www.mauchle.name/blog/?p=235

 

enable ssh
open winscp with root user:

syno_poweroff_task -d 
(turns everything off except ssh)

vgchange -ay vg1000 
(this is the volume name from cat /etc/fstab)

fsck.ext4 -v -n -f /dev/vg1000/lv 
(no changes)

cat /etc/fstab

umount /volume1

mount 
(check if volume is unmounted)

fsck.ext4 -fvp /dev/vg1000/lv
(takes a while)

/sbin/resize2fs -fpF /dev/vg1000/lv

** the filesystem is already 51220480 blocks long. Nothing to do! (Device size is 51220480 blocks long)

 

So at the resize step I get this error:

** the filesystem is already 51220480 blocks long. Nothing to do! (Device size is 51220480 blocks long)

 

What to do next?

I'm stuck...