Installation crashes at the very end before /boot is filled

lsatenstein · April 18, 2020, 12:41am

failure messge Network Install

I get a message /usr/bin/finish script failed or something to this effect.
I went to a second system and mounted /boot and /boot/efi. Both were empty. The crash occurred before they were filled.
The message said that the cleanup tried 480 seconds to clean-up the installed downloads.
I want to use the network installation version because I wanted gnome and print support. I do not want xfce.
Re gnome and printer_support
I tried the two together --failed
I tried gnome alone --failed
I tried printer-support alone --failed

Suggestion. Does your install script do a rm of the downloaded files, once they are installed or does it wait to the very end to rm the lot?

My endevour system config
500meg fat32 boot/efi and esp flags
1500 ext4 /boot
8 gigs swap
24 gigs /
20 gigs /home

hardware 2700x 16gigs ram 3 SSD, 3x 1 TB hard disks.
I always test install on hardware using one of the TB hard disks.
If it is OK, I will relocate the installion to one of the SSDs.

Want me to test with a patch to the APRIL endevour version. Contact me. I am sure that ChrisT and Derick tested the immediately preceeding version
OTB also tested Endevour and had no issues. He tested an earlier release

ricklinux · April 18, 2020, 12:57am

Hello @lsatenstein
I’m sorry to hear you didn’t have success. Are you creating the partitions manually during the install or prior to starting the install with gparted. It would be good if you could provide any pertinent logs as it would be helpful.

Edit: I see you have listed most of your hardware except what Graphics card it is.

lsatenstein · April 18, 2020, 1:24am

Hi Joe,
thanks for responding.

I have a year 2015 old nvidia card. However, I opted to not use it. The issue is a script failure with a cleanup-script failure.
That is the message on the display.
I tried manual setup of /boot/efi, /boot, / and /home.
I tried giving the installer a region.
The problem is past that, All the software is being installed and I can see the ribbon showing me the percent accomplished.
Tell me where on the target system the system logs are located. I did my own search within the target system’s /var and other areas.

By the way, I also have Fedora, SUSE Linux, Ubuntu, Deepin, and CLear Linux on that system. I write C code for a pasttime and I am testing the compilers from each system. I could install Manjaro, but then Manjaro’s grub setup does not allow for multiboot, unless you make Manjaro the startup distro. That I do not want to do. Why do I switch. Compiled sizes of the same program can vary from 38k to 44k.
Has anyone installed to tother than virtual box or kvm with this iso?
I am open to redoing he run and taking snaps with my cellphone and also pulling out the log(s).
If the logs are still on the / or /var of the target system, give me the coordinates and I will “tail the end” to provide the exact cleanup message.

ricklinux · April 18, 2020, 1:29am

Hi @lsatenstein
This is rick here. If you do an install and it fails don’t go out of it as you can post the link for this command if it works to provide the install log. You’ll usually see it in the home folder. This is the Calamares install log.

cat ~/endeavour-install.log | curl -F ‘f:1=<-’ ix.io

Edit: I just did an install with your exact partitioning scheme although i have done it on vbox and it was fine. You didn’t mention what video card you are using?

lsatenstein · April 18, 2020, 1:33am

Correction. I did a re-look I have a the /boot/grub/grub.cfg
mkdir /tmp/bootEFI
mount /dev/sdd2 /tmp/bootEFI
pwd from bottom
/tmp/bootEFI/a

fernandomaroto · April 18, 2020, 1:36am

Hi!
cleaner_script is indeed set to timeout after 480 seconds, is not normal that is taking more than 8 minutes to run on your system. Are you using a good usb drive?

In any case you can try:

open a terminal before launching calamares

type:

sudo su
sed -i ‘s/480/4800/’ /usr/share/calamares/modules/shellprocess.conf

Then launch calamares

I hope it works for you, it changes the timeout value from 8 to 80 minutes.

ricklinux · April 18, 2020, 1:39am

I just did a test but in v-box with same parameters for partitions and it installed. So something is going on?

fernandomaroto · April 18, 2020, 1:41am

i have this crashes if i install from flash drive to flash drive, in my case is because the transfer is slow, then script also takes too long and reach the timeout value.

We added more code to the script later so it may need some extra time to run everything on some hardwares.

@lsatenstein you just gave me a good idea, changing cleaner_script to the last step of install, so even if it fails the user still has a bootable system to work on. I’ll start testing tomorrow.

lsatenstein · April 18, 2020, 1:52am

