I'm lost.

What does that mean?

How serious is it?

What may have caused this error is, I changed the name of the label of the drive from something like:"Linux Mint 19.3 Backups to Linux Backups. Oddly enough the Terminal is seeing the original name; while the software I used in Win10, where I changed the name, sees the new name. (Linux Backups)

Also, I re-partitioned the drive, from one h.u.g.e. partition to 5 separate ones. Home and Root are 100GB, with a good 78x.GB left over.

Hope this information helps...

Pen guin

There is no healthy ext2/3/4 filesystem on sda3.
This depends on what you expect sda3 to contain.

Not really. What exactly did you do to get this error? Can you run lsblk and post the output?

Nooo ... what tool ?. Details.
Rather than the above, let's see these - the latter will need your password.

1 members found this post helpful.

Thanks berndbausch,

What I think was on that partition was backups from my first installation; i.e. that being one huge partition vs. what I have now, five separate partitions. So, if that's what it was, they were totally expendable.

Apologies that the info I posted wasn't helpful, just goes to show how much I didn't understand the error message; and how new I am to Linux (June 10, 2020).

Duggo@loveslinux:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 450M 0 part
├─sda2 8:2 0 99M 0 part
├─sda3 8:3 0 16M 0 part
├─sda4 8:4 0 930.1G 0 part
└─sda5 8:5 0 847M 0 part
sdb 8:16 0 3.7T 0 disk
├─sdb1 8:17 0 1.8T 0 part /media/loves-linux/Backups
├─sdb2 8:18 0 442G 0 part /media/loves-linux/local-data
└─sdb3 8:19 0 1.4T 0 part
nvme0n1 259:0 0 931.5G 0 disk
├─nvme0n1p1 259:1 0 487M 0 part /boot/efi
├─nvme0n1p2 259:2 0 488M 0 part /boot
├─nvme0n1p3 259:3 0 93.1G 0 part /
├─nvme0n1p4 259:4 0 15.9G 0 part [SWAP]
└─nvme0n1p5 259:5 0 93.1G 0 part /home
Duggo@loveslinux:~$

There you go.
Thanks for your help

Seems like /dev/sda is what you repartitioned and renamed - the message is for another physical drive. Essentially irrelevant. I'd guess /dev/sdb3 just hasn't been formatted - ignore the message for now.

1 members found this post helpful.

What I did was I re-partitioned sdb 0 3.7T 0 disk in order to make room for my Linux backups...
So, it went from two partitions of roughly equal size to:

─sdb1 0 1.8T 0 part /media/loves-linux/Backups - My Windows backups are stored here.
─sdb2 0 442G 0 part /media/loves-linux/local-data - My Windows data files are stored here.
─sdb3 0 1.4T 0 part Device not listed in /etc/fstab - hence not mounted?

And I renamed sdb3 from Linux Mint Backups then changed it to Linux Backups.

Hope that helps...

your lsblk output does not indicate that partition to be mounted. running these suggested commands will give a bit more info about what is going on with that partition.
however, running just lsblk -f /dev/sdb3 will leave out the other disks and partitions you don't have questions about.

My understanding is that a device not listed in the /etc/fstab file the device will not be mounted when your electronic marvel boots.

Here is a bit of reading that will tell you how to list/edit your partitions in they /etc/fstab file. https://www.linuxquestions.org/quest...er-4175677779/

My further understanding is you can name the partitions anything you like, but you'll have to make a directory with the same name.. .. .. and perhaps change the created directory's ownership to use it as an ordinary user.

I couldn't find a post that referenced listing a partition in the etc/fstab directory...

Could you tell me which post you were talking about?

Thanks...

this is not strictly true depending on your distro and how you have things set up. it certainly shouldn't keep a partition from being accessible in the file manager. i have an external that mounts at boot to write my timeshift snapshots with no fstab entry.

i haven't had to do this kind of manual intervention with disk mounting and mint. i would recommend starting with the other commands listed to see what is going on with the disk before trying to set up a manual mount or dealing with fstab at all.

Sorry, I should have asked for lsblk -f. It shows if there is a filesystem on the partition (syg00 did ask). My guess is that there isn't.

Have you created a filesystem on sdb3?
And again, what are the circumstances that lead to the error message?

Duggo@loveslinux:/$ lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 ntfs Recovery E2E814B0E81484C7
├─sda2 vfat 8E14-AAD6
├─sda3
├─sda4 ntfs local-disk B094167294163B74
└─sda5 ntfs DC0AD5960AD56E50
sdb
├─sdb1 ntfs Backups 01D303C3794530C0 /media/loves-linux/Backups
├─sdb2 ntfs local-data 01D642014A2D6DA0 /media/loves-linux/local-data
└─sdb3 ext4 e892cd04-3556-4a4d-8d2d-5c13484dcc44
nvme0n1
├─nvme0n1p1 vfat 7443-C9B6 /boot/efi
├─nvme0n1p2 ext2 95c1df67-d6d1-4530-9ac1-be4aba0f35d9 /boot
├─nvme0n1p3 ext4 2058cac7-3654-4ee4-b292-940262cb4305 /
├─nvme0n1p4 swap 77bc2b61-a388-4efc-b06b-43ee0aab083c [SWAP]
└─nvme0n1p5 ext4 af7391d2-1ec5-4d20-ae3a-d582ebe8784b /home

--

sdb3 is the partition in question.....

Thanks

have you ran fsck on sdb3?

What is the exact message you used for e2label?
Ex:

Sorry to disappoint verndog, but I don't know what the exact message was...

As it turns out, I had reason to restart the computer and, then checked Gparted:

Apologies for the tightly cropped photo

sdb3-is-now-mounting by shutterbug1480, on Flickr

Thanks for all the help. I appreciate it.

Pen guin