/etc/fstab error at bootup

[andrewgouw]

My system is a Linux Mint 17.3 Cinnamon.
One of my hard drives died and I replaced it with a new bigger one. It was an NTFS formatted drive since I use it as a backup of my windows files.
When I installed the new drive I made it a NTFS formatted drive too and gave it the same label name.
Copied all files from the old drive to the new one with no problems. When I rebooted the computer displayed: Continue to wait, or press S to skip or press M to manually .......
I had that before some 2 years ago so I know something in my /etc/fstab has something wrong with it.
When I pressed S to continue it boots but the new drive can not be mounted with attached error message (scr0.png) and the content of my etc/fstab is in scr1.png and the result of "blkid" is in Scr2.png
and for good measures I also attached my sys-info in Scr3.png
The offending drive is labeled "Bak" (The new installed drive)
Can any body help me out?

[andrewgouw]

Sorry forgot the attachments.

[Flemur]

Did you do the suggested fix on the error message, namely:
Is it a Soft/Fake-Raid partition?
If NOT, run
chkdsk /f
on windows, and reboot twice.
??

[WharfRat]

I don't know how any of them are mounting since you did not specify the file type in the third field

[kukamuumuka]

I would make a different /etc/fstab without mixin LABEL and UUID. At first making folders for mount-points and add these mount-points to the /etc/fstab. An example:

Code: Select all

sudo mkdir /mnt/BAK

... to the /etc/fstab

Code: Select all

## /dev/sde1
UUID=igliglegilg.... /mnt/BAK ntfs-3g defaults 0 0

... save, quit and run

Code: Select all

sudo mount -a

[andrewgouw]

When I follow the suggestion to do the chkdsk in windows and reboot twice, all data on the disk becomes totally unreadable by windows and by linux mint.
Had to redo all reinitialize the disk, create the partition and format. Then it works again but when I reboot the same error message comes up.
How do I create a new /etc/fstab which I wil not mix UUIDs and LABELs?
If any of you can tell me how to. The mount point are already there. How do I delete the mount point? Is that an option?
I did try
## /dev/sde1
UUID=igliglegilg.... /mnt/BAK ntfs-3g defaults 0 0
with the same result.

[phd21]

HI andrewgouw,

I just read your post and the good replies to it. Here are my thoughts on this as well.

Good instructions in link.

This commmand also Identifies attached disks and their partitions

Code: Select all

sudo lsblk -f

Mounting a new hard disk or disk partition on Linux Mint
https://mintguide.org/system/369-mounti ... -mint.html

Not sure if it matters in "fstab", but use a "#" where there are blank lines.

Hope this helps ...

[andrewgouw]

Here is the result of "sudo lsblk -f".
The dev/sde1 cannot be mounted after a reboot.
This is what I have done :
1. Did the chkdsk /f and it deleted a lot of orphaned files and recovered orphand files, lots of them.
2. Reboot the windows system twice
3. Boot up Linux Mint 17.3
4. dev/sde1 was automatically mounted to /mnt/Bak although strange enough it does not show up in devices of Files.
5 started Windows virtual machine from virtualbox
6. Did a backup to this dev/sde1 drive using SaveNSync and it finished with no problems or errors.
7. All directories and files are accessible OK
8. Reboot Linux Mint and I get the same "Press S ....." and I did press the S button and Linux Mint starts
9. run "sudo lsblk -f". and the result is attached.
10. dev/sde1 is just nothing.
Attached is the /etc/fstab

[phd21]

Hi andrewgouw,

For "/dev/sde1", do you have the "ntfs-3g" and "fuse" packages installed? Try changing that to just "ntfs" or changing the "default" mount options to something else, and reboot or issue a mount all. The second link does show an example of "ntfs-3g" as a Network Mount but not using "default", using "auto,user,rw?

FYI: I have to unmount a partition after making "fstab" changes before I can remount it or issuing a mount all command, that or reboot.

Code: Select all

sudo umount /mnt/data

Code: Select all

sudo mount -a

fstab - ArchWiki
https://wiki.archlinux.org/index.php/fstab

What Is the Linux fstab File, and How Does It Work?
https://www.howtogeek.com/howto/38125/h ... s-it-work/

NTFS-3G - Wikipedia
https://en.wikipedia.org/wiki/NTFS-3G

