SSD won't mount - but it's fine in Windows

[MarshViper]

Hi! I just set up my new PC over the weekend and have been slowly getting things working. I currently have it set up to dual boot Windows 11 and Ubuntu Studio (24.04.3 LTS) but I haven't really touched Windows since I installed it, and I like it that way.

Tonight I was fiddling with drivers trying to get BG3 to work and after I rebooted for the Nth time, I cannot access my second SSD. I get the following error message:

An error occurred while accessing 'QuickSSD', the system responded: The requested operation has failed: Error mounting /dev/nvme0n1p2 at /media/jd/QuickSSD: wrong fs type, bad option, bad superblock on /dev/nvme0n1p2, missing codepage or helper program, or other error

I booted into Windows to check and I can see and interact with the drive fine. Did a complete shutdown and then turned it back on to go into Ubuntu again and still can't interact with the drive. My other drives work fine.

The BG3 game files are stored on the drive that is not working and it did crash a bunch of times.

I haven't used Linux much since my undergrad days, and back then it wasn't my hardware. So I'm pretty new to this all, but I do want to learn and know what I'm doing. Can anyone give me guidance on how to troubleshoot this problem? That error message is giving me it looks like five options plus "other problem" for what could be wrong and I only know what some of them mean.

Thanks in advance

 

[Alexzee]

Sounds like you may need to run fsck (file system check disk) to repair the bad superblocks on the drive.

Before running fsck I would check to see if the drive is failing first. To do that you'll want to run a S.M.A.R.T. (smartmontools) to test the state / health of the drive.

https://linuxconfig.org/how-to-check-an-hard-drive-health-from-the-command-line-using-smartctl

I'll give you the instructions for running fsck once you can confirm that the drive is showing signs of failure. I say that as there wouldn't be any point in fixing the badblocks if the drive is on it's way out.

 

[MarshViper]

Thank you. I'll check it and report back shortly. I will be very irritated if it is failing, as it's brand new!

 

[Alexzee]

Thank you. I'll check it and report back shortly. I will be very irritated if it is failing, as it's brand new!

You're welcome.
I hope for you that the drive isn't failing. BTW Lexar drives don't play nice with Linux.

 

[MarshViper]

Ok, hrm. Based on what I read in that tutorial, I think I should get some test results below this, but it's saying the test failed, in that very last line.

------

redacted:~$ sudo smartctl -a /dev/nvme0n1
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.14.0-32-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number: WD_BLACK SN850X 4000GB
Serial Number: 250143800004
Firmware Version: 624361WD
PCI Vendor/Subsystem ID: 0x15b7
IEEE OUI Identifier: 0x001b44
Total NVM Capacity: 4,000,787,030,016 [4.00 TB]
Unallocated NVM Capacity: 0
Controller ID: 8224
NVMe Version: 1.4
Number of Namespaces: 1
Namespace 1 Size/Capacity: 4,000,787,030,016 [4.00 TB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 001b44 8b4d17a636
Local Time is: Tue Sep 30 21:32:32 2025 CDT
Firmware Updates (0x14): 2 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x00df): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Verify
Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg
Maximum Data Transfer Size: 128 Pages
Warning Comp. Temp. Threshold: 90 Celsius
Critical Comp. Temp. Threshold: 94 Celsius
Namespace 1 Features (0x02): NA_Fields

Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 9.00W 9.00W - 0 0 0 0 0 0
1 + 6.00W 6.00W - 0 0 0 0 0 0
2 + 4.50W 4.50W - 0 0 0 0 0 0
3 - 0.0250W - - 3 3 3 3 3100 11900
4 - 0.0050W - - 4 4 4 4 3900 45700

Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 2
1 - 4096 0 1

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 39 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 276,305 [141 GB]
Data Units Written: 1,473,546 [754 GB]
Host Read Commands: 1,336,118
Host Write Commands: 6,033,277
Controller Busy Time: 2
Power Cycles: 22
Power On Hours: 32
Unsafe Shutdowns: 3
Media and Data Integrity Errors: 0
Error Information Log Entries: 0
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0

Error Information (NVMe Log 0x01, 16 of 256 entries)
No Errors Logged

Read Self-test Log failed: Invalid Field in Command (0x4002)

 

[osprey]

Hi! I just set up my new PC over the weekend and have been slowly getting things working. I currently have it set up to dual boot Windows 11 and Ubuntu Studio (24.04.3 LTS) but I haven't really touched Windows since I installed it, and I like it that way.

Tonight I was fiddling with drivers trying to get BG3 to work and after I rebooted for the Nth time, I cannot access my second SSD. I get the following error message:



