You shouldn’t need a tmpfs entry for /tmp in fstab as it is normally handled by systemd.
Unrelated to the grub issue though.
You shouldn’t need a tmpfs entry for /tmp in fstab as it is normally handled by systemd.
This tmpfs thing is some Calamares related oddity. I’ve seen it once about 3 months ago when installed Manjaro on f2fs. I even had a talk about that with @gohlip and he had no idea why it was so, too.
Okay, so I booted to a live USB (ArcoLinux b/c it already has Gparted), cleared the Partition Table and created a new one then reinstalled Manjaro into sda2.
$ sudo parted -l [sudo] password for spencer: Model: ATA Samsung SSD 860 (scsi) Disk /dev/sda: 500GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 538MB 537MB fat32 boot, esp 2 538MB 108GB 107GB ext4 3 108GB 215GB 107GB ext4 4 215GB 500GB 285GB ext4
$ sudo blkid /dev/sda1: UUID="E597-DAFE" TYPE="vfat" PARTUUID="f8ab7249-7238-4cbb-b839-e67cc9f72cc5" /dev/sda2: UUID="41cb5c96-9831-4d61-b8b1-11d7b4ff657e" TYPE="ext4" PARTUUID="2ebd4ec6-6919-40e0-9e08-76121110e68e" /dev/sda3: UUID="d29230e9-cd4d-4bc2-b136-0bbb4da6731b" TYPE="ext4" PARTUUID="bf525aa3-f833-4ac8-8aad-6dc09522a54d" /dev/sda4: UUID="b538e532-483a-459d-8846-d95d782488df" TYPE="ext4" PARTUUID="ca727c41-8b23-4623-a9c0-fbb95542d2d0"
$ findmnt -s TARGET SOURCE FSTYPE OPTIONS /boot/efi UUID=E597-DAFE vfat defaults,noatime / UUID=41cb5c96-9831-4d61-b8b1-11d7b4ff657e ext4 defaults,noatime,discard /tmp tmpfs tmpfs defaults,noatime,mode=1777
I have no idea why the tmpfs is there either, or what it indicates. It isn’t something I designated.
I haven’t reinstalled Arcolinux yet. Boot time is roughly 90 seconds and the Manjaro Grub menu does not show up.
$ sudo update-grub Generating grub configuration file ... Found theme: /usr/share/grub/themes/manjaro/theme.txt 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 Found memtest86+ image: /boot/memtest86+/memtest.bin done
$ efibootmgr BootCurrent: 0011 Timeout: 2 seconds BootOrder: 0011,0000,0001,0002,0003,0013,000A,0007,0008,0009,000B,000C,000D,000E Boot0000 Setup Boot0001 Boot Menu Boot0002 Diagnostic Splash Screen Boot0003 Lenovo Diagnostics Boot0004 Startup Interrupt Menu Boot0005 ME Configuration Menu Boot0006 Rescue and Recovery Boot0007* USB CD Boot0008* USB FDD Boot0009* ATAPI CD0 Boot000A* ATA HDD0 Boot000B* ATA HDD1 Boot000C* ATA HDD2 Boot000D* USB HDD Boot000E* PCI LAN Boot000F* IDER BOOT CDROM Boot0010* IDER BOOT Floppy Boot0011* manjaro Boot0013* ArcoLinux
and systemd-analyze blame:
$ systemd-analyze blame 798ms systemd-backlight@backlight:intel_backlight.service 320ms upower.service 298ms lvm2-monitor.service 253ms tlp.service 239ms dev-sda2.device 236ms udisks2.service 232ms ModemManager.service 150ms polkit.service 114ms NetworkManager.service 100ms systemd-logind.service 79ms systemd-udevd.service 78ms firstname.lastname@example.org 74ms systemd-journal-flush.service 72ms systemd-udev-trigger.service 56ms systemd-journald.service 52ms avahi-daemon.service 37ms boot-efi.mount
possibly try another kernel, maybe 4.14 since your harware is slightly older, and see if it behaves differently. even if your intention is to re-install, at least you tried it and know it either is or isnt a factor.
Grub menu does not show up?
Can you boot now into manjaro?
How, if the boot menu does not show?
Above quotes shows it did.
Please confirm. Can you boot into manjaro?
ps: don’t worry about tmpfs now. It doesn’t matter. And it doesn’t matter if it is in fstab or not in fstab. We don’t need to worry about it now.
ps: there is no need to reinstall Arcolinux.
Just change the fstab uuid for its /boot/efi
Then from Manjaro grub (if it is working, it should be) manually boot Arco and then just do grub-install && update-grub.
To boot manually arco, at manjaro grub menus, go to prompt and boot manually
grub> set root=(hd0,3) # if it is in sda3, if sda4, (hd0,4)
grub> linux /boot/vmlinuz-linuz root=/dev/sda3 rw
grub> initrd /boot/initramfs-linux.img
I’m away from the computer right now.
Yes, I can boot to Manjaro, but I do not see the Manjaro boot/grub screen. It goes from the “interrupter option screen” to black, then eventually to Manjaro login screen.
I have installed the previous lts kernel but do not know how to select it to use if I don’t have the grub screen option to select it.
Okay, don’t worry about it. just press ‘esc’ (within 5 seconds) to see the grub menu.
It’s our brand new grub (sarcaasm) that works that way.
We’ll fix it after we fix Arco.
See my edited last post on how to fix arco.
ps: I don’ use SArco, check if kernel is in /boot and is vmlinuz-linuz and initramfs file is initramfs-linux.img.
Also is arco in sda3 or sda4? I think sda3, but confirm.
I did try this earlier before the most recent reinstall and I had the grub screen to work with. I didn’t notice any improvement. The Arcolinux was running the 4.20 kernel and it booted very quickly.
I’ll give it a shot when I get home.
Arco was installed in sda3 but I have not reinstalled yet.
Check my recent posts.
Good luck and good night.
ps: @petsam, if he is not sleeping, can help you when I’m sleeping.
Good night and thank you for your help!
Looks like it.
ls /boot efi intel-ucode.img grub linux414-x86_64.kver initramfs-4.14-x86_64-fallback.img linux419-x86_64.kver initramfs-4.14-x86_64.img memtest86+ initramfs-4.19-x86_64-fallback.img vmlinuz-4.14-x86_64 initramfs-4.19-x86_64.img vmlinuz-4.19-x86_64
I’m not sure how to do this. I no longer have a /boot/efi/EFI/Arcolinux.
$ ls /boot/efi/EFI boot Manjaro
How do I know what UUID to enter into fstab?
Still not seeing grub menu. Press ‘esc’ within 5 seconds of what? If I press during reboot before interrupter screen, then it gives me a diagnostic splash screen. If I press after the interrupter screen it gives me nothing until login shows up.
as soon as you see the bios splash screen at boot, you can also hold or tap shift repeatedly during boot and that should show you the grub selection
Strange. I just tried that. rebooted from terminal, saw the splash screen and started tapping shift repeatedly. No grub showed up but the boot was very quick like I would normally expect it. How would pressing shift accelerate this?
So I was reading the documentation on systemctl to learn how to enable and disable systemd-swap and i found the
systemctl reboot command. Previously I was only using
reboot to perform a reboot on the system. The grub menu showed up! Is there a difference in execution between the two commands?
I chose Advanced Manjaro and selected the 4.14 kernel. There seems to be no improvement over the 4.19 kernel.
Further consideration. Would it be possible for the grub menu to be there but I simply couldn’t see it, and thus it was waiting for my response until it timed out? This could account for some of the delay. Also, does pressing
shift accelerate through that selection?
Okay, I’m happy but a wee bit befuddled. I’ve shutdown then restarted the system, and rebooted several times now and the grub menu is showing up reliably and boot time has drastically decreased. I’ve switched back and forth between the 4.14 and the 4.19 kernels and updated grub after each change. Both are now booting fine and quick.
I’m not sure exactly what fixed the issue, but I’m sure it was a combination of everything y’all have suggested. I’ll update if anything changes as I add in some programs and change things to the way I like them.
I’ll take a look at the several things we looked at earlier to see if there are any big differences.
hey, it’s working. thats all that matters. glad it worked out
If the problem is entropy, yes.
You can chroot in Arcolinux, mount $esp at
/boot/efi and install grub, as suggested by the “sleepless” @gohlip .
The UUID in Arco fstab is same as in Manjaro’s, because it is the same $esp partition.
Boot into Arco (after fixing its fstab) when you get to see Manjaro grub and then press ‘c’
You will get to grub prompt (grub>). Then enter these commands and press ‘enter’ after each command.
When booted (to Arco)
To fix Manjaro’s grub… (refer here), at Manjaro terminal…
In /etc/default/grub, add this line
Also in /etc/default/grub, change
sudo rm /boot/grub/grubenv sudo grub-editenv /boot/grub/grubenv create sudo grub-editenv - set boot_success=0 sudo grub-install sudo update-grub
And these 2 additional commands
sudo cp /boot/grub/x86_64-efi/core.efi /boot/efi/EFI/boot/bootx64.efi sudo efibootmgr -c -d /dev/sda -p 1 -L "manjaro" -l "\EFI\Manjaro\grubx64.efi"
And note you must use Manjaro’s grub (or refind or systemd-boot) to boot Manjaro.
Arco grub cannot boot Manjaro. So you must set Manjaro grub as default.
At Arco or Manjaro terminal…
sudo efibootmgr -o 0011
Unless you do not have or want Manjaro, Manjaro bootloader must always be the default.
(also sleepless) @petsam is right about the entropy part (haveged). But the key to get to the manjaro grub is to use ‘esc’ key.
You might get away with ‘shift’ or ‘F8’ but if your system does not allow it, you will get error ‘Interrupt key not found’. Just use ‘esc’ key to get to grub menu. But with the changes in this post, your menu will appear (entropy excepted).
Evening gents. Thank you for the thorough responses.
I was having trouble with your instruction re: booting into Arco because I didn’t have Arco installed on my drive anywhere after i used the live environment to reformat the drive. I had erased everything, built a new partition table, and then installed Manjaro. Were you referring to booting to Arco in a live environment, editing fstab with UUID, etc? If so, I missed the boat on that.
Regarding entropy, I ran
cat /proc/sys/kernel/random/entropy_avail earlier before any re-installation and got a value of 3628. It was suggested to install haveged if I was below 1000. Is this acceptable or should I still install haveged?
There is nothing like the energy of an 18 month old and a 3 year old to encourage a little impatience. I went ahead and used the Arco USB and installed Arco to sda3. I then rebooted, went into BIOS to place Manjaro at the head of the boot order. Manjaro Grub showed up (on its own accord) with Manjaro as the only option. I ran
sudo update-grub and it detected Arco on sda3. I rebooted, Manjaro Grub showed up and both Manjaro and Arco were there as were their associated “advanced” options. I tested booting into both OS’s from Manjaro grub successfully. Both booted quickly (~10seconds) and appear to be functioning well.
Are there any outputs I can provide right now to see if I need to take further action? @gohlip, you have suggested a few things in your most recent post. Do you still recommend them if things appear to be working well?
Thanks again for your time!
EDIT: I’m still processing through the suggestions you made and reading the wiki’s and tutorials you both referred me too. Thank you!
Since everything is working fine now, there’s no need for further action,
But if Manjaro’s grub gives you some silliness, you can do the changes in /etc/default/grub and the terminal commands after that.
Cheers, take care. And you’re welcome.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.