(SOLVED-ish) Unable to mount [Drive name]

[Arvoly]

Hi, I recently Updated my Motherboard firmware (ASUS TUF GAMING B550-Plus) and now my additional storage units can't be mounted.

Error 1: "Error mounting /dev/sda2 at /media/arvoly/Secondary Storage: Unknown error when mounting /dev/sda2" Western Digital
Error 2 : "Error mounting /dev/nvme0n1p2 at /media/arvoly/Small Extra Storage: Unknown error when mounting /dev/nvme0n1p2" Klevv

My main drive is fine, it's just my two other storage units, both SSD drives, won't mount. They worked fine before I updated my firmware.

Is this an easy fix?

Edit: Drives had NTFS tags and didn't work even if they were being picked up. I choose to format them to an ext4 format and added a few lines in fstab to make them automount. They work now.

Edit2: They work now, but they don't use their respective storage, it seems that they are linked to my Main Drive and use my Main drive as their storage.

Edit3: It seems the automount method didn't really work for me, as mounting them to a file caused them to use my Main drive as their storage system. I have now edited my fstab config to not automount them and they work like normal again, by using their own storage and not a linked storage. Although not the intended outcome, it's still better than not having a drive mount at all. I am fine with having to mount them on start up.

[xenopeek]

Can you share the output of these 3 commands:

Code: Select all

cat /etc/fstab
lsblk -o +UUID
sudo mount -a -v

And share your system information; open the System Reports program, go to System Information on the left and then click Copy button at bottom right. Paste the copied information in a reply here.

[Arvoly]

Output for 'cat /etc/fstab'

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/nvme1n1p2 during installation
UUID=7b6447f8-83fd-4508-ab89-ff5ca3b71cac /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme1n1p1 during installation
UUID=0579-33B9  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0

------------------------------------------------------------------------------------------------------
Output for 'lsblk -o +UUID'

Code: Select all

NAME MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS  UUID
sda    8:0    0 931.5G  0 disk              
├─sda1
│      8:1    0    16M  0 part              
└─sda2
       8:2    0 931.5G  0 part              B834F0B534F07828
sdb    8:16   0   1.8T  0 disk              
└─sdb1
       8:17   0   1.8T  0 part /media/arvoly/External Storage 2TB
                                            360A6F7B0A6F3751
nvme1n1
│    259:0    0 931.5G  0 disk              
├─nvme1n1p1
│    259:1    0   512M  0 part /boot/efi    0579-33B9
└─nvme1n1p2
     259:2    0   931G  0 part /            7b6447f8-83fd-4508-ab89-ff5ca3b71cac
nvme0n1
│    259:3    0 238.5G  0 disk              
├─nvme0n1p1
│    259:4    0    16M  0 part              
└─nvme0n1p2
     259:5    0 238.5G  0 part              1C700C3C700C1EE0

------------------------------------------------------------------------------------------------------
Output for 'sudo mount -a -v'

Code: Select all

/                        : ignored
/boot/efi                : already mounted
none                     : ignored

------------------------------------------------------------------------------------------------------

[Arvoly]

Forgot to add my system info

Code: Select all

System:
  Kernel: 6.5.0-25-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 6.0.4 tk: GTK 3.24.33
    wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: TUF GAMING B550-PLUS v: Rev X.0x serial: <superuser required>
    UEFI: American Megatrends v: 3405 date: 12/13/2023
CPU:
  Info: 8-core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP smt: enabled arch: Zen 2 rev: 0
    cache: L1: 512 KiB L2: 4 MiB L3: 32 MiB
  Speed (MHz): avg: 2954 high: 4292 min/max: 2200/4426 boost: enabled cores: 1: 2137 2: 3693
    3: 4266 4: 2153 5: 2146 6: 4292 7: 2146 8: 3263 9: 2051 10: 3796 11: 2200 12: 2200 13: 2146
    14: 4292 15: 2200 16: 4283 bogomips: 114992
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA TU116 [GeForce GTX 1660 SUPER] vendor: ASUSTeK driver: nvidia v: 535.161.07
    pcie: speed: 8 GT/s lanes: 16 ports: active: none off: HDMI-A-1 empty: DP-1,DVI-D-1
    bus-ID: 08:00.0 chip-ID: 10de:21c4 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 92 s-size: 530x301mm (20.9x11.9") s-diag: 610mm (24")
  Monitor-1: HDMI-0 res: 1920x1080 dpi: 93 size: 527x296mm (20.7x11.7") diag: 604mm (23.8")
  OpenGL: renderer: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 v: 4.6.0 NVIDIA 535.161.07
    direct render: Yes
