Announcement

**Snowhog** · Jun 29, 2024, 07:19 AM

Welcome to KFN!

You likely don't have the package ntfs-3g installed. This is necessary for Kubuntu to be able to see and access ntfs formatted drives.

**oshunluvr** · Jun 29, 2024, 07:54 AM

Some terminal output might help. I assume this drive is /dev/sda.

Open Konsole and enter lsblk and it should list all your partitions and file system types. Assuming it reads /dev/sda it should look something like:

Code:

sda
sda1 ntfs HGST 1To <UUID>

If that's similar to what you see, then try and mount it:

Code:

sudo mount /dev/sda1 /mnt

Use your partition number (sda1, sda2, etc.). Then post the output here.

**Bob Nelson** · Jun 29, 2024, 09:07 AM

Originally posted by oshunluvr View Post

Some terminal output might help. I assume this drive is /dev/sda.

Open Konsole and enter lsblk and it should list all your partitions and file system types. Assuming it reads /dev/sda it should look something like:

Code:

sda
sda1 ntfs HGST 1To <UUID>

If that's similar to what you see, then try and mount it:

Code:

sudo mount /dev/sda1 /mnt

Use your partition number (sda1, sda2, etc.). Then post the output here.

lsblk yields this:
sda 8:0 0 931,5G 0 disk
└─sda1 8:1 0 931,5G 0 part

The "sudo mount" command worked! Yay! And thank you. I'll let you know if this still works after a restart.

**Bob Nelson** · Jun 29, 2024, 09:14 AM

Originally posted by oshunluvr View Post

Some terminal output might help. I assume this drive is /dev/sda.

Open Konsole and enter lsblk and it should list all your partitions and file system types. Assuming it reads /dev/sda it should look something like:

Code:

sda sda1 ntfs HGST 1To <UUID>

If that's similar to what you see, then try and mount it:

Code:

sudo mount /dev/sda1 /mnt

Use your partition number (sda1, sda2, etc.). Then post the output here.

After relaunch, the disk was not accessed... but after repeating your "sudo mount /dev/sda1 /mnt" command, Dolphin could access the disk. This is certainly better than inaccessible, but I'd rather not have to go to Konsol at every use.

More ideas??

**oshunluvr** · Jun 29, 2024, 10:23 AM

So the way mounting of file systems generally works is only file systems defined to specific mount points in /etc/fstab/ will be mounted at boot up. So if you want this booted every time you boot up, you would want to define it in fstab. This is usually the way "fixed" (installed) devices are handled.

Non-fixed (removable) device are normally handed by UDEV at insertion, or when selected from the "Disks and Devices" menu in the System Tray or when clicking on them in Dolphin "Devices" section.

So how to proceed depends on how you intend to use the drive. This is Linux so you have a lots of options on how to do this and all the control to do it.

For example, I have 4 nvme devices and 2 hard drives installed in my system. I don't need or want them all to mount at boot so they are listed in /etc/fstab but with the "noauto" option. Then I also add the "users" option whcih lets me mount and un-mount them without having to enter my password every time. Done this way - and with all my file systems having meaningful labels, they appear in the Dolphin Device section as:

Code:

storage
vm_drive
root_backup
vm_backup

etc.

This kind of setup might work for you. I will say normally, removable devices like USB attached drives should be mountable by just attaching and selecting them. To find out why this isn't working will take some more sleuthing.

**Bob Nelson** · Jun 30, 2024, 01:20 AM

Originally posted by oshunluvr View Post

So the way mounting of file systems generally works is only file systems defined to specific mount points in /etc/fstab/ will be mounted at boot up. So if you want this booted every time you boot up, you would want to define it in fstab. This is usually the way "fixed" (installed) devices are handled.

Non-fixed (removable) device are normally handed by UDEV at insertion, or when selected from the "Disks and Devices" menu in the System Tray or when clicking on them in Dolphin "Devices" section.

So how to proceed depends on how you intend to use the drive. This is Linux so you have a lots of options on how to do this and all the control to do it.

For example, I have 4 nvme devices and 2 hard drives installed in my system. I don't need or want them all to mount at boot so they are listed in /etc/fstab but with the "noauto" option. Then I also add the "users" option whcih lets me mount and un-mount them without having to enter my password every time. Done this way - and with all my file systems having meaningful labels, they appear in the Dolphin Device section as:

Code:

storage
vm_drive
root_backup
vm_backup

etc.

This kind of setup might work for you. I will say normally, removable devices like USB attached drives should be mountable by just attaching and selecting them. To find out why this isn't working will take some more sleuthing.

Before moving my stuff to Kubuntu, I made a couple of 500 Go backup sd cards. So... of course... one of them mounted without resorting to your magic formula, but the other did not. Scratching head...

I have no idea what "/etc/fstab" is... I assume it's one of those many unintelligible folders in root. I'll go see now.

