![]() ![]() Verify the /dev/mdX array device under the LVM with the pvdisplay command, and use that for the commands below. NOTE: If df returns something like /dev/vgX/volume_X instead of a /dev/md device, then your system is using LVM. Sign in via SSH, and determine your volume array device (should be /dev/md2 using your example screenshots) $ df | fgrep volume1 Needless to say, have a backup before you try this. Note that even that configuration is implemented within DSM as an array - in your case a 1-disk RAID1. Your situation is probably the least complicated - a Basic, single disk ext4. ![]() This has varying levels of complexity depending upon the array type, whether you are using LVM, whether you are using SHR, and whether you are using btrfs or ext4. To grow a volume manually, the general tasks are: expand the partition(s) on the drive(s) hosting the array, expand the array, and then expand the volume on the array. ![]() In order to increase the size of an MBR disk to more than 2TB, the partition type will need to be changed to GPT, which is beyond the scope of this advice. It also underscores the fact that DSM is really intended to manage the drives directly instead of ESXi or a RAID controller providing disk redundancy.ĮDIT: One limitation of this strategy is if the disk was initially partitioned as MBR, which is possible if the initial size of the disk was less than 2TB. The issue is that DSM only does an automatic expansion when a drive add/replace event occurs. This isn't triggered when you deliberately expand a basic volume using virtualized storage - a user action that would never occur on a "real" Synology hardware system. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |