Unable to mount NVME (PineBook Pro)

[WallStreet]

I searched through the forums and was not able to get my problems fixed. I checked out the arch/manjaro forums.

I want to mount my nvme (nvme0n1) drive (adapter purchased through pine64) it is recognized in in the system but I am unable to save it or view it in the file manager. I purchased the nvme based on the Wiki with working nvme drives.

I am getting super block errors and it is refusing to mount. Does anyone have any suggestions or can help me walk through? I have been going at this for about 3 hours on and off.

$ lsblk

NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
nvme0n1      259:0    0  477G  0 disk
└─nvme0n1p1  259:1    0  477G  0 part


Sudo parted -l

odel: INTEL SSDPEKNW512G8 (nvme)
Disk /dev/nvme0n1: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
-------------------------------------------------------------------------------------------------------------------------------------------
fsck -r /dev/nvme0n1

$sudo fsck -r /dev/nvme0n1
fsck from util-linux 2.35.2
e2fsck 1.45.6 (20-Mar-2020)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/nvme0n1

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
or
    e2fsck -b 32768 <device>

/dev/nvme0n1 contains `DOS/MBR boot sector; partition 1 : ID=0x83, start-CHS (0x1,0,1), end-CHS (0x3c2,21,16), startsector 2048, 1000213168 sectors, extended partition table (last)' data
/dev/nvme0n1: status 8, rss 5136, real 0.127420, user 0.013870, sys 0.026418

Number  Start  End    Size  Type    File system  Flags
1      1049kB  512GB  512GB  primary

[Der Geist der Maschine]

Hello WallStreet,

I take back what I initially wrote. New try:

Can you make sure you have formatted the partition with ext4 filesystem.

[WallStreet]

Hello WallStreet,

I take back what I initially wrote. New try:

Can you make sure you have formatted the partition with ext4 filesystem.

Funny enough before I saw your comment I had just reformatted it (3rd time) and rebooted and now it appears. Sometimes computers hate me.

thanks for your reply!

[xmixahlx]

i have found that asking fstab to check all devices at boot keeps things working. i suspect that the nvme drive is not unmounting correctly at shutdown and reboot.

[Phillip Bell]

Just an FYI for folks that have installed a new NVME drive, but don't know what to do with it.

It needs to be partitioned, formatted and mounted for you to use it.  If you're not used to installing drives on computers, this may not be obvious.

Here is a decent tutorial of how to do that:  https://www.digitalocean.com/community/t...s-in-linux

And here are the commands I used (these are mine only, and may be different for you):

1. Make sure it's recognized by the computer: 

#>   lsblk

(my output):   nvme0n1      259:0    0 931.5G  0 disk

2. Select your partitioning standard (extremely likely you should use GPT):

#> sudo parted /dev/nvme0n1 mklabel gpt

3.  Create the partition (ext4 is the most likely format, and you may want to just use a single partition).  Note that the partition has a slightly different name (nvme0n1p1) than the mount point (nvme0n1):

#> sudo parted -a opt /dev/nvme0n1p1 mkpart primary ext4 0% 100%

4. Create a filesystem: 

#> sudo mkfs.ext4 -L  datapartition  /dev/nvme0n1p1

5. Mount the filesystem:

#> sudo mkdir -p /mnt/data
#> sudo mount -o defaults  /dev/nvme0n1p1  /mnt/data

6. Add mount to fstab, so that it happens on boot:

#> sudo nano /etc/fstab

Code:

LABEL=datapartition /mnt/data ext4 defaults 0 2