[CONFIGURATION] Can not mout drive

[steve7233]

can not figure out the problem with /dev/sdb1. KDEPartitionManager says it can not mount. The error message isn't clear enough for me to figure out what is wrong.

I Look at the last line.
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdc1 during installation
UUID=8900d4b7-dcf0-48e6-9e02-582b56f2ceb8 / btrfs subvol=@ 0 1
# /home was on /dev/sdc1 during installation
UUID=8900d4b7-dcf0-48e6-9e02-582b56f2ceb8 /home btrfs subvol=@home 0 2
# /steam1 was on /dev/sda1 during installation
/dev/sda1 /steam1 btrfs defaults 0 2
/swapfile none swap sw 0 0
# UUID=9c41bb87-72ec-43e0-a283-9a684156b57e /home/steve7233/Booksmount btrfs defaults 0 0
/dev/sdb1 /not_steam btrfs defaults 0 0

[claydoh]

either

sudo mount -a

or

sudo mount /dev/sdb1 /not_steam

to see what the errors might be

[steve7233]

either

sudo mount -a

or

sudo mount /dev/sdb1 /not_steam

to see what the errors might be

wilson-test@steve7233-Z68XP-UD3~$ sudo mount /dev/sdb1 /not_steam
[sudo] password for wilson-test:  
mount: /not_steam: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
wilson-test@steve7233-Z68XP-UD3:~$  ​

That's the same message that KDEPartitionManager says and is not helpful because it is too vague. Thanks for trying.

[claydoh]

Umm......this?
'

wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program

,

These are where you start looking. Something is wrong with the file system. or the drive, or something.

Considering sda1 has no issues, it isn't going to be the "helper program", or probably "missing codepage" (no idea what that is tbh)
Make sure you check the disk for errors and all that before proceeding.


if you have been reformatting this drive quite a bit, or over a period of time, it can sometimes be helpful to wipe out the partition table and other info before re-formatting from scratch.

dd if=/dev/zero of=/dev/sdb bs=512 count=1​

This zeros out the first 512 mb
Be sure to triple check that sdb is the correct drive (lsblk to confirm what you see in a GUI tool)
if you have other partitions on sdb besides sdb1, you will lose those. So don't use that command if you do, as it is sort of a last resort, maybe.

[steve7233]

I thought the data cable might be loose again but now my main Steam library disappeared!

[steve7233]

I made a Linux swap partition on the same drive and it mounts that just fine so why not the other partition since it is on the same SSD?

[Schwarzer Kater]

Has this ever worked and now it does not all of a sudden?
Or did you just add the corresponding line to /etc/fstab ?

-> General advice:
It is not a good idea to use disks by path (e.g. /dev/sda5) in /etc/fstab !
Those device paths can interchange during boot, so e.g. afterwards /dev/sda can randomly become /dev/sdb and vice versa…
It is strongly recommended to use either the disk UUID or the disk label in /etc/fstab (you can get them with lsblk -f in the Konsole terminal emulator).

[dejjanku]

This is similar to mine issue.
Also dev/sda1 was in fstab for no reason.

[claydoh]

This is similar to mine issue.

Which is.......?

Also dev/sda1 was in fstab for no reason.

Not likely. Either you added it yourself manually, or via some other action, or it is from the installation.

You probably want to start a new thread, and include the contents of your fstab as well as the output of lsblk, so we can see your config and list of devices.