How is an added 2TB direct disk mounted?

How many added disks

The add-on is a 2TB NVMe disk at $84.7 a month, available as 0, 1 or 2 disks.

With one added disk the machine carries three direct disks: two of 1TB and one of 2TB. With two, it carries four.

A new disk joins no hardware array and arrives without a prepared filesystem.

Because the system already sits on a default disk, an added disk turns up empty after boot.

Compare sizes in lsblk before partitioning, and never run a partition command against the 1TB system disk.

Partitioning on Linux

Device names can move with slots, so size identifies the 2TB disk more reliably than the name does.

After partitioning comes the filesystem and the mount entry; without them the workload still writes to the system disk.

Proxmox can turn the new disk into a directory or an LVM store and hand it to virtual machines as disk storage.

All of this happens inside the system. The order page offers no hardware RAID option.

The default pair adds up to roughly 2TB. With one added 2TB disk mounted alongside, three disks come to roughly 4TB.

How capacity adds up

An unmounted disk never appears in the df total.

Do not mirror the 2TB disk against one of the 1TB disks, as usable space then follows the smaller one.

On Windows, bring the disk online, initialise it as GPT, then create a simple volume.

One added disk is $84.7 a month and two are $169.4, both inside the same monthly rent.

A 128GB machine rents for $454.8 a month and a 256GB machine for $612.7, neither figure including added disks.

How the cost enters the rent

Quarterly multiplies by 3, semiannual by 6 and annual by 12, with no discount.

1 Gbps bandwidth adds $245.0, 2 Gbps adds $742.7, and each extra IPv4 costs $1.6.

There is no setup fee. An added disk sits in the same machine's monthly rent rather than on a separate call-out invoice.

Changing the disk count means a new order at the new configuration, not an array edit inside the console.

Once the mount succeeds, df shows the new mount point at close to 2TB.

Checks after mounting

Write a test file and read it back to confirm the path lands on the new disk rather than a subdirectory of the system disk.

Where the order records an added-disk count of 0, the machine holds the default two 1TB disks only.

State the order number, the expected disk count and the lsblk output in the ticket.

Once connectable, the console shows SSH or RDP, with the password masked by default and available to reveal and copy.

Write the mount entry against a stable identifier so a change in disk order after a reboot cannot mount the wrong device.

Alongside the default disks

Keep the system disk reinstallable on its own, and avoid binding the data disk into an array that has to be rebuilt at the same time.

The memory tier is fixed at checkout, and an added disk does not raise memory along the way.

The facility is Tokyo, Japan, and one tenant holds one machine.

Linux uses SSH; picking Windows Server Standard or Datacenter switches access to RDP.

The configuration order runs memory first, then added disk count, then bandwidth, addresses and system.

Identify the disk before mounting

An added 2TB NVMe disk costs $84.7 a month and sits in the same machine as the default pair of 1TB disks. With one added, the disk rows should number three: two close to 1TB and one close to 2TB. With two added, four rows. A missing row is a reason to stop before partitioning and check the disk count on the order first.

Partition commands belong only to the row close to 2TB. Formatting the row close to 1TB that already carries the root partition leaves the system unable to boot. Reading the SIZE column is safer than reading the nvme index, which can swap places after a reboot or after a disk is added.

A GPT partition table suits a 2TB disk. One partition is enough unless separate directories are genuinely needed. With the filesystem built, pick an empty directory such as /data as the mount point, write that line into the mount configuration, and use UUID or PARTUUID so a change in disk order at the next boot cannot point the data directory at the system disk.

Proxmox users can add that directory as storage under the datacenter. Once virtual machine images live there, reinstalling the system disk does not delete those files by itself, though the installer still has to be checked for a tick against the 2TB disk beforehand: installers often list every empty disk by default.

Capacity adds up one disk at a time. Two 1TB disks come to about 2TB, one added 2TB disk takes it to about 4TB, and a second added disk to about 6TB. Those are ceilings once every disk is partitioned and mounted. df counts mounted filesystems only, so an empty disk stays out of it without being undelivered.

Costs add up item by item in the same way. A 128GB machine rents for $454.8 a month, one added disk is $84.7, and choosing 1 Gbps adds a further $245.0. The three are summed and then multiplied by the month count, so an annual term is twelve times that rent with no separate discount. A 256GB machine swaps $454.8 for $612.7 and leaves the arithmetic unchanged.

When initialising the disk on Windows, choose GPT rather than MBR. After creating a simple volume and assigning a letter, File Explorer shows a new volume close to 2TB. Do not mirror it against the system disk: a mirror caps usable space at the smaller disk and leaves most of the 2TB unused.

With the mount or the new volume ready, write a test file and read it back from another machine over SSH or RDP. The path has to land on the new mount point or the new drive letter. A file that turns up on the root partition means the copy target is still the system disk and the mount never took effect.

Addresses and passwords in the console appear only after the status becomes connectable. The graphical session gets its address at the same moment and is not written onto public pages. Tickets cover a mismatched disk count: state the order number, the added-disk count at checkout, and the row count actually seen in lsblk or Disk Management.

The default two 1TB disks are always direct-attached, and an added disk is too, so no disk is ever absorbed by a hardware array. Planning directories one purpose per disk — system, virtual machines, backup — keeps data easier to preserve during a reinstall than merging everything into one large volume.

The added-disk count at checkout has to match the disk rows in the system: a count of 1 means three disks and a count of 2 means four. The default pair is not part of that count yet is always on the machine, so reading the count as a total disk number comes up two short.

After the mount is finished, read the rent breakdown once more: machine price, added disk price, bandwidth price and address price sum to the monthly rent, and that rent times the month count gives the amount due. This page settles how a disk is identified and mounted; amounts follow whatever the configuration page calculates at the time.