You are not logged in.
Pages: 1
Ok, it seems that or in general upgrading the system after such a long time (4 months), screwed everything up, as you can see here.
Incidentally, I can't even type anything in there, because the keyboard is powered off as soon as I make the choice in GRUB screen.
I suppose this could be due to the fact that the keyboard is a USB keyboard, but at the moment I don't have an old style keyboard at hand ![]()
Maybe I can fix this breakage with a live USB Arch?
Any suggestions?
---
As a side note, there's windows in dual boot with Arch (that's why GRUB), but I haven't booted it for a long time, definitely not since the breakage in question.
Last edited by Enrico1989 (2024-05-10 21:21:36)
Offline
The initramfs cannot be decompressed.
Boot the install iso, mount root partition into /mnt and if you have one the boot partition into /mnt/boot, "arch-chroot /mnt" and recreate the initramfs, in doubt re-install the kernel.
Pay close attention to errors, post them in doubt.
Exit the chroot and reboot.
Offline
Is /boot out of space?
Offline
and if you have one the boot partition into /mnt/boot
How do I know if I have one?
But I've tried this anyway
"arch-chroot /mnt" and recreate the initramfs
and executing
mkinitcpio -Presults in
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuratin file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
==> ERROR: specified kernel image does not exist: '/boot/vmlinuz-linux'
==> Building image from preset: /etc/mkinitcpio.d/linux.preset : 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
==> ERROR: specified kernel image does not exist: '/boot/vmlinuz-linux'Does it mean I need to reinstall the kernel?
Offline
Does it mean I need to reinstall the kernel?
No, but it's likely the answer to
How do I know if I have one?
which you're supposed to know because you added and configured it.
Also check /mnt/etc/fstab or "lsblk -f" (before the chroot) for what's usually mounted and the general partition layout.
Offline
which you're supposed to know because you added and configured it.
Yeah, but I've installed the system in question long long ago.
Thinking about it, though, I do remember at that time I (stupidly, in hindsight) put / and /home in different partitions, giving only 50GB to the former. And I also created a swap partition. But I don't rember I did anything special for boot.
Or is it important that I have Arch in dual boot with Windows? After all, /dev/sda is divided in 7 partitions:
# fdisk -l
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 850
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4F756C60-7752-47C8-ADD4-1554015CF6BA
Device Start End Sectors Size Type
/dev/sda1 2048 1023999 1021952 499M Windows recovery environment
/dev/sda2 1024000 1228799 204800 100M EFI System
/dev/sda3 1228800 1261567 32768 16M Microsoft reserved
/dev/sda4 1261568 464773119 463511552 221G Microsoft basic data
/dev/sda5 464773120 497541119 32768000 15.6G Linux swap
/dev/sda6 497541120 871915519 374374400 178.5G Linux filesystem
/dev/sda7 871915520 976773119 104857600 50G Linux filesystemAnyway,
# lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squashfs 4.0 0 100% /run/archiso/airootfs
sda
├─sda1 ntfs Ripristino C4642F4B642F3F92
├─sda2 vfat FAT32 D42F-D173
├─sda3
├─sda4 ntfs F670315C70312531
├─sda5 swap 1 210f0217-bab6-487d-b355-eb25db00faa4
├─sda6 btrfs e9ac7043-e39c-4afd-8d3f-b67af1f5d2cb
└─sda7 btrfs 158d9d49-7c23-43b4-bad5-8cf56b19a96b 16.9G 65% /mnt
sdb
└─sdb1 ntfs DATA 7ED342BC43CA67AB
sdc iso9660 Joliet Extension ARCH_202405 2024-05-01-17-04-31-00
├─sdc1 iso9660 Joliet Extension ARCH_202405 2024-05-01-17-04-31-00
└─sdc2 vfat FAT16 ARCHISO_EFI 6665-2677# cat /mnt/etc/fstab
# /dev/sda7
UUID=158d9d49-7c23-43b4-bad5-8cf56b19a96b / btrfs rw,relatime,ssd,space_cache,subvolid=5,subvol=/ 0 0
# /dev/sda2
UUID=D42F-D173 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 2
# /dev/sda6
UUID=e9ac7043-e39c-4afd-8d3f-b67af1f5d2cb /home btrfs rw,relatime,ssd,space_cache,subvolid=5,subvol=/ 0 0
# /dev/sda5
UUID=210f0217-bab6-487d-b355-eb25db00faa4 none swap defaults,pri=-2 0 0
# /dev/sdb1
UUID=7ED342BC43CA67AB /mnt/toshiba ntfs uid=1000,gid=1000,umask=0022,async,auto,rw 0 0
# /dev/sda4
UUID=F670315C70312531 /mnt/winzoz ntfs uid=1000,gid=1000,umask=0022,sync,auto,rw 0 0
# For the fucking Dropbox (see https://metabubble.net/linux/how-to-keep-using-dropbox-even-if-you-dont-use-unencrypted-ext4-workaround/)
#/home/enrico/.dropbox/storage /home/enrico/Dropbox ext4 defaults,user_xattr,loop 0 0Do I need to mount /dev/sda2 into /mnt/boot?
Last edited by Enrico1989 (2024-05-10 20:08:47)
Offline
Do I need to mount /dev/sda2 into /mnt/boot?
Gave this a try, result:
# mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
==> Starting build: '6.8.9-arch1-2'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [microcode]
-> Running build hook: [modconf]
-> Running build hook: [kms]
-> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
-> Early uncompressed CPIO image generation successful
zstd: error 70 : Write error : cannot write block : No space left on device
==> ERROR: Initcpio image generation FAILED: 'zstd' reported an error
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: '6.8.9-arch1-2'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [microcode]
-> Running build hook: [modconf]
-> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
-> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
cat: write error: No space left on device
bsdtar: Write error
bsdtar: Write error
==> ERROR: Early uncompressed CPIO image generation FAILED: 'sort' reported an errorAnd the
cat: write error: No space left on devicemakes me think of
Is /boot out of space?
...
But I haven't created /dev/sda2 myself. It came out of installing Windows, before installing Arch beside it ![]()
Last edited by Enrico1989 (2024-05-10 20:17:29)
Offline
Did you read it?
https://bbs.archlinux.org/viewtopic.php … 8#p2170438
df -hhttps://bbs.archlinux.org/viewtopic.php?id=291900
Last edited by seth (2024-05-10 20:18:28)
Offline
df -h
I suppose you mean before arch-chroot /mnt. If so,
Filesystem Size Used Avail Use% Mounted on
dev 16G 0 16G 0% /dev
run 16G 15M 16G 1% /run
efivarfs 128K 18K 106K 15% /sys/firmware/efi/efivars
copytoram 24G 789M 23G 4% /run/archiso/copytoram
cowspace 256M 1.1M 255M 1% /run/archiso/cowspace
/dev/loop0 789M 789M 0 100% /run/archiso/airootfs
airootfs 256M 1.1M 255M 1% /
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 16G 0 16G 0% /tmp
tmpfs 16G 2.6M 16G 1% /etc/pacman.d/gnupg
tmpfs 3.2G 8.0K 3.2G 1% /run/user/0
/dev/sda7 50G 33G 17G 66% /mnt
/dev/sda2 96M 96M 3.0K 100% /mnt/bootwhere the 100% on the last line is the bad part, right?
I'm reading the other link of yours. Trying to understand I think I'm not really understanding much
But yes, I have a 1080ti.
Last edited by Enrico1989 (2024-05-10 20:35:52)
Offline
96MB is incredibly small, esp. for a dual booting system.
Disable the kms hook, add the i915 module manually and disable the fallback image generation in /etc/mkinitcpio.d/linux.preset and remove /boot/initramfs-linux-fallback.img - the latter will safe a lot of space but you want to make sure to have some live distro (grml, install iso) around in case you cannot boot the regular initramfs anymore.
Edit: alternatively setup the system to boot from the root partition.
Last edited by seth (2024-05-10 20:39:46)
Offline
96MB is incredibly small, esp. for a dual booting system.
I'm pretty sure I'm not responsible for that
I remeber that's what the windows installation left me with.
Disable the kms hook
This means removing kms from the this line
HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block filesystems fsck)right?
add the i915 module manually
Does this mean I just add i915 in that line?
disable the fallback image generation in /etc/mkinitcpio.d/linux.preset
That file contains
# mkinitcpio preset file for the 'linux' package on archiso
PRESETS=('archiso')
ALL_kver='/boot/vmlinuz-linux'
archiso_config='/etc/mkinitcpio.conf.d/archiso.conf'
archiso_image="/boot/initramfs-linux.img"so what do I need to do?
remove /boot/initramfs-linux-fallback.img
You mean "rm that-file"? By the way, I see this only exists in the arch-chroot /mnt, not before, so do you mean I also need to do the previous steps after doing arch-chroot /mnt?
Offline
Edit: alternatively setup the system to boot from the root partition.
Alternative to what? All theprevious part in that message? How do I do that? And is it compatible with the dual boot I have in place?
Offline
right?
Right
Does this mean I just add i915 in that line?
No, MODULES
That file contains
Not the one on the iso, /mnt/etc/mkinitcpio.d/linux.preset in that case.
Offline
It worked, thanks!
But other than letting that partition so small (I wouldn't have known how to avoid that small size, given I haven't chosen it), have I done something wrong to end up with a broken system?
Last edited by Enrico1989 (2024-05-10 21:18:39)
Offline
No, the problem is the udnerdimensioned boot partition - you could arguebly have configured the system to boot from the root partition and might still want to opt for this.
Unmounting the boot partition, reinstalling the kernel and re-running grub-install and grub-mkconfig should™ do.
Is sda2 also the ESP??
Offline
Is sda2 also the ESP??
I woudl assume so:
# fdisk -l Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors Disk model: Samsung SSD 850 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 4F756C60-7752-47C8-ADD4-1554015CF6BA Device Start End Sectors Size Type /dev/sda1 2048 1023999 1021952 499M Windows recovery environment /dev/sda2 1024000 1228799 204800 100M EFI System /dev/sda3 1228800 1261567 32768 16M Microsoft reserved /dev/sda4 1261568 464773119 463511552 221G Microsoft basic data /dev/sda5 464773120 497541119 32768000 15.6G Linux swap /dev/sda6 497541120 871915519 374374400 178.5G Linux filesystem /dev/sda7 871915520 976773119 104857600 50G Linux filesystem
Why?
Offline
Because 100M then is really small and I'm somewhat surprised that you didn't run into space issues ahead.
Offline
Pages: 1