Here you go. 
1 Like
I’ve installed 20.1-rc6 onto a usb stick, booted using this and tried the manjaro-chroot -a command as root but with no success after 5 minutes. I’m leaving it a bit longer but doesn’t look like it’s going to work. Any suggestions ?
Thanks, I’m using chroot.
Most of the update has finished except it’s now stuck here(see below).
Can I stop and re-run ?
==> Image generation successful
( 9/25) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
How much free space left in root?
df -h /
1 Like
Sometimes grub seemingly hangs for quite some time when re-generating it’s configuration. I’ve seen it taking up to 30 minutes.
Most times os-prober is the culprit - if you do not need it (no other OSes installed and/or to be booted via grub), disable it and see if it in fact was causing the long wait:
$ sudo chmod -x /etc/grub.d/30_os-prober
$ sudo update-grub
It can also be uninstalled, remove os-prober package.
1 Like
2.7gb available.
I have re-booted and can gain access to the operating system using the boot DVD and choosing the option boot from local hard disk but am unable to boot directly.
Please advise, thanks.
I have multiple disks and operating systems installed
[peter@peter-pc ~]$ lsblk -a
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
fd0 2:0 1 4K 0 disk
sda 8:0 0 117.4G 0 disk
├─sda1 8:1 0 18.4G 0 part
├─sda2 8:2 0 1K 0 part
├─sda3 8:3 0 17.5G 0 part
├─sda4 8:4 0 54.8G 0 part /mnt/sda4
├─sda5 8:5 0 2.3G 0 part [SWAP]
├─sda6 8:6 0 2G 0 part /home
└─sda7 8:7 0 22.5G 0 part /
sdb 8:16 0 2.7T 0 disk
└─sdb1 8:17 0 2.7T 0 part
sdc 8:32 0 931.5G 0 disk
├─sdc1 8:33 0 774.6G 0 part
├─sdc2 8:34 0 1K 0 part
├─sdc5 8:37 0 6G 0 part [SWAP]
└─sdc6 8:38 0 48.8G 0 part
sdd 8:48 0 931.5G 0 disk
└─sdd1 8:49 0 931.5G 0 part /mnt/sdd1
sde 8:64 0 1.8T 0 disk
└─sde1 8:65 0 1.8T 0 part
sdf 8:80 0 931.5G 0 disk
└─sdf1 8:81 0 931.5G 0 part
sdg 8:96 0 1.8T 0 disk
└─sdg1 8:97 0 1.8T 0 part
sr0 11:0 1 3.4G 0 rom
pktcdvd0 254:0 1 3.4G 0 disk
[peter@peter-pc ~]$
Check the output of
du -h /var/cache/pacman/pkg/
… might have a lot of archived packages. If so, it’s usually safe to run
sudo rm /var/cache/pacman/pkg/*
and run that first command again to see the difference.