receive a blank screen after expanding SD on first boot
New PinePhone user who is also relatively new to Linux as well.
I picked up a 512GB Samsung EVO Select SD and used Rufus in Win10 to restore the mobian-pinephone-phosh-20210517.img I downloaded from https://images.mobian-project.org/pinephone/ (parent of the "installer" folder).
The phone booted to the Mobius splash screen right away; which was a good sign... and indicated it was expanding the disk on first boot.
At some point (maybe after 15 minutes), the screen blanked (transitioned from the splash disk expansion screen)... you could still see the backlight was on... just no more messages echoed to the screen.
In case it was still busy, I left the phone alone to do its thing for about an hour... then powered it down.
I took the SD out of the phone and installed it back into my USB/SD card reader on my PC, brought up the disk manager, and confirmed the partitions had been expanded out to consume the entire disk... 8MB Unallocated, 504 MB Active Primary Partition, and a 476.41 GB Primary partition.
So as far as I can tell, the phone booted the SD image and expanded the disk like it said it was going to, and then went completely silent/blank... was I not patient enough waiting an hour for something to show on the screen, did I pickup an SD that was too big, should I have used the installer image, or is there a known issue here that I can take an action on to yield a successful boot?
In the mean time I also want to test this new SD... so I've used the Win10 Disk Manager to delete the two allocated partitions, created one large NTFS partition, and am in the process of copying a single 368GB (nvme backup) file to it... Windows suggested it was going to take ~80 minutes to copy the file @ 80 MB/s.... at the time of this writing 28% of the file has been written (~103GB) with a 55min ETA.
Hopefully the SD proves to be good... I post again (or maybe just update this post) with those results, and look forward to everyone's feedback and help.
EDIT: I think the SD is good... The 368GB file copied successfully at a sustained 80GB/s second average (bounced between 79.6 and 80.6), I even mounted the backup image, browsed the folder structure, and opened a few random files to confirm their contents were read correctly. I don't think my issue is that the SD is bad.
I picked up a 512GB Samsung EVO Select SD and used Rufus in Win10 to restore the mobian-pinephone-phosh-20210517.img I downloaded from https://images.mobian-project.org/pinephone/ (parent of the "installer" folder).
The phone booted to the Mobius splash screen right away; which was a good sign... and indicated it was expanding the disk on first boot.
At some point (maybe after 15 minutes), the screen blanked (transitioned from the splash disk expansion screen)... you could still see the backlight was on... just no more messages echoed to the screen.
In case it was still busy, I left the phone alone to do its thing for about an hour... then powered it down.
I took the SD out of the phone and installed it back into my USB/SD card reader on my PC, brought up the disk manager, and confirmed the partitions had been expanded out to consume the entire disk... 8MB Unallocated, 504 MB Active Primary Partition, and a 476.41 GB Primary partition.
So as far as I can tell, the phone booted the SD image and expanded the disk like it said it was going to, and then went completely silent/blank... was I not patient enough waiting an hour for something to show on the screen, did I pickup an SD that was too big, should I have used the installer image, or is there a known issue here that I can take an action on to yield a successful boot?
In the mean time I also want to test this new SD... so I've used the Win10 Disk Manager to delete the two allocated partitions, created one large NTFS partition, and am in the process of copying a single 368GB (nvme backup) file to it... Windows suggested it was going to take ~80 minutes to copy the file @ 80 MB/s.... at the time of this writing 28% of the file has been written (~103GB) with a 55min ETA.
Hopefully the SD proves to be good... I post again (or maybe just update this post) with those results, and look forward to everyone's feedback and help.
EDIT: I think the SD is good... The 368GB file copied successfully at a sustained 80GB/s second average (bounced between 79.6 and 80.6), I even mounted the backup image, browsed the folder structure, and opened a few random files to confirm their contents were read correctly. I don't think my issue is that the SD is bad.