F5F Stay Refreshed Software Operating Systems I can help with Proxmox setup and troubleshooting. What specific issue are you facing?

I can help with Proxmox setup and troubleshooting. What specific issue are you facing?

I can help with Proxmox setup and troubleshooting. What specific issue are you facing?

Pages (2): 1 2 Next
C
CookiesDuck
Junior Member
Find
39
11-21-2016, 05:31 PM
#1
Hello, I hope you found the right spot to share this. Today I installed Proxmox multiple times. Initially, RAID wasn’t enabled. I’m using a smaller SSD for Proxmox—1 NVMe SSD and two 2TB HDDs—that I plan to run in RAID 1. The issue is that Proxmox appears to be consuming all available storage, leaving nothing for ZFS or directories. During installation, it was set to the smaller SSD. Can someone assist me? I’m really confused. I’ve also tried reformatting the drives Proxmox shouldn’t use, but that caused the machine to fail to start.
Reply
Reply
C
CookiesDuck
11-21-2016, 05:31 PM #1

Hello, I hope you found the right spot to share this. Today I installed Proxmox multiple times. Initially, RAID wasn’t enabled. I’m using a smaller SSD for Proxmox—1 NVMe SSD and two 2TB HDDs—that I plan to run in RAID 1. The issue is that Proxmox appears to be consuming all available storage, leaving nothing for ZFS or directories. During installation, it was set to the smaller SSD. Can someone assist me? I’m really confused. I’ve also tried reformatting the drives Proxmox shouldn’t use, but that caused the machine to fail to start.

Reply
Reply
Z
Zozo09
Junior Member
Find
3
11-23-2016, 06:17 PM
#2
A simple solution is to disconnect unused drives. Would you like me to display a screenshot of the installer? It seems it will use all available drives by default, so you’ll need to configure it. Can you view the current drive configuration, perhaps using a command like zpool list?
Reply
Reply
Z
Zozo09
11-23-2016, 06:17 PM #2

A simple solution is to disconnect unused drives. Would you like me to display a screenshot of the installer? It seems it will use all available drives by default, so you’ll need to configure it. Can you view the current drive configuration, perhaps using a command like zpool list?

Reply
Reply
N
NadFlam
Junior Member
Find
12
11-23-2016, 06:22 PM
#3
Explain clearly and concisely. Provide the answer without extra words. Include relevant details only.
Reply
Reply
N
NadFlam
11-23-2016, 06:22 PM #3

Explain clearly and concisely. Provide the answer without extra words. Include relevant details only.

Reply
Reply
A
AnnaDonuts
Junior Member
Find
9
11-23-2016, 08:47 PM
#4
With the installer, you pick a specific disk. I wasn’t sure it would cover all places. The issue seems tied to that choice—I plan to change it tomorrow, which could mean removing an NVMe SSD in a difficult spot.
Reply
Reply
A
AnnaDonuts
11-23-2016, 08:47 PM #4

With the installer, you pick a specific disk. I wasn’t sure it would cover all places. The issue seems tied to that choice—I plan to change it tomorrow, which could mean removing an NVMe SSD in a difficult spot.

Reply
Reply
F
Femscout
Junior Member
Find
20
11-29-2016, 07:33 PM
#5
No, the disks weren't partitioned. I might try ZFS across all drives instead. How does lsblk display the current partitions?
Reply
Reply
F
Femscout
11-29-2016, 07:33 PM #5

No, the disks weren't partitioned. I might try ZFS across all drives instead. How does lsblk display the current partitions?

