LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   External WS backup disk doesn't mount (https://www.linuxquestions.org/questions/linux-hardware-18/external-ws-backup-disk-doesnt-mount-4175733073/)

alex4buba 01-22-2024 08:50 PM

External WS backup disk doesn't mount
 
KDE Neon plasma, latest update.
The drive mounts on my Android mobile, mounts on my wife's Apple laptop, but NOT on my HP Probook Laptop.

Any suggestions welcome.

Cheers

wpeckham 01-23-2024 12:17 AM

Need more data.
Speak of connectivity. Also the file system format, versions of operating system distribution and version.
Speak of the boot log and device recognition.
Speak about what you have tried and what results you received, with detail and verbatim if possible.
Speak also of the hardware.
We cannot troubleshoot in the dark.

alex4buba 01-23-2024 02:40 AM

External WD backup disk does not mount
 
1 Attachment(s)
Quote:

Originally Posted by wpeckham (Post 6478711)
Need more data.
Speak of connectivity. Also the file system format, versions of operating system distribution and version.
Speak of the boot log and device recognition.
Speak about what you have tried and what results you received, with detail and verbatim if possible.
Speak also of the hardware.
We cannot troubleshoot in the dark.

Sorry, not familliar with the questions, just attached a screen shot with machine details.
I am using a HP Probook Laptop, tried all the 3 USB ports with the same result, unable to mount.
The disk itself is a WD 3TB and mounts OK as mentioned on other devices I have around me.

What is boot log? How do I find out?, what is device recognition?

Hope it helps explain what I am facing

Many thanks

michaelk 01-23-2024 03:30 AM

What filesystem?

Most likely either exFAT or NTFS. Look at the output of the command:
lsblk -f

You probably need to install the fuse drivers for exFAT.

hazel 01-23-2024 03:48 AM

Quote:

Originally Posted by alex4buba (Post 6478733)
Sorry, not familliar with the questions...
What is boot log? How do I find out?, what is device recognition?

System logs are kept in the /var/log directory/folder. One of these logs is boot, which is simply a record of all the messages the kernel put out when last booting the system. This includes a lot of stuff that no one understands ;) but also the kernel's recognition of all the hardware devices. If it has seen your disk drive, it should record its presence with make, size, partitioning and so on.

wpeckham 01-23-2024 12:45 PM

HP Probook is a series of models that come in two lines that I know about. The Fortis line and the 400 line. Each line has multiple models with slightly different features. I realize now that WE do not know what you have partly because YOU do not know what you have. There are a few ways to look this up. If you have it installed the neofetch utility gives some of the basic information.

I would put this on hold while you investigate the file system, as that is FAR more likely to be the issue.

I look forward to seeing the output of that lsblk command.

alex4buba 01-23-2024 02:34 PM

Quote:

Originally Posted by michaelk (Post 6478736)
What filesystem?

Most likely either exFAT or NTFS. Look at the output of the command:
lsblk -f

You probably need to install the fuse drivers for exFAT.

The file system of the external WD drive is NTFS

Does this help?
Cheers

michaelk 01-23-2024 02:43 PM

Does KDE neon use fuse i.e. ntfs-3g (or just ntfs) or ntfs3 which is the builtin kernel driver (need kernel version 5.15+)?

What happens when you try to manually mount the drive? What is the error or warning messages?

alex4buba 01-23-2024 03:02 PM

1 Attachment(s)
Quote:

Originally Posted by wpeckham (Post 6478827)
HP Probook is a series of models that come in two lines that I know about. The Fortis line and the 400 line. Each line has multiple models with slightly different features. I realize now that WE do not know what you have partly because YOU do not know what you have. There are a few ways to look this up. If you have it installed the neofetch utility gives some of the basic information.

I would put this on hold while you investigate the file system, as that is FAR more likely to be the issue.

I look forward to seeing the output of that lsblk command.

The external WD disk is with NTFS
What is the "lsblk command"? In the setup i see the model is :
HP ProBook 450 15.6 inch G10 Notebook PC

As you can see, I don't know much about all this, I tried to attach the log file, but it doesn't accept it, so i renamed it to .txt, I have no idea what to look for in it.

Thanks

wpeckham 01-23-2024 04:07 PM

I see only one storage device detected. Was that drive connected during the boot?
You might also try the dmesg command
Code:

sudo dmesg
and examine the output for references to /dev/sda or /dev/nvme.


I expect that the issue is that you will have to install or activate one of the NTFS drivers. NTFS is not a native Linux file system, or native to ANY system that is good about sharing information. That is less common these days, because Linux maintainers are good about assuming people might need to access obsolete, faulty, or alien storage like NTFS.

hazel 01-24-2024 01:11 AM

From the boot file (tldr):
Code:

