Largest NVMe drive for Push 3 Standalone

[Wubzy22]

I was trying to drag all files and folders on the original ssd over to the new ssd. All you need is the “music” folder.
I believe I also had gparted open while transferring data which caused errors. You also have to make sure you enable permissions on the destination disk as described, before transferring data.
Then load the sdd in the push, reset, then back into linux for the changing of permissions as described.
Something like that anyway. I forgot the exact order already.

[CH7]

I've got a Gen4 2TB working now on the Push.

The push won't recognize this extra space naturally, as the clone of the original drive also writes the disk block with its original space allocations.

After a successful clone [on Windows i used DiskGenius] you then need a Linux installation to change the drive parameters.
When I did this I didn't have Linux and somehow wrangled a VirtualBox installation of Linux Ubunto with workarounds for the VR to see the external drives. A very long story. I would advise anyone trying this to create a dual boot system and have a real Linux install. Or use a Mac.

Once you have Linux access you can use Gparted to delete and recreate the /data drive to use all of the available space. ;0)
The drive needs to be created as ext4 and labeled 'data' and also named 'data' this is important as the Push OS is looking for this label.

Now for the fun part.

When i first authorized the Push i didn't realize there were write issues. eg important config files weren't being created/updated or saved to the data partition. I have 'Live 11 Suite', yet the Push kept showing 'Live 11 Intro', then i noticed an error whilst trying to factory reset and reauthorize the Push.


[EDIT] repasting what i pasted in another thread.

I had upgraded the SSD from 250gb to 2TB, this required me to delete the /data partition and recreate the partition via Gparted on Linux, to use all of the extra space on the drive. The problem with this is it came with premission errors meaning the Push OS couldn't write the config files it needed to that /data partition.

When i Authorise the PUSH [via a USB to Ethernet dongle] I got the following error -

The file "/data/.local/share/Ableton/Installation.cfg" cannot be opened for writing because it is write-protected.

At least this clue was there.

It seems the same write protection also prevented the WIFI password from being saved along with its config files. There were no other clues to this.
The solution was simple enough, I removed the SSD to a M.2 to USB Dongle, then booted into a Linux installation which allowed me to see the drives.

The following result was found when searching for write-protection faults.
"
Open the terminal.
Type sudo chmod 777 /data/ and press Enter. This command will give all users full read, write, and execute permissions to the directory /data/.
If prompted, enter your password and press Enter.
"

In my case, the /data partition was found as /media/<user name>/data . The command was modified to sudo 'chmod -R 777 /media/<user name>/data'.

[where -R recursively sets read/write/execute globally for all the files on that drive. ]

Now with the SSD back in the Push, I did another factory reset, [as other config files from the initial boot won't be where they need to be. ]
I then reauthorized the Push, this time there were no errors. When i rebooted the PUSH it showed "Ableton Live 11 Suite". 1.8tb space available

As a bonus, the Wifi now works.

After allowing me to save the password, the selected network is displayed in 'green'. I didn't know this. Once again there were no clues to why this had failed before. I guess drive upgrades and write protection faults were never anticipated. A failure to verify a file write could have been followed by the Push OS correcting for that fault.

The Push with this 'slow' 4800Mb/s Gen4 SSD now boots in 35 seconds. These things can do 7400Mb/s which i wish i'd gone for.

I hope others find this useful.

#upgraded SSD

Hey CH7. Thanks for these directions. I tried many times, getting little parts and steps wrong, several times, till I didn't. Cheers mate. Got a 2TB Gen 4 drive in there now. Woop Woop

"Don't you just love it when a plan comes together" ;0)

I'm pleased you got this to work -- paypal.me/ifyoulikedthis

[mslinn]

I finally got an answer:

Push 3 Standalone only supports Gen 4 NVMe drives in compatibility mode, which means they run at Gen 3 speeds. There is no benefit to a Gen 4 NVMe drive when used in a Push 3 Standalone

[zenkick]

