Hey people, i am in a dilema over here, any help would be appreciated.
So i gotten myself a SD-Card with more storage, flashed the OS onto it and tried to get the GS to realize “Oh wait! i have over 200GB of available space now!” but to no avail.
i tried it with diskgenius and a certain command by fellow user hpcodecraft, but i always end up with GS showing the following error message when i dare to rebooth :
-bash: /tmp/x.log: Read-only file system
If it is any help, my pc runs windows 10 and the new SD-Card is a SanDisk Extreme (the ones that are red and yellow instead of red and white) with 256GB of storage.
It could also be your SD reader/writer! Try using a dedicated image writing program like etcher.
Or use a different computer altogether.
Re: self expanding images, let them reboot a few times to do their thing.
Oh dear. Another thought. You may have a counterfeit 256GB card. Basically the header tells the device it’s 256GB, but in reality it keeps rewriting over the same smaller card size.
I’ll post more links later! Gotta go to work!
If the cart is flashed to a fake size, it will report 256GB but it will be less, and filling it or formatting it it will corrupt it.
I like to use this https://www.rmprepusb.com/ to check them. In the past I was hunting fake usb and sd sellers and checking the things they sent me and opening disputes, that way I got a bunch of free cards and pendrives and I removed them from the market from non suspecting victims.
Sweet Christmas that is some extreme altruism if I ever saw it! You’re an online shopper’s hero!! I always abide by the age old adage: if it’s too good to be true, it probably is.
Re: reboots, the way the script works is a notification free reboot cycle, that on first glance, would appear to be a boot loop. As @Petrakis mentioned in another thread, this is technically not be good etiquette or practise, but alas. It is what it is for now.
It should just reboot itself automatically. Perhaps it just takes longer with a larger card? Although if it’s just writing a partition table, and not zeroing any space it shouldn’t be any longer.
On another note, I’ve got complete rom sets for basically all the Mame, Nintendo, and sega consoles and only use a 32GB card. Unless you’re planning on having a complete PSX ISO collection, 256GB is fairly overkill for the gameshell. Perhaps try using a smaller card?
OH WAIT HOLD YOUR HORSES - DID YOU TRY AND UPDATE THE LAUNCHER WITH THE IMAGE I MADE, specifically 191122? That is using some newer experimental Lima drivers that are installed in the user directory, as a temporary testing measure. Doing an update, specifically with that image will break it. Specifically, going into the system menu and choosing to update. That just does the launcher. I mean it shouldn’t actually break things, seeing as the launcher is separate to the user directory, but just a precaution! I’ve updated and tested it from my end.
So have you actually gotten it up and running like, ever? On your 256GB card that is.
Not with your Imagine specifically, no.
However I did update launcher from the settings menu. However that would lead to error mentioned earlier the next time i would try to boot it up.
Not updating seemed to work around this, however when i then try to move some roms onto the card (which i use filezilla for), then it would move like maybe 1 or 2 and then stop moving any more roms onto it, usually followed by the read-only-error.
From a fresh image, that shouldn’t change things. But the fact that it did would imply something is up. I’m guessing that was a completely fresh image, re update. No extra icons, or folder moving etc. that’s usually what messes things up. That said, it doesn’t explain the read only error. I don’t personally use FileZilla so I can’t really comment.
I used to use putty back in my days of using windows. Nowadays, I use CyberDuck or Transmit when not using a CLI. It could be client based? I also remember reading a thread re: the wifi not behaving well while connecting to an open wifi network. That could be a thing.
There could be some strange ownership problems with the Roms you’ve got. That could be causing the permissions error. Particularly, if they were recovered from a failed hard drive, where you have had to adopt ownership/become the parent user.
The good news is, you’re not missing out on too much not updating it. But still. It’s an annoyance, that’s for sure!
Got a little update on the read only error :
This time i only flashed the card with the selfexpanding image (0.4), put it back into the GS and just manually rebooted it. After the third reboot it booted like normal, went to the happy-hacking screen and gave the read-only error again.
I also tried to flash the original 0.4 image again and expand the partition manually with diskgenius again, which got me stuck on the “debian gnu/linux 9 clockworkpi tty1” screen, asking mefor a login.
So at this point I’m really not sure anymore what to do, so I’ll just use the card that came bundled with the gamshell for a while and try a different card.
I’ll try to come back to this card, but for now I am a little burned out on it.
Torrenting in Australia is a ridiculous affair, with the whole great firewall debarcle. Yay politics. It will be a lot of trouble, unfortunately. That said, if you check the OP, there’s a download link. Periodically I repost all the download links in the thread, to keep it current. I won’t post it here, to avoid cross posting/getting off topic.
By all means, you can seed it if you want.