Largest NVMe drive for Push 3 Standalone

Discuss Push with other users.
Wubzy22
Posts: 17
Joined: Sun Feb 23, 2020 12:59 am

Re: Largest NVMe drive for Push 3 Standalone

Post by Wubzy22 » Sat Jan 27, 2024 5:05 pm

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
Posts: 80
Joined: Sat Feb 11, 2017 5:54 pm

Re: Largest NVMe drive for Push 3 Standalone

Post by CH7 » Fri Feb 02, 2024 8:19 pm

Wubzy22 wrote:
Tue Jan 16, 2024 7:18 am
CH7 wrote:
Sun Dec 31, 2023 1:12 am
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

Post Reply