Category: Hardware

A Couple More Ways To Find Your File System Type

Today we’re going to revisit a previous subject and share a couple more ways to find your file system type. I’ve covered this subject before, but I only shared a couple of ways. This being Linux, there are multiple file system types and multiple ways to find the details. So, let’s cover it again but with different options.

If you did your installation manually, you probably already know this information. You probably know the file system types you chose to use during the installation process. On the other hand, if you did your installation by just letting the installer use the defaults, you might not know this information. This may also be something like an unknown computer you’re tasked with fixing. So, there are real-world reasons why you might want to know the file system types in use.

If you want to visit the previous article, you can find that here:

How To: Find The File System Type

You could easily have multiple file system types in use right now. This is quite likely if you’re dual-booting with Windows or you’re using EFI as your boot method. You could even have external disks formatted in all sorts of file types.

All of these various file types may need specific commands to repair them and maintain them. You don’t want to go using the wrong tool for the wrong file type. That’d likely make your problems even worse. So, this is good information to have and this article will show you how to find your file system type.

Find Your File System Type:

This requires an open terminal. Like many of these articles, we’ll be using a terminal. It’s painless and it’s a good idea to know some of these commands. The terminal is fairly universal, so you can open your terminal (usually) by pressing CTRL + ALT + T.

In the previous article, we used lsblk and we also used df. Those are both excellent tools and excellent ways to get this information. They’re simple and easily memorized. The two commands we’ll use today will be similar in those regards. This truly is not a complicated task, it’s just fun to cover the different methods that one could use.

Using The mount Command:

The first command we’re going to learn about is the mount command. Don’t worry, this is part of your standard installation and you won’t need to do anything extra to use it. You can check the man page with man mount if you’d like. If you did do so, you’d find that the mount application is described as:

mount – mount a filesystem

No, we won’t be mounting and unmounting anything. We’ll just be using the command to find your file system types. That command’s syntax would look like this:

That’s the command that will show you all of your drives and all of the drive’s file system types in one go. I plugged a couple of external drives in so that I could run the command and show you the expected output:

using the mount command to find the file system type
You can see that there are vfat and ext4 file systems in use. That’s normal. It’s all good!

There’s nothing too eccentric in that output. Those are fairly normal file systems as far as Linux systems go. There are more. There are many more. You can check a list of file system types on Wikipedia.

Using The fsck Command:

Yes, you can even use the fsck command to find the file system types. You’re telling the command to not actually run and just spit out some information, so there’s nothing laborious or complicated with this command. You will need to know the path to the disk in question. I’m sure you know how to do that. Heck, the first command in this article will do that for you.

When you do this with the fsck command, you’re doing so on a disk-by-disk method. If you’re unfamiliar with the fsck command, you can check the man page with man fsck. Once again, you won’t have to install anything. The fsck command is a part of the standard base, files you’ll find on pretty much every distro by default. Anyhow, the man page describes fsck as:

fsck – check and repair a Linux filesystem

We will not be repairing a Linux filesystem (I’ve intentionally stylized this as ‘file system’ as it appears both spellings are in common usage) but we will sort of be checking them. We won’t be checking them for errors because that’d take too long and isn’t a part of this article. If you do want to check your file systems for errors with fsck, you should read this article:

How To: Check A Disk For Errors

Or maybe this article:

Repair Your Linux Filesystem With a Live USB or DVD

Anyhow, if you want to find your file system type with fsck, the syntax is simile and is as follows:

This is usually going to start with a /dev and then the drives populate  (enumerate?) as is logical. You would have drive sda, then partitions on that drive might be sda1, sda2, etc… So, an example command might be:

An example output is as follows:

you can use the fsck command to find the file system type for a specific drive
This only really works on one drive/partition at a time. That’s plenty useful.

See? Pretty useful if you need to know a file system type before working on it.

Closure:

So, we’ve covered a couple of new ways for you to find your file system type. This time around, we’ve used fsck and mount and both of them are perfectly useful for this application. If you work on multiple computers, if you work on someone else’s computers, if you work on remote computers, etc. then these commands may come in useful. 

Plus, this seemed like a fun article to write. There are all sorts of older articles that could have more information added to them. Some of the older articles contain errors that should be fixed. Some could use being written again but with a more suitable format.

A couple of the articles are just plain garbage and should have been deleted. They weren’t… They should have been, but they weren’t. I should probably go back and write those over again in their entirety. I’ve completely blown it a few times. I do like to point out that I probably learn more than you do by writing these articles and (importantly) getting feedback on them. I do love some feedback, though it’d be cool if it was left here when it adds something to the article.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Find And Remove Duplicate Files With fdupes

