Hot answers tagged

3

This /etc/fstab line matches the UUID of the hanging filesystem in the first picture: /dev/disk/by-uuid/166f7ef4-e8e5-496a-8f69-6e7b65fdb5aa /mnt/120gb_fast auto nosuid,nodev,nofail,x-gvfs-show,x-gvfs-name=120GB%20fast 0 0 The second picture has hanging mount by UUID c04ab358-de52-4c2d-9291-3a140d74b252, which is not mentioned anywhere in /etc/fstab as far ...


2

Your boot loader passes a root= argument to the kernel when it loads it telling it what to mount as the root filesystem. /etc/fstab can not be consulted to find this out because the root filesystem where it lives has not yet been mounted. Back in the ancient times before bootloaders were in widespread use, and the kernel could be directly written to say, a ...


1

thanks to oldfred ive solved the problem just by removing the ubuntu folder in /boot/efi/EFI


1

(I am writing this in a way that other users who come across this answer can hopefully use it, not just the OP.) There are multiple methods available for this kind of problem, as well as issues and trade-offs for each. Typically, you do no want a process running constantly that is using up all your CPU/RAM, or you won't be able to use the system! You can ...


1

Short Answer: These prints should always show in /proc/kmsg, so you can run $ cat /proc/kmsg To view them. Each entry even specifies the log level next to it so look for entries that start with '<7>'. More Information: netdev_dbg() is a macro defined in include/linux/netdevice.h, which eventually results in a call to netdev_printk(KERN_DEBUG, ...). ...


Only top voted, non community-wiki answers of a minimum length are eligible