Results 1 to 9 of 9

Thread: Newly formatted nvme drive shows wrong size, wrong used, wrong unused

  1. #1
    Join Date
    Jul 2015
    Location
    Essex, UK
    Beans
    871
    Distro
    Xubuntu

    Newly formatted nvme drive shows wrong size, wrong used, wrong unused

    I had an nvme drive formatted as NTFS on a dual boot 24.04 system which I thought was causing file system errors although even using a live USB showed it clean.

    I decided to change the format to ext4 as ubuntu was the most used system. I copied al of the data on the drive to another nvme drive also formatted NTFS. Using Gparted I deleted the problem drive, remade and reformatted it to ext4.

    Now in Gparted that drive shows:

    Partition /dev/nvme2n1p1

    Filesystem ext4

    Size 1.82 TiB

    Used 1.94 GiB

    Unused 1.82 TiB

    Examining the system:

    Code:
    makem@makem-22:~$ lsblk -e 7 -o name,fstype,size,fsused,label,UUID,mountpoint
    NAME      FSTYPE   SIZE FSUSED LABEL       UUID                                 MOUNTPOINT
    nvme1n1          476.9G                                                         
    ├─nvme1n1p1
    │         vfat     260M  33.4M SYSTEM      40DB-4F92                            /boot/efi
    ├─nvme1n1p2
    │                  128M                                                         
    ├─nvme1n1p3
    │         ntfs     500M        Recovery    F026DBCE26DB9446                     
    ├─nvme1n1p4
    │         ntfs   181.9G 116.5G Windows     CE6CDDE46CDDC77D                     /media/mak
    ├─nvme1n1p5
    │         ext4    40.2G  23.8G             3388ecd3-9ab1-44d8-90cf-88b70af20f14 /
    ├─nvme1n1p6
    │         ext4    83.8G  63.6G             6e3e25f1-7705-4a68-934a-e5b1676c58b2 /home
    ├─nvme1n1p7
    │         ext4   166.5G  41.1G games-steam 8d58ff3d-fa93-4b35-a343-34883602c151 /media/mak
    └─nvme1n1p8
              swap     3.7G                    4ede3f10-e290-4fe4-970a-27537f3a0499 [SWAP]
    nvme0n1            1.8T                                                         
    ├─nvme0n1p1
    │                   16M                                                         
    └─nvme0n1p2
              ntfs     1.8T   1.2T games       E07CD0EB7CD0BD8A                     /media/gam
    nvme2n1            1.8T                                                         
    └─nvme2n1p1
              ext4     1.8T                    e01623f7-1a20-487d-b800-ddbf49597bf1 
    makem@makem-22:~$
    Code:
    makem@makem-22:~$ sudo fdisk -l | sed -e '/Disk \/dev\/loop/,+5d'
    Disk /dev/nvme1n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
    Disk model: INTEL SSDPEKNW512G8                     
    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: 176110A6-54C5-4712-B23C-642A1CA0CB04
    
    
    Device             Start        End   Sectors   Size Type
    /dev/nvme1n1p1      2048     534527    532480   260M EFI System
    /dev/nvme1n1p2    534528     796671    262144   128M Microsoft reserved
    /dev/nvme1n1p3    796672    1820671   1024000   500M Windows recovery environment
    /dev/nvme1n1p4   1820672  383305727 381485056 181.9G Microsoft basic data
    /dev/nvme1n1p5 391118848  475361279  84242432  40.2G Linux filesystem
    /dev/nvme1n1p6 475361280  651143167 175781888  83.8G Linux filesystem
    /dev/nvme1n1p7 651143168 1000214527 349071360 166.5G Linux filesystem
    /dev/nvme1n1p8 383305728  391118847   7813120   3.7G Linux swap
    
    
    Partition table entries are not in disk order.
    
    
    
    
    Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
    Disk model: WD_BLACK SN770 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: 177AF546-2E8D-4D33-AFC3-36FD08C7F64B
    
    
    Device         Start        End    Sectors  Size Type
    /dev/nvme0n1p1    34      32767      32734   16M Microsoft reserved
    /dev/nvme0n1p2 32768 3907026943 3906994176  1.8T Microsoft basic data
    
    
    
    
    Disk /dev/nvme2n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
    Disk model: CT2000P3PSSD8                           
    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: dos
    Disk identifier: 0x8472d22b
    
    
    Device         Boot Start        End    Sectors  Size Id Type
    /dev/nvme2n1p1       2048 3907028991 3907026944  1.8T 83 Linux
    
    
    
    
    makem@makem-22:~$
    The 1.94 GiB used is obviously wrong and I would like to correct it but don't know how. I do not want to replace the data if the drive is not correct.

    Then I decided to mount on /media where all my other stuff is mounted. But I must have got the mount command wrong because all my 'stuff' show above has gone and I know not where!

    I thought I was mounting it to /media where the other 'stuff' is.

    Can anyone se where my stuff might be?

  2. #2
    Join Date
    Jul 2015
    Location
    Essex, UK
    Beans
    871
    Distro
    Xubuntu

    Re: Newly formatted nvme drive shows wrong size, wrong used, wrong unused

    Addition to above post:

    Code:
    makem@makem-22:~$ findmnt
    TARGET                     SOURCE FSTYPE OPTIONS
    /                          /dev/nvme1n1p5
                                      ext4   rw,relatime,errors=remount-ro
    ├─/sys                     sysfs  sysfs  rw,nosuid,nodev,noexec,relatime
    │ ├─/sys/kernel/security   securityfs
    │ │                               securi rw,nosuid,nodev,noexec,relatime
    │ ├─/sys/fs/cgroup         cgroup2
    │ │                               cgroup rw,nosuid,nodev,noexec,relatime
    │ ├─/sys/fs/pstore         pstore pstore rw,nosuid,nodev,noexec,relatime
    │ ├─/sys/firmware/efi/efivars
    │ │                        efivarfs
    │ │                               efivar rw,nosuid,nodev,noexec,relatime
    │ ├─/sys/fs/bpf            bpf    bpf    rw,nosuid,nodev,noexec,relatime,mode=700
    │ ├─/sys/kernel/debug      debugfs
    │ │                               debugf rw,nosuid,nodev,noexec,relatime
    │ ├─/sys/kernel/tracing    tracefs
    │ │                               tracef rw,nosuid,nodev,noexec,relatime
    │ ├─/sys/fs/fuse/connections
    │ │                        fusectl
    │ │                               fusect rw,nosuid,nodev,noexec,relatime
    │ └─/sys/kernel/config     configfs
    │                                 config rw,nosuid,nodev,noexec,relatime
    ├─/proc                    proc   proc   rw,nosuid,nodev,noexec,relatime
    │ └─/proc/sys/fs/binfmt_misc
    │                          systemd-1
    │                                 autofs rw,relatime,fd=32,pgrp=1,timeout=0,minproto=5,max
    │   └─/proc/sys/fs/binfmt_misc
    │                          binfmt_misc
    │                                 binfmt rw,nosuid,nodev,noexec,relatime
    ├─/dev                     udev   devtmp rw,nosuid,relatime,size=8022724k,nr_inodes=200568
    │ ├─/dev/pts               devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode
    │ ├─/dev/shm               tmpfs  tmpfs  rw,nosuid,nodev,inode64
    │ ├─/dev/mqueue            mqueue mqueue rw,nosuid,nodev,noexec,relatime
    │ ├─/dev/hugepages         hugetlbfs
    │ │                               hugetl rw,nosuid,nodev,relatime,pagesize=2M
    │ └─/dev/binderfs          binder binder rw,relatime,max=1048576
    ├─/run                     tmpfs  tmpfs  rw,nosuid,nodev,noexec,relatime,size=1620568k,mod
    │ ├─/run/lock              tmpfs  tmpfs  rw,nosuid,nodev,noexec,relatime,size=5120k,inode6
    │ ├─/run/qemu              tmpfs  tmpfs  rw,nosuid,nodev,relatime,mode=755,inode64
    │ ├─/run/user/1000         tmpfs  tmpfs  rw,nosuid,nodev,relatime,size=1620564k,nr_inodes=
    │ │ ├─/run/user/1000/doc   portal fuse.p rw,nosuid,nodev,relatime,user_id=1000,group_id=10
    │ │ └─/run/user/1000/gvfs  gvfsd-fuse
    │ │                               fuse.g rw,nosuid,nodev,relatime,user_id=1000,group_id=10
    │ └─/run/rpc_pipefs        sunrpc rpc_pi rw,relatime
    ├─/snap/bare/5             /dev/loop0
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/bitwarden/119      /dev/loop1
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/core/16928         /dev/loop3
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/bitwarden/120      /dev/loop2
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/core/17200         /dev/loop4
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/core18/2829        /dev/loop5
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/core18/2846        /dev/loop6
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/core20/2318        /dev/loop7
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/core20/2379        /dev/loop8
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/core22/1621        /dev/loop9
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/core22/1612        /dev/loop10
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/linux-steam-integration/12
    │                          /dev/loop24
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/snap-store/1113    /dev/loop27
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/snap-store/1216    /dev/loop28
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/nextcloud-desktop-client/214
    │                          /dev/loop26
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/telegram-desktop/6216
    │                          /dev/loop35
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/snapd/21759        /dev/loop30
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/snapd/21465        /dev/loop29
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/gtk-common-themes/1535
    │                          /dev/loop23
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/nextcloud-desktop-client/208
    │                          /dev/loop25
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/gnome-42-2204/172  /dev/loop21
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/steam/191          /dev/loop32
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/gnome-42-2204/176  /dev/loop22
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/telegram-desktop/6205
    │                          /dev/loop34
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/steam/200          /dev/loop33
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/ubpm/3             /dev/loop38
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/thunderbird/526    /dev/loop36
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/ubpm/2             /dev/loop37
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/var/snap/firefox/common/host-hunspell
    │                          /dev/nvme1n1p5[/usr/share/hunspell]
    │                                 ext4   ro,noexec,noatime,errors=remount-ro
    ├─/snap/core24/423         /dev/loop11
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/solus-runtime-gaming/12
    │                          /dev/loop31
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/thunderbird/517    /dev/loop39
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/whatsdesk/28       /dev/loop40
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/boot/efi                /dev/nvme1n1p1
    │                                 vfat   rw,relatime,fmask=0077,dmask=0077,codepage=437,io
    ├─/home                    /dev/nvme1n1p6
    │                                 ext4   rw,relatime
    ├─/media/games             /dev/nvme0n1p2
    │                                 fusebl rw,relatime,user_id=0,group_id=0,allow_other,blks
    ├─/media/makem/Windows     /dev/nvme1n1p4
    │                                 fusebl rw,relatime,user_id=0,group_id=0,allow_other,blks
    ├─/media/makem/games-steam /dev/nvme1n1p7
    │                                 ext4   rw,relatime
    ├─/media                   /dev/nvme2n1p1
    │                                 ext4   rw,relatime
    ├─/snap/core24/490         /dev/loop12
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/firefox/4955       /dev/loop14
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/firefox/5014       /dev/loop13
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/gaming-graphics-core22/166
    │                          /dev/loop15
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/gaming-graphics-core22/184
    │                          /dev/loop16
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/gnome-3-28-1804/194
    │                          /dev/loop17
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/gnome-3-38-2004/140
    │                          /dev/loop18
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/gnome-3-28-1804/198
    │                          /dev/loop19
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    ├─/snap/gnome-3-38-2004/143
    │                          /dev/loop20
    │                                 squash ro,nodev,relatime,errors=continue,threads=single
    └─/var/lib/lxcfs           lxcfs  fuse.l rw,nosuid,nodev,relatime,user_id=0,group_id=0,all
    makem@makem-22:~$

  3. #3
    Join Date
    Jun 2014
    Beans
    7,890

    Re: Newly formatted nvme drive shows wrong size, wrong used, wrong unused

    I copied al of the data on the drive to another nvme drive also formatted NTFS. Using Gparted I deleted the problem drive, remade and reformatted it to ext4.
    How much data did you copy to the problem drive after you formatted it, you say it should be more than 1.94GB? How did you copy it? If you create a mount point then mount with the commands below, do you see any data/files when you do ls -l?

    Code:
    sudo mkdir /mnt/nvme2
    sudo mount  /dev/nvme2n1p1 /mnt/nvme2
    ls -l /mnt/nvme2
    You could also run du -h /mnt/nvme2 to show the size of files/directories on that mount point/partition.

  4. #4
    Join Date
    Jul 2015
    Location
    Essex, UK
    Beans
    871
    Distro
    Xubuntu

    Re: Newly formatted nvme drive shows wrong size, wrong used, wrong unused

    Quote Originally Posted by yancek View Post
    How much data did you copy to the problem drive after you formatted it, you say it should be more than 1.94GB? How did you copy it? If you create a mount point then mount with the commands below, do you see any data/files when you do ls -l?

    Code:
    sudo mkdir /mnt/nvme2
    sudo mount  /dev/nvme2n1p1 /mnt/nvme2
    ls -l /mnt/nvme2
    You could also run du -h /mnt/nvme2 to show the size of files/directories on that mount point/partition.
    The data I copied was a copy I had elsewhere and I unmounted and reformatted the drive and it was at that point when I went to re-mount it I got it wrong and I can't remember exactly what I did.

    None of the mount points /media exist any more except for /home/makem which I have not yet come out of. All mount points such as /media/makem/Windows give an error, no such file or directory when accessed in thunar.

    It is as if the mount points of the following drives have been moved elsewhere.

    Code:
    makem@makem-22:~$ sudo su
    [sudo] password for makem: 
    root@makem-22:/home/makem# cd ..
    root@makem-22:/home# cd ..
    root@makem-22:/# cd /home
    root@makem-22:/home# ls -lh
    total 20K
    drwx------  2 root  root   16K Nov 10  2022 lost+found
    drwxr-x--- 39 makem makem 4.0K Oct  9 16:20 makem
    root@makem-22:/home# cd ..
    root@makem-22:/# cd /media/games
    bash: cd: /media/games: No such file or directory
    root@makem-22:/# cd /media/makem/Windows
    bash: cd: /media/makem/Windows: No such file or directory
    root@makem-22:/# cd /media/makem/games-steam
    bash: cd: /media/makem/games-steam: No such file or directory
    root@makem-22:/# cd /media
    root@makem-22:/media# ls -lh
    total 20K
    drwx------  2 root root  16K Oct  9 19:02 lost+found
    drwxr-x---+ 2 root root 4.0K Oct  9 23:24 makem
    root@makem-22:/media# 
    root@makem-22:/media# cd ..
    root@makem-22:/#
    Last edited by makem2; October 10th, 2024 at 12:25 AM.

  5. #5
    Join Date
    Jul 2015
    Location
    Essex, UK
    Beans
    871
    Distro
    Xubuntu

    Re: Newly formatted nvme drive shows wrong size, wrong used, wrong unused

    Code:
    root@makem-22:/# df -h
    Filesystem      Size  Used Avail Use% Mounted on
    tmpfs           1.6G  2.4M  1.6G   1% /run
    /dev/nvme1n1p5   40G   25G   14G  66% /
    tmpfs           7.8G  163M  7.6G   3% /dev/shm
    /dev/nvme1n1p6   82G   64G   14G  83% /home
    tmpfs           1.6G  5.2M  1.6G   1% /run/user/1000
    /dev/nvme2n1p1  1.8T   32K  1.7T   1% /media
    root@makem-22:/#
    Code:
    makem@makem-22:~$ mount
    sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
    proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
    udev on /dev type devtmpfs (rw,nosuid,relatime,size=8022724k,nr_inodes=2005681,mode=755,inode64)
    devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
    tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1620568k,mode=755,inode64)
    /dev/nvme1n1p5 on / type ext4 (rw,relatime,errors=remount-ro)
    tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
    cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime)
    /dev/nvme1n1p6 on /home type ext4 (rw,relatime)
    /dev/nvme0n1p2 on /media/games type fuseblk (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
    /dev/nvme1n1p4 on /media/makem/Windows type fuseblk (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
    /dev/nvme1n1p7 on /media/makem/games-steam type ext4 (rw,relatime)
    sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
    tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1620564k,nr_inodes=405141,mode=700,uid=1000,gid=1000,inode64)
    /dev/nvme2n1p1 on /media type ext4 (rw,relatime)
    makem@makem-22:~$
    Last edited by makem2; October 10th, 2024 at 12:14 AM.

  6. #6
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: Newly formatted nvme drive shows wrong size, wrong used, wrong unused

    Before anything else change this on drive you redid togpt, nvme2n1:
    Disklabel type: dos
    Converting to or from GPT - must have good backups.
    http://www.rodsbooks.com/gdisk/mbr2gpt.html

    The only place for MBR(msdos) is for old systems with Windows installs in BIOS boot mode.
    Windows requires dos fro BIOS boot, but requires gpt for UEFI.
    Ubuntu does not care, but should have gpt for UEFI, all data drives & must have gpt for drives over 2TiB.
    Last edited by oldfred; October 10th, 2024 at 01:43 AM.
    UEFI boot install & repair info - Regularly Updated :
    https://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  7. #7
    Join Date
    Jul 2015
    Location
    Essex, UK
    Beans
    871
    Distro
    Xubuntu

    Re: Newly formatted nvme drive shows wrong size, wrong used, wrong unused

    Quote Originally Posted by oldfred View Post
    Before anything else change this on drive you redid togpt, nvme2n1:


    Converting to or from GPT - must have good backups.
    http://www.rodsbooks.com/gdisk/mbr2gpt.html

    The only place for MBR(msdos) is for old systems with Windows installs in BIOS boot mode.
    Windows requires dos fro BIOS boot, but requires gpt for UEFI.
    Ubuntu does not care, but should have gpt for UEFI, all data drives & must have gpt for drives over 2TiB.
    Thank you but I am in such a mess now I am going to have to reinstall both OS.

  8. #8
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: Newly formatted nvme drive shows wrong size, wrong used, wrong unused

    If installer sees DOS, MBR(msdos), with Windows it will try to install in BIOS mode. If Ubuntu installs in either UEFI or BIOS mode to MBR drive, you lose the advantages of gpt. Msdos goes back to the 1980's and has required many fixes to allow it to work with newer systems. But it cannot fix drive size limit so all drives over 2TB must be gpt.

    How you boot install media UEFI or BIOS is then how it installs.
    With multiple drives often better to disconnect other drives than the one you are installing into Often new systems do not require you to physically disconnect but have setting in UEFI to disable a drive.
    UEFI boot install & repair info - Regularly Updated :
    https://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  9. #9
    Join Date
    Mar 2010
    Location
    Been there, meh.
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Newly formatted nvme drive shows wrong size, wrong used, wrong unused

    Looks to me like you are trying to mount onto
    Code:
    Filesystem      Size  Used Avail Use% Mounted on
    /dev/nvme2n1p1  1.8T   32K  1.7T   1% /media
    /media and not a subdirectory of /media. When you mount storage on /media, it hides all previously created storage and mounts below that point.

    The fix is to mount to different empty directories under /media/ ... so go and create all the empty directories where you want to mount your different file systems (hopefully all data file systems), then mount each below. In general, doing this for NVMe is handled in the /etc/fstab file, so if you'll post the contents of that, we can tell you what is wrong.

    In post #1, the mount locations are cut off from the post. Use a wider terminal when you copy/paste that data into these forums. Also, if you add a label to nvme2n1p1, then you'll be able to use that LABEL to mount the storage where you like more easily than using the UUID method (yuck).

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •