Logs discoveries, part 1: Timed out waiting for device
- Inicie sesión ou rexístrese para enviar comentarios
Dear Trisquel users,
After a lot of unexpected screen freezes I'm now watching Logs (Gnome SystemD Journal viewer)
After booting there's an impressive list. On the "Important" tab, at the top there is the following error:
Timed out waiting for device dev-disk-by\x2duuid-447610aa\x2db7da\x2d45af\x2d9d33\x2db98539ae96f3.device.
Priority: 3
Unit dev-disk-by\x2duuid-447610aa\x2db7da\x2d45af\x2d9d33\x2db98539ae96f3.device has failed
Defined by: systemd
Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Unit dev-disk-by\x2duuid-447610aa\x2db7da\x2d45af\x2d9d33\x2db98539ae96f3.device has failed.
The result is timeout.
Thank you.
What is the output of this command, to be executed in a terminal?
$ lsblk -f
$ lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sr0
sda
├─sda2 ext4 813b4f15-4ce7-4f63-93c3-b3b60819133d /home
├─sda3 swap 390b3c50-9920-426d-b68e-660b14c72d46 [SWAP]
└─sda1 ext4 fa3e72e0-50a7-4278-b61e-1d0c52024acc /
The UUID does not identify any partition on your disk. What is in your /etc/fstab?
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/sda1 during installation
UUID=fa3e72e0-50a7-4278-b61e-1d0c52024acc / ext4 errors=remount-ro 0 1
# /home was on /dev/sda2 during installation
UUID=813b4f15-4ce7-4f63-93c3-b3b60819133d /home ext4 defaults 0 2
# swap was on /dev/sda3 during installation
UUID=390b3c50-9920-426d-b68e-660b14c72d46 none swap sw 0 0
UUID=447610aa-b7da-45af-9d33-b98539ae96f3 /media/data ext4 noexec,nofail 0 0
The last line makes the init try to attach an ext4 filesystem at /media/data. Where does this partition come from? An external disk? A partition on /dev/sda you have removed since then? The init does not find it, hence the error, which would be suppressed if you remove or comment (inserting # at the beginning) the last line of /etc/fstab. To do so, you need administrative privileges:
$ sudo pluma /etc/fstab # you can substitute pluma with your favorite text editor
Thank you very much.
It could be my external harddrive.
Now, a few screen freezes further, this particular message doesn't show up in the log files anymore.
Executing 'lsblk -f' after plugging the external disk would confirm/infirm you hypothesis. I believe its ext4 filesystem would then be attached at /media/data, thanks to the last line in your /etc/fstab... but the default directory, without that line, would be similar (at least it would be in /media), if not the same. Since you apparently have not added the line yourself, I guess your external disk was plugged when you installed the system.
All that written, I do not think the error has any impact on the init time, because nothing depend on that filesystem being mounted. If you are interested in graphically analyzing what takes time during the init:
$ systemd-analyze plot > systemd.svg
"systemd.svg" can then be opened with Eye of MATE (or any other viewer that understands SVG).
- Inicie sesión ou rexístrese para enviar comentarios