I have had failed updates, manjaro repository seems to "stall"
I got the black screen too, I forget how I recovered, I think I had a vt and used pamac
(setfont -d to get readable)
So for updates, ALWAYS set the --go to sleep-- to 2 hrs when plugged in (and set back later)
I don't know your level of skill, so this below may not apply
I would check sd and emmc have same number of partitions (fdisk -l)
update, upgrade the sd, save emmc extlinux.conf and fstab
(likely the emmc partitions are mountable, might need a fsck tho),
dd the sd partitions (as partitions) to emmc, restore extlinux.conf and fstab,
make sure they are "right" (blkid), fsck the emmc partitions
and maybe expand2fs (or gparted)
check with blkid hat there are not label and uuid clashes
You already know the uboot (on emmc) is OK, since it manages to boot the sd
----
BTW, you can check status of upgrade, switch to another desktop (patience)
start term, htop OR top, oddly they tell different things
I got the black screen too, I forget how I recovered, I think I had a vt and used pamac
(setfont -d to get readable)
So for updates, ALWAYS set the --go to sleep-- to 2 hrs when plugged in (and set back later)
I don't know your level of skill, so this below may not apply
I would check sd and emmc have same number of partitions (fdisk -l)
update, upgrade the sd, save emmc extlinux.conf and fstab
(likely the emmc partitions are mountable, might need a fsck tho),
dd the sd partitions (as partitions) to emmc, restore extlinux.conf and fstab,
make sure they are "right" (blkid), fsck the emmc partitions
and maybe expand2fs (or gparted)
check with blkid hat there are not label and uuid clashes
You already know the uboot (on emmc) is OK, since it manages to boot the sd
----
BTW, you can check status of upgrade, switch to another desktop (patience)
start term, htop OR top, oddly they tell different things