How to show a SSD HD on Other Location

**satimis** · January 6th, 2022

Hi all,

On this computer I have other HDs;
a 1TB Nvme PCIe 3.0x4 SSD HD on this PC, running Ubuntu 20.04
a 4TB WD HD for data storage without OS running
Booting controlled via BIOS

On
-> Files -> Other Locations
It only shows the 4TB WD HD (pls refers to attached screenshot)
1TB SSD HD missing

Please advise how to show the 1TB SSD HD

Thanks

Regards

**Bashing-om** · January 6th, 2022

Hey satimis -

What shows terminal command:

Code:

sudo parted -l

If not seen here one will have to look at bios and hardwire connections.

-my bit to try and help-

**satimis** · January 6th, 2022

Originally Posted by Bashing-om

Hey satimis -

What shows terminal command:

Code:

sudo parted -l

If not seen here one will have to look at bios and hardwire connections.

Thanks for your advice.

On Terminal ran;
$ sudo parted -l > parted.txt

The output file is attached here

Regards

Edit
===
It is there

Code:

Model: INTEL SSDPEKNW010T8 (nvme)
Disk /dev/nvme0n1: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

**Bashing-om** · January 6th, 2022

welp --

Disk /dev/nvme0n1: 1024GB >> 2 538MB 1024GB 1024GB lvm

The drive is there and set up for LVM/

I have no experience here so the rest is up to others.

-A know it all I am not-

**Dennis N** · January 6th, 2022

Please advise how to show the 1TB SSD HD

Some devices in this "Other Locations" window are filtered out. Devices mounted through an entry in /etc/fstab will not appear here, but will appear in parted output. Access such devices through their mount point. I suggest you make bookmarks for quick access from the file manager side pane.

**satimis** · January 6th, 2022

Originally Posted by Dennis N

Some devices in this "Other Locations" window are filtered out. Devices mounted through an entry in /etc/fstab will not appear here, but will appear in parted output. Access such devices through their mount point. I suggest you make bookmarks for quick access from the file manager side pane.

Here is /etc/fstab

$ cat /etc/fstab

Code:

# /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>
# / was on /dev/sda2 during installation
UUID=f60e0b05-1944-402f-8029-81a9013711bc /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=7735-7864  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw

Regards

**Dennis N** · January 6th, 2022

It would help to post the output of:

Code:

lsblk -o name,fstype,mountpoint

to expose more details of the LVM structure on the NVMe device.

**satimis** · January 7th, 2022

Originally Posted by Dennis N

It would help to post the output of:

Code:

lsblk -o name,fstype,mountpoint

to expose more details of the LVM structure on the NVMe device.

$ lsblk -o name,fstype,mountpoint

Code:

NAME        FSTYPE      MOUNTPOINT
loop0       squashfs    /snap/bare/5
loop1       squashfs    /snap/gnome-3-34-1804/77
loop2       squashfs    /snap/gtk-common-themes/1515
loop3       squashfs    /snap/gnome-3-34-1804/72
loop4       squashfs    /snap/core18/2128
loop5       squashfs    /snap/core20/1270
loop6       squashfs    /snap/snap-store/558
loop7       squashfs    /snap/snapd/12704
loop8       squashfs    /snap/core18/2253
loop9       squashfs    /snap/gtk-common-themes/1519
loop10      squashfs    /snap/gnome-3-38-2004/87
loop11      squashfs    /snap/snap-store/547
loop12      squashfs    /snap/snapd/14295
sda                     
└─sda1      ext4        
sdb                     
├─sdb1      vfat        /boot/efi
└─sdb2      ext4        /
nvme0n1                 
├─nvme0n1p1 vfat        
└─nvme0n1p2 LVM2_member

$ ls -l /dev/disk/by-uuid

Code:

total 0
lrwxrwxrwx 1 root root 15 Jan  7 11:28 0E3A-4ABA -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 10 Jan  7 11:28 7735-7864 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Jan  7 11:28 786a6a67-06f5-428f-a24d-fe75cd0b08d5 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan  7 11:28 f60e0b05-1944-402f-8029-81a9013711bc -> ../../sdb2

Regards

**Dennis N** · January 7th, 2022

On the NVME drive, the LVM2 member is not directly mountable, so won't display in Files. You will need to make a volume group (VG) containing p2, and then a logical volume (LV) in that volume group which can then be formatted ext4. After that, the file manager will show the ext4 file system that was created in the "Other Locations".