I am in the /var/log
It is complaining that it can’t find a grub in /dev/sde.
I presume that /dev/sde is the USB. I am installing to /dev/sdd
BTW, when I try to boot the new installation, system locks up.
I propose to leave this to tomorrow as it is almost 10pm.
There is a large system core dump.
I wonder if I can boot to the new system and do a chimage or something like that
Then I could try to run grub-install
The last three messages from pacman.log
[2020-04-17T19:33:26-0400] [ALPM] running ‘30-systemd-update.hook’…
[2020-04-17T19:33:27-0400] [PACMAN] Running ‘pacman -Rsn --noconfirm xf86-video-intel’
[2020-04-17T19:33:27-0400] [PACMAN] Running ‘pacman -Rsn --noconfirm xf86-video-amdgpu’
[2020-04-17T19:33:27-0400] [PACMAN] Running ‘pacman -Rsn --noconfirm xf86-video-ati’
[2020-04-17T19:33:27-0400] [PACMAN] Running ‘pacman -Rsn --noconfirm broadcom-wl-dkms’

This part bothers me
[2020-04-17T19:24:23-0400] [ALPM-SCRIPTLET] WARNING: Failed to connect to lvmetad. Falling back to device scanning.
[2020-04-17T19:32:59-0400] [ALPM-SCRIPTLET] grub-probe: error: cannot find a GRUB drive for /dev/sde1. Check your device.map.
[2020-04-17T19:32:59-0400] [ALPM-SCRIPTLET] Found Fedora 31 (Workstation Edition) on /dev/nvme0n1p3
[2020-04-17T19:33:05-0400] [ALPM-SCRIPTLET] Found Fedora 32 (Workstation Edition) on /dev/sda4

lsatenstein · April 18, 2020, 1:53am

My root partition is always formatted xfs (following RH advice).
Will do a fresh test tomorrow.
Good night.

fernandomaroto · April 18, 2020, 1:55am

Ok, you may have found more than one issue…

I’m leaving here too, good night!

Pudge · April 18, 2020, 3:25am

Hi Leslie, welcome to the EndeavourOS forums. I hope you enjoy your time here.
This is Pudge from the Fedora Forums. Glad to see you here.

Still trying to keep busy during the Shutdown I see, at least I assume that’s what brought you here.

Pudge

lsatenstein · April 18, 2020, 12:47pm

Hi Pudge,
About two years ago I had installed Manjaro alongside Fedora. It was fine, but the forum and the distro and forum were not enjoyable. I wanted to install arch or an arch based system. From youtube (DT, OTB, ChrisTyler and SwitchToLinux demoed Endeavour. These guys like an arch based system.

I want to try arch via Endeavour. Mainly because it took away some drudgery (A full install into Gnome).
As an aside, being a true senior a stone throw away from age 80, my wife and I have not left our home since early March, when we were told “to live, stay safely inside”.

I am going to start a fresh installation now.
This is my setup before I start.

Targeting a standalone mechanical hard disk at /dev/sdd

500meg fat32 for /boot/efi (flag boot, flag esp)
1.5gig ext4 for /boot
8gig swap for swap
24gig xfs for /
24gig ext4 for /home
unassigned 323gigs
backup1 250gigs Current year
backup2 300gigs last year.

I will be omitting using the nvidea option
I will reset a timeout value to 4800 (80 minutes)
sudo su
sed -i ‘s/480/4800/’ /usr/share/calamares/modules/shellprocess.conf

Re journalctl I presume it is the journal from within the installation flashdrive. The flashdrive is a 8gig one.
blkid /dev/sde* (flashdrive)

/dev/sde: UUID=“2020-04-11-19-17-24-00” LABEL=“ENDEAVOUROS” TYPE=“iso9660” PTUUID=“56226b04” PTTYPE=“dos”
/dev/sde1: UUID=“2020-04-11-19-17-24-00” LABEL=“ENDEAVOUROS” TYPE=“iso9660” PTUUID=“56226b04” PTTYPE=“dos” PARTUUID=“56226b04-01”
/dev/sde2: SEC_TYPE=“msdos” LABEL_FATBOOT=“ARCHISO_EFI” LABEL=“ARCHISO_EFI” UUID=“52AC-A508” TYPE=“vfat” PARTUUID=“56226b04-02”

fernandomaroto · April 18, 2020, 3:27pm

I’m antecipating some issues you’ll find, I hope I’m wrong…

lsatenstein · April 18, 2020, 5:48pm

Failed. I looked at the logs and the clean took 10+ minutes so, 480 is insufficient.
Perhaps 960 for the future would be a safe limit
again, it failed.
I have a bit of the end of the journal and my mount attached as “Saturday”
journalctl -b | grep clean

Apr 18 09:05:35 archiso kernel: XFS (sdd6): Ending clean mount
Apr 18 09:10:14 archiso systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Apr 18 09:10:14 archiso audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-tmpfiles-clean comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
Apr 18 09:10:14 archiso audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-tmpfiles-clean comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
Apr 18 09:10:14 archiso kernel: audit: type=1130 audit(1587215414.055:97): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-tmpfiles-clean comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
Apr 18 09:10:14 archiso kernel: audit: type=1131 audit(1587215414.055:98): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-tmpfiles-clean comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
mount -l
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=8135756k,nr_inodes=2033939,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
/dev/sde on /run/archiso/bootmnt type iso9660 (ro,relatime,nojoliet,check=s,map=n,blocksize=2048) [ENDEAVOUROS]
cowspace on /run/archiso/cowspace type tmpfs (rw,relatime,size=10485760k,mode=755)
/dev/loop0 on /run/archiso/sfs/airootfs type squashfs (ro,relatime)
airootfs on / type overlay (rw,relatime,lowerdir=/run/archiso/sfs/airootfs,upperdir=/run/archiso/cowspace/persistent_ENDEAVOUROS/x86_64/upperdir,workdir=/run/archiso/cowspace/persistent_ENDEAVOUROS/x86_64/workdir)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=30261)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1637360k,mode=700,uid=1000,gid=985)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=985)
/dev/sdd6 on /tmp/calamares-root-dyo_wiwe type xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota) [sddslash]
/dev/sdd4 on /tmp/calamares-root-dyo_wiwe/boot type ext4 (rw,relatime)
/dev/sdd2 on /tmp/calamares-root-dyo_wiwe/boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
dev on /tmp/calamares-root-dyo_wiwe/dev type devtmpfs (rw,nosuid,relatime,size=8135756k,nr_inodes=2033939,mode=755)
/dev/sdd7 on /tmp/calamares-root-dyo_wiwe/home type ext4 (rw,relatime) [sddHome]
proc on /tmp/calamares-root-dyo_wiwe/proc type proc (rw,relatime)
tmpfs on /tmp/calamares-root-dyo_wiwe/run type tmpfs (rw,relatime)
run on /tmp/calamares-root-dyo_wiwe/run/udev type tmpfs (rw,nosuid,nodev,relatime,mode=755)
sys on /tmp/calamares-root-dyo_wiwe/sys type sysfs (rw,relatime)
efivarfs on /tmp/calamares-root-dyo_wiwe/sys/firmware/efi/efivars type efivarfs (rw,relatime)
~
I will put the journal output to a file~