Push 3 Standalone only supports Gen 4 NVMe drives in compatibility mode, which means they run at Gen 3 speeds. There is no benefit to a Gen 4 NVMe drive when used in a Push 3 Standalone

Curious. Were these details sourced from Ableton?

[mslinn]

Yes

[CH7]

Push 3 Standalone only supports Gen 4 NVMe drives in compatibility mode, which means they run at Gen 3 speeds. There is no benefit to a Gen 4 NVMe drive when used in a Push 3 Standalone

Curious. Were these details sourced from Ableton?

https://www.intel.com/content/dam/suppo ... D_SPEC.pdf

The PCIe bus speed is refered to on page 12 in the block diagram. PCIe x4 Gen 3 Sata

[mslinn]

I am glad my information has been validated

[mslinn]

I just discovered that the NVMe retaining pin on a P3S does not attach to WD Black SN750 NVMes. Only NVMe modules with perfectly smooth backsides can lie flat. The SN750 has lots of hardware hung on its flip side. Maybe I could use bubble gum to hold the SN750 down?

Back side:


Top side:


Actually, instead of bubble gum, a silicon gel thermal pad under the NVMe might do the job, if I can figure out an alternative capture mechanism. For that, maybe just jamming it with a short strip of nylon cut from a tie wrap?

[mslinn]

I just published Ableton Push 3 NVMe Replacement, along with 3 support articles: VirtualBox Setup, Clonezilla, and Supersizing a Partition and Its File System. Originally this started as one article, but it kept growing and growing so I split the information into more manageable articles. I spent a lot of time trying to make them readable, informative and bite-sized. Please let me know of any errors, omissions or confusing portions. I will update the articles as appropriate.

[littletinymonkey]

I just published Ableton Push 3 NVMe Replacement, along with 3 support articles: VirtualBox Setup, Clonezilla, and Supersizing a Partition and Its File System. Originally this started as one article, but it kept growing and growing so I split the information into more manageable articles. I spent a lot of time trying to make them readable, informative and bite-sized. Please let me know of any errors, omissions or confusing portions. I will update the articles as appropriate.

This is the greatest thing on the internet today. Wonderful, wonderful job writing all of this up. The level of detail is incredible. Thank you.

[mslinn]

*Blush*

Thank you!

[AlexDLarge]

I need to find time and energy to do this mod. So far I’ve read the description and I think it’s a hyper detailed manual. Superb job!! Thanks a LOT for this!

[mslinn]

Thanks for making me feel good.

Mike

[CH7]

I just published Ableton Push 3 NVMe Replacement, along with 3 support articles: VirtualBox Setup, Clonezilla, and Supersizing a Partition and Its File System. Originally this started as one article, but it kept growing and growing so I split the information into more manageable articles. I spent a lot of time trying to make them readable, informative and bite-sized. Please let me know of any errors, omissions or confusing portions. I will update the articles as appropriate.

I was just reading your guide and i see you recommend a thermal pad on the M.2 drive.

The drive and the processor/compute element would not normally share a heatsink, since the processor produces so much more heat than the drive ever would.
A case of buyers beware. I hope you have suitable disclaimers to cover you.

[mslinn]

Are you suggesting that it would better not to use a thermal pad on the larger, hotter NVMe? If not, what are you proposing? Install a larger NVMe but without any cooling? Never make any changes to this perfectly optimized device?

You also seem to imply that it is better to run the P3S without a thermal pad on the factory-installed NVMe. That seems unlikely to me.

I dispute your intimation that I should live in fear that someone blows up something, and they sue me as a private individual. That would be very unlikely; the suit would have to be brought in Canada, and the cost of the lawsuit would much greater than the expense; even if they won, they would not get their expenses covered.

The worst that should happen is that the system throttles back as it heats up. Doing this repeatedly to the extent that the system ages quickly is unlikely because it would run unacceptably slowly. Without a concrete suggestion, this sounds like fearmongering.

What would be helpful would be publishing the results of running a P3S hard while monitoring the CPU heat via ssh, and putting a temperature probe on various NVMes.

Data and provable facts rule. I welcome any test results that you can provide.