Problem with Hard Drive

[Melatto]

What is the output of ..

cat /etc/fstab

gmel@GBox:~$ cat /etc/fstab
# /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/nvme0n1p2 during installation
UUID=9a3eef69-dc19-4587-b796-e0ce5d76e996 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=3246-52FF /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0

 

[dos2unix]

UUID=9a3eef69-dc19-4587-b796-e0ce5d76e996 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=3246-52FF /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0

You have 3 hard drives as others have mentioned. But you only have two entries in your fstab.
Somehow, it seems your fstab file may have been modified or changed.

Normally, even though /boot/efi has it's own mount point, it's typically located on the main OS drive.
I do not see your /dev/sda or your /dev/sdb drives in here at all. We can add them back in if you like.

What is the output of...

blkid /dev/sda1

..and ...

blkid /dev/sdb1

It seems that your sda drive is formatted with FAT/exFat or NTFS?

 

[Melatto]

You have 3 hard drives as others have mentioned. But you only have two entries in your fstab.
Somehow, it seems your fstab file may have been modified or changed.

Normally, even though /boot/efi has it's own mount point, it's typically located on the main OS drive.
I do not see your /dev/sda or your /dev/sdb drives in here at all. We can add them back in if you like.

What is the output of...

blkid /dev/sda1

..and ...

blkid /dev/sdb1

It seems that your sda drive is formatted with FAT/exFat or NTFS?

gmel@GBox:~$ sudo blkid /dev/sda1
[sudo] password for gmel:
/dev/sda1: LABEL="New Volume" BLOCK_SIZE="512" UUID="8A223E18223E0A29" TYPE="ntfs" PARTUUID="baec8c2c-01"

(base) gmel@GBox:~$ sudo blkid /dev/sdb1
/dev/sdb1: LABEL="Storage" UUID="7c05f99a-d9e7-48aa-a7fb-a577549ab711" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="G Store" PARTUUID="669cd0a7-6b58-4a63-8ff7-0fe667869cf6"
(base) gmel@GBox:~$

 

[dos2unix]

Ok, let's do this.

mkdir /drive_sda

mkdir /drive_sdb

You can name these anything you like ( no spaces ), but just name them something that makes sense so you know which is which.

Next edit your fstab file.

and add these lines at the bottom. beneath the swapfile line is fine.

UUID=7c05f99a-d9e7-48aa-a7fb-a577549ab711 /drive_sdb ext4 defaults 0 0
UUID=8A223E18223E0A29 /drive_sda ntfs defaults 0 0

then save this file.

Now try these commands.

mount /drive_sda

mount /drive_sdb

Assuming those work, you should be able to ...

cd /drive_sdb

ls

.. and see your files here.

If all this works, I would recommend rebooting your computer, to make sure the drives are still there after you reboot.

 

[Melatto]

Ok, let's do this.

mkdir /drive_sda

mkdir /drive_sdb

You can name these anything you like ( no spaces ), but just name them something that makes sense so you know which is which.

Next edit your fstab file.

and add these lines at the bottom. beneath the swapfile line is fine.

UUID=7c05f99a-d9e7-48aa-a7fb-a577549ab711 /drive_sdb ext4 defaults 0 0
UUID=8A223E18223E0A29 /drive_sda ntfs defaults 0 0

then save this file.

Now try these commands.

mount /drive_sda

mount /drive_sdb

Assuming those work, you should be able to ...

cd /drive_sdb

ls

.. and see your files here.

If all this works, I would recommend rebooting your computer, to make sure the drives are still there after you reboot

what am I missing here?

gmel@GBox:~$ mkdir /drive_sda
mkdir: cannot create directory ‘/drive_sda’: File exists

 

[dos2unix]

gmel@GBox:~$ mkdir /drive_sda
mkdir: cannot create directory ‘/drive_sda’: File exists

what is the output of

ls /

 

[Melatto]

what is the output of

ls /

ls /
bin dev etc lib32 lost+found opt run srv tmp
boot drive_sda home lib64 media proc sbin swapfile usr
cdrom drive_sdb lib libx32 mnt root snap sys var

 

[dos2unix]

It's just telling you that you already have a drive_sda directory and a drive_sdb directory.

You can skip the "mkdir" commands.

 

[Melatto]

It's just telling you that you already have a drive_sda directory and a drive_sdb directory.

You can skip the "mkdir" commands.

my fstab is read only
how do I get editing permissions?

 

[dos2unix]

my fstab is read only
how do I get editing permissions?

