Did you try to install btrfs recently?
It all looks good to me. It could a faulty harddrive if you couldn’t start the chroot environment, but you could, so I don’t know what else it could be.
@soundofthunder do you have any ideas, because I’m full out…
OH! Only thing I can think of, is rebooting when done, which I’m guessing you’ve donee.
No
I never touch anything related to filesystem as i am nood so I fear of breaking things
yes the issue is same.
up to the login it’s file but after login stuck as loading screen
should I install a different kernel
Hmmm…well, enter the chroot environment again, run the following:
journalctl --boot=-1 --priority=warning..err --catalog --no-pager
…and provide the output here, please.
[manjaro /]# journalctl --boot=-1 --priority=warning..err --catalog --no-pager
Nov 27 17:54:16 ritoarch kernel: ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20220331/tbfadt-615)
Nov 27 17:54:16 ritoarch kernel: AMD-Vi: [Firmware Bug]: : IOAPIC[0] not in IVRS table
Nov 27 17:54:16 ritoarch kernel: AMD-Vi: [Firmware Bug]: : No southbridge IOAPIC found
Nov 27 17:54:16 ritoarch kernel: AMD-Vi: Disabling interrupt remapping
Nov 27 17:54:16 ritoarch kernel: ata2.00: supports DRM functions and may not be fully accessible
Nov 27 17:54:16 ritoarch kernel: ata2.00: supports DRM functions and may not be fully accessible
Nov 27 17:54:16 ritoarch kernel: vboxdrv: loading out-of-tree module taints kernel.
Nov 27 17:54:16 ritoarch kernel: VBoxNetAdp: Successfully started.
Nov 27 17:54:16 ritoarch kernel: VBoxNetFlt: Successfully started.
Nov 27 17:54:15 ritoarch systemd-modules-load[253]: Failed to find module 'nvidia-uvm'
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:9 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:16 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:19 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:22 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:25 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:28 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:30 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:33 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:36 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:37 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:40 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:43 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:45 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:48 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:51 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:54 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:55 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:58 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:61 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:64 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:67 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:68 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:71 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:74 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:77 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:78 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:79 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:80 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:81 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:84 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:87 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:90 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:93 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:94 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:97 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:98 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:99 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:100 Unknown group 'plugdev', ignoring.
Nov 27 17:54:16 ritoarch systemd-udevd[339]: /etc/udev/rules.d/60-openocd.rules:101 Unknown group 'plugdev', ignoring.
[manjaro /]#
@Mirdarthos this is the output
Maybe. You don’t seem to have been updating as frequently, or as thoroughly, as you should. I noticed community among your list of repos, which hasn’t existed for a while. There was a pacnew file provided for that, and mentioned in the respective Update Announcement. That’s an easy fix, however, it does indicate you’ve probably neglected to follow other things aswell.
I think some logs would be useful at this… time… (Mirdarthos beat me to it). 
yes you are right I forgot to update. 
So go back into the chroot environment, and so a complete upgrade:
pamac upgrade && pamac upgrade --aur --devel || echo -e '\033[0;91mThere was an error upgrading the system. AUR packages not upgraded.\e[0m'
This will update your system and ONLY if that was successful update any AUR packages.
a Reminder: While use of the AUR is possible, it’s neither recommended nor supported.
I recommend pamac instead of pacman, especially for newcomers as pamac was developed by Manajaro (developers) for Manjaro and just takes care of more thing than pacman. For example:
Afterwards, before a reboot, remember to handlee any andd all .pacnew files:
Those logs look like they are only from the Live media. You need to again use manjaro-chroot -a and try again, to get logs from your actual system.
Or, follow the reinstall route and ignore this.
1 Like
[manjaro /]# pamac upgrade && pamac upgrade --aur --devel || echo -e '\033[0;91mThere was an error upgrading the system. AUR packages not upgraded.\e[0m'
Warning: Building packages as dynamic user
Warning: Setting build directory to /var/cache/pamac
Preparing...
Synchronizing package databases...
Checking python-protonvpn-nm-lib dependencies...
Checking paru-bin dependencies...
Checking recon-ng dependencies...
Checking transcode dependencies...
Checking teamviewer dependencies...
Resolving dependencies...
Checking inter-conflicts...
To install (15):
python-jaraco.functools 3.9.0-1 (Required By: python-protonvpn-nm-lib) extra
python-jaraco.context 4.3.0-3 (Required By: python-protonvpn-nm-lib) extra
python-autocommand 2.2.2-4 (Required By: python-protonvpn-nm-lib) extra
python-annotated-types 0.6.0-1 (Required By: python-protonvpn-nm-lib) extra 21.7 kB
python-pydantic-core 1:2.10.1-1 (Required By: python-protonvpn-nm-lib) extra 1.6 MB
python-pydantic 2.4.2-1 (Required By: python-protonvpn-nm-lib) extra 736.9 kB
python-inflect 7.0.0-2 (Required By: python-protonvpn-nm-lib) extra
python-jaraco.text 3.11.1-3 (Required By: python-protonvpn-nm-lib) extra
python-ordered-set 4.1.0-4 (Required By: python-protonvpn-nm-lib) extra
python-tomli 2.0.1-3 (Required By: python-protonvpn-nm-lib) extra
python-fastjsonschema 2.18.1-1 (Required By: python-protonvpn-nm-lib) extra
python-trove-classifiers 2023.11.9-1 (Required By: python-protonvpn-nm-lib) extra 15.3 kB
python-validate-pyproject 0.13-1 (Required By: python-protonvpn-nm-lib) extra
python-setuptools 1:68.0.0-1 (Required By: python-protonvpn-nm-lib) extra
nasm 2.16.01-1 (Required By: transcode) extra
To build (5):
paru-bin 2.0.0-1 (1.11.2-1) AUR
python-protonvpn-nm-lib 3.16.0-1 (3.14.0-1) AUR
recon-ng 5.1.2-2 (5.1.2-1) AUR
teamviewer 15.48.4-1 (15.34.4-1) AUR
transcode 1.1.7-42 (1.1.7-41) AUR
Total download size: 2.4 MB
Total installed size: 20.7 MB
Edit build files : [e]
Apply transaction ? [e/y/N] y
Cloning paru-bin build files...
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Error: Failed to prepare transaction: Failed to clone paru-bin build files
There was an error upgrading the system. AUR packages not upgraded.
[manjaro /]#
@Mirdarthos another error is paru-bin something important if not should I just remove it with “pacman -R paru-bin”
yes I did use chroot before running that command
No, if you don’t know what it is, you o9bviously don’t use it and you can remove it.
@Mirdarthos i did the above you mentioned and this this time with no error and also I read the system maintenance section and performed it but the pacnew part i got concussed can you explain.
really sorry for being noob
I don’t know what there is to explain. .pacnew files are created wheen a piece of software requires a new configuration file, but the current one in use has been edited by the user. So it needs to be manually merged, so that it reflects what’s necessary.
But, and I don’t mean offense by this, if that idea goes above your head, and like you said concusses you now, it’s quite likely to happen again. And don’t feel bad, I didn’t get .pacnew files at first either, but if that’s not for you, please work through this essay: 
Edit:
About:
No reason to apologize for something when you’ve just started.
1 Like
there may be some pacnew-files to process 
1 Like
As we mentioned higher up…
1 Like
Thanks @andreas85 @soundofthunder @Mirdarthos for the support you made me realise it’s ok to let go.
In fedora now and enjoy it but still with plasma though I still love plasma 
2 Likes
This topic was automatically closed 3 hours after the last reply. New replies are no longer allowed.