[SOLVED] Timed out waiting for device on boot

FuturisticFume · 2024-05-30 18:46:23

I was trying to auto-mount one of my hard drives on boot and copied the line in my /etc/fstab for my /home drive like so.

UUID=8fe1f51e-bff5-46a0-a847-ece8ea4e3f6f     	/mnt/linux-files-2	ext4      	rw,relatime,noauto,x-systemd.automount	0 2

I got the UUID for the hard drive I wanted to mount on boot (/dev/sdd1) from running lsblk and wanted to mount it on /mnt/linux-files-2 which I had a folder for already and was running sudo mount /dev/sdd1 /mnt/linux-files-2 before which worked:

/dev/sdd1: UUID="8fe1f51e-bff5-46a0-a847-ece8ea4e3f6f" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="linux-files-2" PARTUUID="73510b05-1a23-4ec8-9481-3fcd17ea6b60"
/dev/sdb4: BLOCK_SIZE="512" UUID="E030443C30441BC2" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="24638db9-4990-4d22-82b4-47003593a082"
/dev/sdb2: UUID="EE35-254C" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="e3b81953-59b0-43e7-8805-7719a9b7d5e6"
/dev/sdb1: LABEL="Recovery" BLOCK_SIZE="512" UUID="108C2F0C8C2EEC42" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="b9173f0e-b7f7-49fe-be8d-e6939e2c9a2e"
/dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/sde2: SEC_TYPE="msdos" LABEL_FATBOOT="ARCHISO_EFI" LABEL="ARCHISO_EFI" UUID="F938-A458" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="0f8bc94a-02"
/dev/sde1: BLOCK_SIZE="2048" UUID="2018-12-01-10-17-30-00" LABEL="ARCH_201812" TYPE="iso9660" PTUUID="0f8bc94a" PTTYPE="dos" PARTUUID="0f8bc94a-01"
/dev/sdc2: UUID="cbf38663-fc84-4f7d-bf47-efb699ad4d19" TYPE="swap" PARTUUID="ed8d6cb0-02"
/dev/sdc3: UUID="d3ed2df3-bca0-4806-965a-9972b52d8b3c" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="ed8d6cb0-03"
/dev/sdc1: UUID="35cf6588-879a-44c9-a971-2b113ddf3f3a" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="ed8d6cb0-01"
/dev/sda2: UUID="76fab828-b7d3-4b29-b9c3-d1a505c71b5b" TYPE="swap" PARTUUID="24c99faf-02"
/dev/sda3: UUID="6add3a8b-a77d-4dc5-aab2-d7e3ceaaba49" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="24c99faf-03"
/dev/sda1: UUID="82c7a2ef-a680-4300-b9b3-67a9df9c5e5e" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="24c99faf-01"
/dev/sdb3: PARTLABEL="Microsoft reserved partition" PARTUUID="9c90ec21-2999-4b93-a15d-9e0ab6e55db8"

But once I rebooted, I got this error of "Timed out waiting for device":
https://i.imgur.com/YBUbbjh.jpeg

Once this happened, I tried commenting out the line that I added with a # in front of it. This still didn't work. The part that seems strange to me is that the device it is waiting for doesn't match any of the UUID's from lsblk.

I looked up this issue and found this post saying to run pacman -S linux which I did by booting from a Arch Linux USB and arch-chroot'ing in, but this still didn't work.

This is my final /etc/fstab.

## fstab
# <device> 					<dir>		<type> 		<options> 		<dump> <fsck>
# /dev/sda1
UUID=82c7a2ef-a680-4300-b9b3-67a9df9c5e5e	/         	ext4      	rw,discard,relatime	0 1

# /dev/sda3
UUID=6add3a8b-a77d-4dc5-aab2-d7e3ceaaba49	/home     	ext4      	rw,discard,relatime	0 2

# /dev/sda2
UUID=76fab828-b7d3-4b29-b9c3-d1a505c71b5b	none      	swap      	defaults,pri=-2	0 0

# /dev/sdc2
# UUID=d746543f-b996-469a-9c6d-cd298d1870f0     	/mnt/linux-files	ext4      	rw,relatime,noauto,x-systemd.automount	0 2
# UUID=d746543f-b996-469a-9c6d-cd298d1870f0   /mnt/linux-files ext4   defaults,exec,uid=1000,gid=1000	0 2

# /dev/sdd
# UUID=8fe1f51e-bff5-46a0-a847-ece8ea4e3f6f     	/mnt/linux-files-2	ext4      	rw,relatime,noauto,x-systemd.automount	0 2

How do I recover from this issue?

Last edited by FuturisticFume (2024-05-31 14:27:00)

V1del · 2024-05-30 19:33:36

Your fstab is likely incorrectly/old in your initramfs. Assuming that fstab you have above is correct (when the relevant comments uncommented again), simply regenerate your initramfs with

mkinitcpio -P

Last edited by V1del (2024-05-30 19:34:16)

FuturisticFume · 2024-05-30 19:45:39

I tried this command in an arch-chroot but am still getting the same error.

I would also post journalctl -xb, but I can't install netcat for termbin.com since I get this error when I do pacman -Sy netcat.
https://i.imgur.com/xcCBwYp.jpeg

Is there an alternative way to post it if you need this the journalctl output?

Last edited by V1del (2024-05-30 21:59:53)

