lazz0r
Posts: 6
Joined: Mon May 02, 2016 3:37 am

Timed Out Waiting For Device During Boot

Wed Aug 15, 2018 2:15 am

I'm Kind of a noob at Linux. I generally know enough to get myself in trouble. That being said, I purchased a 128GB Sandisk Memory Card hoping to run it in a Raspberry Pi. It generally appears to work okay except when the disk has to be checked on system startup.

Then this happens:
strangeboot.png
strangeboot.png (18.69 KiB) Viewed 592 times
Am I reading correctly that it takes too long to check the disk and the system times out waiting for it? I've tried to research how to change this timeout and have come up empty. After things settle down, I press Enter to continue and it appears the RPi can sill run normally. It's kind of annoying, but is this anything I should even be concerned with?

User avatar
DougieLawson
Posts: 34096
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website

Re: Timed Out Waiting For Device During Boot

Thu Aug 16, 2018 2:01 pm

It means the UUID/PARTUUID in your /etc/fstab doesn't match the ID on your /boot partition.

You're probably not going to be able to fix it with the emergency console. So you'll need a new SDCard, a copy of Raspbian, a copy of Etcher (to write Raspbian to the new SDCard) and a USB reader.

Boot the new Raspbian, insert the broken system in the USB reader, insert the USB reader in your RPi. Use that "rescue" system to discover the UUID/PARTUUID that needs to be in /etc/fstab with a sudo blkid command. Fix up /etc/fstab with nano. Power off, swap cards and see how it goes.
Microprocessor, Raspberry Pi & Arduino Hacker
Mainframe database troubleshooter
MQTT Evangelist
Twitter: @DougieLawson

2012-18: 1B*5, 2B*2, B+, A+, Z, ZW, 3Bs*3, 3B+

Any DMs sent on Twitter will be answered next month.

lazz0r
Posts: 6
Joined: Mon May 02, 2016 3:37 am

Re: Timed Out Waiting For Device During Boot

Fri Aug 17, 2018 4:48 am

DougieLawson wrote:
Thu Aug 16, 2018 2:01 pm
It means the UUID/PARTUUID in your /etc/fstab doesn't match the ID on your /boot partition.

You're probably not going to be able to fix it with the emergency console. So you'll need a new SDCard, a copy of Raspbian, a copy of Etcher (to write Raspbian to the new SDCard) and a USB reader.

Boot the new Raspbian, insert the broken system in the USB reader, insert the USB reader in your RPi. Use that "rescue" system to discover the UUID/PARTUUID that needs to be in /etc/fstab with a sudo blkid command. Fix up /etc/fstab with nano. Power off, swap cards and see how it goes.

Thank you for your help!
I am in some unfamiliar territory here.

I gather that I'm looking for 174bf115-01 and 174bf115-02. From blkid:

Code: Select all

[email protected]:~ $ sudo blkid
/dev/mmcblk0p1: LABEL="boot" UUID="13C6-2676" TYPE="vfat" PARTUUID="a43ca768-01"
/dev/mmcblk0p2: UUID="037616fd-28fe-4652-8248-2042ea30b929" TYPE="ext4" PARTUUID="a43ca768-02"
/dev/sda1: LABEL="boot" UUID="0298-4814" TYPE="vfat" PARTUUID="174bf115-01"
/dev/sda2: LABEL="rootfs" UUID="d4f0fd64-ad9d-4cfd-aa76-8d3541fbf008" TYPE="ext4" PARTUUID="174bf115-02"
/dev/mmcblk0: PTUUID="a43ca768" PTTYPE="dos"

And from file: /media/pi/rootfs/etc/fstab on the 128GB card:

Code: Select all

proc            /proc           proc    defaults          0       0
PARTUUID=174bf115-01  /boot           vfat    defaults          0       2
PARTUUID=174bf115-02  /               ext4    defaults,noatime  0       1
# a swapfile is not a swap partition, no line here
#   use  dphys-swapfile swap[on|off]  for that
I think the PARTUUIDs are already set correctly. I didn't modify anything there.

A few more details:
Raspbian appears to boot correctly and run without issue when booted off of the 128GB card, but only when the card isn't checked on startup.

When the card is checked on startup, it doesn't seem to finish checking the card before the system appears to continue without it. Eventually it goes on about being in emergency mode while the card check is still ongoing at this point. I let the card check finally finish and press Enter per the prompt. Raspbian finishes booting into the GUI at that point, and the system appears to work normally (from what I can tell). Even after all of the alarming text about being in emergency mode.

User avatar
DougieLawson
Posts: 34096
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website

Re: Timed Out Waiting For Device During Boot

Fri Aug 17, 2018 4:03 pm

What's in /boot/cmdline.txt?
Microprocessor, Raspberry Pi & Arduino Hacker
Mainframe database troubleshooter
MQTT Evangelist
Twitter: @DougieLawson

2012-18: 1B*5, 2B*2, B+, A+, Z, ZW, 3Bs*3, 3B+

Any DMs sent on Twitter will be answered next month.

lazz0r
Posts: 6
Joined: Mon May 02, 2016 3:37 am

Re: Timed Out Waiting For Device During Boot

Fri Aug 17, 2018 11:50 pm

Code: Select all

dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=PARTUUID=174bf115-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait consoleblank=0

User avatar
DougieLawson
Posts: 34096
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website

Re: Timed Out Waiting For Device During Boot

Sat Aug 18, 2018 8:46 am

That's interesting. Something needs a longer timeout before assuming the fsck has failed.
Microprocessor, Raspberry Pi & Arduino Hacker
Mainframe database troubleshooter
MQTT Evangelist
Twitter: @DougieLawson

2012-18: 1B*5, 2B*2, B+, A+, Z, ZW, 3Bs*3, 3B+

Any DMs sent on Twitter will be answered next month.

lazz0r
Posts: 6
Joined: Mon May 02, 2016 3:37 am

Re: Timed Out Waiting For Device During Boot

Sat Aug 18, 2018 2:29 pm

I've been doing research off and on about this before I go to work in the morning. I found some info relating to the device timeout at https://wiki.archlinux.org/index.php/Fs ... th_systemd .

I changed my fstab to include ,x-systemd.device-timeout=120 .

Code: Select all

proc            /proc           proc    defaults,x-systemd.device-timeout=120          0       0
PARTUUID=174bf115-01  /boot           vfat    defaults,x-systemd.device-timeout=120          0       2
PARTUUID=174bf115-02  /               ext4    defaults,noatime,x-systemd.device-timeout=120  0       1
# a swapfile is not a swap partition, no line here
#   use  dphys-swapfile swap[on|off]  for that
And that took care of most of the issue, emergency mode and all.

the only issue that remains now is the line

Code: Select all

[ TIME ] Timeout waiting for device dev-serial1.device.
Perhaps there a config for that somewhere too.

justinatienza
Posts: 3
Joined: Thu Oct 04, 2018 5:22 pm

Re: Timed Out Waiting For Device During Boot

Wed Oct 10, 2018 12:59 am

DougieLawson wrote:
Sat Aug 18, 2018 8:46 am
That's interesting. Something needs a longer timeout before assuming the fsck has failed.
@DougieLawson

I am having the same issue as well on raspbian 4.14.70, latest from apt-get upgrade. i have created a copy of my pi image doing the following:
1. dd bs=4M if=/dev/sda of=imagefile.img
2. i then run pishrink to get it down to smaller size
3 .Then from there i use etcher to burn that image onto multiple SD cards.

I am getting the partuuid error on a good majority of them, how do i backup and sd card and then burn onto other sd cards.

any help would be appreciated.

another interesting point is that the blkid partuuid value matches that of my cmdline.txt AND the /etc/fstab

Thank you
Last edited by justinatienza on Wed Oct 10, 2018 1:45 am, edited 1 time in total.

Return to “Troubleshooting”