A USB device is not getting the device node you expect. You want to watch, live, the kernel uevents and the resulting udev events as you unplug and replug it. Which command does that?
LPIC-1 Exam 101-500, objective 101. System architecture hard
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.
The options
Not correct dmesg -w
Wrong. dmesg -w follows the kernel ring buffer, so you see the kernel's own messages about the device, but udev's rule processing and the resulting device naming never appear there.
Not correct udevadm info --query=all --name=/dev/sdb
Wrong for this purpose. udevadm info queries the udev database for one device's attributes and properties, a static snapshot rather than a live event stream. It is what you use afterwards to find attributes to match on in a rule.
Not correct udevadm trigger
Wrong. udevadm trigger re-emits events for devices already present, which makes new rules apply without a reboot. It generates events, it does not display them.
Correct udevadm monitor
Correct. udevadm monitor prints kernel uevents (KERNEL lines) and the events udev emits after processing its rules (UDEV lines) as they happen, which is the standard way to see what rules actually fire.
Why
The usual udev debugging loop is: udevadm monitor to see the event, udevadm info to read the device's attributes, a rule written under /etc/udev/rules.d (which takes precedence over the rules shipped by packages in /usr/lib/udev/rules.d, still spelled /lib/udev/rules.d on some Debian-derived systems), then udevadm control --reload and udevadm trigger to apply it. dmesg shows the kernel side of the same plug event but nothing about udev.
Where this comes from
- Cited
- LPI exam objective 101.1
- What it says
- Basic understanding of udev, its rule locations and the tools used to inspect device events.
Practise this
Reading one question is not practice. The trainer will draw a short set from objective 101 and space the ones you get wrong.
More questions on this objective
- You have a module file for a network driver on disk but the driver is not loaded. Which command reports the module's description, license, its dependencies and the parameters it accepts, without loading it into the kernel? machine-checked
- A module was loaded together with several modules it depends on. Which command unloads that module and then also unloads the dependencies that are left with a use count of zero? machine-checked
- You are filing a hardware bug report and the maintainer asks for the raw PCI vendor and device ID numbers rather than the human-readable names lspci normally prints. Which lspci option produces the numeric IDs? machine-checked
- On a traditional BIOS PC, the firmware has completed its power-on self test and selected the hard disk as the boot device. What happens next? machine-checked
- A systemd-based machine fails during a normal boot because a service hangs. At the boot loader menu you want to edit the kernel command line for this one boot so the system comes up in single-user rescue mode instead. Which parameter do you append? machine-checked
- A systemd server with a persistent journal rebooted overnight. You need the log messages from the boot that ended in that reboot, not from the current boot. Which command shows them? machine-checked