Can't boot past splash, timed out waiting for device

I’ve been using gnome for well over a year but have recently run into problems at reboots with “timed out waiting for device” along with “dependency failed.” Usually I’d have to force another reboot and it would then start.

Except now it won’t! Can anyone help me learn to solve this issue? I’m just not sure where to start and searches haven’t gotten me very far.

I can boot from live usb, for all the good it does me because I’m not quite sure what to do from there!

I do appreciate some help with this.

Hello @Kelltech :wink:

Have a look at /etc/fstab :wink: First thought would be that the UUID changed somehow and therefore it can’t find the partition. That happens when you resize a partition for example or the a partition is not there anymore or the SSD/HDD died…

Open a terminal and type manjaro-chroot -a when on a live session. Then please post these outputs:

cat /etc/fstab

and

blkid

Hey megavolt, thank you for your reply. Here is the results of the two outputs:

[manjaro-gnome /]# cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>

UUID=B087-574B	/boot/efi	vfat	umask=0077	0	2
UUID=af2b505e-d0e1-4a35-8165-3f29ae45a52f	/	ext4	defaults,noatime	0	1
UUID=0785422f-231a-4033-b244-0a84826dd733	swap	swap	defaults,noatime	0	2
/dev/disk/by-uuid/19a6e033-41fb-4132-8234-8ae8908189dd	/mnt/19a6e033-41fb-4132-8234-8ae8908189dd	auto	nosuid,nodev,nofail,x-gvfs-show	0	0
UUID=a4fdf2f3-223b-46c0-989b-6a996557f19d	/home	ext4	defaults	0	2
[manjaro-gnome /]# blkid
/dev/nvme0n1p1: UUID="B087-574B" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="9d062975-c4ab-49b2-8456-d1f2b3558f56"
/dev/nvme0n1p2: UUID="af2b505e-d0e1-4a35-8165-3f29ae45a52f" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="e47b1889-2243-4726-9a99-0cc68d6a49ef"
/dev/nvme0n1p3: UUID="0785422f-231a-4033-b244-0a84826dd733" TYPE="swap" PARTUUID="327bf7d2-1f43-4c6d-8cdc-54b9e3d7750e"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/sda1: BLOCK_SIZE="2048" UUID="2020-12-03-10-06-11-00" LABEL="MANJARO_GNOME_202" TYPE="iso9660"
/dev/sda2: SEC_TYPE="msdos" LABEL_FATBOOT="MISO_EFI" LABEL="MISO_EFI" UUID="7239-C206" BLOCK_SIZE="512" TYPE="vfat"

I don’t know if this is helpful, but here’s some information I see just before I entered those commands:

grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
==> Mounting (ManjaroLinux) [/dev/nvme0n1p2]
--> mount: [/mnt]
--> mount: [/mnt/boot/efi]
-> mount: [/mnt/home]
mount: /mnt/home: special device /dev/disk/by-uuid/a4fdf2f3-223b-46c0-989b-6a996557f19d does not exist.

Here is the issue. This UUID is not available on your disks.

Well, that doesn’t sound so good. Where can I start looking for a fix, or is there one?

Where do you expect that the /home partition should be? Can’t see any partition which could match…

This could say more:

sudo parted -l
[manjaro-gnome /]# sudo parted -l
Model: USB Driver (scsi)
Disk /dev/sda: 4008MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 2      2816MB  2820MB  4194kB  primary               esp


Model: WDC WDS256G1X0C-00ENX0 (nvme)
Disk /dev/nvme0n1: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system     Name  Flags
 1      2097kB  317MB  315MB   fat32                 boot, esp
 2      317MB   238GB  237GB   ext4
 3      238GB   256GB  18.4GB  linux-swap(v1)        swap

@Kelltech If there was another partition on /dev/nvme0n1 for home then it is not there anymore… Maybe it it is now on nvme0n1p2 ? In this case you can comment out the line with /home in fstab or just delete the line.

@megavolt I was able to edit that line out and booted right up to the login screen. After entering my password it just refreshes the login screen though. :joy:

I think it’s time now to tell us why and when the fstab entry for /home has been implemented. I fear you don’t tell us all what is needed to help you. :upside_down_face:

If I knew why I’d certainly say so :grin:
The best I can think of is because I had a lot of trouble getting things running with Nvidia/Intel graphics and getting set up with a secondary hdd. That was more than a year ago now and the good man that helped me through that was all on the former Manjaro board.

And I’ve been learning ever since then :joy:

Could it be that your /home partition is located on the secondary hdd?

Connect it and run

sudo parted -l

again.

I will do that as soon as I can figure out how to log in, its rejecting my password :disappointed_relieved:

Boot a live ISO (USB stick), the password when booting a live ISO (whenever needed) is:

manjaro

Right, but I’m trying to log in to my system. I can boot to my login screen but entering the password shows me the splash screen and back to the login. Quite strange.

This does not help for the moment. Let’s see where your /home partition is located, first (in case there exists one).

Ah, sorry I misunderstood, but have now booted from live once more and have the output. What I have is a 256gb SSD and a 1tb HDD where I keep files, apps, installed programs, etc.

Edit: If I’m not mistaken, I don’t even see that 1tb hdd represented here. :thinking:

[manjaro-gnome /]# sudo parted -l
Model: USB Driver (scsi)
Disk /dev/sda: 4008MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 2      2816MB  2820MB  4194kB  primary               esp


Model: WDC WDS256G1X0C-00ENX0 (nvme)
Disk /dev/nvme0n1: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system     Name  Flags
 1      2097kB  317MB  315MB   fat32                 boot, esp
 2      317MB   238GB  237GB   ext4
 3      238GB   256GB  18.4GB  linux-swap(v1)        swap

If that is true, then i would say the HDD died or the connector has a loose contact…

Sadly I will agree it has died. I opened up and checked, all connections seem good.

Perhaps a question for a new thread, or else I can search tomorrow, can I create a new /home on the existing SSD, or do I need to wipe it and start fresh?