Probe #f4cadd1885 of ASUSTek TUF Gaming B650-PLUS... Desktop Computer

Log: fdisk

Disk /dev/nvme2n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: Samsung SSD 970 EVO Plus 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: -- Device Start End Sectors Size Type /dev/nvme2n1p1 34 262177 262144 128M Microsoft reserved /dev/nvme2n1p2 264192 3611061961 3610797770 1.7T Microsoft basic data /dev/nvme2n1p3 3611062272 3612112895 1050624 513M EFI System /dev/nvme2n1p4 3612112896 3907028911 294916016 140.6G Linux filesystem Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: Samsung SSD 970 EVO Plus 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: -- Device Start End Sectors Size Type /dev/nvme0n1p1 2048 34815 32768 16M Microsoft reserved /dev/nvme0n1p2 34816 1058815 1024000 500M EFI System /dev/nvme0n1p3 1058816 3889188863 3888130048 1.8T Microsoft basic data /dev/nvme0n1p4 3889188864 3907026943 17838080 8.5G Windows recovery environment Disk /dev/nvme1n1: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: CT4000P3SSD8 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes


Hardware for Linux and BSD

GitHub