How to partition SSD to HDD correctly for Plesk

[Nayeem1]

I am running a CentOS 6.6 (Final) with Plesk 12.0.18 Update #27 on my dedicated server. I was advised to upgrade my server to one that has a SSD due to better performance. What they failed to tell me was that I would need to perform additional configurations so that Plesk stores the subscription files in the /HDD-var/ directory and NOT the /SDD-var/ directory. Current server

I am by no means a sys admin, so please be as detailed as possible (thank you). Here are my questions:

1. How difficult would it be (I am a quick learner and can follow exact steps or directions very well) to make Plesk store the files on the HDD rather than the SDD?
2. Is this something I should undertake or is this very difficult to do?
3. If I perform these changes, will they revert to the old way if I perform Plesk updates? Or will the changes I make become permanent?

Perhaps I should be asking different questions than what I am, but at the moment this is all I know and what I believe to be the solution. Any help would be immensely appreciated. I really don’t want to get another server then go through the process of making it into a Name Server, Security & Hardening processes and configurations, application downloads, etc. Please help!!

SSH: df -h

Filesystem Size Used Avail Use% Mounted on

/dev/md1 4.0G 916M 3.1G 23% /

/dev/mapper/ssd-usr 3.9G 1.9G 1.8G 51% /usr

/dev/mapper/ssd-var 3.9G 3.7G 2.7M 100% /var (Plesk is storing data here)

/dev/mapper/ssd-home 3.9G 792M 2.9G 22% /home (Would also like this data to be on the HDD)

/dev/mapper/hdd-data 3.9G 8.0M 3.7G 1% /data (Plesk should be saving data here)

none 16G 288K 16G 1% /tmp



I ran the fdisk -l command via ssh:

Disk /dev/sdb: 240.1 GB, 240057409536 bytes

255 heads, 63 sectors/track, 29185 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x11aab2d9



Device Boot Start End Blocks Id System

/dev/sdb1 1 523 4194304 fd Linux raid autodetect

Partition 1 does not end on cylinder boundary.

/dev/sdb2 523 784 2097152 82 Linux swap / Solaris

Partition 2 does not end on cylinder boundary.

/dev/sdb3 784 29186 228138584 fd Linux raid autodetect

Partition 3 does not end on cylinder boundary.



Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes

81 heads, 63 sectors/track, 765633 cylinders

Units = cylinders of 5103 * 512 = 2612736 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0xbce36541



Device Boot Start End Blocks Id System

/dev/sdc1 1 765634 1953513560 fd Linux raid autodetect



Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes

81 heads, 63 sectors/track, 765633 cylinders

Units = cylinders of 5103 * 512 = 2612736 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x59c72bb0



Device Boot Start End Blocks Id System

/dev/sdd1 1 765634 1953513560 fd Linux raid autodetect



Disk /dev/sda: 240.1 GB, 240057409536 bytes

255 heads, 63 sectors/track, 29185 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x28ac7c73



Device Boot Start End Blocks Id System

/dev/sda1 1 523 4194304 fd Linux raid autodetect

Partition 1 does not end on cylinder boundary.

/dev/sda2 523 784 2097152 82 Linux swap / Solaris

Partition 2 does not end on cylinder boundary.

/dev/sda3 784 29186 228138584 fd Linux raid autodetect

Partition 3 does not end on cylinder boundary.



Disk /dev/md3: 233.6 GB, 233613819904 bytes

2 heads, 4 sectors/track, 57034624 cylinders

Units = cylinders of 8 * 512 = 4096 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x00000000





Disk /dev/md1: 4294 MB, 4294901760 bytes

2 heads, 4 sectors/track, 1048560 cylinders

Units = cylinders of 8 * 512 = 4096 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x00000000





Disk /dev/md11: 2000.4 GB, 2000397795328 bytes

2 heads, 4 sectors/track, 488378368 cylinders

Units = cylinders of 8 * 512 = 4096 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x00000000





Disk /dev/mapper/hdd-data: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x00000000





Disk /dev/mapper/ssd-usr: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x00000000





Disk /dev/mapper/ssd-var: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x00000000





Disk /dev/mapper/ssd-home: 4294 MB, 4294967296 bytes

255 heads, 63 sectors/track, 522 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x00000000

 

[IgorG]

You can use transvhosts.pl utility for relocation vhosts directories to new location on HDD - http://kb.odin.com/en/1186
Recent discussion of mailboxes relocation is here - http://talk.plesk.com/threads/mount-new-harddisk-without-loosing-data-settings.328936
I hope it will help and give you direction.

 

[Nayeem1]

thanks for the response. I’ve reviewed the info and can’t make heads or tails of it. Do you know anyone who can fix this for me? I’d be willing to pay them for their time. I’m assuming it shouldn't take a whole lot of time if they know what they are doing. What do you think?

 

[IgorG]

You can order Plesk per-incident support at http://odin.com/hcap/support/buy-support/. Support team will contact you as soon as purchase is processed, and they will do the best to resolve it.