Ubuntu sees external drive but won't mount

An external hard drive shows up in “Disks” but Ubuntu fails to mount it . I cannot run any diagnostic test on it as “SMART Data & Self Test” is grayed out. The drive was working fine yesterday, I have no idea what changed. I’m new with Ubuntu and all of the potential fixes I’ve found are very complicated and way over my head. I’ve tried many of them without any clue as to what I’m doing and nothing has worked. I’ve restarted the computer several times but no luck. I’ve tried a different Ubuntu laptop but with the same result. A Windows computer also recognizes the drive is present but won’t assign a drive letter so I can’t access files. Please pretend I am 5 years old. Is there any easy way to fix this? Thank you in advance.

System Details Report

Hardware Information:

Hardware Model: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X515JA_F515JA

Memory: 4.0 GiB

Processor: Intel® Core™ i3-1005G1 × 4

Graphics: Intel® UHD Graphics (ICL GT1)

Disk Capacity: 128.0 GB

Software Information:

Firmware Version: X515JA.310

OS Name: Ubuntu 24.04.4 LTS

OS Build: (null)

OS Type: 64-bit

GNOME Version: 46

Windowing System: Wayland

Kernel Version: Linux 6.17.0-20-generic

That and the fact that a different Ubuntu laptop also shows the same issue, is a strong indication that the drive is defective. And that usually happens after reboots or just regular cold boots after some downtime. The drive just fails to spin up, most probably.

Thanks, you may be right, it may be defective. But I can feel it spinning and it does show up in “Disks” so I’m hoping it can be repaired. Thanks again.

Don’t laugh … put the drive in the fridge for 10 min, then connect again to your laptop. Old IT tale, the goal is to shrink internal components to temporarily fix issues but probably drive is dead.

Also, pop a terminal and type sudo dmesg do you any errors when the drive is connected?

The next thing that can be defective is the read/write head or the controller moving it. There are plenty moving parts in disks, so they are kind of doomed to fail eventually. As the old saying goes: there are three types of disks, those that have died, those that will die, and those that have been replaced before dying. :man_shrugging:

And that could also kill it for good, because of condensation. If it’s outside the temperature window of it’s specs, it may fail for any reason.

See this Seagate spec [PDF] for an example. And big differences in temps cause condensation, which may short out some circuits, which is why it is good practice to let devices that come fresh off the delivery van, which drove through the cold winter snow, to acclimate for at least an hour before even plugging them in.

Thanks I’ll try the frig trick. I get the following error message when the drive is plugged in “Unable to access ”Seagate” Error mounting /dev/sda2 at /media/richc101/Seagate: wrong fs type, bad option, bad superblock or /dev/sda2,missing codepage or helper program or other error.” None that helps me at all.

Okay, never mind about the refrigerator.

1 Like

Partition and file system info would be useful?

Is it ntfs?

I’m pretty sure that it is.

What does this say:

lsblk -e7 -o NAME,PARTLABEL,LABEL,UUID,FSTYPE

NAME PARTLABEL LABEL UUID FSTYPE

sda

├─sda1

│ Microsoft reserved partition

└─sda2

Basic data partition Seagate 7C2E84B92E846DC8 ntfs

sdb

└─sdb1

CANON_DC 827C-0BA4 exfat

nvme0n1

├─nvme0n1p1

│ EFI system partition SYSTEM 30AE-1F1A vfat

├─nvme0n1p2

│ Microsoft reserved partition

├─nvme0n1p3

│ Basic data partition OS 1AB8AFD6B8AFAF27 ntfs

├─nvme0n1p4

│ Basic data partition RECOVERY FCB668A0B6685D60 ntfs

├─nvme0n1p5

│ Basic data partition MYASUS 622B-B4DC vfat

├─nvme0n1p6

│ 3ce92e29-adad-48d0-b514-94d39883719b ext4

└─nvme0n1p7

88681a8b-d406-4024-8b9b-06259543c3de

Then, attach it to a Windows 11 PC and see if you can run chkdsk (or other similar Windows utilities)
Depending on the condition of the disk, it may fix it, it may not.

1 Like

That partition is awfully short.

I don’t have access to a Windows 11 computer but I could reboot this laptop to Windows 10. I ‘ll try that after I’ve exhausted other potential fixes. Thanks.

The only thing that comes to mind, given that the GUID partition table seems to be botched, is testdisk. But it’s not for the faint of heart.

sudo apt install testdisk

Ideally you should make a bit-for-bit image of the whole drive first, before committing any changes suggested by testdisk. And don’t write anything to the drive, because that might destroy still recoverable information.

I ran the testdisk install and it seemed to work but testdisk doesn’t show up in my apps. Where do I locate it? Sorry if I seem stupid. This is all new to me.

testdisk is a CLI tool.

1 Like

And I do reiterate: not for the faint of heart. :wink:

1 Like