Today’s article has you cleaning up your storage space as you learn to find and remove duplicate files with fdupes. This isn’t something you need to do often and it’s something that could theoretically break your system. If you’re going to remove duplicate files, it’s a good idea to exercise some caution.

I’ve previously shared another way to remove duplicate files:

Find And Remove Duplicate Files With rdfind

I suppose it’s pretty obvious as to why one might want to remove duplicate files. You do so to keep your storage tidy and you do so to make space when space is limited. There are all sorts of ways to make free space and removing duplicate files is just one of them.

The tool we’ll be using this time around is known as ‘fdupes’ and the man page describes it like this:

fdupes – finds duplicate files in a given set of directories

It’s an easy enough application to install and this article shouldn’t be all that long. You’ll find that fdupes is available in your default repositories, or there’s a good chance that it is in there. Of course, this means it’s easy enough to install.

Installing fdupes:

You can install fdupes with a GUI and your software manager, but you can just as easily install it via the terminal. We’ll cover the latter, as it’s the most universal (and, I find, quickest) method. Of course, you’ll need an open terminal. In most cases you can just press CTRL + ALT + T and your default terminal should open.

With your terminal now open, let’s go ahead and install fdupes:

Debian/Ubuntu/derivatives:

SUSE/OpenSUSE/derivatives:

RHEL/Fedora/Rocky/derivatives:

Arch/Manjaro/derivatives:

Gentoo/Calculate/derivatives:

And More! (Just search your default repositories for ‘fdupes’ and it’ll almost certainly be there.)

As you can see, you’ll find that fdupes is available for pretty much every Linux system out there. Not only is it available, it’s already packaged for you and easy enough to install via the terminal. On top of that, it doesn’t take much space to install fdupes, a mere 110 kB or so.

NOTE: I do not have anything against GUI tools. While I have terminals open at all times, I do the majority of my computer interaction in a browser – specifically a GUI browser. I suggest and write about the terminal because it’s more universal. It’s also often faster, assuming you can type or at least cut and paste than it is to go mucking about with a GUI software installer.

Anyhow, it’s nice and easy to remove duplicate files with fdupes. This article is going to show you how – and the article shouldn’t even be that long! It’s pretty simple.

Remove Duplicate Files With fdupes:

I’m going to assume that you left your terminal open after installing fdupes. If you didn’t, you’ll need to open it again. The only way to run the fdupes application is in the terminal. So, even if you installed it with a GUI, it’s a CLI tool and you’ll need the command line to use it.

The basic syntax is pretty easy, and not entirely unlike rdfind. For example, if you want to find duplicate files, you simply run this command:

So, if you wanted to find duplicates in your home directory, you’d run this:

Don’t worry, you’re safe running that command. That won’t delete anything at all. That fdupes command will simply show you the duplicate files that it found.

If you want to run the fdupes command recursively, that is to check all the folders within the directory, you’d run the command like this:

If you want to calculate the size of the files that would be removed when removing the duplicates, the command is just this:

A summary is also available with this command:

You can also search multiple directories for duplicates. That’d be something like this:

Of course, you can run those commands together to get quite a bit of customization. They’re all reasonably harmless and will simply point out the duplicates as well as some meta information. You can then remove the duplicates by hand if you want.

You can also tell fdupes to remove the duplicates that it found. You’d never want to run this command without knowing what exactly is going to be removed, so don’t do that. Always check to make sure you’re not removing anything of value before automatically removing duplicates.

Fortunately, there’s a bit of a stopgap. You can run the following command and fdupes will ask for confirmation before removing the file:

If you want to go whole-hog and remove every duplicate found, and remove the files without any confirmation, you can run this command:

Of course, that’s just the basics. If you want to know more about fdupes, simply check the man page (man fdupes) for more information.

Closure:

Hmm… I think I need to clean or replace this keyboard. The colon key is sticking on me. It’s a bit of a pain in the butt.

Anyhow, if you’ve ever wanted to remove duplicate files with fdupes, you now have directions to do so. This being Linux, you have all sorts of options when it comes to removing duplicate files, though I again urge caution when doing so. If you were to run this on the root directory, you’d likely find a lot of duplicates, and removing them might break your system. So, be careful with these tools, as they’re pretty powerful.

