You are not logged in.
Hi,
I'd like to imagine that a fresh reinstall and re-writing over all of that would probably be the way to go, though I'm not sure how far into the installation you got...
Could you perhaps give any details on what you did during the installation? (although tbf it looks like, from how old your account is, you'd have much more experience than me)
Other than that I/anyone else have/has very little information to go off of for now...
Offline
If you do believe you installed correctly, however, the most prominent issue I can imagine would be the case is hardware.
In order to check the disk health then you would have to insert a USB bootable medium, and then from there run
smartctl -a /dev/sda <replace sda with your disk name>
And then inspect the results from therein
(It feels awful to so confidently command whom I can assume is an arch veteran...)
Offline
Thanks bro I never face this kind of error before always I could find solution for my problem but at this I don't have any clues I did juts an upgrade I think this may related to groups or user don't know by the way smart say its fine everything on my drive
Offline
by the way smart say its fine everything on my drive
While I don't really think that this is a broken disk, please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Fwwi, the "overall health status: passed" and an empty bag have about the value of the bag (ie. that line is meaningless)
don't know what to do just did a update
Do you get a rescue shell?
What's the output of "uname -a"?
The main issue is likely the failure to mount the HPFS (do you use that as your root partition??) and the most common cause is to boot a different kernel than installed, failing to load any on disk modules for the booting kernel.
The usual cause for that is to forget or fail to mount the /boot partition before installing the kernel.
In that case, boot the install iso, make sure everything is properly mounted into place, chroot into the system and re-install the kernel.
Online
Do you get a rescue shell?
No
What's the output of "uname -a"?
Dont Have shell to perform
The main issue is likely the failure to mount the HPFS (do you use that as your root partition??) and the most common cause is to boot a different kernel than installed, failing to load any on disk modules for the booting kernel.
The usual cause for that is to forget or fail to mount the /boot partition before installing the kernel.
i'm sure did correct before installing kernel i was on arch did upgrade and kernel installed
In that case, boot the install iso, make sure everything is properly mounted into place, chroot into the system and re-install the kernel.
I Did. mount root and boot reinstalled kernel but same error like image on First post
Offline
From the install iso:
lsblk -f | curl -F 'file=@-' 0x0.st
then make sure you've internet and arch-chroot into the installed system w/ the boot partition mounted into place
(df -h; cat /etc/fstab; pacman -Qs kernel; file /boot/vmlinuz-*; ls -l /boot) | curl -F 'file=@-' 0x0.st
journalctl -b -1| curl -F 'file=@-' 0x0.st
LC_ALL=C pacman -Qkk 2>&1 | grep -v ', 0 altered files' | grep -v backup > /tmp/howbadisit.txt
cat /tmp/howbadisit.txt | curl -F 'file=@-' 0x0.st
Online
While I don't really think that this is a broken disk, please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Sorry, My bad...
Suppose I should've just left it as the install problem, and asked for more info. I was gonna mention something about issues mounting or the fstab (excuses), but...
At the end of the day I have loads to learn (since I literally got arch 2 weeks ago)
Offline
Sorry, My bad...
No, why?
In the end it could still be all down to the disk falling apart - the request to not paraphrase was for the OP, specifically w/ the assertion that "smart say its fine everything on my drive", cause that's typically a misreading (because of the misleading overall health assessment)
Rule of thumb: ebkac >> bug >> hardware defect (except if a cable is involved, then it's: "cable >>>>> ebkac >> bug >> hardware defect" )
Online
ohhh ok.
Thanks
Offline
From the install iso:
lsblk -f | curl -F 'file=@-' 0x0.st
then make sure you've internet and arch-chroot into the installed system w/ the boot partition mounted into place
(df -h; cat /etc/fstab; pacman -Qs kernel; file /boot/vmlinuz-*; ls -l /boot) | curl -F 'file=@-' 0x0.st journalctl -b -1| curl -F 'file=@-' 0x0.st LC_ALL=C pacman -Qkk 2>&1 | grep -v ', 0 altered files' | grep -v backup > /tmp/howbadisit.txt cat /tmp/howbadisit.txt | curl -F 'file=@-' 0x0.st
http://0x0.st/8gpI.txt
http://0x0.st/8gpl.txt
http://0x0.st/8gpU.txt
also smart data
smartctl 7.5 2025-04-30 r5714 [x86_64-linux-6.14.8-1.1-cachyos] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, [url=http://www.smartmontools.org]www.smartmontools.org[/url]
=== START OF INFORMATION SECTION ===
Model Number: SAMSUNG MZVL2512HCJQ-00B00
Serial Number: S675NX2T113677
Firmware Version: GXA7601Q
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 512,110,190,592 [512 GB]
Unallocated NVM Capacity: 0
Controller ID: 6
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 512,110,190,592 [512 GB]
Namespace 1 Utilization: 413,281,607,680 [413 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 002538 b121c6f6cd
Local Time is: Sat Jun 7 08:24:13 2025 UTC
Firmware Updates (0x16): 3 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0057): Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x0e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size: 128 Pages
Warning Comp. Temp. Threshold: 81 Celsius
Critical Comp. Temp. Threshold: 85 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 8.37W - - 0 0 0 0 0 0
1 + 8.37W - - 1 1 1 1 0 200
2 + 8.37W - - 2 2 2 2 0 200
3 - 0.0500W - - 3 3 3 3 2000 1200
4 - 0.0050W - - 4 4 4 4 500 9500
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning: 0x00
Temperature: 33 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 2%
Data Units Read: 51,210,515 [26.2 TB]
Data Units Written: 29,238,568 [14.9 TB]
Host Read Commands: 521,783,604
Host Write Commands: 473,333,361
Controller Busy Time: 2,960
Power Cycles: 803
Power On Hours: 3,696
Unsafe Shutdowns: 74
Media and Data Integrity Errors: 0
Error Information Log Entries: 0
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 33 Celsius
Temperature Sensor 2: 34 Celsius
Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged
Self-test Log (NVMe Log 0x06, NSID 0xffffffff)
Self-test status: No self-test in progress
No Self-tests Logged
FSTAB :
# /dev/nvme0n1p6
UUID=de4fcf4b-dbb7-4a5a-8d90-7d1461bc5924 / ext4 rw,relatime 0 1
# /dev/nvme0n1p1 LABEL=SYSTEM
UUID=D248-472D /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
Last edited by mojtabazn (Today 09:14:40)
Offline
Is this Arch or Cachyos? If the latter you would need to ask here https://discuss.cachyos.org/
Rlu: 222126
Offline
yeah I did notice that...
x86_64-linux-6.14.8-1.1-cachyos wrote:
Last edited by airbus777neo (Today 17:15:49)
Offline
Please use [code][/code] tags, not "quote" tags. Edit your post in this regard.
warning: grub: /etc/grub.d/10_linux (No such file or directory)
warning: grub: /etc/grub.d/20_linux_xen (No such file or directory)
warning: grub: /etc/grub.d/25_bli (No such file or directory)
warning: grub: /etc/grub.d/30_os-prober (No such file or directory)
warning: grub: /etc/grub.d/30_uefi-firmware (No such file or directory)
warning: grub: /etc/grub.d/40_custom (No such file or directory)
warning: grub: /etc/grub.d/41_custom (No such file or directory)
Why?
So is this cachyos, or blackarch, or a frankenstein collection of repos?
The last successful boot was on the - not updated - 6.13 cachyos kernel, which one are you trying to boot right now?
Does the other kernel boot?
Does the fallback image?
Edit: +b and also F5.
Last edited by seth (Today 09:11:49)
Online
no its arch just have some cachyos packages i have one cachyos kernel and official arch before update both was working after update both don't work even with fallback
Offline
Ok, remove the "quiet" from the boot parameters, instead add "sysrq_always_enabled=1 systemd.unit=rescue.target"
See what of the failing boot you can preserve, ideally, if the root partition (which is just ext4) gets mounted, rebooting w/ the magic sysrq (the print key is usually the sysrq) and the entire alt+sysrq+r,e,i,s,u,b (give it a second between each shortcut) you can properly reboot and preserve the journal of the boot.
Online
Ok, remove the "quiet" from the boot parameters, instead add "sysrq_always_enabled=1 systemd.unit=rescue.target"
See what of the failing boot you can preserve, ideally, if the root partition (which is just ext4) gets mounted, rebooting w/ the magic sysrq (the print key is usually the sysrq) and the entire alt+sysrq+r,e,i,s,u,b (give it a second between each shortcut) you can properly reboot and preserve the journal of the boot.
I fixed that by overwrite shadow package don't know why it was bugged now system load but have problem with desktop
Xorg works just by startx
Starting kde on Wayland black screen with courser
Starting kde on xorg give black screen with courser
Start sddm give black screen with courser
Offline
shadow lacked a bunch of manpages and I missed
warning: shadow: /usr/bin/groupmems (Permissions mismatch)
warning: shadow: /usr/bin/groups (Modification time mismatch)
warning: shadow: /usr/bin/groups (Size mismatch)
warning: shadow: /usr/bin/groups (SHA256 checksum mismatch)
For the updated situation, please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Online
shadow lacked a bunch of manpages and I missed
warning: shadow: /usr/bin/groupmems (Permissions mismatch) warning: shadow: /usr/bin/groups (Modification time mismatch) warning: shadow: /usr/bin/groups (Size mismatch) warning: shadow: /usr/bin/groups (SHA256 checksum mismatch)
For the updated situation, please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Here sir
Last edited by mojtabazn (Today 14:17:09)
Offline
I suspect https://0x0.st/8gO7.txt ?
Jun 07 17:34:40 bl-ck0ut kernel: i915 0000:00:02.0: Direct firmware load for edid/edid.bin failed with error -2
Jun 07 17:34:40 bl-ck0ut kernel: i915 0000:00:02.0: [drm] *ERROR* [CONNECTOR:241:eDP-2] Requesting EDID firmware "edid/edid.bin" failed (err=-2)
…
Jun 07 17:34:40 bl-ck0ut kernel: nvidia 0000:01:00.0: Direct firmware load for edid/edid.bin failed with error -2
Jun 07 17:34:40 bl-ck0ut kernel: nvidia 0000:01:00.0: [drm] *ERROR* [CONNECTOR:127:HDMI-A-1] Requesting EDID firmware "edid/edid.bin" failed (err=-2)
Jun 07 17:34:40 bl-ck0ut kernel: nvidia 0000:01:00.0: Direct firmware load for edid/edid.bin failed with error -2
Jun 07 17:34:40 bl-ck0ut kernel: nvidia 0000:01:00.0: [drm] *ERROR* [CONNECTOR:130:eDP-1] Requesting EDID firmware "edid/edid.bin" failed (err=-2)
Jun 07 17:34:40 bl-ck0ut kernel: nvidia 0000:01:00.0: Direct firmware load for edid/edid.bin failed with error -2
Jun 07 17:34:40 bl-ck0ut kernel: nvidia 0000:01:00.0: [drm] *ERROR* [CONNECTOR:133:DP-1] Requesting EDID firmware "edid/edid.bin" failed (err=-2)
Jun 07 17:34:40 bl-ck0ut kernel: nvidia 0000:01:00.0: Direct firmware load for edid/edid.bin failed with error -2
Jun 07 17:34:40 bl-ck0ut kernel: nvidia 0000:01:00.0: [drm] *ERROR* [CONNECTOR:133:DP-1] Requesting EDID firmware "edid/edid.bin" failed (err=-2)
…
Jun 07 17:34:40 bl-ck0ut kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64 575.57.08 Release Build (root@)
Jun 07 17:34:40 bl-ck0ut kernel: NVRM: testIfDsmSubFunctionEnabled: GPS ACPI DSM called before _acpiDsmSupportedFuncCacheInit subfunction = 11.
Jun 07 17:34:40 bl-ck0ut kernel: NVRM: testIfDsmSubFunctionEnabled: GPS ACPI DSM called before _acpiDsmSupportedFuncCacheInit subfunction = 11.
That aside, there seems no effort to start SDDM or plasma?
Online
Offline
Start sddm
http://0x0.st/8gVq.txt
Last edited by mojtabazn (Today 14:26:45)
Offline
…
Jun 07 15:54:26 bl-ck0ut kwin_x11[5233]: Could not initialize GLX
…
Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General
Online
Offline
[ 811.713] (II) modeset(0): EDID vendor "TMX", prod id 5633
[ 808.591] (II) NVIDIA(G0): Setting mode "NULL"
[ 808.616] (II) AIGLX: Screen 0 is not DRI2 capable
[ 808.639] (II) IGLX: Loaded and initialized swrast
[ 808.639] (II) GLX: Initialized DRISWRAST GL provider for screen 0
There's an output on the intel chip, nvidia works for prime offloading - and you somehow end up w/ the software rasterizer.
pacman -Qikk mesa xorg-server nvidia-utils
Online