Funny0facer · 2024-05-30 20:27:18

have a look at https://wiki.archlinux.org/title/List_o … ted_client

FuturisticFume · 2024-05-30 20:41:47

It can't resolve the host when using 0x0.st.
https://i.imgur.com/r1ZMR2G.jpeg

ping 8.8.8.8 gives ping: connect: Network is unreachable.

Last edited by V1del (2024-05-30 21:59:33)

seth · 2024-05-30 21:35:40

You don't need network access for "mkinitcpio -P" the other thre ran a - itr - pointelss kernel update that implciitly regenerates the initramfs.

You still need to setup your network in the install iso and if you're gonna chroot, use the arch-chroot script.
Then please post the output of "lsblk -f" (before! chrooting)

nb. the bogus device is your /home partition and there's a stray UTF-8 character instead of "d3e" in the error message.
vim-accident?

V1del · 2024-05-30 22:00:45

Mod note, please don't embed huge images directly, just link to them instead.

FuturisticFume · 2024-05-30 22:14:58

I ran "mkinitcpio -P" in the arch-chroot script fine without networking.

This is the "lsblk -f" before chrooting:

NAME   FSTYPE   LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINT
loop0  squashfs                                                        0   100% /run/archiso/sfs/airootfs
sda                                                                             
├─sda1 ext4                 82c7a2ef-a680-4300-b9b3-67a9df9c5e5e                
├─sda2 swap                 76fab828-b7d3-4b29-b9c3-d1a505c71b5b                
└─sda3 ext4                 6add3a8b-a77d-4dc5-aab2-d7e3ceaaba49                
sdb                                                                             
├─sdb1 ntfs     Recovery    108C2F0C8C2EEC42                                    
├─sdb2 vfat                 EE35-254C                                           
├─sdb3                                                                          
└─sdb4 ntfs                 E030443C30441BC2                                    
sdc                                                                             
├─sdc1 ext4                 35cf6588-879a-44c9-a971-2b113ddf3f3a                
├─sdc2 swap                 cbf38663-fc84-4f7d-bf47-efb699ad4d19                
└─sdc3 ext4                 d3ed2df3-bca0-4806-965a-9972b52d8b3c                
sdd                                                                             
└─sdd1 ext4                 8fe1f51e-bff5-46a0-a847-ece8ea4e3f6f                
sde    iso9660  ARCH_201812 2018-12-01-10-17-30-00                              
├─sde1 iso9660  ARCH_201812 2018-12-01-10-17-30-00                     0   100% /run/archiso/bootmnt
└─sde2 vfat     ARCHISO_EFI F938-A458

So, I see that the offending partition is /dev/sdc3 from this. But, this isn't in my /etc/fstab for sda which is the hard drive I'm trying to boot from. So, why is it trying to mount /dev/sdc3 which is a /home partition for another Arch installation? I don't even know where the Vim error could be since the "d3ed2df3-bca0" UUID isn't in my /etc/fstab for sda.

Side note responding to V1del: Will link to images in further posts.

seth · 2024-05-31 06:55:00

Sure you're booting the proper system?
nb. that the sdX order is NOT deterministic, sda and sdc could swap places anytime - always address them by UUID in grub and fstab.

Also as V1del pointed out you might have had a bogus fstab in the initramfs - did the mkinitcpio change anything about that?
Did you mount any partition into /boot before running it?
From the rescue.target, run and post the output of

cat /proc/cmdline

FuturisticFume · 2024-05-31 14:26:34

@Seth: Yes, so I was modifying the wrong /etc/fstab. I was modifying sda when I was trying to boot into sdc. You also mentioned the UTF-8 character in my error message. What worked and helped me boot was "lsblk -f >> /etc/fstab" and replacing the same UUID.

Thanks everyone for the help!

seth · 2024-05-31 14:45:56

Make sure you've no double entries left in your fstab - ftr. and out of curiosity: any idea what might have caused the bogus character?

FuturisticFume · 2024-05-31 15:17:57

There are no double entries, thanks. I have no idea about the bogus character. When I checked the fstab, it all looked like normal characters to me. I even tried manually replacing/typing out the characters before what the error was saying was bogus, and it still didn't work.

Arch Linux

#1 2024-05-30 18:46:23

[SOLVED] Timed out waiting for device on boot

#2 2024-05-30 19:33:36

Re: [SOLVED] Timed out waiting for device on boot

#3 2024-05-30 19:45:39

Re: [SOLVED] Timed out waiting for device on boot

#4 2024-05-30 20:27:18

Re: [SOLVED] Timed out waiting for device on boot

#5 2024-05-30 20:41:47

Re: [SOLVED] Timed out waiting for device on boot

#6 2024-05-30 21:35:40

Re: [SOLVED] Timed out waiting for device on boot

#7 2024-05-30 22:00:45

Re: [SOLVED] Timed out waiting for device on boot

#8 2024-05-30 22:14:58

Re: [SOLVED] Timed out waiting for device on boot

#9 2024-05-31 06:55:00

Re: [SOLVED] Timed out waiting for device on boot

#10 2024-05-31 14:26:34

Re: [SOLVED] Timed out waiting for device on boot

#11 2024-05-31 14:45:56

Re: [SOLVED] Timed out waiting for device on boot

#12 2024-05-31 15:17:57

Re: [SOLVED] Timed out waiting for device on boot

Board footer