Search results

I gave up under windows. Under Linux, works fine.

For anyone following along from home, this worked: zpool create -m /mnt/datastore/zpool1 zpool1 raidz2 sda sdb sdc sdd sde sdf sdg sdh sdi zpool create -m /mnt/datastore/zpool2 zpool2 raidz2 sdj sdk sdl sdm sdn sdo sdp sdq sdr zpool create -m /mnt/datastore/zpool3 zpool3 raidz2 sds sdt sdu sdv...

This completed normally: zpool create zpool1 raidz2 sda sdb sdc sdd sde sdf sdg sdh sdi root@test1:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 3.6T 0 disk ├─sda1 8:1 0 3.6T 0 part └─sda9 8:9 0 8M 0 part sdb 8:16...

Thank you, I was indeed confused. I didn't realize the installer for Centos 7 now defaults to XFS so the VM was running XFS on root, and that was the XFS that Docker was complaining about. I created a new VM on EXT4, and Docker is now happy. Storage Driver: overlay2 Backing Filesystem: extfs...

The Initialize Disk with GPT is greyed out. I'll see if I can get the binaries to talk to the disks.

root@test1:~# sas3ircu list Avago Technologies SAS3 IR Configuration Utility. Version 17.00.00.00 (2018.04.02) Copyright (c) 2009-2018 Avago Technologies. All rights reserved. Adapter Vendor Device SubSys SubSys Index Type ID ID Pci...

I've created some VMs for clients that are on CEPH on a new test setup, and got back this from them: Here's the error message docker gives when I explicitly set docker to use the overlay2 driver: failed to start daemon: error initializing graphdriver: overlay2: the backing xfs filesystem is...

root@test1:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 3.6T 0 disk sdb 8:16 0 3.6T 0 disk sdc 8:32 0 3.6T 0 disk sdd 8:48 0 3.6T 0 disk sde 8:64 0 3.6T 0 disk sdf 8:80 0 3.6T...

03:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02) Subsystem: Super Micro Computer Inc AOC-S3008L-L8e Physical Slot: 0-2 Flags: bus master, fast devsel, latency 0, IRQ 75, NUMA node 0 I/O ports at 6000 [size=256]...

I'm trying to get backup running on a Supermicro SSG-6048R-E1CR36L chassis. This has a SAS card: 03:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02) I can't seem to get the disks on that card to be available to Proxmox: root@test1:~/raid#...

I'm having the same issue- First VMs for Windows 10 and Windows Server 2019. Followed the instructions: PS C:\Users\Administrator> get-service qemu-ga Status Name DisplayName ------ ---- ----------- Running qemu-ga QEMU Guest Agent But: # qm agent...

I was able to deploy Unbuntu images, then wipe them and boot off of an ISO via IPMI, to give me Proxmox nodes on my MAAS managed hardware. MAAS still thinks they are Ubuntu, but at least they are deployed/tracked. I had to setup everything manually of course. Not ideal, but at least I didn't...

Looks like the answer is no- MAAS has no intention of supporting Debian: https://discourse.maas.io/t/how-to-deploy-debian-on-maas/1639

Is it possible to use MAAS to deploy new Proxmox nodes? I have MAAS running, and really like its ability to keep track of hardware. I've not been able to get MAAS 3.0 to upload my ESXi 7.0 image yet, but I got it built. Is there a tutorial for building/uploading a Proxmox image so I can deploy...