Audio:
  Device-1: NVIDIA TU116 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
    pcie: speed: 8 GT/s lanes: 16 bus-ID: 08:00.1 chip-ID: 10de:1aeb class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
    speed: 16 GT/s lanes: 16 bus-ID: 0a:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: JMTek LLC. USB PnP Audio Device type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus-ID: 1-10:6 chip-ID: 0c76:161e class-ID: 0300
  Sound Server-1: ALSA v: k6.5.0-25-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: 5 GT/s
    lanes: 1 port: f000 bus-ID: 07:00.0 chip-ID: 10ec:8125 class-ID: 0200
  IF: enp7s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 3.87 TiB used: 1.01 TiB (26.0%)
  ID-1: /dev/nvme0n1 vendor: KLEVV model: CRAS C710 M.2 NVMe SSD 256GB size: 238.47 GiB
    speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: S0614B0G temp: 47.9 C scheme: GPT
  ID-2: /dev/nvme1n1 vendor: Corsair model: Corsair MP600 PRO size: 931.51 GiB speed: 63.2 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: EIFM11.0 temp: 43.9 C scheme: GPT
  ID-3: /dev/sda vendor: Western Digital model: WDS100T2B0A-00SM50 size: 931.51 GiB
    speed: 6.0 Gb/s type: SSD serial: <filter> rev: 90WD scheme: GPT
  ID-4: /dev/sdb type: USB vendor: Seagate model: Expansion size: 1.82 TiB type: N/A
    serial: <filter> rev: 9300 scheme: MBR
Partition:
  ID-1: / size: 915.32 GiB used: 144.79 GiB (15.8%) fs: ext4 dev: /dev/nvme1n1p2
  ID-2: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/nvme1n1p1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 256 KiB (0.0%) priority: -2 file: /swapfile
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 10 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-1:2 info: China Resource Semico USB Gaming Keyboard type: Keyboard,Mouse
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s power: 100mA
    chip-ID: 1a2c:8014 class-ID: 0301
  Device-2: 1-2:3 info: KYE Systems (Mouse Systems) Scorpion M8-610 Gaming Mouse
    type: Mouse,HID,Keyboard driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s
    power: 300mA chip-ID: 0458:017d class-ID: 0300
  Device-3: 1-6:4 info: ASUSTek AURA LED Controller type: HID driver: hid-generic,usbhid
    interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 16mA chip-ID: 0b05:1939 class-ID: 0300
    serial: <filter>
  Hub-2: 1-7:5 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
    chip-ID: 05e3:0610 class-ID: 0900
  Device-1: 1-7.1:7 info: Cooler Master AMD SR4 lamplight Control type: Keyboard,HID
    driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 2516:0051
    class-ID: 0300
  Device-2: 1-7.3:8 info: Seagate RSS LLC SRD0NF1 Expansion Portable (STEA) type: Mass Storage
    driver: uas interfaces: 1 rev: 2.1 speed: 480 Mb/s power: 100mA chip-ID: 0bc2:2322
    class-ID: 0806 serial: <filter>
  Device-3: 1-10:6 info: JMTek LLC. USB PnP Audio Device type: Audio,HID
    driver: hid-generic,snd-usb-audio,usbhid interfaces: 3 rev: 1.1 speed: 12 Mb/s power: 100mA
    chip-ID: 0c76:161e class-ID: 0300
  Hub-3: 2-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-4: 3-0:1 info: Hi-speed hub with single TT ports: 2 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-5: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-6: 5-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-7: 6-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: nvidia temp: 46 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 33%
