Search results

Try to change /etc/passd from root:x:0:0:root:/root:/bin/bash to root:x:0:0:Michael:/root:/bin/bash

I do not need RAID for Proxmox OS, cos it's easy to reinstall (although the less downtime is better). But I would like to have all customers data on some kind of RAID1 or RAID10. I did some tests a couple of years ago with mdadm raids on some HW with differrent FS and I realized RAID10 is very...

https://pve.proxmox.com/wiki/Software_RAID It seems that ZFS is only official option for RAID by Proxmox staff

Well I am not sure. I assume that he has soem kind of logical volume on the HW RAID, but it seems that PVE installer saw all disks instead of LV, cos he has too many options for booting.

https://forum.proxmox.com/threads/howto-proxmox-ve-7-with-software-raid-1.93745/post-543609 https://www.youtube.com/watch?v=eRqsbS3s554

I am sorry I have no notifications of a new posts, so I think my lost is lost. As I wrote OS was installed to a single consumer NVME LVM, ext4 and 4x consumer HDD works like zpool ZFS RAID10 (not RAID1 as I wrote before, it's a typo). zpool had a correct name, import was OK, partitions on all...

@esi_y I can't named myself as a friend of ZFS but I am not an enemy neither. As I wrote before I have dozens PVE, PBS runing with ZFS. Some of them are using ZFS only (for root too). I have one installation on HP too (with disabled of HW RAID functionality, because I was curious what...

ZFS is never a good idea to install to HW RAID. But there are plenty of users satisfied with ZFS. @esi_y is obviously not one of them. But if you don't need some of ZFS features you can stay with HW RAID

Proxmox (maybe only with ZFS) hates HW raides. So U have 2 destroy any raid volumes in raid bios of that HP server and leave all disks alone, then reinstall Proxmox and choose all disks and ZFS RAID10

U have 2 destroy HW RAID, if exist and use separate HDDs, not raided.

I have good experiences with virtio-win-0.1.96.iso, but @mariol is right, you have to start with IDE a then install drivers. I am using virtio virtio0: local-zfs:vm-106-disk-1,size=50Gvirtio1: local-zfs:vm-106-disk-2,size=476672M. You can also install drivers on physical server before cloning...

Hello, I made a test cluster of three nodes, then on every node I put some VMs and LXCs. Everything works nice, but today, I notices in GUI weird things. One of my node had ? in his name and in all VMs and LXCs. I could ssh to that node, there were no errors in logs, but qm list or pct list...

I used to backup script on all PVEs (https://github.com/DerDanilo/proxmox-stuff/blob/master/prox_config_backup.sh), but when I started to use PBS I don't use that script anymore (edit: I lied my crontabs still have line with that skript and all my PROD PVE configurations are stored to NFS...

As I wrote before, I can accept that PVE system hdd crashed, but I do not understand why it wiped all zvols on zpool. If there were some power outage and my server goes down, than maybe I can accept that ZFS could be broken. But that server is on UPS with other server, which are fine.

Ext4 or xfs

Well, you puzzled me. I don't like have a data on non raid disks or partitions. If I have a HW raid, I am using it,if not I am using SW LVM RAID. The same scenario I choose when start using PVE. What better/other options do I have?

I don't have any issues with ZFS before, except it eats huge amount of RAM. I don't have any comparision with LVM or any other system on Proxmox. But I am using ZFS for years on all proxmox servers, PBS too. Maybe it's because Proxmox installer can use RAID10 on ZFS only. There is no option to...

zpool status shows no pool. So I import and than I can see my imported pool, but zfs list not showing my zvols

I know, I relay on fact that all configs are included in backup on PBS, so I can take all configs from PBS. I can restore all VMs too, but I have backups 20hours old, so I loose data and want to know what happend and how to deal with this situation in the future

No, on all disks are all partitions related to ZFS RAID10, so I could zpool import, but without any ZFS subvols