Search results

In deiner smb.conf von #6 schreibst du /data/paperless/consume rein. Ändere das mal in /opt/paperless/consume oder besser: mkdir -p /data/paperless/consume/ Mann sollte mMn das Spooldir separat halten von Programmdatei.

Gib mal ls -la /opt/paperless/ und ls -la /data/paperless/ aus... --edit: auf die 192.168.115.139 aka paperless-ngx

IPadresse ist 192.168.115.239 oder 192.168.115.139 ?? 2 unterschiedliche Ip-adressen verwendet im Post #4 und #6 Statt smbclient -L 192.168.115.239 -U=paperless mal smbclient -L 192.168.115.139 -U=paperless versuchen.

Möglich dass SMB v1 gegen SMB v2 gemischt ist? Mein alter HP-Scanner macht nur SMBv1, für das ich ein V1-V2-Gateway geschaffen habe, das nur 1 Share freisetzt. Use the googlefu. Auch sehe ich in #6 path = /data/paperless/consume/ und in #15 path = /opt/consume/ Stimmt das? --edit-- virtus223...

https://itsnotdns.itwasdns.net/

Been there. https://forum.proxmox.com/threads/garbage-collector-error-due-to-datastore-full.136813/#post-607732 You will temporary have to move some chunk dir's in /mnt/datastore/HDD1/.chunks/ to another disk. Enable maintanance mode on datastore HDD1 mv /mnt/datastore/HDD1/.chunks/ff*...

Oben sehe ich mehrere IO-error (dmesg output?). Lost page writes. Möglich Hardware Fehler. Am besten das zuerst prüfen.

Updated today: Same issue. root@pve3:~# pveversion -v proxmox-ve: 8.0.2 (running kernel: 6.2.16-15-pve) pve-manager: 8.0.4 (running version: 8.0.4/d258a813cfa6b390) pve-kernel-6.2: 8.0.5 proxmox-kernel-helper: 8.0.3 pve-kernel-5.15: 7.4-4 proxmox-kernel-6.2.16-15-pve: 6.2.16-15...

proxmox:~# dmesg | grep scsi | grep Direct-Access [ 3.038526] scsi 1:0:0:0: Direct-Access ATA GB0250EAFYK HPG2 PQ: 0 ANSI: 5 [ 3.047625] scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD103SJ 0001 PQ: 0 ANSI: 5 [ 3.091783] scsi 3:0:0:0: Direct-Access ATA...

Just login, do the "apt install chrony", hit the ENTER 2x, sit back and relax... Reading package lists... Building dependency tree... Reading state information... Suggested packages: networkd-dispatcher The following packages will be REMOVED: systemd-timesyncd The following NEW packages will...

Use the googlefu: p2v and Disk2vhd. https://www.sage.uk.net/2022/02/10/elementor-1165/

I need to read up on the use case of using a /32...

Well, that is new(s) for me. proxmox:~# cat /etc/network/interfaces auto lo iface lo inet loopback auto vmbr0 iface vmbr0 inet static address 192.168.1.2 netmask 255.255.255.0 gateway 192.168.1.254 bridge_ports enp2s0f0 bridge_stp off bridge_fd...

You have working ping so you should be reachable on https://51.81.11.97:8006 if your connecting computer is in the same network... Comparing to my /etc/network/interfaces you could comment out the 5 lines with pre-down and post-up and restart networking: sudo systemctl restart networking

Just start giving info, so we can all join in! Log in in on the server and start giving info: proxmox:~# dmesg | grep eth proxmox:~# ip a proxmox:~# cat /etc/network/interfaces proxmox:~# ping 1.1.1.1

Edit /etc/network/interfaces (including gateway) Edit /etc/hosts Edit /etc/issue (This is shown on the screen after boot) Reboot

These threads are so valuable. Respect for posting progress!

More or less in the same boat. Old and rusty Proxmox, installed it 2011, kept up-to-date. Now forced to do a IP-rearrangement in my home-environment. Noticed: expired pve-root-ca and pve-ssl files. With above help and...

Doing the same since about april 2020. No real issues, other than selfgenerated ones...

Works like magic! root@pve-ML110:/etc/proxmox-backup# zpool status pool: PassPort2TB state: ONLINE scan: scrub repaired 0B in 12:34:54 with 0 errors on Sun Jul 11 12:58:56 2021 config: NAME STATE READ WRITE CKSUM...