I booted into Windows to check and I can see and interact with the drive fine. Did a complete shutdown and then turned it back on to go into Ubuntu again and still can't interact with the drive. My other drives work fine.

The BG3 game files are stored on the drive that is not working and it did crash a bunch of times.

I haven't used Linux much since my undergrad days, and back then it wasn't my hardware. So I'm pretty new to this all, but I do want to learn and know what I'm doing. Can anyone give me guidance on how to troubleshoot this problem? That error message is giving me it looks like five options plus "other problem" for what could be wrong and I only know what some of them mean.

Thanks in advance

AIUI the default Desktop Environment (DE) for ubuntu studio is KDE Plasma.

It looks like the DE is configured to automatically mount one or more partitions of the ssd, but fails, then provides the error message output.

One can test the mounting independently by selecting a mount point and running a mount command as root or sudo from a terminal.

One issue is the filesystem of the ssd. If it works in MS it's possibly an ntfs filesystem rather than one native to linux like ext4. In that case one can reference the filesystem in the mount command.

To see what filesystem the ssd is run:

lsblk -f

If the filesystem is indeed ntfs, one can select a mount point such as /mnt in the mount command, and run the command such as the following as root or sudo:

mount -t ntfs-3g /dev/nvme0n1p2 /mnt

If there are no errors, one can navigate in the filesystem to /mnt and see the files on the ssd. Hopefully, the filesystem will mount. The ntfs-3g driver in linux allows reading and writing to that filesystem.

If by chance the ntfs-3g driver is not installed, it can be installed and try the process again. Most major distros have the driver installed by default, but if not, then it's certainly available. It's the package: ntfs-3g, in many distros.

 

[MarshViper]

Yes, it is NTFS.

I tried to do the tutorial that Alexzee linked and my post with all the results is trapped in moderation

It gave me the info about the drive (and I don't see any major red flags, though I don't understand it all). But, it won't actually run the tests. At the end it says "Read Self-test Log failed: Invalid Field in Command (0x4002)"

Does "Critical Warning: 0x00" mean there is a warning or that there isn't one?
The drive is not getting too hot. It had 3 unsafe shutdowns (no doubt when I was trying to get BG3 to work).
It says the overall health self-assessment test PASSED.
It says No Errors Logged.

Since the tests wouldn't run, I cheated and booted into Windows. The Windows test found some errors (orphaned files and things like that). I suppose I could try fixing them in Windows and see if the drive starts working again, but I'm interested to know what y'all have to say first!

 

[Alexzee]

Yes, it is NTFS.

I tried to do the tutorial that Alexzee linked and my post with all the results is trapped in moderation

It gave me the info about the drive (and I don't see any major red flags, though I don't understand it all). But, it won't actually run the tests. At the end it says "Read Self-test Log failed: Invalid Field in Command (0x4002)"

Does "Critical Warning: 0x00" mean there is a warning or that there isn't one?
The drive is not getting too hot. It had 3 unsafe shutdowns (no doubt when I was trying to get BG3 to work).
It says the overall health self-assessment test PASSED.
It says No Errors Logged.

Since the tests wouldn't run, I cheated and booted into Windows. The Windows test found some errors (orphaned files and things like that). I suppose I could try fixing them in Windows and see if the drive starts working again, but I'm interested to know what y'all have to say first!

The "Critical Warning: 0x00" is referring to the temperature.

To see if the drive is hot run:

smartctl -a /dev/nvme01P1

When you can run the commands osprey asked you for and post the output. That will help us to help you.

The "Read Self-test Log failed: Invalid Field in Command" is sometimes a problem with how the command is being used or how the smartctl command interacts with the nvme device.

I use a Live Linux USB to test the drive but that's just my preference.

 

[MarshViper]

The drive is only 40 C.

And, Osprey's command worked! I can see the files now, in the terminal and the GUI both.

 

[Alexzee]

The drive is only 40 C.

And, Osprey's command worked! I can see the files now, in the terminal and the GUI both.

Good! The mount command is handy. You may want to go find a cheat sheet for frequently used commands.
Cool so you can see the files now can you click on them in the GUI and view them as well?

 

[MarshViper]

Good! The mount command is handy. You may want to go find a cheat sheet for frequently used commands.
Cool so you can see the files now can you click on them in the GUI and view them as well?

Yes, I can.

 

[Alexzee]

Yes, I can.

Great, then if all is good and you can mount the files on that drive....kindly mark your thread Solved.

 

[MarshViper]

Thank you all for your help. One more question: this has happened a couple more times. Is this normal to have a drive unmount itself and have to remount it?

 

[Brickwizard]

With not a lot to do, I did some searching on your Invalid Field in Command 0x4002 error, it appears that it is not uncommon, and is more common on larger drives