Installation Recovery

Installation Recovery

Recover a Kubuntu Focus System

All general purpose OSes (Windows, MacOS, Linux) can be changed so that the system will no longer boot completely or will behave strangely. A corrupt or full system disk, broken software packages, misconfiguration, and many other situations can cause this. Read on to find how you can use FocusRx and other tools to recover a system.

Please read the disclaimer before proceeding. We review and update guided solutions like this regularly. If you have suggestions or requests, please write support@kfocus.org.

Limitations

Before you proceed, first determine if this is actually a system issue. If your system boots fine, this is likely an application issue. We recommend you first visit the Focus Support page and search for a topic using the list or the search box. These are almost always more current and correct for your hardware than HOWTOs or forum posts you might find on the web. You should continue here only if your system does not completely boot or if you are getting warnings about missing dependencies or libraries.

Recovering an installation may be preferable because applications, settings, and other data will not need to be restored. However, like with all OSes, a badly broken system can take hours to recover and still be problematic. While a Clean Install requires recovery of data, it usually takes well under 30 minutes and can solve issues you do not have time to research or understand. For these reasons, we recommend you always keep a clean installation as an alternative and limit the time you dedicate to recovery efforts.

Any system work always has inherent risks. Mistakes happen, and in this context, that can mean data loss. It is important, therefore, to keep your data safe using a backup solution on an external disk. See the Backup Guided Solution to save your data before proceeding if possible.

Recover from BusyBox Shell

Sometimes the system will boot but drop to a BusyBox Shell as shown below.

BusyBox v1.30.1 (1:1.30.1-4ubuntu6.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) _

This frequently results from a corrupt filesystem, as detailed by this Ask Ubuntu ticket. The solution is to enter the command exit into the shell to report the corrupt filesystem. You may then repair it using fsck <device-file> as shown below.

BusyBox v1.30.1 (1:1.30.1-4ubuntu6.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) exit The root filesystem on /dev/mapper/vgkubuntu-root requires a manual fsck BusyBox v1.30.1 (1:1.30.1-4ubuntu6.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) fsck /dev/mapper/vgkubuntu-root -y fsck from util-linux 2.34 e2fsck 1.45.5 (07-Jan-2020) /dev/mapper/vgkubuntu-root contains a filesystem with errors, check forced.

After the filesystem repair is complete, type in reboot or exit to reboot the system. If the repair was good (which it usually is), the system should now boot normally.

Fix Your System Using FocusRx

Focus systems have a recovery tool called FocusRx which can identify and resolve many issues:

You can run FocusRx as shown below.

Use a Live USB for Recovery

Use a Live USB for Recovery

Please Download the ISO Disk Image and create a bootable, live USB. Then return here to proceed.

Boot using the USB stick as shown below.

Use chroot to Recover a System

1. Use the live USB procedure (above) to boot into the Try Kubuntu mode. Then open a Konsole terminal and enter the lines as shown below.

2a. ENCRYPTED DRIVE ONLY: Decrypt the drive and mount the root filesystem.

sudo -i # Decrypt drive cryptsetup luksOpen /dev/nvme0n1p3 nvme0n1p3_crypt # Mount decrypted drive mount /dev/mapper/vgkubuntu-root /mnt # Proceed if you see 'etc' and 'home': cd /mnt ls

2b. UNENCRYPTED DRIVE ONLY: Mount the root filesystem.

sudo -i # Mount drive mount /dev/nvme0n1p2 /mnt # Proceed if you see 'etc' and 'home': cd /mnt ls

3. Back up your data.

If you haven’t yet backed up your data, please do so NOW! See the Take a Snapshot with USB Drive to save your important files to a separate drive. You can find your user data under /mnt/home/. While each subsequent step below is usually safe, each brings additional risk because of an unknown system state or human error. Better safe than sorry.

4a. ENCRYPTED DRIVE ONLY: Mount the boot and boot/efi filesystems.

# Mount boot and boot/efi cd /mnt mount /dev/nvme0n1p2 boot mount /dev/nvme0n1p1 boot/efi # Proceed if you see 'vmlinuz' and 'initrd.img': ls boot # Proceed if you see 'EFI': ls boot/efi

4b. UNENCRYPTED DRIVE ONLY: Mount the boot/efi filesystem.

# Mount boot/efi cd /mnt mount /dev/nvme0n1p1 boot/efi # Proceed if you see 'EFI': ls boot/efi

5. Prepare and use chroot.

cd /mnt mount -t proc /proc proc mount --rbind /sys sys mount --rbind /dev dev rm etc/resolv.conf cp /etc/resolv.conf etc/resolv.conf chroot .

6. Once the system has successfully switched to chroot mode, you may run FocusRx (above) to fix packages and other common issues.

focusrx -f # One may also repair /etc/default/grub # and run update-grub

7. Here are a few more steps you might try if FocusRx does not solve the problem:

Aptitude package management

See this article for additional details on using chroot.

8. When you are finished fixing the chroot environment, enter exit into terminal. Close the terminal and restart. If the repairs worked, the system should start as normal.

Troubleshooting

Content will be added as needed.

Revisions

This is a partial revision history. See the git repository for all entries.

Disclaimer

We try hard to provide a useful solution validated by professionals. However, we cannot anticipate every situation, and therefore cannot guarantee this procedure will work for your needs. Always backup your data and test the solution to determine the correct procedure for you.

THIS SOLUTION IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOLUTION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

HAVE QUESTIONS? Call 844-536-2871 or write
TellMeMore@kfocus.org | GET FOCUS GEAR

KFocus Logo