Thanks again.

**oshunluvr** · Jun 30, 2024, 07:01 AM

Yeah, you might want to do a little reading up on basic Linux stuff before you start slogging about with your system and data.

/etc/fstab means: folder = /etc/, file = fstab

Here's more than anyone needs to know about fstab.

I'll emphatically state one thing often said to new Linux users: "Linux is not Windows". You're in for some learnin', lol

Like I said though - if one mounted "magically" and the other didn't there's likely a reason. We just haven't sussed it out yet.

Since you're a newbie - let's throw you into the fire - AKA the terminal

Open the program "Konsole." With both drives not connected to your system, type this:

Code:

sudo dmesg

This will dump a huge amount of text onto the screen.
Look at the last line and note the time on the left side.
This is the time the last entry was sent to dmesg.
Now plug in the drive that works and wait a few seconds. Then type

Code:

sudo dmesg

again. All the lines after the time you previously noted were caused by the insertion of the drive.
In Konsole, highlight the new lines with your mouse - just highlight them and leave them highlighted.
Open the program "Kate" and click "New" in the upper left to open a new file.
Hover your mouse cursor over the blank document and click the middle mouse button.
The highlighted test should appear in the document.
Add a couple blank lines below the text.
Unplug the drive

You now have some output about how your "working" drive is detected by the system.

Now do the whole thing above again. Do the first

Code:

sudo dmesg

and again note the timestamp.
Plug the "bad" drive and collect the dmesg output as described above and pate it into the text document at the bottom.

Save the file somewhere, and copy the contents into a post on this thread and we'll have a look.

**Bob Nelson** · Jun 30, 2024, 07:42 AM

Originally posted by oshunluvr View Post

Yeah, you might want to do a little reading up on basic Linux stuff before you start slogging about with your system and data.

/etc/fstab means: folder = /etc/, file = fstab

Here's more than anyone needs to know about fstab.

I'll emphatically state one thing often said to new Linux users: "Linux is not Windows". You're in for some learnin', lol

Like I said though - if one mounted "magically" and the other didn't there's likely a reason. We just haven't sussed it out yet.

Since you're a newbie - let's throw you into the fire - AKA the terminal

Open the program "Konsole." With both drives not connected to your system, type this:

Code:

sudo dmesg

This will dump a huge amount of text onto the screen.
Look at the last line and note the time on the left side.
This is the time the last entry was sent to dmesg.
Now plug in the drive that works and wait a few seconds. Then type

Code:

sudo dmesg

again. All the lines after the time you previously noted were caused by the insertion of the drive.
In Konsole, highlight the new lines with your mouse - just highlight them and leave them highlighted.
Open the program "Kate" and click "New" in the upper left to open a new file.
Hover your mouse cursor over the blank document and click the middle mouse button.
The highlighted test should appear in the document.
Add a couple blank lines below the text.
Unplug the drive

You now have some output about how your "working" drive is detected by the system.

Now do the whole thing above again. Do the first

Code:

sudo dmesg

and again note the timestamp.
Plug the "bad" drive and collect the dmesg output as described above and pate it into the text document at the bottom.

Save the file somewhere, and copy the contents into a post on this thread and we'll have a look.

The deep end!

I ran the sudo dmesg command, but I can't see the forest because of all the trees. The output all looks the same. It changed some when I inserted the external disk that works. I had to tell Dolphin to mount it, but that wasn't a problem.

The second dmesg dump (after the HD insertion) looked like this:

[27347.644978] rtw_8822bu 3-3:1.0: rtw_usb_reg_sec: reg 0x4e0, usb write 1 fail, status: -71
[27347.645740] rtw_8822bu 3-3:1.0: rtw_usb_reg_sec: reg 0x4e0, usb write 1 fail, status: -71
[27347.793499] rtw_8822bu 3-3:1.0: timed out to flush queue 0
[27347.819580] rtw_8822bu 3-3:1.0: rtw_usb_reg_sec: reg 0x4e0, usb write 1 fail, status: -71
[27347.820709] rtw_8822bu 3-3:1.0: rtw_usb_reg_sec: reg 0x4e0, usb write 1 fail, status: -71
[27347.822017] rtw_8822bu 3-3:1.0: rtw_usb_reg_sec: reg 0x4e0, usb write 1 fail, status: -71
[27428.821671] kioslave5[68494]: segfault at 0 ip 000075e59379e9e4 sp 00007ffc1993e958 error 4 in libKPim5GAPIDrive.so.5.24.5[75e59379a000+46000] likely on CPU 5 (core 2, socket 0)
[27428.821687] Code: 05 06 00 48 89 de 48 8d 15 39 06 06 00 e8 44 cc ff ff 4c 89 e7 e8 5c c8 ff ff 48 89 d8 5b 41 5c 5d c3 0f 1f 40 00 f3 0f 1e fa <8b> 07 31 d2 85 c0 74 0a 83 f8 ff 75 0f ba 01 00 00 00 89 d0 c3 0f
[27439.145275] ntfs3: sdc1: ino=24, Correct links count -> 1.
[27439.147174] kioslave5[68518]: segfault at 0 ip 000076b2fda209e4 sp 00007ffdcd597ce8 error 4 in libKPim5GAPIDrive.so.5.24.5[76b2fda1c000+46000] likely on CPU 10 (core 5, socket 0)
[27439.147192] Code: 05 06 00 48 89 de 48 8d 15 39 06 06 00 e8 44 cc ff ff 4c 89 e7 e8 5c c8 ff ff 48 89 d8 5b 41 5c 5d c3 0f 1f 40 00 f3 0f 1e fa <8b> 07 31 d2 85 c0 74 0a 83 f8 ff 75 0f ba 01 00 00 00 89 d0 c3 0f
b@m5:~$

