Dang
Comment on Trying to flash 256GB image to almost 256GB flash drive, space is barely not enough!
sudo@programming.dev 2 days ago
Storage devices are frequently smaller than advertised just as 2"x4" boards are.
You cannot flash an image onto a device smaller than the image’s size. Your only options are to get a larger device or shrink the image. Shrinking the image is possible but not without understanding how the image is created. It should be possible by taking the published image and somehow editing it. Or by simply rebuilding the image yourself from source. Either way you’ll want to start by reading .github/workflows/build.yml from that repo.
Also, because this is doing some PS4 exploits, its possible that the exploits depend on the 256GB size. Unlikely by conceivable.
sbeak@sopuli.xyz 2 days ago
truthfultemporarily@feddit.org 2 days ago
This is because for the OS 1 GB=1024 MB, but for storage 1 GB = 1000 MB.
sudo@programming.dev 2 days ago
1GiB = 1024MiB and 1GB = 1000MB. OP does seem to get those confused.
sbeak@sopuli.xyz 2 days ago
It’s not that, the amount in GB is less than 256! Comparing GiB to GiB is easier on Linux since it doesn’t do the Windows thing and obfuscate the unit to all be GB. I just got the shirt end of the stick in terms of silicon (this was a drive by Asus, sooooo)
Uli@sopuli.xyz 2 days ago
To be fair, 256! is about 8.5781777534 × 10⁵⁰⁶. Lots of numbers are less than that.
bamboo@lemmy.blahaj.zone 2 days ago
I think it’s pretty common for less reputable storage manufactures to have a drive which reports to be a certain size, but trying to read data back from some sectors doesn’t work. There is this windows tool to check the drive: www.grc.com/validrive.htm