Okay, at least I was able to do some reporting. When I mount the SSD as it's whole partition e.g. nvme0n1, I get errors.
When I mount each of it's sub partitions, e.g. nvme0n1p1 it seems to work fine.
sudo fdisk -l
Code:
Disk /dev/nvme0n1: 476.96 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: THNSN5512GPUK NVMe TOSHIBA 512GB
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: 6A0A95FD-90DA-4D2A-B396-15B583BFA4AE
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1968127 1966080 960M EFI System
/dev/nvme0n1p2 1968128 212905983 210937856 100.6G Linux filesystem
/dev/nvme0n1p3 212905984 466812927 253906944 121.1G Linux swap
/dev/nvme0n1p4 466812928 1000214527 533401600 254.4G Linux filesystem
Disk /dev/sda: 5.47 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: WDC WD6004FZWX-0
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: 1106BD65-71F7-43EE-956C-0706C2192522
Device Start End Sectors Size Type
/dev/sda1 2048 11721043967 11721041920 5.5T Linux filesystem
Results from this
ubuntu@ubuntu:~$ sudo fsck -y /dev/nvme0n1
Code:
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-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>
Found a gpt partition table in /dev/nvme0n1
ubuntu@ubuntu:~$ sudo fsck -y /dev/nvme0n1p1
Code:
fsck from util-linux 2.34
fsck.fat 4.1 (2017-01-24)
/dev/nvme0n1p1: 22 files, 13875/245276 clusters
ubuntu@ubuntu:~$ sudo fsck -y /dev/nvme0n1p2
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
/dev/nvme0n1p2: clean, 56244/6594560 files, 1923900/26367232 blocks
ubuntu@ubuntu:~$ # note p3 is a swap partition
ubuntu@ubuntu:~$ sudo fsck -y /dev/nvme0n1p3
fsck from util-linux 2.34
ubuntu@ubuntu:~$ sudo fsck -y /dev/nvme0n1p4
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
/dev/nvme0n1p4: clean, 292379/16670720 files, 3617722/66675200 blocks
ubuntu@ubuntu:~$ sudo fsck -y /dev/sda
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-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/sda
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>
Found a gpt partition table in /dev/sda
ubuntu@ubuntu:~$ sudo fsck -y /dev/sda1
Code:
fsck from util-linux2.34
e2fsck 1.45.5 (07-Jan-2020)
/dev/sda1: clean,210380/183144448 files, 14390401/1465130240 blocks
ubuntu@ubuntu:~$ sudo mount -rw /dev/nvme0n1 /mnt/SSD
mount:/mnt/SSD: wrong fs type, bad option, bad superblock on /dev/nvme0n1,missing codepage or helper program, or other error.
ubuntu@ubuntu:~$sudo mount -rw /dev/sda /mnt/HDD
mount: /mnt/HDD: wrong fs type,bad option, bad superblock on /dev/sda, missing codepage or helperprogram, or other error.
All of these mounts seem to work tho:
Code:
ubuntu@ubuntu:~$ sudo mount -rw/dev/sda1 /mnt/HDD
ubuntu@ubuntu:~$ sudo mount -rw/dev/nvme0n1p1 /mnt/SSD/p1
ubuntu@ubuntu:~$ sudo mount -rw/dev/nvme0n1p2 /mnt/SSD/p2
ubuntu@ubuntu:~$ sudo mount -rw/dev/nvme0n1p4 /mnt/SSD/p4
ubuntu@ubuntu:~$sudo lsblk -e 7 -oname,type,fstype,size,FSAVAIL,FSUSE%,label,mountp oint
note that sdb is my thumb drive 16Gb flash
Code:
NAME TYPE FSTYPE SIZE FSAVAIL FSUSE% LABEL MOUNTPOINT
sda disk 5.5T
|_sda1 part ext4 5.5T 5.1T 0% /mnt/HDD
sdb disk 14.6G
|_sdb1 part vfat 14.6G 13.9G 5% JOHN K WO /mnt/flash
sr0 rom iso9660 2.6G 0 100% Ubuntu 20.04.1 LTS amd64 /cdrom
nvme0n1 disk 477G
|_nvme0n1p1 part vfat 960M 903.9M 6% /mnt/SSD/p1
|_nvme0n1p2 part ext4 100.6G 88.2G 5% /mnt/SSD/p2
|_nvme0n1p3 part swap 121.1G
|_nvme0n1p4 part ext4 254.4G 227.8G 4% /mnt/SSD/p4
So do I have bad superblocks, whatever those are?