jumpdrive software might be faulty (or my pinephone hardware)

[zetabeta]

jumpdrive software might be faulty (or my pinephone hardware)

this is quite preliminary view and when i get more information, i clarify what's going on. still it's headzup issue for some. i have pinephone hardware 1.2a.

i noticed that using jumdrive software, both 0.7 and 0.8, computer only saw 6GB intenal storage instead of 32GB. using telnet, then size was correct. this meant that flashing was not succesful.
https://github.com/dreemurrs-embedded/Ju...e/releases

i ended up installing o.s. to the memory card and after that i installed to the internal memory.

serious disclaimer, my pinephone could be faulty by hardware because i have some issues with gps as well.

[zetabeta]

jumpdrive software might be faulty (or my pinephone hardware)

this is quite preliminary view and when i get more information, i clarify what's going on. still it's headzup issue for some. i have pinephone hardware 1.2a.

i noticed that using jumdrive software, both 0.7 and 0.8, computer only saw 6GB intenal storage instead of 32GB. using telnet, then size was correct. this meant that flashing was not succesful.
https://github.com/dreemurrs-embedded/Ju...e/releases

i ended up installing o.s. to the memory card and after that i installed to the internal memory.

serious disclaimer, my pinephone could be faulty by hardware because i have some issues with gps as well.

probably false alarm

seems to be that i have problem with my computer, in this case debian. for some reason 32GiB usb memories function as 6.79GiB in size. happened also with other usb memory. actually usb adapter for sd card.

[hiimtye]

it could also be the ISO, double check it to make sure it's not a 6GiB iSO

[zetabeta]

old fashion reboot and computer showed sizes correctly. so, i assume something was messy with linux kernel when attaching and detaching usb mems.

i don't have optical drive (actually i have usb based optical drive but rarely used). if bug repeats, i check is it optimal image or something else weird.

side note: i use "lsblk" , "fdisk -l" and others to show sizes. in this case i meant whole disk/mem size and not partition sizes.