I’m not yet out of ideas for articles but it’d be great if folks might suggest something they’d like to read about. You never know, it might be something I know about. As it is, I have to search this site before writing an article, or else I’d end up with even more duplicate articles. I don’t want that and you don’t want that. It’s not all that easy to keep up this pace, writing a new article every other day. I’ve managed so far, but I’m eventually going to miss a day or two. It’s going to happen.

As always…

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

How To: Find Your CPU Information

Today’s article shouldn’t be all that long, as it’s a subject touched on before, as we discuss how to find your CPU information. This will be in the terminal, of course. There are also many ways to find your CPU information. This article will just cover another way that I don’t think we’ve already covered.

I’ve touched on this subject before:

One Way To See CPU Information

In that article, we simply used the ‘cat’ command to read information from a text file. It’s a pretty handy way to find CPU information, but it is not the only way.

You can also get some basic information about your CPU with Screenfetch or Neofetch. I’ve written about those as well:

Screenfetch vs. Neofetch, You Decide!

I’ve even covered ‘lscpu’ in the past. You can read that article here:

A Little About The ‘lscpu’ Command

So, as you can see, there are lots of ways to find out what CPU you’re working with. You can do it graphically, that is in a GUI, if you’d rather. It’s as simple as installing an application called ‘HardInfo’ and you can read more about it here:

Graphically Examine Hardware Info With HardInfo

See? There are all sorts of ways to get information about your CPU. You have all sorts of choices and this article is going to simply detail yet another way to gather this information.

Why? Well, I like to be the kind of person that gives you options. I like that there are so many ways to accomplish a task in Linux.

Why would you want this information? Perhaps you bought a new computer. Then again, you might have paid for a server (virtual or real) and want to confirm that you’re getting what you paid for. You could have multiple devices, such as myself, and not remember what hardware is in each of those devices. 

There are all sorts of reasons why you might want to know your CPU information. There are all sorts of ways to get this information. Today can have a shorter article than we’ve had lately, as we cover this topic yet again.

Find Your CPU Information:

As mentioned in the opening of this article, we’ll be doing this in the terminal. My regular readers will be used to this and will know how to open the terminal. If you don’t know how to open the terminal, you can almost always just press CTRL + ALT + T, and your default terminal will open up. You may otherwise need to open a terminal from your application menu.

With your terminal open, we’ll be using the ‘lshw’ command. You shouldn’t need to install anything. The ‘lshw’ should come pre-installed as it’s a rather basic piece of the common Linux toolbox. If you check the man page (with man lshw), you’ll see that the program is just like many of the other ‘ls* applications, in that it lists hardware. Specifically, it says this:

lshw – list hardware

That’s an accurate enough short description. The actual description says this:

lshw is a small tool to extract detailed information on the hardware configuration of the machine. It can report exact memory configuration, firmware version, mainboard configuration, CPU version and speed, cache configuration, bus speed, etc. on DMI-capable x86 or IA-64 systems and on some PowerPC machines (PowerMac G4 is known to work).

So, the lshw tool is a pretty good tool to have handy when you’re wanting to know information about your hardware. I once botched an article on lshw! I’m sure I’ll botch another one eventually!

Specifically, you simply want to use the command as follows:

You want to run the lshw command with sudo (or as root, if sudo is not available) so that you have the elevated permissions to retrieve full information in the command’s output. If you try to run lshw without elevated permissions, it will remind you that you should do so.

On the man page, you will discover a bug. I’ve yet to see this bug in real life, but there is a bug. The man page explains it like this:

Not all architectures supported by GNU/Linux are fully supported (e.g. CPU detection).

So, that’s something to be aware of. I doubt it’s going to impact (m)any of my readers because we’re almost always using fairly common CPUs. It should correctly identify your CPU.

Closure:

Well, it’s a pretty basic subject and an easy enough command to keep in mind. If you want to find your CPU information, there are a ton of ways to do so and we’ve just covered one more way. This seemed like an easy article to write and I could use an easy day. I think we could all use an easy day once in a while, but the show must go on and you get yet another article for your enjoyment.

I have been making the articles longer. I’m trying to share more information along with the directions. I think it’s good for understanding and it doesn’t take that much more time. If you have an opinion on the matter, please leave a comment.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

How To: List Mounted Partitions

Today we’ll have a nice and simple article, simply because we can, about how to list mounted partitions in Linux. Like so many of these articles, we’re going to need an open terminal. On the other hand, we’ll just be exploring a couple of tools to help us along the way.