Reply
Reply
X
XepToX
Junior Member
Find
40
12-01-2016, 04:21 PM
#6
root@pve:~# fdisk -l Disk /dev/nvme0n1: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 980 PRO 500GB
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: D917B651-3101-43DF-87AF-067D01FE3B79
Device Start End Sectors Size Type /dev/nvme0n1p1 2048 976773134 976771087 465.8G
Linux filesystem
Disk /dev/sdc: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Disk model: OCZ-VERTEX4
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: BAA7BB00-711A-4BDE-9B8E-E24E323A7F86
Device Start End Sectors Size Type /dev/sdc1 34 2047 2014 1007K
BIOS boot
Disk /dev/sdc2 2048 1050623 1048576 512M
EFI System
Disk /dev/sdc3 1050624 250069646 249019023 118.8G
Linux LVM
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000DM010-2EP1
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: 0x158a76ba
Device Boot Start End Sectors Size Id Type /dev/sda1 2048 1953525167 1953523120 931.5G
Linux
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000DM010-2EP1
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: dos
Disk identifier: 0xecae4de0
Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 1953525167 1953523120 931.5G
Linux
Disk /dev/mapper/pve-swap: 8 GiB, 8589934592 bytes, 16777216 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
Reply
Reply
X
XepToX
12-01-2016, 04:21 PM #6

root@pve:~# fdisk -l Disk /dev/nvme0n1: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 980 PRO 500GB
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: D917B651-3101-43DF-87AF-067D01FE3B79
Device Start End Sectors Size Type /dev/nvme0n1p1 2048 976773134 976771087 465.8G
Linux filesystem
Disk /dev/sdc: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Disk model: OCZ-VERTEX4
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: BAA7BB00-711A-4BDE-9B8E-E24E323A7F86
Device Start End Sectors Size Type /dev/sdc1 34 2047 2014 1007K
BIOS boot
Disk /dev/sdc2 2048 1050623 1048576 512M
EFI System
Disk /dev/sdc3 1050624 250069646 249019023 118.8G
Linux LVM
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000DM010-2EP1
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: 0x158a76ba
Device Boot Start End Sectors Size Id Type /dev/sda1 2048 1953525167 1953523120 931.5G
Linux
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000DM010-2EP1
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: dos
Disk identifier: 0xecae4de0
Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 1953525167 1953523120 931.5G
Linux
Disk /dev/mapper/pve-swap: 8 GiB, 8589934592 bytes, 16777216 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

Reply
Reply
C
CaydenJr
Member
Find
64
12-02-2016, 12:27 AM
#7
A few come from older setups while others are brand new. I’ve used fdisk to remove and replace partitions. However, the breaks proxmox isn’t detecting any disks during startup.
Reply
Reply
C
CaydenJr
12-02-2016, 12:27 AM #7

A few come from older setups while others are brand new. I’ve used fdisk to remove and replace partitions. However, the breaks proxmox isn’t detecting any disks during startup.

Reply
Reply
R
rakapaka3
Member
Find
59
12-02-2016, 08:52 AM
#8
Check the precise boot failure message. It could indicate incorrect disk placement or an unusual boot sequence. Using ZFS might help standardize storage. Ensure all partitions were created on the correct drives.
Reply
Reply
R
rakapaka3
12-02-2016, 08:52 AM #8

Check the precise boot failure message. It could indicate incorrect disk placement or an unusual boot sequence. Using ZFS might help standardize storage. Ensure all partitions were created on the correct drives.

Reply
Reply
E
ElectricPlayer
Junior Member
Find
49
12-03-2016, 07:06 AM
#9
Include an image of the process when attempting to create a ZFS volume.
Reply
Reply
E
ElectricPlayer
12-03-2016, 07:06 AM #9

Include an image of the process when attempting to create a ZFS volume.

Reply
Reply
K
Kawaiichan1776
Member
Find
216
12-03-2016, 09:08 AM
#10
These sections were originally identical. Now I’m trying to rearrange them, but it seems like I might have made a mistake. It’s possible I selected the incorrect option somewhere.
Reply
Reply
K
Kawaiichan1776
12-03-2016, 09:08 AM #10

These sections were originally identical. Now I’m trying to rearrange them, but it seems like I might have made a mistake. It’s possible I selected the incorrect option somewhere.

Reply
Reply
Pages (2): 1 2 Next