KDE's Dolphin File Manager Does Not See 4TB HDD Hard Drive?

Hi,

On a newly built desktop with Manjaro KDE(fully updated).
I have a 4TB HDD hard drive installed, but Dolphin file manager does not see it?
The 4TB HDD drive is listed in the desktop’s BIOS.
Any ideas?

Jesse

Bro, whats the desktop’s BIOS?
The BIOS of your Desktop PC, i guess?

Checked the entry in the fstab? Can you mount it?
Or more basic, do you see the HDD in the Partition Manager?
Have you created a partition and formated with an filesystem?

format it in Kde Partitionsmanager with an GPT Table and ext4 or other file system

execute this;
sudo fdisk -l

and post output

check in UEFI motherboard that all disks are on AHCI

Hi,

This is a brand new 4TB HDD which I thought I formatted in EXT4 with LUKS encryption.
Please see below screenshot, thanks!

Jesse

you’ve partitioned only 2 of 4.

Hi @JeZxLee,

Please return the output for:

fdisk -l
    ~  disk -l                                                                                        ✔ 
zsh: correct 'disk' to 'gdisk' [nyae]? y
GPT fdisk (gdisk) version 1.0.9

Problem opening -l for reading! Error is 2.
The specified file does not exist!
    ~ 

Apologies,

fdisk -l

Note: the f in fdisk.

    ~  fdisk -l                                                                                       ✔ 
fdisk: cannot open /dev/nvme0n1: Permission denied
fdisk: cannot open /dev/sda: Permission denied
fdisk: cannot open /dev/mapper/luks-440db0cd-b663-44ee-ab79-06933f85b48c: Permission denied
    ~ 

Hmmm, it should give you much more than those 3 lines. Try:

sudo fdisk -l
    ~  sudo fdisk -l                                                                                  ✔ 

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

[sudo] password for jlp: 
Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Samsung SSD 980 PRO 2TB                 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 32276B0C-7B93-7C47-BBB4-5257BF4D404E

Device          Start        End    Sectors  Size Type
/dev/nvme0n1p1   4096     618495     614400  300M EFI System
/dev/nvme0n1p2 618496 3907024064 3906405569  1.8T Linux filesystem


Disk /dev/sda: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: ST4000DX005-3GH1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: D28AB434-5DD9-2D4E-9EA4-D9CD25E469A2

Device     Start        End    Sectors  Size Type
/dev/sda1   2048 7814035455 7814033408  3.6T Linux filesystem


Disk /dev/mapper/luks-440db0cd-b663-44ee-ab79-06933f85b48c: 1.82 TiB, 2000077554176 bytes, 3906401473 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
    ~                                                                                          ✔  6s 

It seems it is there, might just not be mounted. Please provide the output of:

mount

And

sudo fdisk -l /dev/sda
1 Like
   ~  mount                                                                                          ✔  
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=16379872k,nr_inodes=4094968,mode=755,inode64)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755,inode64)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
/dev/mapper/luks-440db0cd-b663-44ee-ab79-06933f85b48c on / type ext4 (rw,noatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,di
rect,pipe_ino=11864)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,noatime,inode64)
/var/lib/snapd/snaps/skype_211.snap on /var/lib/snapd/snap/skype/211 type squashfs (ro,nodev,relatime,errors=c
ontinue,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/bare_5.snap on /var/lib/snapd/snap/bare/5 type squashfs (ro,nodev,relatime,errors=continu
e,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/gnome-3-28-1804_161.snap on /var/lib/snapd/snap/gnome-3-28-1804/161 type squashfs (ro,nod
ev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/core18_2409.snap on /var/lib/snapd/snap/core18/2409 type squashfs (ro,nodev,relatime,erro
rs=continue,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/gtk-common-themes_1534.snap on /var/lib/snapd/snap/gtk-common-themes/1534 type squashfs (
ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/snapd_16010.snap on /var/lib/snapd/snap/snapd/16010 type squashfs (ro,nodev,relatime,erro
rs=continue,x-gdu.hide,x-gvfs-hide)
/dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortnam
e=mixed,utf8,errors=remount-ro)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=3278080k,nr_inodes=819520,mode=700,uid=1000,
gid=1000,inode64)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
   ~                                                                                                 ✔
    ~  sudo fdisk -l /dev/sda                                                                         ✔ 
[sudo] password for jlp: 
Disk /dev/sda: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: ST4000DX005-3GH1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: D28AB434-5DD9-2D4E-9EA4-D9CD25E469A2

Device     Start        End    Sectors  Size Type
/dev/sda1   2048 7814035455 7814033408  3.6T Linux filesystem
    ~                                                                                          ✔  4s 

You must give the drive (partition) a mount point and mount options.
You can do that with the KDE partitions manager.

Am i the only one ticking at the KDE Partition Manager not recognizing the partition’s file system?

No, you’re not. I just wanted to confirm what I saw first.

My next idea was to ensure it’s empty, and unmounted. Then removing the partition and recreating it. To make sure everything’s good. Then mounting it.

1 Like

Not sure what I did, but it works now, thanks!