To do these tasks, you need to understand LVM concepts and LVM commands, which requires some study on your part if you don't already know how.

Here is the same setup on this computer, but with two logical volumes added, each formatted ext4 and with an OS installed on it:

Code:

nvme0n1                           
├─nvme0n1p1                          vfat        
└─nvme0n1p2                          LVM2_member 
  ├─wdsn500-manjaro--nvme            ext4        
  └─wdsn500-ubuntu_1904              ext4

There are many tutorials and articles about LVM on the web, but here are two I used to learn about LVM several years ago:
Ubuntu LVM Guide
It's a bit old, but the commands haven't changed. Ignore any references to the GUI tool mentioned, as it's no longer available and you don't need it.
Also read and study this article:
LVM Demystified

**satimis** · January 7th, 2022

Originally Posted by Dennis N

On the NVME drive, the LVM2 member is not directly mountable, so won't display in Files. You will need to make a volume group (VG) containing p2, and then a logical volume (LV) in that volume group which can then be formatted ext4. After that, the file manager will show the ext4 file system that was created in the "Other Locations".

To do these tasks, you need to understand LVM concepts and LVM commands, which requires some study on your part if you don't already know how.

Here is the same setup on this computer, but with two logical volumes added, each formatted ext4 and with an OS installed on it:

Code:

nvme0n1                           
├─nvme0n1p1                          vfat        
└─nvme0n1p2                          LVM2_member 
  ├─wdsn500-manjaro--nvme            ext4        
  └─wdsn500-ubuntu_1904              ext4

There are many tutorials and articles about LVM on the web, but here are two I used to learn about LVM several years ago:
Ubuntu LVM Guide
It's a bit old, but the commands haven't changed. Ignore any references to the GUI tool mentioned, as it's no longer available and you don't need it.
Also read and study this article:
LVM Demystified

Thanks for your advice.

This is a newly added 500G SATA 6G/s SSD HD. I purchased this SSD for testing KVM/QEMU and Video Editing software, in particular Shotcut, running on bare-metal HD, in combination.

1st I selected Linuxmint 11.2 as host of KVM/QEMU. KVM/QEMU works without problem but unfortunately Shotcut unable to run on Linuxmint 11.2. On File Manager of Linuxmint 11.2, the 1TB NVMe PCIe SSD can be displayed. Files can be shared btw the 1TB SSD and 500G SSD.

Then I wiped out Linuxmint 11.2 and installed Debian 20.2. But I couldn't make my Dell 32" 4K display to work,

Again I wiped out Debien 20.2 and installed Ubuntu 20.04, coming to the present situation. Shotcut and Avidemux Video Editors works on the bare-metal SSD. I haven't tested KVM/QEMU yet.

I have a spare PC with following HD config:
HD-1 2TB SSD running Ubuntu 20.04
HD-2 2TB WD HD for data storage
HD-3 2TB WD HD for data storage
HD-4 500G SSD running Windows 10
HD-5 250G SSD running Ubuntu 20.04

It has the same situation. HD-1 is unable to be mounted automatically on HD-5 after starting Ubuntu 20.04, Files sharing btw HD-1 and HD-5 is unable to work.

On HD-5 of the spare PC Terminal
$ cat /etc/fstab

Code:

# /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>
# / was on /dev/sda5 during installation
UUID=2fc7a0c1-f447-46b1-ba7c-ebc7a7ec9bf2 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=5DFD-253C  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0

$ lsblk -o name,fstype,mountpoint
(please refer to attached mountpoint.txt file)

If the problem is unable to solve I'll leave it, at least I can test Video Editing softwares here, running on bare-metal HD

Lot of thanks for your advice.

Regards

Thread: How to show a SSD HD on Other Location

Thread Tools

Display

How to show a SSD HD on Other Location

Re: How to show a SSD HD on Other Location

Re: How to show a SSD HD on Other Location

Re: How to show a SSD HD on Other Location

Re: How to show a SSD HD on Other Location

Re: How to show a SSD HD on Other Location

Re: How to show a SSD HD on Other Location

Re: How to show a SSD HD on Other Location

Re: How to show a SSD HD on Other Location

Re: How to show a SSD HD on Other Location

Bookmarks

Bookmarks

Posting Permissions