Your disk drives, be they solid state or hard disk drives, will be separated into partitions. It can get confusing until you realize that the outputs from these commands won’t always just represent what I’ll call physical partitions. Sometimes, there are virtual partitions – sometimes with their fun file systems.

You may have everything from mounted temporary partitions to software designed to run in its own mounted partition space. When you run these bellow commands, you’ll learn that there are all sorts of mounted partitions. This is completely normal. It’s also pretty easy to weed out the physical partitions.

Why would you want to do this? Well, I’m having a goofy error when I boot one of my computers and I need to narrow it down to which disk it is that’s giving me the error. Once I take the time to do that, I can move on to troubleshooting the problem and finding a solution for the problem.

The tools we’ll be using are ‘findmnt’ and ‘df’. They’re described as the following:

finding:

findmnt – find a filesystem

df:

df – report file system disk space usage

As you can see from the description, both of those have something to do with getting information about a file system. That makes them good tools for the job.

NOTE: There are multiple ways to list mounted partitions. You have GUI and CLI-based tools available to you. One of the goals surrounding this whole project is not just to make people more familiar with Linux but also to help them get comfortable working within the terminal. You’ll be just fine!

List Mounted Partitions:

As I mentioned above, we’ll be using a terminal for this. I do not mind which terminal you’re using but you can usually open the default terminal by pressing CTRL + ALT + T. That works most of the time.

With your terminal now open, you can try the following command:

The output from that command will list your mounted partitions. It’s a lot of text, but most folks are probably only interested in the start of the line. The output of the findmnt command may look a little something like this:

The next command you’re going to want to try will be the ‘df’ command. We’ll be using a few flags. It’s not very complicated, though it may look like it. The command is a simple ‘df’ command and looks like this:

We use the -a flag for ‘all’. Then we use the -T flag because that means type. Finally, we use the -h flag because that means the output will be “human readable” (or more easily read by us mortals.) The output of which looks something like this:

No matter which of those commands you use, it will make your terminal list mounted partitions. If you need to know which partitions are mounted, these are the tools you can start with. They’re easy enough to work with.

Closure:

Well, it’s a bit late in the evening. I almost forgot that there was an article due tomorrow. This happens when I get a lot of responses (elsewhere) on the wrong day. My brain just doesn’t click. I should probably set an automated notification to let me know which days require articles, but I haven’t failed yet. In fact, you get an interesting article about how you can list mounted partitions.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

How To: Find The File System Type

Today’s article will be an article that is fairly simple and easy enough for almost anyone, as we discuss how to find the file system type. We’ll discuss a few ways to find this information and we’ll be doing so in the terminal. If that’s something you’re interested in learning, this just might be the article for you!

Before you installed Linux, you formatted the disks. You chose (or didn’t bother choosing) which file system you wanted to go with. There are numerous options, each with its own set of features. Among the choices are file systems like ext4, Btrfs, ZFS, and more!

Here’s a giant list of file system types.

You use file systems on every bit of storage media, even if it’s done behind the scene and not something you manually interact with. If you’re using a thumb drive, it’s formatted with a file system type. This is true even with an SD card, external hard drive, solid-state drive, and all the rest. It’s required for storing and organizing data.

Well, rather than make this a longer article, we can just cut to the chase…

Find The File System Type:

As I mentioned in the intro, we’re going to be using the terminal to find the file system type. So, you’ll need an open terminal. Usually, you can just press CTRL + ALT + T to open the default terminal.

With your terminal open, you can try the following command:

The output of that would look similar to this:

If you look, you’ll see one of the columns is helpfully labeled ‘type’ and that’s the file system type. If you just care about the first two columns, you could run something like this:

You can also use the ‘lsblk’ command to find the file system type. This might be the command most folks are more familiar with and the command you’d want to run would be this:

The output of the command would look similar to this:

Again, the second column is helpfully labeled as “FSTYPE” which stands for ‘file system type’ – which is exactly the information we’re after and exactly the information mentioned in the article’s headline.

See? Pretty neat! You can easily find the system type with just a couple of commands. There are other ways, but these are a couple of quick and easy ways. If you don’t know the file system type, perhaps because you’re new and didn’t pay much attention during OS installation, you can now do so.

Closure:

Well, it’s another article. It’s probably not the most interesting of articles, but not all articles are going to be that interesting. Today we cover file system types and how to find them, who knows what the next article will be? One thing you can be reasonably certain of is that there will be another article in just a couple of days. If this one didn’t interest you much, the next one might be right up your alley!

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Linux Tips
Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.