20220823 testing .iso installation report
Page 1 of 1 (2 posts)
Tags:
None
Registered Member 
|
FAILURE.
0-Target system: multiboot UEFI NVME Intel Kaby Lake with 11 previously installed distros, targeting the 8,000 MiB space previously occupied by Mint 19.3 1-Where are the installation logs located? 2-Installer announced nothing about why the target partition could not be selected. With there being no alternative available, I had to start over and use a 32G USB stick pre-partitioned with 320G ESP and EXT4 using the rest. 3-Everything seemed to go well enough until the progress bar either neared or reached the end. Then a popup appeared announcing failure in a generic fashion that essentially said nothing about why the failure occurred. 4-After the apparent abort, I mounted and glanced at the EXT4 filesystem to see a typical root file list, so I rsync'd it from the USB EXT4 to the originally intended NVME partition 13 target to find no kernel or initrd in /boot. Neon's 8G / filesystem then stood at 70% in use. 5-I booted the previously installed Focal, chrooted to Neon, and used apt to force install the missing 5.15 kernel, mc, and a select few other packages I find essential. I also removed the unnecessary grub, os-prober and plymouth. 6-After the first two attempts to boot Neon due to typos in manual bootloader configuration, it booted without apparent error on try three. However, network was not configured, even though I had booted the installer using Debian's method of configuring static networking. I disabled the default network, configured systemd-network, rebooted to an apparent fully functioning system. 7-This time I ran apt update; apt-upgrade; apt full-upgrade and tried to reboot. It quickly hung, unable to find / filesystem, after switch to clocksource tsc: "ALERT! LABEL=zm2p13neon does not exist. Dropping to a shell!" 8-I chrooted from Focal again to find the upgrade had installed the 5.4 kernel. After reconfiguring bootloader again, Neon was able to boot several times on 5.4, but with 5.15 still failing to find / filesystem even after rebuilding initrd with nvme modules forced into it. I even tried copying the 5.15.0-46 initrd that Focal boots successfully on every attempt, without success. By this point, with two installed kernels and their monster initrds, / space consumed 80% of 8G, proving that the 10G minimum target size for installation is bloated. 9-Eventually I found that 5.4 would no longer boot, also like 5.15, unable to find / filesystem. Several tries later I found that on an unpredictably random basis, Neon would boot on either kernel. 5.4 is succeeding usually, 5.15 rarely. This is where bootability now stands. 10-Neon's initrds are about 10X the size of Focal's, even though in both Focal and Neon MODULES=dep in /etc/initramfs-tools/initramfs.conf. Initial 5.15 was 89.8MiB, as is current. Next grew to 95.2, while current 5.4.0-125 is 62.2MiB. 11-SDDM shows up on tty2, ignoring MinimumVT=7 in both /etc/sddm.conf and /etc/sddm/*.conf. |
|
Registered Member
|
I boot using symlinks to kernels and initrds. Apparently there was some defect in the one to the 5.15 initrd. I recreated both 5.15 symlinks, and now 5.15 is booting normally every time.
I'm still getting nowhere trying to move SDDM to VT7. https://www.linuxquestions.org/question ... 175716540/ 
|
Page 1 of 1 (2 posts)
Bookmarks
Who is online
Registered users: bancha, Bing [Bot], Evergrowing, Google [Bot], lockheed, mesutakcan, mickae, Sogou [Bot]
