What does that mean, exactly?
Iām in console and did
# cd etc/default
# nano grub
saved the file āgrubā after removing ātextā and ānoplymouthā and did
# sudo update grub
This produced few lines, the last one
/usr/bin/grub-probe: Warning: Unknown device type nvme0n1
Shall I try to reboot?
/usr/bin/grub-probe: Warning: Unknown device type nvme0n1
Thatās normal and can be ignored.
Shall I try to reboot?
Only one way to find out if the changes made any difference.
Done, but as far as I can see, the same picture:
Dependency failed for /home
Dependency failed for /home/nn/VirtualBoxVMs
Dependency failed for Local File System
Little bits and pieces of the log isnāt going to help us help you. Please see:
Difficulty: ā āāāā The first step for troubleshooting an issue is to find an error log: a trace produced by an application when failing/crashing, and providing the first trail a user/developer can follow to fix it. 1. Reach a usable system Obviously, it will be impossible to acquire those logs if you canāt have access to a usable system. See: [HowTo] Reach a minimal system 2. Find the faulty application If you donāt know which application failed ā this is usually the case on a system or graā¦
BOOT_IMAGE=//boot/vmlinuz-5.15
Is that //
also a typo ?
Welcome to Manjaro!
- Please read the information behind this link. It will help you to post necessary information. [HowTo] Provide System Information
- Please press the three dots ā¦ below your post and then press the
- If you give us information about your system, we can see what weāre talking about and make better suggestions.
- You can do this by using
inxi
in a terminal or in console.
inxi --admin --verbosity=7 --filter --no-host --width
- Personally identifiable information such as serial numbers and MAC addresses are filtered out by this command
- Presenting the information in this way allows everyone to be familiar with the format and quickly find the items they need without missing anything.
- Copy the output from inxi (including the command) and paste it into your post.
- To make it more readable, add 3 backticks ``` on an extra line before and after the pasted text.
(Wisdom lies in reading )
I can run
journalctl --boot=-1 --priority=3 --catalog --no-pager
this shows issues for four device(s) /dev/disk/by-uuidā¦ If there is a way to save this output (almost full screen) I will upload it here.
My Data-Device is /mnt/Daten. I can cd this and it shows all the files. Also I see the file f.e. in /var, /opt, /etc. Then I did
# cd /home
# ls
and it is empty.
Sorry, Iām dead for today and will follow up tomorrow ā¦
Did you change /etc/fstab
?
Did you change
/etc/fstab
?
No, but I double checked it now:
# cd /etc
# ls fstabb -l
-rw-r--r-- 1 root root 2854 05. May 2021 fstab
#
What can I do? I have a recent rsync backup for /home on an external USB-HDD; actuallly looks like this:
# cd /home
# ls -laR
.:
total 12
drwr-xr-x 2 root root 4096 7. Nov. 2020
drwr-xr-x 18 root root 4096 3. Nov. 10:27
Is it worth to copy it back? If so, how can I get the drive connected to tje system in emergencĆ½ mode?
I also have a timeshift backup:
# sudo timeshift --restore
...
7 > 2022-12-28 18-00-01 D
restore the timeshift ā¦
or boot into manjaro usb, chroot, and compare uuids in
cat /etc/fstab
and
blkid
the ones in fstab should match the ones in blkid
or boot into manjaro usb, chroot, and compare uuids in
This part first:
I booted the System > EmergencyMode > Enter password
So Iām logged in as root in /. I can run cat /etc/fstab and blkid, the outputs look similar with differences: blkid sows timeshift, fstab does not. But I found all UUIDs from fstab in blkid.
Would it be possible, to copy that output to show it here?
thats good if they matchā¦ you can take a picture of them and post it hereā¦
and was your system working previously?
what did you do prior to this issue? updating/uninstalling/modifying something?
you can take a picture of them and post it hereā¦
and was your system working previously?
Yes!
what did you do prior to this issue? updating/uninstalling/modifying something?
System was working fine after this issue.
Yesterday there were two updates (xnviewmap and zsh-shellā¦) which I installed via pamac, also no issue.
I was working on the machine, left for few hours shutting it down. After that, I started it and found the issue.
did you boot with the 515 kernel?
run this:
journalctl -b0 -p4 --no-pager
and take a pic of itā¦
run this:
journalctl -b0 -p4 --no-pager
UUID 36bā¦ is /home. The myBook- and HDD2go-entries are defined in fstab for manual mounting (noauto).
you have there some errors on your filesystem, so that could be the reasonā¦ check the 5 line of the logs and run the e2fsck command manually:
e2fsck /dev/xxxx
where xxxx is the nvmpā¦ that you have in the logs
Sorry, which nvmp? Tried nvme0n1p3 from line 5: "Is mounted, canāt continue ā¦
the nvmp in the logs in the 5 line from top ends with p3
check with:
lsblk -f
is it the home partition, thats mentioned in the logs with uuid36be?
so its your root/manjaro partition thats p3ā¦
run the e2fsck on the home partition 1p4 anyway and see if there are any errorsā¦
then boot into manjaro usb, and run the e2fck on the 1p3 when its unmountedā¦