View Single Post
Old 03-29-2025, 08:49 PM   #3379
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,084
Karma: 169815798
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
You may want to redo the image writing with either the recommended USB Duplicator Image Writer tool or Balena Etcher. Several people have reported issues trying to use Win32 Disk Imager.

If you are using a new µSD card and your Glo does not boot after inserting the imaged card and powering on, your Glo has other hardware issues which a new image will not help with. And yes, I strongly suggest using a new µSD card since very often the issue is with the µSD card having issues including having reached the end of it's write life. You can try using the SD Card Association Formatter to do a slow re-format to see if that helps but that is not going to fix any issues with the old µSD card though it may mask them for a while.

As for the disk not being recognized after imaging? As PeterT said, the µSD card after imaging has 3 partitions, 2 Linux ext4 and 1 FAT32. Windows does not recognize an ext4 partition and pops up a request to format the partition. Doing so is a very bad idea.
DNSB is online now   Reply With Quote