Some of the error on Linux is annoying and the “umount target is busy” error is one of the them. It normally occurs while you try to umount a filesystem or drive in Linux. It happens when you are trying to mount a device or filesystem that is being used by the some process in Linux. It occurs to prevent data loss in Linux.  In this tutorial, we will gudie you through the process to fix umount target is busy in Linux.

How to Fix umount target is busy in Linux

There are multiple ways to to fix umount target is busy error in Linux.

1. Using fuser –  Kill processes accessing the file

In this method, we will take the help of fuser command. It normally identify the processes which are accessing sockets or files on filesystems. Run the following command with -m option to list down the all processes that is accessing the files or mount point on the file system in a tabular format.

fuser -mv /media/dsk

After figuring out the processes that is using the file on the mounted filesystem, You can use the following kill command to delete or terminate those processes.

fuser -kmv /media/dsk

2. Using lsof – Find and Kill the processes using the file

In this method, we will use  lsof  command to display the all open files and the processes associated with them and kill them afterward. Run the following command to find PID (process id) corresponding to the mount point.

lsof /media/dsk or lsof  | grep '/media/dsk'

Now, Run the kill process to terminate the particular process:

kill -9 3522
kill -9 4001

3. Lazy unmount

Lazy unmounting command removes all references to the detached file system when the process holding or occupying particular filesystem or the mount is no longer using it or holding it. Once no processes are accessing the unmounted file system, the umount command executes and actually detaches the file system. To lazy unmount run the command with  -l option followed by the mount path:

umount -l

4. Force unmount to Fix “umount target is busy” in Linux

You can use this option if you are trying to unmount an NFS filesystem in Linux. Force unmount will detach the server mount point by terminating the running processes.

unmount -f /path/to/busy-nfs-mount

The post How To Fix “umount target is busy” in Linux first appeared on AtoZ Linux.

Have you ever came across the error “locale: Cannot Set LC_ALL to default locale: No such file or directory” in Linux then this blog post is for you. Here we have the solution for the error  “locale: Cannot Set LC_ALL to default locale: No such file or directory”.

How To Fix Error “Locale: Cannot Set LC_ALL to default locale: No such file or directory”

Locales are mainly used in Linux to define the language that the user can use.  You will come across this error if you messed up while setting up the correct locale for the non-ASCII characters.

You can list all system’s currently installed locales with the following command

locale -a

You will see the output something like below:

LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

Let’s go to the process to fix the error:

At first, run the following command to export variable to LC_ALL parameter

$ export LC_ALL="en_US.UTF-8"

Now, run the following command to enable the locales:

$ sudo locale-gen "en_US.UTF-8"
$ sudo dpkg-reconfigure locales

You can also enable the locales by editing the /etc/default/locale file. You need to set LANG parameter as below

LANG=en_US.UTF-8

Now at the last, Make sure you have installed glibc-locale package on the system.

The post How To Fix Error “Locale: Cannot Set LC_ALL to default locale: No such file or directory” first appeared on AtoZ Linux.

Are you tired of error RESULT_CODE_HUNG while browsing internet with Google Chrome or any other  Chromium-based browsers then you are at the right place. We will help you to solve the “Aw Snap” issue with the error code RESULT_CODE_HUNG in Google Chrome or any other Chromium browsers.

Multiple Ways To Fix RESULT_CODE_HUNG Error in Google Chrome

Before jumping into the solution, let’s have a look into the what actually the error means.

What is the meaning of RESULT_CODE_HUNG error in Google Chrome?

It means that a specific tab has become unresponsive and is not working properly.

Allright, let’s have a look into the solution for the RESULT_CODE_HUNG Error in Google Chrome.

1. Check Your Internet Connection

Sometime internet might be reason behind the error. A slow internet connection will not be able to load the web pages that might contain heavy files properly and the “Aw Snap” issue may appear. You can try by restarting your routers or checking your internet connection. You can also see if there is any other unwanted users using your internet by hacking your routers.

2. Clear Browser Cache and Cookies

Sounds strange but you might see the Aw snap error When the cache and cookie files stored in the Chrome become outdated. Go through the following steps to clear browser cache and cookies:

1. Open  Chrome.
2. In your keyboard, Press CTRL + SHIFT + DELETE.
3. Select time range All time and click Clear data. Make sure to check the boxes for Cookies and other site data and Cached images and files before clearing the data.
4. Now try reloading the pages.

3. Hard Refresh Chrome Browser

This is probably the most effective way to fix the RESULT_CODE_HUNG error in Chrome. By performing a hard refresh, you can reloads a page along with its cache. Windows users can press Ctrl + Shift + R keys for hard refresh. If you are a Mac user, hold Shift ⇧ and click the Reload ↻ button to hard refresh Chrome.

4. Reset Google Chrome Settings to Default

If you have recently modified your settings in Chrome, it could potentially cause conflicts and make the browser unresponsive. To resolve this issue, try resetting all browser settings to their default state. Then, restart Chrome and access the website to check if RESULT_CODE_HUNG is fixed.

To do this:

1. Open Chrome and click on the three-dots ⋮ menu icon in the top right corner.
2. Choose Settings from the dropdown menu.
3. Navigate to Reset Settings on the left menu.
4. Click Restore Settings to their original defaults.
5. Confirm by clicking Reset Settings.
6. Access the problematic page again to check if it opens.

5. Disable Conflicting Chrome Extensions

Outdated or malicious extensions can lead up to this error. Go through the following steps to remove any conflicting Chrome extensions.

1. Open your Google Chrome browser
2. In the top right corner, Click the three-dots ⋮ menu icon in Chrome.
3. Select Extensions > Manage Extensions from the menu.
4. Toggle off the switch to disable the extensions
5. Restart your Google Chrome browser to see if the RESULT_CODE_HUNG error has been solved or not.

The post Multiple Ways To Fix RESULT_CODE_HUNG Error in Google Chrome first appeared on AtoZ Linux.