Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My pc stuck on boot process, it enters to the emergency mode and i can't access to user folders from that mode (home folder of my default user does not appear under root directory). I can enter root password but could not detect the problem.
@OP Check that the UUID shown in the output of lsblk -f for /home is the same as in the log output below, i.e. 1d152923-1a42-4186-b72d-69aec580a779
(Just copied the relevant part of the log here for whomever will find this useful)
Code:
Apr 18 18:44:41 localhost.localdomain systemd[1]: dev-disk-by\x2duuid-1d152923\x2d1a42\x2d4186\x2db72d\x2d69aec580a779.device: Job dev-disk-by\x2duuid-1d152923\x2d1a42\x2d4186\x2db72d\x2d69aec580a779.device/start timed out.
Apr 18 18:44:41 localhost.localdomain systemd[1]: Timed out waiting for device /dev/disk/by-uuid/1d152923-1a42-4186-b72d-69aec580a779.
-- Subject: A start job for unit dev-disk-by\x2duuid-1d152923\x2d1a42\x2d4186\x2db72d\x2d69aec580a779.device has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit dev-disk-by\x2duuid-1d152923\x2d1a42\x2d4186\x2db72d\x2d69aec580a779.device has finished with a failure.
--
-- The job identifier is 154 and the job result is timeout.
Apr 18 18:44:41 localhost.localdomain systemd[1]: Dependency failed for /home.
-- Subject: A start job for unit home.mount has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit home.mount has finished with a failure.
--
-- The job identifier is 152 and the job result is dependency.
Apr 18 18:44:41 localhost.localdomain systemd[1]: Dependency failed for Local File Systems.
-- Subject: A start job for unit local-fs.target has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit local-fs.target has finished with a failure.
--
-- The job identifier is 147 and the job result is dependency.
Apr 18 18:44:41 localhost.localdomain systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Apr 18 18:44:41 localhost.localdomain systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
Apr 18 18:44:41 localhost.localdomain systemd[1]: home.mount: Job home.mount/start failed with result 'dependency'.
Apr 18 18:44:41 localhost.localdomain systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/1d152923-1a42-4186-b72d-69aec580a779.
-- Subject: A start job for unit systemd-fsck@dev-disk-by\x2duuid-1d152923\x2d1a42\x2d4186\x2db72d\x2d69aec580a779.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit systemd-fsck@dev-disk-by\x2duuid-1d152923\x2d1a42\x2d4186\x2db72d\x2d69aec580a779.service has finished with a failure.
--
-- The job identifier is 153 and the job result is dependency.
Apr 18 18:44:41 localhost.localdomain systemd[1]: systemd-fsck@dev-disk-by\x2duuid-1d152923\x2d1a42\x2d4186\x2db72d\x2d69aec580a779.service: Job systemd-fsck@dev-disk-by\x2duuid-1d152923\x2d1a42\x2d4186\x2db72d\x2d69aec580a779.service/start failed with result 'dependency'.
Apr 18 18:44:41 localhost.localdomain systemd[1]: dev-disk-by\x2duuid-1d152923\x2d1a42\x2d4186\x2db72d\x2d69aec580a779.device: Job dev-disk-by\x2duuid-1d152923\x2d1a42\x2d4186\x2db72d\x2d69aec580a779.device/start failed with result 'timeout'.
Starting Switch Root...
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
[FAILED] Failed to mount Arbitrary Executable File Formats File System.
See 'systemctl status proc-sys-fs-binfmt_misc.mount' for details.
(there are more like these)
You can find the commands you need to execute to get more info.
Probably your disk has gone, but probably "only" the filesystem was corrupted (or something else).
Starting Switch Root...
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
[FAILED] Failed to mount Arbitrary Executable File Formats File System.
See 'systemctl status proc-sys-fs-binfmt_misc.mount' for details.
(there are more like these)
You can find the commands you need to execute to get more info.
Probably your disk has gone, but probably "only" the filesystem was corrupted (or something else).
I use linux-Win dual boot, i can access and copy the home folder files from windows.
systemctl status systemd-modules-load.service
Code:
● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
Active: active (exited) since Mon 2020-04-20 13:01:47 +03; 4min 44s ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 536 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS)
Main PID: 536 (code=exited, status=0/SUCCESS)
CPU: 8ms
[FAILED] Failed to mount Arbitrary Executable File Formats File System.
[FAILED] Failed to start ABRT Automated Bug Reporting Tool.
[FAILED] Failed to start Avahi mDNS/DNS-SD Stack.
[FAILED] Failed to start Bluetooth service.
[FAILED] Failed to start D-Bus System Message Bus.
[FAILED] Failed to start Load Kernel Modules.
[FAILED] Failed to start Network Manager.
[FAILED] Failed to start RealtimeKit Scheduling Policy Service.
[FAILED] Failed to start Set Up Additional Binary Formats.
These are the failed services. Need to find the reason, but the information you posted looks insufficient (at least I could not catch it).
Probably you can use smartctl to check your disks, maybe one of them does not work properly.
@pan64 But these are all old messages (before Apr 14, 17:02:59, which was the first boot time in the log that /home couldn't be mounted). I don't see any failed service message in the provided boot.log after that.
I tried with live cd, then check the disk , windows files accessable but linux home folder cant detect. But i can see the linux home folder from windows disk-menager:
can you post the output of: sudo fdisk -l
and the file: /etc/fstab
fdisk -l:
Code:
omitting empty partition (7)
Disk /dev/sda: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x3d186752
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 1026047 1024000 500M 7 HPFS/NTFS/exFAT
/dev/sda2 1026048 448589823 447563776 213.4G 7 HPFS/NTFS/exFAT
/dev/sda3 448589824 450686975 2097152 1G 83 Linux
/dev/sda4 450686976 976773119 526086144 250.9G 5 Extended
/dev/sda5 450689024 467013631 16324608 7.8G 82 Linux swap / Solaris
/dev/sda6 467015680 571873279 104857600 50G 83 Linux
Disk /dev/sdb: 7.47 GiB, 8010072064 bytes, 15644672 sectors
Disk model: Flash Drive
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0029287f
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 15644671 15642624 7.5G c W95 FAT32 (LBA)
/etc/fstab:
Code:
# /etc/fstab
# Created by anaconda on Sun Jun 10 00:27:51 2018
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=6a70d03d-8673-4c85-b0e9-0fafbda576d7 / ext4 defaults 1 1
UUID=9da1a604-899a-444d-b020-6d3d40775b20 /boot ext4 defaults 1 2
UUID=1d152923-1a42-4186-b72d-69aec580a779 /home ext4 defaults 1 2
UUID=68d9f546-dbcf-471f-b213-c4a391fc9c73 swap swap defaults 0 0
/dev/disk/by-id/usb-Flash_USB_Disk_372720284E12CB3932703-0:0 /mnt/usb-Flash_USB_Disk_372720284E12CB3932703-0:0 auto nosuid,nodev,nofail,noauto,x-gvfs-show 0 0
You have still a lot of lines like this: The unit XXX has successfully entered the 'dead' state, which looks abnormal for me. But probably not.
Can you post the result of blkid too?
You have still a lot of lines like this: The unit XXX has successfully entered the 'dead' state, which looks abnormal for me. But probably not.
Can you post the result of blkid too?
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda4
Could this be a zero-lenght partition?
Last edited by hnoz; 04-20-2020 at 06:29 PM.
Reason: Code update ++++++
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.