hello guys,
i have a problem with the system i think, it started last week, when i suddenly couldnt open any program anymore, i findled a bit and learned that my nvme0 was set to read-only , with a dmesg error of "invalid/missing subnqn field" so i tried the btrfsck -repair but it couldnt fix it ... so i tried to reinstall from usbstick but got this error, so i tried this solution but that didnt work either with some strange "cannot write" errors, so i figured it might be the harddrive broken and ordered a new one (M.2 this time), which came today and i wanted to install the system on it, but it gives me the very same error of bootloader fail again and dmesg now gives me two nvme= missing subnqn errors ......
i know, i noobishly did stuff to the old drive, that may have crashed it, i put that under appreanticeship and though the new hd would solve the problem, but with the error coming up again, im out of a clue
i tried that how to chroot only on the old one, but without success, because it couldnāt write on it ā¦
so far, i didnt try anything on the new one yet, just the delete-install from the stickā¦
here is the check of the fat32 part:
sudo fsck /dev/nvme1n1p1
fsck from util-linux 2.38.1
fsck.fat 4.2 (2021-01-31)
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
65:01/00
1) Copy original to backup
2) Copy backup to original
3) No action
[123?q]? 3
Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
[12?q]? 2
/dev/nvme1n1p1: 3 files, 77/76646 clusters
What I meant is to try reinstalling, making sure that the EFI system partition is placed on the new disk. So the old disk is not touched at all.
If not working, you could try chrooting, but please consider that the grub-install command is different in the post I linked.
yeh, installer was using nvme1 only , last time i tried with nvme0
but trying to chroot as your link gives me this:
āāgaruda@garuda in ~ as š§ took 17s
ā°āĪ» sudo mkdir /mnt
mkdir: cannot create directory ā/mntā: File exists
āāgaruda@garuda in ~ as š§ took 7ms
[š“] Ć sudo mount /dev/nvme1n1p1 /mnt
āāgaruda@garuda in ~ as š§ took 7ms
ā°āĪ» sudo garuda-chroot /mnt/@
==> ERROR: Can't create chroot on non-directory /mnt/@
āāgaruda@garuda in ~ as š§ took 18ms
[ā”] Ć sudo garuda-chroot /mnt/dev/nvme1n1p1
==> ERROR: Can't create chroot on non-directory /mnt/dev/nvme1n1p1
This is most likely unrelated to your issue, but you have an old ISO (from the previous release). You should download a more recent ISO for your new installation from here: Garuda Linux | Download
This is too vague to be helpful. If you can reproduce the issue, please capture the log output and paste it into the thread so we can see exactly what is happening.
Check to see if you need to delete obsolete boot variables. Some firmware may limit the number of boot entries that can be stored on the NVRAM, or the NVRAM can actually become full in some cases if there are a lot of large boot entries.
efibootmgr -v
If you are starting fresh, I would just delete them all and then try reinstalling.(efibootmgr -b 1 -B, for exampleāreplace ā1ā with the boot variable you wish to delete).
Check on the website for the vendor of the NVMe drive to see if they have release a firmware update. You can update the firmware of a hard drive with fwupd, or check and see what is recommended for the specific brand of hard drive you have: Solid state drive - ArchWiki
ok, this one seems to have worked, as much as it finished the core installation, but i already had to reboot two times on the follow up installations which seems to struggle with the nvida-prop.drivers and also with some outdated keyrings ā¦ (sadly the actual errormessages got lost on systemfreeze)
should i open a new thread for that?
iāll put the last output here
---> Building NVIDIA DKMS module for kernel 6.2.10-zen1-1-zen
Module nvidia 530.41.03 is not installed for kernel 6.2.10-zen1-1-zen (x86_64). Skipping...
Module nvidia 530.41.03 is not built for kernel 6.2.10-zen1-1-zen (x86_64). Skipping...
Deleting module nvidia-530.41.03 completely from the DKMS tree.
Sign command: /usr/lib/modules/6.2.10-zen1-1-zen/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Creating symlink /var/lib/dkms/nvidia/530.41.03/source -> /usr/src/nvidia-530.41.03
Building module:
Cleaning build area...
'make' -j24 IGNORE_PREEMPT_RT_PRESENCE=1 NV_EXCLUDE_BUILD_MODULES='__EXCLUDE_MODULES' KERNEL_UNAME=6.2.10-zen1-1-zen modules....(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.2.10-zen1-1-zen (x86_64)
Consult /var/lib/dkms/nvidia/530.41.03/build/make.log for more information.
---> Failed to build NVIDIA DKMS module for kernel 6.2.10-zen1-1-zen
Yes, this will be best so your new issue is not lost in the thread related to the bootloader. Go ahead and mark the solution on this thread, then open a new one with a description of the issue with the Nvidia driver and the troubleshooting steps you have taken so far to resolve it, as well as an updated garuda-inxi output.
well, i was wondering, because for me, it is still the same problem, that started last week out of the blue and let to this point now, so iām wondering if it wouldnāt be easier to rename this post and collect the steps iāve done/ iām doing ā¦ ?
PS: this kernel-dump-overflow made me think about, and it seems to explain the behaviour of the issue quite well ... also the keyring-thing and other instabillities remember me of my tries last week ...
so is there some things i can check to see if there is other stuff influenced by that overflow, or the source of the overflow, that i dont know yet either ... ?!
btw: here is the keyring (actually not keyring, but gpg-signature, mixed that up, sorry) error
when i try to install audacious and firefox :
:: Retrieving packages...
(1/8) firefox-adblock-plus-3.16.1-1-any
checking keys in keyring
checking package integrity
error: libcue: signature from "Jelle van der Waa " is invalid
:: File /var/cache/pacman/pkg/libcue-2.2.1-3-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
error: libmms: signature from "BallĆ³ Gyƶrgy " is invalid
:: File /var/cache/pacman/pkg/libmms-0.6.4-4-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
error: libsidplayfp: signature from "Antonio Rojas " is invalid
:: File /var/cache/pacman/pkg/libsidplayfp-2.4.2-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
error: libcddb: signature from "Evangelos Foutras " is invalid
:: File /var/cache/pacman/pkg/libcddb-1.3.2-7-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
error: audacious: signature from "Evangelos Foutras " is invalid
:: File /var/cache/pacman/pkg/audacious-4.2-3-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
Befehl endete mit FEHLERN !