$ grep nvme boot.txt
/dev/nvme0n1p2: recovering journal
/dev/nvme0n1p2: Clearing orphaned inode 19187184 (uid=1000, gid=1000, mode=0100664, size=2099)
/dev/nvme0n1p2: Clearing orphaned inode 19187631 (uid=1000, gid=1000, mode=0100664, size=726454)
/dev/nvme0n1p2: clean, 465971/60260352 files, 43853205/241039096 blocks
/dev/nvme0n1p2: clean, 465953/60260352 files, 43857483/241039096 blocks
/dev/nvme0n1p2: clean, 465957/60260352 files, 43861669/241039096 blocks
/dev/nvme0n1p2: clean, 465960/60260352 files, 43866041/241039096 blocks
/dev/nvme0n1p2: clean, 466129/60260352 files, 43878384/241039096 blocks
/dev/nvme0n1p2: clean, 466813/60260352 files, 43905797/241039096 blocks

So one drive with at least 2 partitions. I assume nvme0n1p1 is the ESP. But this isn't a normal boot log. It's one of those systemd-journald byproducts, so hard for an old woman like me to interpret. I agree that lsblk would give a more reliable answer.

@OP: open a terminal and just type lsblk. Then post the result. But before you do that, you might like to type man lsblk and you will get the user manual entry for the command. Make a point of doing that in future for any command you haven't met before. It's an excellent way of finding out new tricks.

As you have noticed, this site expects attachments to have certain suffixes and that includes .txt for text files, no matter where they come from.

alex4buba 01-24-2024 04:01 PM

[QUOTE=hazel;6478930]From the boot file (tldr):
Code:

$ grep nvme boot.txt
/dev/nvme0n1p2: recovering journal
/dev/nvme0n1p2: Clearing orphaned inode 19187184 (uid=1000, gid=1000, mode=0100664, size=2099)
/dev/nvme0n1p2: Clearing orphaned inode 19187631 (uid=1000, gid=1000, mode=0100664, size=726454)
/dev/nvme0n1p2: clean, 465971/60260352 files, 43853205/241039096 blocks
/dev/nvme0n1p2: clean, 465953/60260352 files, 43857483/241039096 blocks
/dev/nvme0n1p2: clean, 465957/60260352 files, 43861669/241039096 blocks
/dev/nvme0n1p2: clean, 465960/60260352 files, 43866041/241039096 blocks
/dev/nvme0n1p2: clean, 466129/60260352 files, 43878384/241039096 blocks
/dev/nvme0n1p2: clean, 466813/60260352 files, 43905797/241039096 blocks

So one drive with at least 2 partitions. I assume nvme0n1p1 is the ESP. But this isn't a normal boot log. It's one of those systemd-journald byproducts, so hard for an old woman like me to interpret. I agree that lsblk would give a more reliable answer.

Hello Hazel, I followed your instructions (I know very little about any of that), here is what I got:

Code:

sudo blkid
[sudo] password for alexe:
/dev/nvme0n1p3: LABEL="swap" UUID="f8ef5427-63f3-41d9-ac23-dbce86b352de" TYPE="swap" PARTUUID="fbe64281-d6f1-184a-9aab-68840fda149c"
/dev/nvme0n1p1: UUID="84D7-0865" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="d5a137d7-a0aa-5848-99bc-2eda2c2218d3"
/dev/nvme0n1p2: UUID="f7103309-b50d-4cd5-b216-823bd6d081da" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="root" PARTUUID="aeada4ea-708c-fb49-9587-ff54509c867a"
/dev/loop1: TYPE="squashfs"
/dev/loop8: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop13: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop0: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/sda2: LABEL="Elements" BLOCK_SIZE="512" UUID="0A26F6D61BA81F4A" TYPE="ntfs" PARTLABEL="Elements SE" PARTUUID="4d57cc78-3f9b-4cc0-9379-09732a036346"
/dev/loop5: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"

It seems the culprit is this line:

Code:

/dev/sda2: LABEL="Elements" BLOCK_SIZE="512" UUID="0A26F6D61BA81F4A" TYPE="ntfs" PARTLABEL="Elements SE"
What can I do, I have important data that I need to salvage on that disk. It mounts OK on an Apple laptop as well as on my Android tablet and phone, but too large to copy other then to another disk.

I installed NTFS-3G but it doesn't help fix anything

Thanks

michaelk 01-24-2024 04:13 PM

What is the error message when you try to manually mount the drive?

alex4buba 01-24-2024 04:45 PM

Could NOT mount
 
1 Attachment(s)
Quote:

Originally Posted by michaelk (Post 6479064)
What is the error message when you try to manually mount the drive?

Please see attached

Thanks

michaelk 01-24-2024 04:51 PM

From the command line...
mount -t ntfs-3g /dev/sda2 /mnt/some_directory

You can also try just:
mount -t ntfs /dev/sda2 /mnt/some_directory


All times are GMT -5. The time now is 03:37 PM.