lsatenstein · April 18, 2020, 6:00pm

Installation log with a rename to allow upload cat ~/endeavour-install.log | curl -F ‘f:1=<-’ ix.io

I have the entire journal as a file on my system.
My USB Creater is the FEDORA mediawriter.
I could retry with DD. I found that often DD was usually OK.
I will sha1sum the USB flashdrive next.
I think its time to prepare debugging stuff for you.

lsatenstein · April 18, 2020, 6:10pm

lsatenstein · April 18, 2020, 7:04pm

PARTIAL SUCCESS I have a way to boot from the recovery line
The first main grub menu entry did not work. The last in the list of the grub.entries did.
So I will return to research why the first entry fails.

fernandomaroto · April 18, 2020, 7:46pm

Changing timeout from 480 to 4800 didn’t show timeout error yet still failed to install bootloader?

freebird54 · April 19, 2020, 12:41am

A look at the actual menuentry thatt works, as opposed to the one that doesn’t, may make things clearer. I’ve had menuentries that tried to boot a picture file (vmlinuz-linux.png) and entries that tried to set initrd to only the microcode file (amd-ucode.img) - that certainly didn’t lead to successful boots! If you’re not sure, a little copy/paste here might help…

Freebird54

Installation crashes at the very end before /boot is filled

failure messge Network Install

I am going to start a fresh installation now. This is my setup before I start.

Re journalctl I presume it is the journal from within the installation flashdrive. The flashdrive is a 8gig one. blkid /dev/sde* (flashdrive)

Failed. I looked at the logs and the clean took 10+ minutes so, 480 is insufficient. Perhaps 960 for the future would be a safe limit again, it failed. I have a bit of the end of the journal and my mount attached as “Saturday” journalctl -b | grep clean

I am going to start a fresh installation now.
This is my setup before I start.

Re journalctl I presume it is the journal from within the installation flashdrive. The flashdrive is a 8gig one.
blkid /dev/sde* (flashdrive)

Failed. I looked at the logs and the clean took 10+ minutes so, 480 is insufficient.
Perhaps 960 for the future would be a safe limit
again, it failed.
I have a bit of the end of the journal and my mount attached as “Saturday”
journalctl -b | grep clean