由于我对 Linux 的经验很少，所以我决定尝试 Kubuntu 而不是“升级”到 Windows 10/11，而且很早就遇到了麻烦。
简而言之，我想用它作为我的主要电脑，用它来播放 Steam 游戏等等。
安装过程一切顺利，直到需要在辅助 NVMe 驱动器上创建新的 Steam 库文件夹。我尝试使用 Steam 创建文件夹，但出现错误，提示驱动器为只读。
我认为 Steam 肯定有问题，所以我自己通过 Kubuntu GUI 创建了文件夹。不，只读。请注意，这是在全新安装的全新驱动器上，我刚刚将其安装为 ext4，以实现与 Steam 的最大兼容性。Steam 允许我在主驱动器上安装东西，但它和我都无法通过 nvme0n1 上的 GUI 创建新文件夹。
我通过命令行终端和 GUI（通过 KDE 分区管理器）卸载、重新安装过，但感觉非常沮丧。以下是我发现在类似问题中经常被问到的一些命令的结果：
username@username-System-Product-Name:~$ sudo parted -l
Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/vgkubuntu-swap_1: 2051MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:
Number Start End Size File system Flags
1 0.00B 2051MB 2051MB linux-swap(v1)
Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/vgkubuntu-root: 998GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:
Number Start End Size File system Flags
1 0.00B 998GB 998GB ext4
Model: CT1000P3SSD8 (nvme)
Disk /dev/nvme0n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 538MB 537MB fat32 boot, esp
2 538MB 1000GB 1000GB lvm
Model: INTEL SSDPEKNW010T8 (nvme)
Disk /dev/nvme1n1: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
username@username-System-Product-Name:~$ sudo fsck /dev/nvme1n1
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
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/nvme1n1
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/nvme1n1
username@username-System-Product-Name:~$ sudo fdisk -l
Disk /dev/loop0: 61.96 MiB, 64970752 bytes, 126896 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: 4 KiB, 4096 bytes, 8 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: 63.23 MiB, 66301952 bytes, 129496 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: 163.29 MiB, 171225088 bytes, 334424 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: 238.43 MiB, 250015744 bytes, 488312 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: 400.8 MiB, 420265984 bytes, 820832 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/loop6: 346.33 MiB, 363151360 bytes, 709280 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/loop7: 91.69 MiB, 96141312 bytes, 187776 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/nvme1n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: INTEL SSDPEKNW010T8
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: D4E53ED1-F214-2B48-967F-0432400645C1
Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: CT1000P3SSD8
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: 0A634D48-6E20-4CF5-B5B6-C1F09A298087
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
/dev/nvme0n1p2 1050624 1953523711 1952473088 931G Linux LVM
Disk /dev/mapper/vgkubuntu-root: 929.1 GiB, 997611012096 bytes, 1948459008 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/mapper/vgkubuntu-swap_1: 1.91 GiB, 2051014656 bytes, 4005888 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/loop8: 49.62 MiB, 52031488 bytes, 101624 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
顺便说一下，我不知道那些大量的 /dev/loop# 是什么，但从粗略的网络搜索来看，它们似乎不太可能是罪魁祸首。
我也不明白为什么 Linux/Kubuntu 显然要以 /dev/mapper/vgkubuntu-root 的形式安装第三个虚拟驱动器，但我确信对于知道自己在做什么的人来说，这完全合乎逻辑，不像我。我一头扎进 Linux 中，甚至没有学习 /dev/ 和 /root/ 之间的区别，相信我，我计划在接下来的几个小时/几天内学习这些。
现在...如果您能帮助我在 /nvme1n1 上安装一个大型游戏，我将不胜感激。
编辑于 12/23/22 @ 1231 ET ：自阅读前两条评论以来采取的步骤：
Create a new partition table (type: gpt) on ‘/dev/nvme1n1’
Job: Create new partition table on device ‘/dev/nvme1n1’
Command: sfdisk --wipe=always /dev/nvme1n1
Create new partition table on device ‘/dev/nvme1n1’: Success
Create a new partition table (type: gpt) on ‘/dev/nvme1n1’: Success
Create a new partition (488.28 GiB, ext4) on ‘/dev/nvme1n1’
Job: Create new partition on device ‘/dev/nvme1n1’
Command: sfdisk --force --append /dev/nvme1n1
Command: sfdisk --list --output Device,UUID /dev/nvme1n1
Create new partition ‘/dev/nvme1n1p1’: Success
Job: Create file system ‘ext4’ on partition ‘/dev/nvme1n1p1’
Command: mkfs.ext4 -qF /dev/nvme1n1p1
Command: sfdisk --part-type /dev/nvme1n1 1 0FC63DAF-8483-4772-8E79-3D69D8477DE4
Create file system ‘ext4’ on partition ‘/dev/nvme1n1p1’: Success
Job: Set the file system label on partition ‘/dev/nvme1n1p1’ to "SteamLibrary"
Command: e2label /dev/nvme1n1p1 SteamLibrary
Set the file system label on partition ‘/dev/nvme1n1p1’ to "SteamLibrary": Success
Job: Check file system on partition ‘/dev/nvme1n1p1’
Command: e2fsck -f -y -v /dev/nvme1n1p1
Check file system on partition ‘/dev/nvme1n1p1’: Success
Create a new partition (488.28 GiB, ext4) on ‘/dev/nvme1n1’: Success
仍然无法在该分区中创建新文件夹。如果我右键单击“新建”，该选项将变灰，当我进入新分区的“属性”->“权限”->“高级权限”时，它有一个如下表：
| 类型 | 名称 | r | w | x | 有效|
| ---- | ---- | - | - | - | --------- |
| 所有者 | | X | X | X | rwx |
| 拥有组 | | X | | X | rx|
| 其他 | | X | | X | rx |