Kubuntu cannot access 256GB Hard Disk via enclosure

snowmagician · 07-05-2021, 07:40 PM

https://kin-phinf.pstatic.net/202107...705_200110.jpg

https://kin-phinf.pstatic.net/202107...705_195828.jpg

result of hostnamectl && sudo lsusb

Code:

   Static hostname: snow-K53E
         Icon name: computer-laptop
           Chassis: laptop
        Machine ID: da1c596b36664feeadb767ea2e6cba4e
           Boot ID: 0e5714fb15944b918e30265d91439bc2
  Operating System: Ubuntu 20.04.2 LTS
            Kernel: Linux 5.4.0-77-generic
      Architecture: x86-64
[sudo] password for snow: 
Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 13d3:5710 IMC Networks UVC VGA Webcam
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

frankbell · 07-05-2021, 08:49 PM

Let me make sure I understand: This is a USB drive placed inside an enclosure that is in turn connected to the computer via a USB port?

snowmagician · 07-05-2021, 08:56 PM

Quote:

Originally Posted by frankbell

Let me make sure I understand: This is a USB drive placed inside an enclosure that is in turn connected to the computer via a USB port?

That is an NVMe drive, 256GB, which came with my laptop. It looked like this when I pulled it out of my laptop

https://i.ebayimg.com/images/g/AZcAA...k8j/s-l300.jpg

and I replaced it with Samsung 512GB NVMe because 256 was too small for me to do the development and online classes

By the way the result of the sudo lsusb looks exactly the same even after I disconnect it from my laptop

frankbell · 07-05-2021, 09:25 PM

I have no experience with NVMe drives.

Does it show up when you connect it and run this command:

Code:

fdisk -l

This article leads me to think that your kernel version may be relevant to this issue. What version are you running?

lovemeslk · 07-05-2021, 09:54 PM

Quote:

sudo blkid

It will display it.
sudo not needed for users in kubuntu. ?

Quote:

Then use gparted to partition it and format.

snowmagician · 07-06-2021, 01:09 AM

Displaying the results

PHP Code:


			
[B]snowmagician@snowinspi:~$ sudo fdisk -l[/B]

[sudo] password for snowmagician: 

Disk /dev/loop0: 61.72 MiB, 64720896 bytes, 126408 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





Disk /dev/loop1: 61.73 MiB, 64729088 bytes, 126424 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





Disk /dev/loop2: 16.64 MiB, 17444864 bytes, 34072 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





Disk /dev/loop3: 9.35 MiB, 9801728 bytes, 19144 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





Disk /dev/loop4: 32.28 MiB, 33845248 bytes, 66104 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





Disk /dev/loop5: 32.29 MiB, 33853440 bytes, 66120 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





Disk /dev/nvme0n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors

Disk model: Samsung SSD 980 500GB                   

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 16384 bytes / 131072 bytes

Disklabel type: gpt

Disk identifier: 07E81854-C7B3-49DD-B78B-316749C2AB3D



Device             Start       End   Sectors   Size Type

/dev/nvme0n1p1      2048    206847    204800   100M EFI System

/dev/nvme0n1p2    206848    239615     32768    16M Microsoft reserved

/dev/nvme0n1p3    239616 409561087 409321472 195.2G Microsoft basic data

/dev/nvme0n1p4 409561088 410583039   1021952   499M Windows recovery environment

/dev/nvme0n1p5 410583040 788070399 377487360   180G Microsoft basic data

/dev/nvme0n1p6 788070400 976771071 188700672    90G Windows recovery environment

and the next command

PHP Code:


			
snowmagician@snowinspi:~$ sudo blkid

[sudo] password for snowmagician: 

/dev/nvme0n1p6: UUID="8c160205-50c7-4e60-bf0c-8965c507c045" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="bf7ac54f-46bb-4b95-a06a-9b73178fc9fb"

/dev/loop0: TYPE="squashfs"

/dev/loop1: TYPE="squashfs"

/dev/loop2: TYPE="squashfs"

/dev/loop3: TYPE="squashfs"

/dev/loop4: TYPE="squashfs"

/dev/loop5: TYPE="squashfs"

/dev/nvme0n1p1: UUID="7CF3-CF66" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EF" PARTUUID="8ea5b9ef-538b-4664-bb9d-2bcc46387a81"

/dev/nvme0n1p2: PARTLABEL="Mi" PARTUUID="30e5a69f-3822-4ed3-81a6-08839fdda6e6"

/dev/nvme0n1p3: BLOCK_SIZE="512" UUID="C89E082D9E08169A" TYPE="ntfs" PARTUUID="24f87597-57a2-44bf-85c8-d070496d3ee8"

/dev/nvme0n1p4: BLOCK_SIZE="512" UUID="96C40672C4065541" TYPE="ntfs" PARTUUID="21957908-72da-48cc-bae9-0dbc9ddaa2fd"

/dev/nvme0n1p5: BLOCK_SIZE="512" UUID="01D72B2372192820" TYPE="ntfs" PARTUUID="326b7076-066b-5b8e-7980-72fbf53426b4"

snowmagician@snowinspi:~$

lovemeslk · 07-06-2021, 03:16 AM

Already partitioned and formatted. Next question is. How do I mount a a ntfs partition.
Then the next question may lead to. I can access it but unable to change data.
https://linuxconfig.org/how-to-mount...d-write-access

computersavvy · 07-07-2021, 09:40 PM

That output is showing ONE nvme0n1 device at 500GB. and is also showing NO linux partitions.
I think you are not seeing the 250 GB device.

Is the enclosure you put the drive into rated for an nvme M.2 drive or is it only rated for a sata M.2 drive. If not rated for nvme then it will not work.

snowmagician · 07-08-2021, 06:19 PM

Quote:

Originally Posted by computersavvy

That output is showing ONE nvme0n1 device at 500GB. and is also showing NO linux partitions.
I think you are not seeing the 250 GB device.

Is the enclosure you put the drive into rated for an nvme M.2 drive or is it only rated for a sata M.2 drive. If not rated for nvme then it will not work.

Here is the photo of the 256GB

https://kin-phinf.pstatic.net/202107.../fortheweb.jpg

I tried to access the 256GB with Kubuntu, Win 10, and neither recognizes the 256GB. I also tried switching the cable with a different cable.

This is the enclosure. It is impossible for a SATA drive to be placed in there, physically

https://www.walmart.com/ip/Zewfffr-L...sure/776669252

computersavvy · 07-08-2021, 07:04 PM

No, it is not impossible to put a sata drive in an M.2 enclosure. The M.2 format is used for both sata and nvme hardware so it is critical that you verify that the enclosure you have has the interface to support nvme and not sata if you expect an M.2 nvme drive to be supported.

With that said, the referenced enclosure is certainly touted to be for nvme and uses USB-C connection so as long as you have the proper USB connection it certainly should work. The fact that neither windows nor linux can see it does, however, imply that either the enclosure or the cable are not working properly. The drive itself should not be an issue, unless it is not cleanly mounted to the connector in the enclosure.

You have already tried a different cable, so the only other thing you can really try is to remove the drive from the enclosure then reinstall it to make certain it is properly connected. While it is out try cleaning the contacts on the drive. You said this had been in your laptop for a while so it is possible there may be some oxidation on the contacts that could interfere when placed in a different connector..