I found the fstab file:

# /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>
UUID=DB1D-FA51 /boot/efi vfat defaults 0 2
UUID=575e24f9-318d-4064-82ad-c363f7b149d8 / ext4 defaults 0 1
/swapfile swap swap defaults 0 0
tmpfs /tmp tmpfs noatime,mode=1777 0 0
/dev/sda1 none ntfs users,x-gvfs-show 0 0

**Bob Nelson** · Jun 30, 2024, 07:47 AM

Now the HGST disk mounted without my having to wave the magic wand.

A dmesg dump looks like before. Line after line of... stuff...

**oshunluvr** · Jun 30, 2024, 08:12 AM

This:

Code:

[27428.821671] kioslave5[68494]: segfault at 0 ip 000075e59379e9e4 sp 00007ffc1993e958 error 4 in libKPim5GAPIDrive.so.5.24.5[75e59379a000+46000] likely on CPU 5 (core 2, socket 0)

may be the issue. Not sure where or why this is happening but it's not normal. Hopefully, an update or kernel change will fix it sooner rather than later.

Breaking down your fstab:

The EFI oe ESP partition:
UUID=DB1D-FA51 /boot/efi vfat defaults 0 2

Your installation "root" partition:
UUID=575e24f9-318d-4064-82ad-c363f7b149d8 / ext4 defaults 0 1

Not a partition, but a swap file:
/swapfile swap swap defaults 0 0

Temporary File System (tempfs) mounted here:
tmpfs /tmp tmpfs noatime,mode=1777 0 0

Your Windows partition:
/dev/sda1 none ntfs users,x-gvfs-show 0 0

So like I said, those two external drives are not in here, but could be if that's what you want. With that segfault happening, it might not be a bad idea. Like I said before, the external drives will never be mounted automatically because they are removable. You can write a specific UDEV rule to create this behavior but that might be a little beyond your level at this point and frankly probably not worth it. "Clicking" on the drive with Dolphin or in the System Tray > Devices is the normal way to access removable devices.

The thing with mounting USB drives in fstab is they often change device names, so they should be mounted using UUID or File System Label.

This is a UUID: 575e24f9-318d-4064-82ad-c363f7b149d8

This is a Device Name: /dev/sda1

Labeling the File System on the drives can be done using KDE Partition Manager and IMO a good idea because it makes it easier to know one from the other. Then you would need to create folders to use as mount points for them, and then edit fstab to make them available that way if you want.

**Bob Nelson** · Jul 01, 2024, 07:07 AM

Thanks for your help.
Today, the WD disk and both sd cards mounted just fine in Dolphin. I had to say the magic words to get the HGST to mount, but that's not really much of a problem. I can live just fine with the situation... and a reminder post-it stuck to the HGST...

**oshunluvr** · Jul 02, 2024, 08:26 AM

Saw an article this morning that may have something to do with the issues you were having.

Anyway, made me think that there is an "automount" feature where you can control removable devices:

System Settings > Connected Devices > Disks and Camera > Device Automount

From that menu, you can select: All Known Devices, Attached Devices, or Disconnected Devices.

Assuming your external drives are attached, open the Attached Device drop down and they should be listed there. Check the "On Attach" box and the "Apply" in the lower right. From then on, they should mount when plugged in.

**Bob Nelson** · Jul 03, 2024, 10:12 AM

I didn't find exactly what you said, but this:

Removable Storage

Removable Devices

Attached Devices

(Here there are check-boxes for "on login" and "on attach", which I checked for "All Known Devices".
I also checked "Automatically mount removable media that have never been mounted before".)

After a restart, Dolphin still needed the magic words to mount the HGST... but the Windows nvme was mounted...

I love it!

**oshunluvr** · Jul 03, 2024, 03:27 PM

LOL, OK there's clearly a demon at work here.

I just want to verify the HGST drive is NTFS file system?

Announcement

Cannot mount external ntfs hard disk

[System] Cannot mount external ntfs hard disk

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment