Rescue a broken system with chroot from a live USB
Boot a live USB, mount the installed system and chroot into it so repairs (grub, packages, fstab) run against the real system.
01Command
$ sudo mount /dev/nvme0n1p2 /mnt && sudo mount --bind /dev /mnt/dev && sudo mount --bind /proc /mnt/proc && sudo mount --bind /sys /mnt/sys && sudo chroot /mnt02What it does
chroot changes the root directory a shell sees, letting you run the installed distribution's own tools even though you booted from a live USB. This is the standard way to reinstall GRUB, rebuild the initramfs, fix a bad fstab entry or reset a forgotten root password. The bind mounts are essential: package managers and grub-install need access to /dev, /proc and /sys of the running kernel.
03Risk
04Undo
$ exit && sudo umount -R /mnt05Sources
- chroot(8) - run command or interactive shell with special root directoryEvidence: chroot runs a command with a specified directory as root; the shell inside sees the target filesystem as /.
- Chroot - ArchWikiEvidence: Rescue procedure: mount the root partition, bind-mount /dev /proc /sys, then chroot to repair bootloaders, packages or passwords.
Last verified: 2026-09-18 · Category: Security & Privacy
06Related solutions
One command that prints every interface with its state and IPv4/IPv6 addresses in a short table — the modern, memorable replacement for digging through `ifconfig` or the verbose `ip addr` output.
The routing table is the first thing to check when traffic leaves the wrong interface or the gateway seems dead — and `ip route show` is the quick, modern way to read it.
The fastest way to answer 'is the firewall blocking me?' — netcat in scan mode attempts one TCP connection and prints whether it succeeded.