On 2019-12-13 20:23, Ed Greshko wrote:
Right, I could see that happening. That is leaving one in a situation where they had to clear some locks
before being able to do proper updates. But, I don't see that having the effect of breaking the system
so it could not boot.
But, since Bob has decided to abandon efforts to fix what happened.:-)
.
The use of dnfdragors is not very intuitive for me, whenever I tried to
use it I usually gave up and went elsewhere, possibly leaving it in some
unknown condition? Whatever, that system always seemed a bit slower and
when I noticed the maxed out cpu core, something I don't recall looking
at until the other day, I decided to remove it, after which gkrellm and
top still indicated 100% so I rebooted and the reboot failed ...
Anyway I see a forgotten system on a third drive:
SATA1 Fedora 30 corrupted
SATA2 Fedora 31 Updated, configured and working
SATA3 Fedora 30 a smaller 250GB drive
So I still have a functioning F30 on the last drive, only partly
configured with xfce and I suspect it may be LVM rather than the
Standard Partitions that I prefer. I'm not sure of how to determine what
it is except try to deduce that from df ...
--
Bob Goodwin - Zuni, Virginia,
Fedora Linux-31 XFCE
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