Repos:
  Packages: 2483 apt: 2458 flatpak: 25
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //packages.linuxmint.com virginia main upstream import backport
    2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  No active apt repos in: /etc/apt/sources.list.d/steam-beta.list
  Active apt repos in: /etc/apt/sources.list.d/steam-stable.list
    1: deb [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https: //repo.steampowered.com/steam/ stable steam
    2: deb-src [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https: //repo.steampowered.com/steam/ stable steam
Info:
  Processes: 371 Uptime: 2h 32m wakeups: 0 Memory: 15.51 GiB used: 4.7 GiB (30.3%) Init: systemd
  v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Cinnamon v: 6.0.4 inxi: 3.3.13

[xenopeek]

Where/when are you getting these errors?

Error 1: "Error mounting /dev/sda2 at /media/arvoly/Secondary Storage: Unknown error when mounting /dev/sda2" Western Digital
Error 2 : "Error mounting /dev/nvme0n1p2 at /media/arvoly/Small Extra Storage: Unknown error when mounting /dev/nvme0n1p2" Klevv

Because these partitions aren't set up in /etc/fstab to be mounted at boot so how are you mounting them?

As these look to be internal storage -- so permanently attached -- I'd suggest to set up mounting them in /etc/fstab so they mount at boot. And not mount them to /media as that is for removable storage. To help with what to put in /etc/fstab need some extra info, share output of:

Code: Select all

lsblk -o NAME,SIZE,TYPE,FSTYPE,UUID

[Arvoly]

I get those errors when I try to mount the drives through my Files. I don't know why I have to mount them as they are supposed to be permanently attached as Slave drives.

Also here is the 'lsblk -o' output:

Code: Select all

NAME          SIZE TYPE FSTYPE UUID
sda         931.5G disk        
├─sda1         16M part        
└─sda2      931.5G part ntfs   B834F0B534F07828
sdb           1.8T disk        
└─sdb1        1.8T part ntfs   360A6F7B0A6F3751
nvme1n1     931.5G disk        
├─nvme1n1p1   512M part vfat   0579-33B9
└─nvme1n1p2   931G part ext4   7b6447f8-83fd-4508-ab89-ff5ca3b71cac
nvme0n1     238.5G disk        
├─nvme0n1p1    16M part        
└─nvme0n1p2 238.5G part ntfs   1C700C3C700C1EE0

The 1.8TB drive is an external storage and works fine.

[AndyMH]

I'm guessing that udisks is trying to automount them.

Both partitions are ntfs, if dual booting run chkdsk on them.

[Arvoly]

I am only running Mint on my system, no dual booting.

[xenopeek]

I don't know enough about NTFS. It would preferable to format these as ext4 so they use a Linux native filesystem, not a Windows one. I guess you have data on the drives you would need to recover first?

The general steps to set these up as permanent attached storage is to create a "Secondary Storage" and "Small Extra Storage" directory in your home directory, or elsewhere so long as you make yourself the owner of the directories and they are not in /media or /mnt as these are treated special by the system and shouldn't be used for permanent attached storage.

Then edit fstab (xed admin:///etc/fstab) and add lines like following:

Code: Select all

# was on /dev/sda2
UUID=B834F0B534F07828/home/arvoly/Secondary\040Storage    	ext4      	rw,relatime	0 2
# was on /dev/nvme0n1p2
UUID=1C700C3C700C1EE0	/home/arvoly/Small\040Extra\040Storage    	ext4      	rw,relatime	0 2

The UUIDs can change if you format those partitions so you'll have to update that. The above won't work right now because I only know for Linux filesystems. So the "ext4" part needs to be changed to whatever is used for NTFS these days, and you'll need to add fmask and dmask and uid and gid options to "rw,relatime" because NTFS can't handle the truth isn't compatible with Linux filesystem permissions so you have to make it pretend so you can read & write files on it. I haven't used NTFS on Linux ever but somebody else can surely help here.

[Arvoly]

I mostly used them for Extra storage where I would off-load games and large files onto just so I don't clutter my main drive. It would be slightly inconvinient to format them, but I can redownload games if I need to. However I do not know how to format a disk if it isn't mounted. When I right-click them I only get the options to:

Code: Select all

Open
Open in New Tab
Open in New Window
Add Bookmark
Mount

If someone could explain how to format them and how to attach them to different directories it would be appreciated.

[xenopeek]

You can use the GParted or the Disks program to format the partitions. They do not need to be mounted to format. Recommend to format as ext4.

After formatting run the lsblk -o NAME,SIZE,TYPE,FSTYPE,UUID command again to find the UUIDs of these partitions. Then as detailed above:
1) for each partition create a directory to use as its mount point. In the example it put them in your home directory but you can put there where you want.
2) then add lines as in the example to /etc/fstab where you use the correct UUID and full path to the mount directory
3) the mount directory must be owned by you (so if you create the directory outside your home directory, you will have to change the ownership from root to yourself)

