Recent content by codingspiderfox

It's hard to make a screenshot just at the right point in time as I don't know when the next crash will happen

Setup: Microserver Gen10 Plus with 48GB ECC (Memtest is OK) 4x4TB ZFS inside Proxmox 8.1.10 Latest TrueNAS Scale inside VM with 32GB RAM, 30GB System Disk and 3,2TB data Disk Inside TrueNAS: 1 Dataset on ZFS (encrypted) Exposed to LAN over SMB When I copy over files, it crashes - the likelihood...

My weekly backup is still a manual process where I would turn on my backup server machine via Wake On LAN Until now, I always added my backup node to the cluster so I can power it on via right click in the nodes list in the web UI. But this leads to more and more problems, for example when one...

which file exactly?

OK, it was very simple, I just edited the config file before: boot: order=scsi0;ide2;net0 cores: 1 ide2: local:iso/TrueNAS-13.0-U2.iso,media=cdrom,size=1015130K memory: 4096 meta: creation-qemu=7.0.0,ctime=1665080338 name: sharedTrueNAS net0: virtio=<HIDDEN_MAC>,bridge=vmbr0,firewall=1 numa: 0...

Does that only work with hardware disk passthrough or am I just too tired and confused already? I don't really understand what I should do

I installed TrueNAS on my Proxmox 7.2 node with a 32GB virtual disk for OS and a 1.5T disk for data. When I want to create a pool in TrueNAS, I get the following error There are 1 disks available that have non-unique serial numbers. Non-unique serial numbers can be caused by a cabling issue...

Probably yes. Which log file could help us find that out maybe?

Freeing up enough storage fixed the problem. The disk of the container with the config in the backed up state was indeed targeted to the ceph storage that was full. I feel like I would have never found the cause of the problem myself. Wouldn't it be possible for PVE to detect when the target...

Indeed there is a ceph problem in the cluster: Full OSDs blocking recovery: 1 pg recovery_toofull I will try to resolve that and then restart the restore

PS: I cancelled the restore on the PVE node now. The logs of the restore are now recovering backed-up configuration from '<SERVER>:backup/ct/100/2022-09-21T23:00:01Z' Using encryption key from file descriptor.. Fingerprint: 34:1d:00:b2:c6:bd:c4:ed /dev/rbd0 Creating filesystem with 3932160...

Yes, the restore is still in progress on the PVE side and I can still browse the available backups list on the PBS storage from that node

Next morning, still no progress

4 Minutes later, still no new chunk has been read. The logs of the restore in Proxmox VE so far are: Task viewer: CT 100 - Restore recovering backed-up configuration from '<SERVER>:backup/ct/100/2022-09-21T23:00:01Z' Using encryption key from file descriptor.. Fingerprint...

Just restarted the restore process once more 5 minutes ago. A task "Datastore data Read Objects ct/100/2022-09-21T23:00:01Z" appeared. These are the logs so far 2022-10-03T23:41:50+02:00: starting new backup reader datastore 'data': "/rpool/data" 2022-10-03T23:41:50+02:00: protocol upgrade...