2TB partition limit – Fact or Fiction?

Max2Play Home 2016 (en) Forums Max2Play as Squeezebox (Player / Server) 2TB partition limit – Fact or Fiction?

This topic contains 1 reply, has 2 voices, and was last updated by  sfraser131 2 hours ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • 9. November 2016 at 1:56 #23781

    Hi all – I just plugged a 4TB WD “My Passport” drive into my RPi3b running Max2Play 2.37 and seem to have successfully created a 4TB mount point and samba share for it via the Filesystem Mount page. I can see the data on the drive via the samba share and am copying some test data to it now.

    But… There’s this ominous warning on the page that states: “Important: the maximum partition size is 2TB. If using larger disks you need to divide the disk space into partitions smaller than 2TB.” So my question is: Or what? What horrible thing will befall me or my data? The drive came formatted with a single GPT/NTFS partiton with 4096 byte cluster size and seems to have mounted fine. Is the stated 2TB limit obsolete?

    Here’s the output from parted -l:
    Model: WD My Passport 259D (scsi)
    Disk /dev/sdb: 4001GB
    Sector size (logical/physical): 512B/4096B
    Partition Table: gpt
    Disk Flags:

    Number Start End Size File system Name Flags
    1 1049kB 4001GB 4001GB ntfs My Passport msftdata

    Thanks for any additional info!!

    UPDATE: I now have about 1.5TB of audio files on the 4TB partition and all appears to be working fine so far. (I copied them onto the drive with it plugged into the USB3 port of a Win10 box, not over the RPi3’s Samba share. That would have taken about 4 days.) LMS took about 3 hours to build its database but appears to have been successful. Is this whole thing going to self destruct when I exceed 2TB or does the M2P statement of a 2TB limit not consider the current technology “Advanced Format” drives?

    8. December 2016 at 18:09 #24703

    I have found that I cannot create a NTFS partition any greater than approx. 2T from within the max2play environment. However, if I create the 4T (3.6 T actually) NTFS partition’s from within a Windows 7 environment (2 Bay external USB3 unit configured with 2x4T drives) and then relocate back on the Pi everything is recognised accordingly and seems to work fine. I am using one drive as an LMS music storage and the other as a DLNA video storage. One benefit of this approach is when migrating hundreds of Gigs of content over, I can bring the max2play offline and relocate the external USB drive’s back onto my windows 7 machine and enjoy the high USB3 transfer rate. While the Pi’s 100mbps Ethernet/USB chipset is fine for streaming, it is a bit of a bottle neck when initially moving content over.

    M2P engineers, please chime in if above approach is not supported.


Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

Register here