Finally, after having set up the mount directories and adding the lines to /etc/fstab, you can run sudo mount -a to test the configuration. That should now mount the partitions. If that works without errors, it will mount them for you automatically every boot.

[altair4]

One more command output please, Sorry:

Code: Select all

sudo blkid -c /dev/null -o list

[AndyMH]

Lets see if we can find out more about the error.

Create a temporary folder in home, e.g. /home/you/testmount then in a terminal:

Code: Select all

sudo mount -vvvv -t ntfs /dev/sda2 /home/you/testmount -o defaults,uid=1000,gid=1000

Replace you with your username, does it work, can you see your files in testmount, if not post the errors, the -vvvv is to give verbose output.

[altair4]

BTW, you do realize that if you format the partitions to ext4 whatever data you have in them will be lost, right?

[Arvoly]

I ultimately decided to format both Drives. Though the loss of data is unfortunate, it's still not a big loss.
After some testing, research and help from xenopeek I got my drives working and they auto mount to their respective directories.

My fstab config:

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/nvme1n1p2 during installation
UUID=7b6447f8-83fd-4508-ab89-ff5ca3b71cac /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme1n1p1 during installation
UUID=0579-33B9  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0
# was on /dev/sda2
UUID=2ca67758-43ae-480c-b3e4-30c0296ccd48 /home/arvoly/SecondaryStorage     ext4     rw,relatime    0 2
# was on /dev/nvme0n1p2
UUID=3b267861-89ce-4527-a438-cd635304f021 /home/arvoly/SmallExtraStorage     ext4      rw,relatime   0 2

A good thing to note, do not input your UUID incorrectly as it will cause an infinite boot screen and force you into emergency mode.

I even put in dummy files to see if it would persist and they did. I have restarted my device several times to test this and so far it works.

Although it seems I can't rename the devices, though it is not a problem. Thank you for your willingness to help me.

[AndyMH]

You might want to add nofail to the options on sda2, that way if the drive is not plugged in on boot the system is not going to hang for 90 secs trying to find it. I would also add user so if you plug it in later, you can mount it, without this only root can mount it. I usually use just defaults,user,nofail on my ext4 partitions.

[Arvoly]

The Drives work now, but they don't use their respective storage, it seems that they are linked to my Main Drive and use my Main drive as their storage.
My 256GB drive now has the exact same size as my main drive.

[Arvoly]

It seems the automount method didn't really work for me as mounting them to a file caused them to use my Main drive as their storage system. I have now edited my fstab config to not automount them and they work like normal again, by using their own storage and not a linked storage. Although not the intended outcome, it's still better than not having a drive mount at all. I am fine with having to mount them on start up.

[xenopeek]

With this in the /etc/fstab file, if the UUIDs are correct and those directories exist, it will automount;

Code: Select all

# was on /dev/sda2
UUID=2ca67758-43ae-480c-b3e4-30c0296ccd48 /home/arvoly/SecondaryStorage     ext4     rw,relatime    0 2
# was on /dev/nvme0n1p2
UUID=3b267861-89ce-4527-a438-cd635304f021 /home/arvoly/SmallExtraStorage     ext4      rw,relatime   0 2

Are /home/arvoly/SecondaryStorage and /home/arvoly/SmallExtraStorage the correct paths? Did those directories have that exact name?

After editing /etc/fstab you can test mount them with sudo mount -a. You can check with lsblk if they are correctly mounted to those directories.

[AndyMH]

The Drives work now, but they don't use their respective storage, it seems that they are linked to my Main Drive and use my Main drive as their storage.
My 256GB drive now has the exact same size as my main drive.

I don't think you understand the linux filesystem, everything mounts somewhere under /. When you let linux automount it uses udisks and it mounts partitions at /media/arvoly. If you have a label on the partition it will mount at /media/arvoly/labelname, if you don't have a label it uses the UUID which is not particularly user friendly.

When you mount partitions via fstab you get to choose where in the filesystem they mount. You chose to mount them at /home/arvoly/SecondaryStorage and /home/arvoly/SmallExtraStorage. You could have mounted them somewhere else, e.g. /media/SecondaryStorage. Your choice.