(Solved) HDD won't mount after reboot.

[Gardenia]

Hello.

I moved large amount of files from an external USB HDD to my internal HDD.
After I rebooted the system, the drive won't mount, and I can't see the files in the drive.

Code: Select all

System:
  Kernel: 5.4.0-77-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 4.8.6 wm: muffin 4.8.1 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME Z370-P v: Rev X.0x 
  serial: <filter> UEFI: American Megatrends v: 2001 date: 04/24/2019 
CPU:
  Topology: 6-Core model: Intel Core i7-8700K bits: 64 type: MT MCP 
  arch: Kaby Lake rev: A L2 cache: 12.0 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 88796 
  Speed: 800 MHz min/max: 800/4700 MHz Core speeds (MHz): 1: 800 2: 800 
  3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 801 12: 800 
Graphics:
  Device-1: Intel UHD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:3e92 
  Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 20.2.6 
  direct render: Yes 
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:a2f0 
  Sound Server: ALSA v: k5.4.0-77-generic 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASUSTeK driver: r8169 v: kernel port: e000 bus ID: 03:00.0 
  chip ID: 10ec:8168 
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 4.09 TiB used: 462.74 GiB (11.0%) 
  ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
  ID-2: /dev/sdb vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB 
  speed: 6.0 Gb/s rotation: 5425 rpm serial: <filter> rev: 0001 scheme: MBR 
Partition:
  ID-1: / size: 456.96 GiB used: 231.37 GiB (50.6%) fs: ext4 dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
  1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com ulyssa main upstream import backport #id:linuxmint_main
  2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
Info:
  Processes: 287 Uptime: 7m Memory: 15.51 GiB used: 2.41 GiB (15.5%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 

[Flemur]

Hello.
I moved large amount of files from an external USB HDD to my internal HDD.
After I rebooted the system, the drive won't mount, and I can't see the files in the drive.

How did you mount to the partition when you copied the files to it? (I'm assuming "the drive won't mount" refers to partition(s) on the internal drive that you just copied to).

Does "the drive won't mount" mean that it didn't mount automatically at boot, or that you tried to mount it and got error messages?

How about posting the output of these commands, inside code brackets (like [code]stuff[/code]):

Code: Select all

blkid
cat /etc/fstab | grep -v ^#

[Gardenia]

I mounted the drive from the files folders and formatted the file system to NTFS in disk manager.
Before the reboot I could see all the files in the HDD and could open them. But now, I cannot even open it and this is the error message I receive: https://postimg.cc/CZ8kRFjf

Code: Select all

/dev/sda1: UUID="2302-C4CB" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="bd6922d3-9aba-4bfb-b7a2-4a35e7f4a3f4"
/dev/sda2: UUID="a5f05d46-c80a-4915-982b-325197da70f9" TYPE="ext4" PARTUUID="1ea09f12-ac64-4762-ae07-03a2cf41cddb"
/dev/sdb: LABEL="Seagate internal 4TB" UUID="77BFEF1D34484163" TYPE="ntfs" PTTYPE="dos"

I tried to mount the drive since it didn't do it automatically, but received the above error message.

Also, the terminal says I'm only using 462.74 GiB, which is incorrect.

[Gardenia]

Should I start "Repair Filesystem" from the disk manager?
Something is definitely not right here.

[AndyMH]

I mounted the drive from the files folders and formatted the file system to NTFS in desk manager.

When you reformatted it, I suspect it lost the label that fstab is using to mount it. The UUID will also have changed.

You didn't provide the output from blkid.

[Gardenia]

Here it is:

Code: Select all

/dev/sda1: UUID="2302-C4CB" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="bd6922d3-9aba-4bfb-b7a2-4a35e7f4a3f4"
/dev/sda2: UUID="a5f05d46-c80a-4915-982b-325197da70f9" TYPE="ext4" PARTUUID="1ea09f12-ac64-4762-ae07-03a2cf41cddb"
/dev/sdb: LABEL="Seagate internal 4TB" UUID="77BFEF1D34484163" TYPE="ntfs" PTTYPE="dos"

[AndyMH]

My bad, you gave us blkid, but not fstab, post the output from cat /etc/fstab.

[Gardenia]

Code: Select all

# /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
UUID=a5f05d46-c80a-4915-982b-325197da70f9 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=2302-C4CB  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0

I'm going to try the file system repair since I luckily have a backup of the files from that HDD. I'll report back on the results.

[Gardenia]

The fix was very simple.

I ran the file system repair in the disk manager, and I can now access my files and everything is working correctly for now.
But beware that one might lose files by running this tool. I took the risk, but had a backup of the files.

I recommend having backups of all your personal files. It is now that I realise how important that is.

Thank you guys for your time!