Hey @thetechnobear would this patch work on the OrganelleM?
No, not at the moment!
(and in patchstorage now it should fail to run or an Organelle-m, but don’t try as it will kill you OS ) )
but its not hard to update, as the process identical for the organelle-m,
however, needs to delete and recreate partition 3 (not 2, as on the organelle-1)
you can do this manually if you wish, using fdisk and resize2fs … I think i detailed this in another post somewhere
a few notes about the organelle-m
note: the supplied SD card with the organelle-m is 8gb, so its already maximized, this would only be useful if you were to be buy and use a bigger card on the Organelle-m
the posts above are about the organelle-1, so things like the image details above are not appropriate for the organelle-m
AH I’ll see if I can dig up that post then!
I’ve actually already cloned the image onto a larger card, now currently just attempting to expand the available storage space
ive now tried to flash a new and larger sd card for my organelle-1 and it has failed repeatedly. When i unzip the disk image in win rar it says the file is corrupt. Ive also tried using the native windows10 extract function and it too fails.
is the image corrupt or am i missing something?
I assume we are taking about the resize patch?
( not organelle os image?)
You should just transfer zip file to organelle patches directory , then menu will offer install.
Does that not work ?
no i mean the disk image, not the patch
Was ok last time I downloaded it.
If your using something like etcher.io then you don’t need to unzip it.
strange. ive tried etcher on two SD cards with it zipped, and it has failed everytime. I will commandeer another computer in the house and check from there.
as always, your input is greatly appreaciated!
im getting corruption notices on a mac laptop as well
update: but i WAS able to decompress the zip and flash from that, and it worked.
Had a look at the resizeSD script and checked with the organelle-m. Two significant differences, though. Then whole procedure has to be applied to partition 3 rather than 2 and you have to manually change the starting sector to the original sector count. You may get that magic starting sector number listing the partitions by entering p within fdisk. Other than that everything works fine.
Does the sector thing really needs to be changed…? I’m trying to adapt the script, i’ve replaced partition 2 to 3 but then i don’t understand what to do with the sector numbers… i can see them but then i guess i need to add an option to one of the command lines (resize2fs or fdisk), could you help or post/send the modified script if it worked on your unit please ?
I’ll sort this out…
for now you’re best to run fdisk manually and it will prompt you for info it needs, you can take the defaults
What the mighty bear said.
I should have been more precise. I did not execute or adapt the script. Rather, I had a look at it and did all via ssh on the organelle
The individual steps in the script (basically executing fdisk) with the two deviations I mentioned. One you spotted yourself. The other is the sector number, which you might get from p.
If you want to try by yourself you might have a look at this:
That being said. There is a reason why this is a script and not a tutorial to do that by yourself. Doing that manually means that you know what you are doing. I would not recommend it in case you have little linux experience. It is very easy to kill stuff (even though fdisk is gentle in terms of unwanted changes).
@technobear: Are you sure about the defaults? I think I had to set the sector count manually. I have to admit, though that I do not remember.
Thanks for your answers.
I did it with fdisk and @opty is right, the start sector number must be changed to match the one from the p command before, otherwize it creates a 3mb partition.
Now i have 25gb free, thanks!
On the organelle 1 (= arch Linux) defaults are ok
But it maybe M is setup differently, but when I did it manually I thought I went with the defaults.
I’d have to check but if the patches are on a separate portion which is the the last partition, you simply delete that one, the recreate it with defaults.
This works because fdisk by default uses first unallocated sector.
But it’s possible I’ve forgotten some small detail about when I did this in the M
I have maxxed out my size on the organelle M
@thetechnobear Mark is this the current how to for Organelle M?
I gifted my v1 to a student learning pd and i would love to exapnd my M for more storage and i recall following a post of yours that was super straightforward./ is this most recent?
i want to tackle this today and i am hopeful this is still relevant
It looks like the resize-sd patch was written for v1
i’m going to grab a new sdcard but i am going to wait until i hear from someone who’s successfully re-sized M — i hope there’s a simple way but it’s not crucial just convenient
I don’t feel comfortable automating it but I tried to write up a very detailed guide of what worked for me to resize my organelle-m SD card. I stuck it in a gist https://gist.github.com/rupa/9ee4d2f3f00c06c722b1ccd4ed58c50f hope it helps
You can definitely screw things up if you get something wrong but the worst case scenario is you have to reimage the sdcard so, you know, backup yer stuff etc etc …
Thank you, the patch works perfectly on my Organelle 1, now i have 25gb free on the SD Card
Has anyone found a way to automate the maximization of SD card patch storage for the Organelle M? I just got one and want to store patches on a larger SD card to free up one of the USBs (using the other for WIFI). I ask because, unfortunately, I know nothing about linux, using fdisk, etc, and don’t want to mess anything up or kill anything.
I am, however, super open to learning! So, aside from my question, if anyone has any good beginner resources for these things, please share or message me. I’d love to learn more!
yeah. so in case anyone is reading this and thinking about doing it themselves… i just followed these instructions and they worked perfectly as described. thanks @rupa!