For context, I am flashing the extended storage Vue After Free onto a drive marketed as “256GB”, but it’s actually a few GB short for some reason. (guide for context: https://github.com/Vuemony/vue-after-free#extended-storage-setup)
The drive I have has 234.3 GiB (~252GB), while the image of Vue After Free is 258 GiB (~256GB), so it cannot flash. Tried both KDE ISO image writer and balenaetcher. Is there any way to force the image to be written, as far as I understand, most of that 256GB is actually empty and it’s only because the PS4 requires a 256GB drive to register an external drive.
The way I see it, it looks like I could either a) spoof the drive into reporting as 256GB (it’s nearly there anyways), and undo that once I need to use it normally again or b) force the image to be flashed despite the storage on the drive being just short, and hoping the PS4 agrees with it given it’s not exactly 256GB
edit: Attempting to use dd to write the image to the drive, if that doesn’t work I’ll just get a later (but slower) drive
This is because for the OS 1 GB=1024 MB, but for storage 1 GB = 1000 MB.
1GiB = 1024MiB and 1GB = 1000MB. OP does seem to get those confused.
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 short end of the stick in terms of silicon (this was a drive by Asus, sooooo)
To be fair, 256! is about 8.5781777534 × 10⁵⁰⁶. Lots of numbers are less than that.
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: https://www.grc.com/validrive.htm