Can you use sudo? Or login as root?

 

[Melatto]

Can you use sudo? Or login as root?

yes @ sudo through the terminal

 

[dos2unix]

sudo gedit /etc/fstab ( I don't know what editor you are using, but just replace gedit with whatever you use ).

 

[Melatto]

Ok, let's do this.

mkdir /drive_sda

mkdir /drive_sdb

You can name these anything you like ( no spaces ), but just name them something that makes sense so you know which is which.

Next edit your fstab file.

and add these lines at the bottom. beneath the swapfile line is fine.

UUID=7c05f99a-d9e7-48aa-a7fb-a577549ab711 /drive_sdb ext4 defaults 0 0
UUID=8A223E18223E0A29 /drive_sda ntfs defaults 0 0

then save this file.

Now try these commands.

mount /drive_sda

mount /drive_sdb

Assuming those work, you should be able to ...

cd /drive_sdb

ls

.. and see your files here.

If all this works, I would recommend rebooting your computer, to make sure the drives are still there after you reboot.

gmel@GBox:~$ sudo mount /drive_sda
[sudo] password for gmel:
$MFTMirr does not match $MFT (record 3).
Failed to mount '/dev/sda1': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.

 

[dos2unix]

Ok, lets fix one thing at a time.

Does your /drive_sdb work? Can you see the files on this drive at least?

Linux doesn't support ntfs by default, usually some other packages are needed to be installed.
If this was working before, they are probably already installed ( unless they got removed somehow ).
The names of these packages are different depending on which distro you use.

You can try running the ntfsfix command, some distro's have this, other's do not.

sudo ntfsfix /dev/sda1

 

[Melatto]

Ok, lets fix one thing at a time.

Does your /drive_sdb work? Can you see the files on this drive at least?

this drive seems to be functioning just fine

 

[Melatto]

Ok, lets fix one thing at a time.

Does your /drive_sdb work? Can you see the files on this drive at least?

Linux doesn't support ntfs by default, usually some other packages are needed to be installed.
If this was working before, they are probably already installed ( unless they got removed somehow ).
The names of these packages are different depending on which distro you use.

You can try running the ntfsfix command, some distro's have this, other's do not.

sudo ntfsfix /dev/sda1

gmel@GBox:~$ sudo ntfsfix /dev/sda1
[sudo] password for gmel:
Mounting volume... $MFTMirr does not match $MFT (record 3).
FAILED
Attempting to correct errors...
Processing $MFT and $MFTMirr...
Reading $MFT... OK
Reading $MFTMirr... OK
Comparing $MFTMirr to $MFT... FAILED
Correcting differences in $MFTMirr record 3...OK
Processing of $MFT and $MFTMirr completed successfully.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sda1 was processed successfully.

 

[dos2unix]

NTFS partition /dev/sda1 was processed successfully.

OK, it looks like the drive is fixed.
Now you can try to re-mount it.

mount /drive_sda

If this doesn't work, there is one more thing we can try.
Try changing this line in your /etc/fstab

/dev/sda1 /drive_sda ntfs defaults 0 0

to this...

/dev/sda1 /drive_sda ntfs-3g defaults 0 0

notice I added a "-3g" after ntfs.

then try the mount command again.

 

[Melatto]

OK, it looks like the drive is fixed.
Now you can try to re-mount it.

mount /drive_sda

If this doesn't work, there is one more thing we can try.
Try changing this line in your /etc/fstab

/dev/sda1 /drive_sda ntfs defaults 0 0

to this...

/dev/sda1 /drive_sda ntfs-3g defaults 0 0

notice I added a "-3g" after ntfs.

then try the mount command again.

I rebooted my computer and now both drives are gone

should I still try this mount command?

 

[dos2unix]

I rebooted my computer and now both drives are gone

Then something is wrong. Can you...

cat /etc/fstab

..again.

Are the lines for /drive_sda and /drive_sdb still in this file?

 

[Melatto]

Then something is wrong. Can you...

cat /etc/fstab

..again.

Are the lines for /drive_sda and /drive_sdb still in this file?

gmel@GBox:~$ cat /etc/fstab
# /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/nvme0n1p2 during installation
UUID=9a3eef69-dc19-4587-b796-e0ce5d76e996 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=3246-52FF /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
UUID=7c05f99a-d9e7-48aa-a7fb-a577549ab711 /drive_sdb ext4 defaults 0 0
UUID=8A223E18223E0A29 /drive_sda ntfs defaults 0 0