Today after turning on my Jetson Orin Nano (running Ubuntu 20.04) I noticed I was connected to Wi-Fi but could not connect to the internet using my browser.
After some testing I noticed I was connected to the LAN and could ping hosts inside and outside my network.
The problem appears to be with the DNS which cannot resolve names. I manually added the DNS IPs to the file `/etc/resolv.conf` like so:
```
nameserver
```
Great, the DNS is now set up and I can ping domains.
The problem is that the file is overwritten each time I restart the Jetson. Looking into it I discovered that the `systemd-resolved` service manages the DNS in Ubuntu.
I then ran `journalctl -u systemd-resolved.service` to see the service logs which produced the following error several times:
```
– Logs begin at Wed 2023-03-15 16:04:16 CET, end at Fri 2025-09-05 17:45:59 CEST. –
mar 15 16:04:19 user systemd[1]: Starting Network Name Resolution…
mar 15 16:04:20 user systemd[476]: systemd-resolved.service: Failed to execute command: Structure needs cleaning
mar 15 16:04:20 user systemd[476]: systemd-resolved.service: Failed at step EXEC spawning /lib/systemd/systemd-resolved: Structure needs cleaning
mar 15 16:04:20 user systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=203/EXEC
mar 15 16:04:20 user systemd[1]: systemd-resolved.service: Failed with result ‘exit-code’.
mar 15 16:04:20 user systemd[1]: Failed to start Network Name Resolution.
mar 15 16:04:20 user systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 1.
```
Some formus suggests that the `Structure needs cleaning` error is related to a possible file system corruption.
Does anyone have any suggestions on how to fix the error?
*** Please note that this reply is generated by LLM automatically ***
The issue you’re experiencing with the DNS resolution on your Jetson Orin Nano running Ubuntu 20.04 seems to be related to the systemd-resolved service. The error message “Structure needs cleaning” is quite generic and can be caused by various factors, including file system corruption, configuration issues, or even a bug in the systemd-resolved service.
Before we dive into potential solutions, let’s compare the behavior of systemd-resolved on your Jetson Orin Nano with other similar issues reported by users.
Similar issues:
Some users have reported similar issues with systemd-resolved on Ubuntu-based systems, where the service fails to start or resolve DNS queries due to file system corruption or configuration issues.
In some cases, the issue was resolved by running fsck to check and repair file system errors.
Others have reported success by disabling and re-enabling the systemd-resolved service or by restarting the service after making changes to the DNS configuration.
Potential solutions:
Run fsck to check and repair file system errors: As some users have reported success with this approach, it’s worth trying. Run fsck on the root file system to check for errors and repair them if necessary.
sudo fsck -f -y /
Disable and re-enable systemd-resolved: Try disabling the systemd-resolved service, waiting for a few seconds, and then re-enabling it. This may help resolve any configuration issues or corruption.
Restart systemd-resolved after DNS configuration changes: If you’ve made changes to the DNS configuration, try restarting the systemd-resolved service to ensure the changes take effect.
sudo systemctl restart systemd-resolved
Check DNS configuration: Verify that the DNS configuration is correct and that the systemd-resolved service is configured to use the correct DNS servers. You can check the DNS configuration by running:
sudo resolvectl status
Reconfigure systemd-resolved: If none of the above steps resolve the issue, you can try reconfiguring systemd-resolved by running:
sudo dpkg-reconfigure systemd-resolved
This will prompt you to reconfigure the systemd-resolved service and may help resolve any underlying issues.
Comparison with other Jetson boards:
While the issue you’re experiencing is specific to your Jetson Orin Nano, it’s worth noting that other Jetson boards may have similar issues with DNS resolution. For example, some users have reported issues with DNS resolution on the Jetson Xavier NX, which were resolved by updating the systemd-resolved service or by configuring the DNS settings manually.
In summary, the issue you’re experiencing with DNS resolution on your Jetson Orin Nano is likely related to the systemd-resolved service. By trying the potential solutions outlined above, you may be able to resolve the issue and get DNS resolution working correctly on your device.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***