I got a second drive for my new Protectli Vault and set up Proxmox with ZFS by doing a total reinstall. There were five drives on the ZFS setup page. I set three of the drives to ignore and just chose the two 4TB ones. The installation completed and came up.
On the disks page I have /dev/nvme0n1 (an nvme drive) and /dev/sda (an SSD). The fdisk output is show at the bottom. Is this all I should see? There are only two drives in the Vault.
Under the node, two disks are shown:
local (pve1) VZDump backup file, ISO image, Container template
local zfs (pve1) Disk image, Container
Both show 3.86TB with a very small amount used.
I didn't pay attention to what the other options were for three drives I set to ignore and I have been unable to find anywhere on the web that shows what they are. The reason I'm asking is that I got the following errors twice now in the last eight hours or so after set up so I wanted to be sure I set up ZFS correctly.
Jan 12 17:34:31 pve1 kernel: ata1.00: exception Emask 0x10 SAct 0x800 SErr 0x4050000 action 0xe frozen
Jan 12 17:34:32 pve1 kernel: ata1.00: irq_stat 0x00000040, connection status changed
Jan 12 17:34:32 pve1 kernel: ata1: SError: { PHYRdyChg CommWake DevExch }
Jan 12 17:34:32 pve1 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Jan 12 17:34:32 pve1 kernel: ata1.00: cmd 61/10:58:38:41:27/00:00:34:00:00/40 tag 11 ncq dma 8192 out res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Jan 12 17:34:32 pve1 kernel: ata1.00: status: { DRDY }
Jan 12 17:34:32 pve1 kernel: ata1: hard resetting link
Jan 12 17:34:32 pve1 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 12 17:34:32 pve1 kernel: ata1.00: supports DRM functions and may not be fully accessible
Jan 12 17:34:32 pve1 kernel: ata1.00: supports DRM functions and may not be fully accessible
Jan 12 17:34:32 pve1 kernel: ata1.00: configured for UDMA/133
Jan 12 17:34:32 pve1 kernel: ahci 0000:00:17.0: port does not support device sleep
Jan 12 17:34:32 pve1 kernel: ata1: EH complete
Jan 12 17:34:32 pve1 kernel: ata1.00: Enabling discard_zeroes_data
root@pve1:~# fdisk -l
Disk /dev/sda: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: Samsung SSD 870
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: 8C104D34-DB82-42FE-ABA3-7E3C2013C998
Device Start End Sectors Size Type
/dev/sda1 34 2047 2014 1007K BIOS boot
/dev/sda2 2048 2099199 2097152 1G EFI System
/dev/sda3 2099200 7813988352 7811889153 3.6T Solaris /usr & Apple ZFS
Disk /dev/mmcblk0: 14.56 GiB, 15634268160 bytes, 30535680 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
Disklabel type: gpt
Disk identifier: 672DE19B-10DD-42C5-BD3E-F01FE43E8DA3
Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 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/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 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/nvme0n1: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: KINGSTON SNV2S4000G
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: 43C67346-B5D4-4338-B216-E8029751D930
Device Start End Sectors Size Type
/dev/nvme0n1p1 34 2047 2014 1007K BIOS boot
/dev/nvme0n1p2 2048 2099199 2097152 1G EFI System
/dev/nvme0n1p3 2099200 7813988352 7811889153 3.6T Solaris /usr & Apple ZFS
On the disks page I have /dev/nvme0n1 (an nvme drive) and /dev/sda (an SSD). The fdisk output is show at the bottom. Is this all I should see? There are only two drives in the Vault.
Under the node, two disks are shown:
local (pve1) VZDump backup file, ISO image, Container template
local zfs (pve1) Disk image, Container
Both show 3.86TB with a very small amount used.
I didn't pay attention to what the other options were for three drives I set to ignore and I have been unable to find anywhere on the web that shows what they are. The reason I'm asking is that I got the following errors twice now in the last eight hours or so after set up so I wanted to be sure I set up ZFS correctly.
Jan 12 17:34:31 pve1 kernel: ata1.00: exception Emask 0x10 SAct 0x800 SErr 0x4050000 action 0xe frozen
Jan 12 17:34:32 pve1 kernel: ata1.00: irq_stat 0x00000040, connection status changed
Jan 12 17:34:32 pve1 kernel: ata1: SError: { PHYRdyChg CommWake DevExch }
Jan 12 17:34:32 pve1 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Jan 12 17:34:32 pve1 kernel: ata1.00: cmd 61/10:58:38:41:27/00:00:34:00:00/40 tag 11 ncq dma 8192 out res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Jan 12 17:34:32 pve1 kernel: ata1.00: status: { DRDY }
Jan 12 17:34:32 pve1 kernel: ata1: hard resetting link
Jan 12 17:34:32 pve1 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 12 17:34:32 pve1 kernel: ata1.00: supports DRM functions and may not be fully accessible
Jan 12 17:34:32 pve1 kernel: ata1.00: supports DRM functions and may not be fully accessible
Jan 12 17:34:32 pve1 kernel: ata1.00: configured for UDMA/133
Jan 12 17:34:32 pve1 kernel: ahci 0000:00:17.0: port does not support device sleep
Jan 12 17:34:32 pve1 kernel: ata1: EH complete
Jan 12 17:34:32 pve1 kernel: ata1.00: Enabling discard_zeroes_data
root@pve1:~# fdisk -l
Disk /dev/sda: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: Samsung SSD 870
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: 8C104D34-DB82-42FE-ABA3-7E3C2013C998
Device Start End Sectors Size Type
/dev/sda1 34 2047 2014 1007K BIOS boot
/dev/sda2 2048 2099199 2097152 1G EFI System
/dev/sda3 2099200 7813988352 7811889153 3.6T Solaris /usr & Apple ZFS
Disk /dev/mmcblk0: 14.56 GiB, 15634268160 bytes, 30535680 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
Disklabel type: gpt
Disk identifier: 672DE19B-10DD-42C5-BD3E-F01FE43E8DA3
Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 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/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 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/nvme0n1: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: KINGSTON SNV2S4000G
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: 43C67346-B5D4-4338-B216-E8029751D930
Device Start End Sectors Size Type
/dev/nvme0n1p1 34 2047 2014 1007K BIOS boot
/dev/nvme0n1p2 2048 2099199 2097152 1G EFI System
/dev/nvme0n1p3 2099200 7813988352 7811889153 3.6T Solaris /usr & Apple ZFS