Thinking I must have done something wrong with my previous failed fienix upgrade, I decided I would try again with the Feb 18 soar version. I reformatted the partition I had put the last one in, and copied the new one in. But I may have some telling problems right there. For one thing, I think I am supposed to fix the size somehow, but I don't remember how I did that before I went senile. I don't understand how I have 101 GiB in the partition which has 5 GiB used, but only 1 GiB free instead of 94.
/dev/sda6 (!)|[]ext4 | | FIENIX | 100.95 GiB | 5.15 GiB | 1.21 GiB |
Also the Used size, 5.15 GiB, doesn't correspond to the image I dd'ed into it. The if file, if=Downloads/fienix-soar_20200218.img, was listed as 6.8 GB.
In any event, I tried running the new image, and I was delighted that it didn't give me that minute and a few seconds running some start job, but it ended with a black screen with a text cursor in the upper left corner.
I tried typing something there, and got the following, spread across and a little down the screen:
Code: Select all
[OK] Started Disk Manager
[OK] Reached target Graphical Interface
Starting Update UTMP about System Runlevel Changes
[OK] Started Update UTMP about System Runlevel Changes
[OK] Started Daily man-db regeneration
I finally had to hit the reboot button and go back to ubuntu.
I spent quite a bit of time looking at the new Fienix logs thinking there must be a clue to my problem there, if only I knew how to read them.
/var/log/ has some /lightdm/ documents from December!
alternatives.log is a blank LibreOffice file.
auth.log is a short LibreOffice file that ends
Code: Select all
Mar 2 17:46:27 Fienix systemd: pam_unix(systemd-user:session): session closed for user lightdm
Mar 2 17:50:09 Fienix runuser: pam_unix(runuser:session): session opened for user nobody by (uid=0)
Mar 2 17:50:27 Fienix runuser: pam_unix(runuser:session): session closed for user nobody
auth.log.1 is longer, a few pages dated Feb 18 then jumps to Mar 2 for the last four entries.
btmp is empty.
daemon.log is six-and-a-half pages of mostly (interesting?) <info>.
dpkg.log is empty, but dpkg.log.1 is a very long file dated 2020-02-11 and 2020-02-12 about upgrading, (half) unpacking and installing.
kern.log is dated Mar 2 and full of repetitious stuff mostly about radeon and "last fence id." kern.log.1, dated Feb 18, is very different, very long, and more interesting.
messages looks a lot like kern.log, but messages.1 (Feb 18) looks real, like it has something to say.
user.log, short, seems to report key problems:
Code: Select all
Mar 2 17:45:12 Fienix udisksd[3945]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Mar 2 17:45:12 Fienix udisksd[3945]: mountpoint /media/fienix/FIENIX-BOOT is invalid, cannot recover the canonical path
Mar 2 17:45:12 Fienix udisksd[3945]: Cleaning up mount point /media/fienix/FIENIX-BOOT (device 8:17 is not mounted)
Mar 2 17:45:12 Fienix udisksd[3945]: mountpoint /media/fienix/home is invalid, cannot recover the canonical path
Mar 2 17:45:12 Fienix udisksd[3945]: Cleaning up mount point /media/fienix/home (device 8:33 no longer exists)
I'm hoping someone will see something here that I can fix. I would really like to be able to use Fienix again!
It expands the file system to the total size of the specified partition.