You are not logged in.
https://s22.postimg.cc/6bber66pr/IMG_20 … 112812.jpg
This omnious screen showed up after I performed a major Windows 10 upgrade(I dual boot Windows and Arch Linux on the same drive), but I'm not sure if it was the cause. Unfortunately the system is in Italian, so I'm not sure what the error text is like in English, but it should be something like
Loading Linux linux
Error: premature end of file /vmlinuz-linux.
Loading initial ramdisk
Error: you need to load the kernel first
Press a key to continue
I can access GRUB and boot into Windows just fine, however trying to boot with the fallback kernel still gets me to the same error screen. I don't know how to fix it, can I even recover this system?
-- Mod note: Converted oversized image to URL, please follow the CoC on image sizes -- V1del
Last edited by quirico (2018-07-20 20:18:14)
Offline
Boot a live system (the install iso will do) and inspect the boot partition. You're probably short on space and windows created some BOFH style…
Chroot into the installed system, ensure to mount the boot partition and re-install linux, see https://wiki.archlinux.org/index.php/Pa … _rebooting
Of course, you may have to free some space on the boot partition first.
Offline
Please only paste thumbnails or links to huge screenshots like that: https://wiki.archlinux.org/index.php/Co … s_and_code
Offline
Boot a live system (the install iso will do) and inspect the boot partition. You're probably short on space and windows created some BOFH style…
Chroot into the installed system, ensure to mount the boot partition and re-install linux, see https://wiki.archlinux.org/index.php/Pa … _rebootingOf course, you may have to free some space on the boot partition first.
How do I safely free up space in /boot?
Offline
Depends on whether there're disposable files. Backups or i18n related files are good candidates.
However, first ensure that it's really a space issue and also be prepared that windows might keep dumping stuff there. If this ends up being a permanent issue, you'll have to grow the partition (what's gonna be PITA because of it's position) or move the linux boot to another partition.
Is this an EFI or a BIOS boot?
Offline
Depends on whether there're disposable files. Backups or i18n related files are good candidates.
However, first ensure that it's really a space issue and also be prepared that windows might keep dumping stuff there. If this ends up being a permanent issue, you'll have to grow the partition (what's gonna be PITA because of it's position) or move the linux boot to another partition.Is this an EFI or a BIOS boot?
It is an EFI boot. I'll get to work tomorrow.
Offline
OK I'm in the installation CD right now, how do I check the remaining free space? The output of df -h doesn't show me the partitions in my hard drive.
Offline
Have you mounted the boot partition?
Offline
Have you mounted the boot partition?
I did, still not showing up. But root partition shows up just fine.
EDIT: running df -h -a shows https://s22.postimg.cc/n4dk6hlb5/IMG_20 … 155010.jpg which I have no idea of what to make out of.
Last edited by quirico (2018-07-19 13:53:40)
Offline
You mounted sda1 and sda4 both into /mnt …
Please do not paste pictures of text - paste the text.
Offline
Boot a live system (the install iso will do) and inspect the boot partition. You're probably short on space and windows created some BOFH style…
Chroot into the installed system, ensure to mount the boot partition and re-install linux, see https://wiki.archlinux.org/index.php/Pa … _rebootingOf course, you may have to free some space on the boot partition first.
I'm back to square one. First off, I actually managed to ensure it is not a space issue, somehow I got df to show the right output. Then I followed the instructions in the wiki word for word, and managed to perform a full update with pacman, with a seemingly successful rebuild of the Linux kernel. However upon reboot nothing seemed to chance. While pacman was doing its thing I glanced at a message saying "/boot is not mounted", maybe I messed up something in the process. I'd really appreciate a step to step guide right now...
Offline
You mounted sda1 and sda4 both into /mnt …
Please do not paste pictures of text - paste the text.
I am afraid something went over my head... am I not supposed to do it that way?... Sorry if it is incredibly stupid but it is probably the frustration and confusion getting the best of me, I suck at staying concentrated when troubleshooting
Offline
seth wrote:You mounted sda1 and sda4 both into /mnt …
Please do not paste pictures of text - paste the text.
I am afraid something went over my head... am I not supposed to do it that way?... Sorry if it is incredibly stupid but it is probably the frustration and confusion getting the best of me, I suck at staying concentrated when troubleshooting
You want to mount the root partition on /mnt. Then, inside of that partition (/mnt) there is to be a directory called /boot. Initially, you create that. You use that directory /mnt/boot to mount your boot partition.
Then you perform the installation. Then you unmount /mnt/boot, then /mnt. You set your bootloader to tell the kernel to use the root partition. You should have (during the installation) built your /etc/fstab file to mount the boot partition on /boot. If you have not done that already, do it now.
Last edited by ewaller (2018-07-19 15:12:28)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
You set your bootloader to tell the kernel to use the root partition. You should have (during the installation) built your /etc/fstab file to mount the boot partition on /boot. If you have not done that already, do it now.
This is something that is all done during installation and doesn't need to be redone now, right? If so, I have already done that obviously, as I had a fully working Arch install for over a year prior to this happening.
Offline
Is your system booted now? What is the output of the mount command? Post the full text; not a photo.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Is your system booted now? What is the output of the mount command? Post the full text; not a photo.
# mount
/dev/sda4 on /mnt type ext4 (rw,realtime)
/dev/sda1 on /mnt/boot type vfat (rw,realtime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
This means I'm good to go, right?
Offline
Now you can post `df -h /mnt/boot`
Offline
Now you can post `df -h /mnt/boot`
Size 256M, Used 80M, Use% 32%. Most likely not a full partition issue. While I am at it might as well post some pacman errors that I got while trying to reinstall mkinitcpio, linux and systemd yesterday, with the boot partition not mounted properly
[ALMP] upgraded linux (4.17.3-1 -> 4.17.6-1)
[ALPM-SCRIPTLET] WARNING: /boot appears to be a separate partition but is not mounted.
[ALPM] running 'systemd-binfmt.hook'...
[ALPM-SCRIPTLET] Skipped: Current root is not booted.
[ALPM] running 'systemd-daemon-reload.hook'...
[ALPM-SCRIPTLET] Skipped: Current root is not booted.
[ALPM] running 'systemd-sysctl.hook'...
[ALPM-SCRIPTLET] Skipped: Current root is not booted.
[ALPM] running 'systemd-udev-reload.hook'...
[ALPM-SCRIPTLET] Skipped: Device manager is not running.
I understand the linux error but not the systemd errors, what do they mean?
Offline
That you're running "pacman --sysroot" - the critical one is about the unmounted boot partition, so re-install the kernel again (w/ the now mounted /boot partition)
Offline
That you're running "pacman --sysroot" - the critical one is about the unmounted boot partition, so re-install the kernel again (w/ the now mounted /boot partition)
So if I understand correctly, the systemd errors are inconsequential, right?
Offline
Those are no "errors", not even "warnings" - you're merely informed that certain steps are not executed because it would be ill-advised in this context.
Offline
Fixed it, finally. To summarize the steps I followed
>booted into LiveCD
>mounted the root and boot partitions, properly.
>reinstalled mkinitcpio, linux and systemd
>rebooted
Now the system is running fine again, as if nothing happened . In hindsight it was pretty easy but that's noob mistakes for you...
Offline