Update: I just changed my NTFS local partition to "ntfs-3g" and it worked (seems faster too).

Code: Select all

/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/sda3 during installation
UUID=66ecc341-0224-426f-bb8a-efea2671d853 /               ext4    noatime,errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=e5c961dd-04d1-46a3-a31b-8c6aba142d5f none            swap    sw              0       0
# / was on /dev/sda4 during installation
UUID=273949B600CF0319                  /mnt/data          ntfs-3g    errors=remount-ro 0       3

Update2: I just changed my NTFS partition in "fstab" to this and it also mounted

Code: Select all

# / was on /dev/sda4 during installation
UUID=273949B600CF0319                  /mnt/data          ntfs-3g    auto,user,rw,errors=remount-ro 0       3

Hope this helps ...

[andrewgouw]

It was eventually able to work and I don't know how or why.

This is my /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/sda2 during installation
# /dev/sdb2
UUID=96b49976-f94b-4a46-b0d0-d658be5e1c5f / ext4 errors=remount-ro, 0 1
# /boot was on /dev/sda1 during installation
# /home was on /dev/sda6 during installation
# /dev/sdb6
UUID=a187a4d7-1488-42ec-800f-0b98b983f44f /home ext4 defaults 0 2
# swap was on /dev/sda5 during installation
# /dev/sdb5
UUID=625a4a07-09ca-459f-b3e2-297c0b0e3f15 none swap sw 0 0
#
# /dev/sda1
# UUID=0A2F64C5EE289C63 /mnt/Bak ntfs-3g defaults 0 0
#
LABEL=Personal /mnt/Personal auto nosuid,nodev,nofail,x-gvfs-show 0 0
LABEL=Resource /mnt/Resource auto nosuid,nodev,nofail,x-gvfs-show 0 0
LABEL=Bak /mnt/Bak auto nosuid,nodev,nofail,x-gvfs-show 0 0
LABEL=2-Personal /mnt/2-Personal auto nosuid,nodev,nofail,x-gvfs-show 0 0
LABEL=2-Resource /mnt/2-Resource auto nosuid,nodev,nofail,x-gvfs-show 0 0
# LABEL=RES /mnt/RES auto nosuid,nodev,nofail,x-gvfs-show,noauto 0 0
#
LABEL=Bak2 /mnt/Bak2 auto nosuid,nodev,nofail,x-gvfs-show,noauto 0 0

And this is my blkid result:
sudo blkid:
/dev/sda1: LABEL="Bak" UUID="42AAFCDEAAFCCF81" TYPE="ntfs"
/dev/sda2: LABEL="RES" UUID="24920C84920C5CA4" TYPE="ntfs"
/dev/sdb1: UUID="3415e163-e814-4bf8-902a-5026c2b64730" TYPE="ext4"
/dev/sdb2: UUID="96b49976-f94b-4a46-b0d0-d658be5e1c5f" TYPE="ext4"
/dev/sdb3: LABEL="Recovery image" UUID="DEECDABFECDA90DF" TYPE="ntfs"
/dev/sdb5: UUID="625a4a07-09ca-459f-b3e2-297c0b0e3f15" TYPE="swap"
/dev/sdb6: UUID="a187a4d7-1488-42ec-800f-0b98b983f44f" TYPE="ext4"
/dev/sdc1: LABEL="Personal" UUID="0CA99B7958518E04" TYPE="ntfs"
/dev/sdc2: LABEL="Resource" UUID="0D1EEA96B8B44298" TYPE="ntfs"
/dev/sdc3: LABEL="Bak2" UUID="47F501E3E5B28AEB" TYPE="ntfs"
/dev/sdd1: LABEL="System Reserved" UUID="545855DA5855BB84" TYPE="ntfs"
/dev/sdd2: UUID="AC1E6C4E1E6C139C" TYPE="ntfs"
/dev/sde1: LABEL="2-Personal" UUID="6628455628452681" TYPE="ntfs"
/dev/sde3: LABEL="2-Resource" UUID="3ABA3D8D4414172C" TYPE="ntfs"

For as long as I donot reboot it keeps working. At reboot most likely dev/sda1 and dev/sda2 will be deemed corrupt and I might loose some data when I boot in Windows and it chkdsk either disk.
This is so frustrating.