Festplatten Problem.

Pfann · Oct 1, 2017

Hallo. Ich nutze seint längerer Zeit Proxmox. Mein Problem ist, dass meine Windows Vmaschine bei aktionen wie größere Daten kopieren oder verschieben sich das ganze System aufhängt und total langsam wird.
Ich habe sämtliche Googleaktionen durchgeführt, jedoch hat nichts davon helfen können.

Bei meinem Linux Vserver (Debian8) läuft alles wie es soll.

Beim Windows habe ich die Treiber von virtio installiert. Die Festplatten bereits verändert von qcow2 zu vmdk. Leider ohne Erfolg.

Ich hoffe, dass jemand helfen kann.

fireon · Oct 1, 2017

Hallo Pfann und herzlich willkommen hier im Forum

...bitte niemals Dinge wie vmdk verwenden. Vmdk ist nur für den Übergang von Migrationen gedacht. Raw oder qcow2. Poste mal bitte folgendes:

Code:

pvepversion -v
qm config <vmid-windows>

Was für eine Maschine hast du denn da? Wie viele Festplatten wie schnell, was für ein Raid? Wie alte ist das Gerät? Was für ein Storageformat benutzt du?

Code:

pvesm status

Pfann · Oct 1, 2017

Vielen Dank für die Antwort. Zunächst sollte ich das format wieder aufg qcow2 machen. Zeitlich werde ich es jetzt nicht schaffen. Die gewünschten daten sende ich, sobald ich zeitlich in der Lage bin

Pfann · Oct 4, 2017

zu ergänzen: Habe festgestellt, das dieses Problem den gesamten Root betrifft und nicht nur den Windows Vserver .

pvesm status
local dir 1 1056763060 497421652 505637936 50.09%
sdb1 dir 1 2884152988 887474108 1850165604 32.92%

Provider Hetzner

windows Vserver

Linux Debian 8 Vserver

Haupt Root

Oct 03 21:54:06 Proxmox-VE systemd[1]: Starting Mail Transport Agent.
Oct 03 21:54:06 Proxmox-VE systemd[1]: Reached target Mail Transport Agent.
Oct 03 21:54:06 Proxmox-VE postfix/master[1341]: daemon started -- version 2.11.3, configuration /etc/postfix
Oct 03 21:54:06 Proxmox-VE systemd[1]: Started LXC Container Initialization and Autoboot Code.
Oct 03 21:54:06 Proxmox-VE systemd[1]: Started The Proxmox VE cluster filesystem.
Oct 03 21:54:06 Proxmox-VE systemd[1]: Starting Regular background program processing daemon...
Oct 03 21:54:06 Proxmox-VE systemd[1]: Started Regular background program processing daemon.
Oct 03 21:54:06 Proxmox-VE systemd[1]: Started Corosync Cluster Engine.
Oct 03 21:54:06 Proxmox-VE systemd[1]: Starting Proxmox VE firewall...
Oct 03 21:54:06 Proxmox-VE systemd[1]: Starting PVE Status Daemon...
Oct 03 21:54:06 Proxmox-VE systemd[1]: Starting PVE API Daemon...
Oct 03 21:54:06 Proxmox-VE cron[1350]: (CRON) INFO (pidfile fd = 3)
Oct 03 21:54:06 Proxmox-VE cron[1350]: (CRON) INFO (Running @reboot jobs)
Oct 03 21:54:07 Proxmox-VE pve-firewall[1358]: starting server
Oct 03 21:54:07 Proxmox-VE systemd[1]: Started Proxmox VE firewall.
Oct 03 21:54:07 Proxmox-VE pvestatd[1364]: starting server
Oct 03 21:54:07 Proxmox-VE systemd[1]: Started PVE Status Daemon.
Oct 03 21:54:07 Proxmox-VE kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Oct 03 21:54:07 Proxmox-VE kernel: ip_set: protocol 6
Oct 03 21:54:08 Proxmox-VE webmin[1143]: Webmin starting
Oct 03 21:54:09 Proxmox-VE pvedaemon[1370]: starting server
Oct 03 21:54:09 Proxmox-VE pvedaemon[1370]: starting 3 worker(s)
Oct 03 21:54:09 Proxmox-VE pvedaemon[1370]: worker 1371 started
Oct 03 21:54:09 Proxmox-VE pvedaemon[1370]: worker 1372 started
Oct 03 21:54:09 Proxmox-VE pvedaemon[1370]: worker 1373 started
Oct 03 21:54:09 Proxmox-VE systemd[1]: Started PVE API Daemon.
Oct 03 21:54:09 Proxmox-VE systemd[1]: Starting PVE Cluster Ressource Manager Daemon...
Oct 03 21:54:09 Proxmox-VE systemd[1]: Starting PVE API Proxy Server...
Oct 03 21:54:09 Proxmox-VE pve-ha-crm[1380]: starting server
Oct 03 21:54:09 Proxmox-VE pve-ha-crm[1380]: status change startup => wait_for_quorum
Oct 03 21:54:09 Proxmox-VE systemd[1]: Started PVE Cluster Ressource Manager Daemon.
Oct 03 21:54:09 Proxmox-VE systemd[1]: Starting PVE Local HA Ressource Manager Daemon...
Oct 03 21:54:10 Proxmox-VE pve-ha-lrm[1385]: starting server
Oct 03 21:54:10 Proxmox-VE pve-ha-lrm[1385]: status change startup => wait_for_agent_lock
Oct 03 21:54:10 Proxmox-VE systemd[1]: Started PVE Local HA Ressource Manager Daemon.
Oct 03 21:54:10 Proxmox-VE pveproxy[1386]: starting server
Oct 03 21:54:10 Proxmox-VE pveproxy[1386]: starting 3 worker(s)
Oct 03 21:54:10 Proxmox-VE pveproxy[1386]: worker 1387 started
Oct 03 21:54:10 Proxmox-VE pveproxy[1386]: worker 1388 started
Oct 03 21:54:10 Proxmox-VE pveproxy[1386]: worker 1389 started
Oct 03 21:54:10 Proxmox-VE systemd[1]: Started PVE API Proxy Server.
Oct 03 21:54:10 Proxmox-VE systemd[1]: Starting PVE SPICE Proxy Server...
Oct 03 21:54:10 Proxmox-VE systemd[1]: Started LSB: Start or stop the Webmin server.
Oct 03 21:54:10 Proxmox-VE spiceproxy[1401]: starting server
Oct 03 21:54:10 Proxmox-VE spiceproxy[1401]: starting 1 worker(s)
Oct 03 21:54:10 Proxmox-VE spiceproxy[1401]: worker 1402 started
Oct 03 21:54:10 Proxmox-VE systemd[1]: Started PVE SPICE Proxy Server.
Oct 03 21:54:10 Proxmox-VE systemd[1]: Starting PVE VM Manager...
Oct 03 21:54:11 Proxmox-VE pve-manager[1403]: <root@pam> starting task UPID

roxmox-VE:00000599:00000C0F:59D3EAE3:startall::root@pam:
Oct 03 21:54:11 Proxmox-VE pve-manager[1403]: <root@pam> end task UPID

roxmox-VE:00000599:00000C0F:59D3EAE3:startall::root@pam: OK
Oct 03 21:54:11 Proxmox-VE systemd[1]: Started PVE VM Manager.
Oct 03 21:54:11 Proxmox-VE systemd[1]: Starting Multi-User System.
Oct 03 21:54:11 Proxmox-VE systemd[1]: Reached target Multi-User System.
Oct 03 21:54:11 Proxmox-VE systemd[1]: Starting Graphical Interface.
Oct 03 21:54:11 Proxmox-VE systemd[1]: Reached target Graphical Interface.
Oct 03 21:54:11 Proxmox-VE systemd[1]: Starting Update UTMP about System Runlevel Changes...
Oct 03 21:54:11 Proxmox-VE systemd[1]: Started Update UTMP about System Runlevel Changes.
Oct 03 21:54:11 Proxmox-VE systemd[1]: Startup finished in 12.702s (kernel) + 18.244s (userspace) = 30.947s.
Oct 03 21:54:14 Proxmox-VE ntpdate[895]: step time server 131.188.3.221 offset -0.142847 sec
Oct 03 21:54:14 Proxmox-VE systemd[1]: Time has been changed
Oct 03 21:54:14 Proxmox-VE pvedaemon[1371]: <root@pam> successful auth for user 'root@pam'
Oct 03 21:54:27 Proxmox-VE ntpdate[1460]: step time server 131.188.3.221 offset -0.000138 sec
Oct 03 21:54:27 Proxmox-VE systemd[1]: Time has been changed
Oct 03 21:54:29 Proxmox-VE systemd-timesyncd[668]: Using NTP server [2a01:4f8:0:a112::2:2]:123 (ntp2.hetzner.com).
Oct 03 21:54:29 Proxmox-VE systemd-timesyncd[668]: interval/delta/delay/jitter/drift 64s/+0.001s/0.000s/0.000s/+0ppm
Oct 03 21:54:44 Proxmox-VE ntpdate[1477]: adjust time server 131.188.3.221 offset -0.000527 sec
Oct 03 21:55:04 Proxmox-VE ntpdate[1493]: adjust time server 131.188.3.221 offset -0.000628 sec
Oct 03 21:55:34 Proxmox-VE systemd-timesyncd[668]: interval/delta/delay/jitter/drift 128s/+0.001s/0.000s/0.000s/+4ppm
Oct 03 21:55:59 Proxmox-VE sshd[1545]: Received disconnect from 59.45.175.96: 11: [preauth]
Oct 03 21:57:42 Proxmox-VE systemd-timesyncd[668]: interval/delta/delay/jitter/drift 256s/-0.002s/0.000s/0.002s/+1ppm
Oct 03 21:57:57 Proxmox-VE pvedaemon[1371]: <root@pam> starting task UPID

roxmox-VE:0000065F:00006466:59D3EBC5:qmstart:100:root@pam:
Oct 03 21:57:57 Proxmox-VE pvedaemon[1631]: start VM 100: UPID

roxmox-VE:0000065F:00006466:59D3EBC5:qmstart:100:root@pam:
Oct 03 21:57:58 Proxmox-VE systemd[1]: Starting qemu.slice.
Oct 03 21:57:58 Proxmox-VE systemd[1]: Created slice qemu.slice.
Oct 03 21:57:58 Proxmox-VE systemd[1]: Starting 100.scope.
Oct 03 21:57:58 Proxmox-VE systemd[1]: Started 100.scope.
Oct 03 21:57:58 Proxmox-VE systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
Oct 03 21:57:58 Proxmox-VE systemd-sysctl[1645]: Overwriting earlier assignment of net/ipv4/conf/all/rp_filter in file '/usr/lib/sysctl.d/pve-firewall.conf'.
Oct 03 21:57:59 Proxmox-VE kernel: device tap100i0 entered promiscuous mode
Oct 03 21:57:59 Proxmox-VE kernel: vmbr0: port 2(tap100i0) entered forwarding state
Oct 03 21:57:59 Proxmox-VE kernel: vmbr0: port 2(tap100i0) entered forwarding state
Oct 03 21:57:59 Proxmox-VE kernel: kvm: SMP vm created on host with unstable TSC; guest TSC will not be reliable
Oct 03 21:58:00 Proxmox-VE pvedaemon[1371]: <root@pam> end task UPID

roxmox-VE:0000065F:00006466:59D3EBC5:qmstart:100:root@pam: OK
Oct 03 21:58:03 Proxmox-VE kernel: kvm: zapping shadow pages for mmio generation wraparound
Oct 03 21:58:03 Proxmox-VE kernel: kvm: zapping shadow pages for mmio generation wraparound
Oct 03 21:58:04 Proxmox-VE pvedaemon[1371]: <root@pam> starting task UPID

roxmox-VE:00000688:000066E0:59D3EBCC:qmstart:101:root@pam:
Oct 03 21:58:04 Proxmox-VE pvedaemon[1672]: start VM 101: UPID

roxmox-VE:00000688:000066E0:59D3EBCC:qmstart:101:root@pam:
Oct 03 21:58:04 Proxmox-VE systemd[1]: Starting 101.scope.
Oct 03 21:58:04 Proxmox-VE systemd[1]: Started 101.scope.
Oct 03 21:58:04 Proxmox-VE systemd-sysctl[1687]: Overwriting earlier assignment of net/ipv4/conf/all/rp_filter in file '/usr/lib/sysctl.d/pve-firewall.conf'.
Oct 03 21:58:04 Proxmox-VE kernel: device tap101i0 entered promiscuous mode
Oct 03 21:58:04 Proxmox-VE kernel: vmbr0: port 3(tap101i0) entered forwarding state
Oct 03 21:58:04 Proxmox-VE kernel: vmbr0: port 3(tap101i0) entered forwarding state
Oct 03 21:58:05 Proxmox-VE pvedaemon[1371]: <root@pam> end task UPID

roxmox-VE:00000688:000066E0:59D3EBCC:qmstart:101:root@pam: OK
Oct 03 21:58:07 Proxmox-VE kernel: kvm: zapping shadow pages for mmio generation wraparound
Oct 03 21:58:07 Proxmox-VE kernel: kvm: zapping shadow pages for mmio generation wraparound
Oct 03 21:59:28 Proxmox-VE pvedaemon[1371]: <root@pam> successful auth for user 'root@pam'
Oct 03 22:01:02 Proxmox-VE sshd[1888]: Accepted password for root from 217.83.200.166 port 55330 ssh2
Oct 03 22:01:02 Proxmox-VE sshd[1888]: pam_unix(sshd:session): session opened for user root by (uid=0)
Oct 03 22:01:02 Proxmox-VE systemd[1]: Starting user-0.slice.
Oct 03 22:01:02 Proxmox-VE systemd[1]: Created slice user-0.slice.
Oct 03 22:01:02 Proxmox-VE systemd[1]: Starting User Manager for UID 0...
Oct 03 22:01:02 Proxmox-VE systemd-logind[1134]: New session 1 of user root.
Oct 03 22:01:02 Proxmox-VE systemd[1]: Starting Session 1 of user root.
Oct 03 22:01:02 Proxmox-VE systemd[1890]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Oct 03 22:01:02 Proxmox-VE systemd[1]: Started Session 1 of user root.
Oct 03 22:01:03 Proxmox-VE systemd[1890]: Starting Paths.
Oct 03 22:01:03 Proxmox-VE systemd[1890]: Reached target Paths.
Oct 03 22:01:03 Proxmox-VE systemd[1890]: Starting Timers.
Oct 03 22:01:03 Proxmox-VE systemd[1890]: Reached target Timers.
Oct 03 22:01:03 Proxmox-VE systemd[1890]: Starting Sockets.
Oct 03 22:01:03 Proxmox-VE systemd[1890]: Reached target Sockets.
Oct 03 22:01:03 Proxmox-VE systemd[1890]: Starting Basic System.
Oct 03 22:01:03 Proxmox-VE systemd[1890]: Reached target Basic System.
Oct 03 22:01:03 Proxmox-VE systemd[1890]: Starting Default.
Oct 03 22:01:03 Proxmox-VE systemd[1890]: Reached target Default.
Oct 03 22:01:03 Proxmox-VE systemd[1890]: Startup finished in 77ms.
Oct 03 22:01:03 Proxmox-VE systemd[1]: Started User Manager for UID 0.
Oct 03 22:01:58 Proxmox-VE systemd-timesyncd[668]: interval/delta/delay/jitter/drift 512s/-0.003s/0.000s/0.003s/-1ppm
Oct 03 22:02:54 Proxmox-VE sshd[1971]: Received disconnect from 59.45.175.24: 11: [preauth]
Oct 03 22:03:25 Proxmox-VE sshd[2001]: Received disconnect from 121.18.238.119: 11: [preauth]
Oct 03 22:09:00 Proxmox-VE sshd[2294]: Received disconnect from 59.45.175.94: 11: [preauth]
Oct 03 22:09:00 Proxmox-VE systemd[1]: Starting Cleanup of Temporary Directories...
Oct 03 22:09:00 Proxmox-VE systemd[1]: Started Cleanup of Temporary Directories.
Oct 03 22:10:30 Proxmox-VE systemd-timesyncd[668]: interval/delta/delay/jitter/drift 1024s/-0.004s/0.000s/0.004s/-3ppm
Oct 03 22:14:28 Proxmox-VE pvedaemon[1372]: <root@pam> successful auth for user 'root@pam'
Oct 03 22:14:58 Proxmox-VE sshd[2643]: Connection closed by 217.160.142.116 [preauth]
Oct 03 22:15:17 Proxmox-VE pvedaemon[1371]: <root@pam> successful auth for user 'root@pam'
Oct 03 22:17:01 Proxmox-VE CRON[2743]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 03 22:17:01 Proxmox-VE CRON[2744]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Oct 03 22:17:01 Proxmox-VE CRON[2743]: pam_unix(cron:session): session closed for user root
Oct 03 22:17:20 Proxmox-VE sshd[2760]: Received disconnect from 185.165.29.77: 11: Bye Bye [preauth]
Oct 03 22:20:23 Proxmox-VE sshd[2940]: Received disconnect from 185.56.80.121: 11: Bye Bye [preauth]
Oct 03 22:21:56 Proxmox-VE sshd[3008]: Received disconnect from 221.194.47.236: 11: [preauth]
Oct 03 22:24:06 Proxmox-VE smartd[1118]: Device: /dev/sda [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 104 to 105
Oct 03 22:24:06 Proxmox-VE smartd[1118]: Device: /dev/sda [SAT], SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 8 to 9
Oct 03 22:24:06 Proxmox-VE smartd[1118]: Device: /dev/sdb [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 75 to 82
Oct 03 22:24:06 Proxmox-VE smartd[1118]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 61 to 60
Oct 03 22:24:06 Proxmox-VE smartd[1118]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 39 to 40
Oct 03 22:24:22 Proxmox-VE sshd[3117]: Invalid user admin from 219.148.63.61
Oct 03 22:24:22 Proxmox-VE sshd[3117]: input_userauth_request: invalid user admin [preauth]
Oct 03 22:24:22 Proxmox-VE sshd[3117]: pam_unix(sshd:auth): check pass; user unknown
Oct 03 22:24:22 Proxmox-VE sshd[3117]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.148.63.61
Oct 03 22:24:25 Proxmox-VE sshd[3117]: Failed password for invalid user admin from 219.148.63.61 port 59969 ssh2
Oct 03 22:24:25 Proxmox-VE sshd[3117]: pam_unix(sshd:auth): check pass; user unknown
Oct 03 22:24:27 Proxmox-VE sshd[3117]: Failed password for invalid user admin from 219.148.63.61 port 59969 ssh2
Oct 03 22:24:27 Proxmox-VE sshd[3117]: pam_unix(sshd:auth): check pass; user unknown
Oct 03 22:24:28 Proxmox-VE sshd[3117]: Failed password for invalid user admin from 219.148.63.61 port 59969 ssh2
Oct 03 22:24:28 Proxmox-VE sshd[3117]: pam_unix(sshd:auth): check pass; user unknown
Oct 03 22:24:30 Proxmox-VE sshd[3117]: Failed password for invalid user admin from 219.148.63.61 port 59969 ssh2
Oct 03 22:24:30 Proxmox-VE sshd[3117]: pam_unix(sshd:auth): check pass; user unknown
Oct 03 22:24:32 Proxmox-VE sshd[3117]: Failed password for invalid user admin from 219.148.63.61 port 59969 ssh2
Oct 03 22:24:32 Proxmox-VE sshd[3117]: pam_unix(sshd:auth): check pass; user unknown
Oct 03 22:24:34 Proxmox-VE sshd[3117]: Failed password for invalid user admin from 219.148.63.61 port 59969 ssh2
Oct 03 22:24:34 Proxmox-VE sshd[3117]: Disconnecting: Too many authentication failures for invalid user admin from 219.148.63.61 port 59969 ssh2 [preauth]
Oct 03 22:24:34 Proxmox-VE sshd[3117]: PAM 5 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.148.63.61
Oct 03 22:24:34 Proxmox-VE sshd[3117]: PAM service(sshd) ignoring max retries; 6 > 3
Oct 03 22:25:01 Proxmox-VE sshd[3195]: Received disconnect from 121.18.238.106: 11: [preauth]
Oct 03 22:29:21 Proxmox-VE systemd-timesyncd[668]: Timed out waiting for reply from [2a01:4f8:0:a112::2:2]:123 (ntp2.hetzner.com).
Oct 03 22:29:21 Proxmox-VE systemd-timesyncd[668]: Using NTP server 213.239.239.165:123 (ntp2.hetzner.com).
Oct 03 22:29:21 Proxmox-VE systemd-timesyncd[668]: interval/delta/delay/jitter/drift 2048s/-0.006s/0.000s/0.004s/-5ppm
Oct 03 22:30:17 Proxmox-VE pvedaemon[1371]: <root@pam> successful auth for user 'root@pam'
Oct 03 22:42:27 Proxmox-VE sshd[4078]: Connection closed by 67.207.85.131 [preauth]
Oct 03 22:45:18 Proxmox-VE pvedaemon[1371]: <root@pam> successful auth for user 'root@pam'
Oct 03 22:54:04 Proxmox-VE rrdcached[1163]: flushing old values
Oct 03 22:54:04 Proxmox-VE rrdcached[1163]: rotating journals
Oct 03 22:54:04 Proxmox-VE rrdcached[1163]: started new journal /var/lib/rrdcached/journal/rrd.journal.1507064044.924065
Oct 03 22:54:06 Proxmox-VE smartd[1118]: Device: /dev/sdb [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 82 to 76
Oct 03 22:54:06 Proxmox-VE smartd[1118]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 60 to 63
Oct 03 22:54:06 Proxmox-VE smartd[1118]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 40 to 37
Oct 03 23:00:18 Proxmox-VE pvedaemon[1372]: <root@pam> successful auth for user 'root@pam'
Oct 03 23:01:52 Proxmox-VE pveproxy[1389]: worker exit
Oct 03 23:01:52 Proxmox-VE pveproxy[1386]: worker 1389 finished
Oct 03 23:01:52 Proxmox-VE pveproxy[1386]: starting 1 worker(s)
Oct 03 23:01:52 Proxmox-VE pveproxy[1386]: worker 5123 started
Oct 03 23:03:30 Proxmox-VE systemd-timesyncd[668]: interval/delta/delay/jitter/drift 2048s/-0.008s/0.000s/0.006s/-7ppm
Oct 03 23:05:26 Proxmox-VE pveproxy[1388]: worker exit
Oct 03 23:05:26 Proxmox-VE pveproxy[1386]: worker 1388 finished
Oct 03 23:05:26 Proxmox-VE pveproxy[1386]: starting 1 worker(s)
Oct 03 23:05:26 Proxmox-VE pveproxy[1386]: worker 5274 started
Oct 03 23:07:22 Proxmox-VE pveproxy[1387]: worker exit
Oct 03 23:07:22 Proxmox-VE pveproxy[1386]: worker 1387 finished
Oct 03 23:07:22 Proxmox-VE pveproxy[1386]: starting 1 worker(s)
Oct 03 23:07:22 Proxmox-VE pveproxy[1386]: worker 5408 started
Oct 03 23:08:42 Proxmox-VE sshd[5460]: Address 187.252.208.82 maps to 187.252.208.82.cable.dyn.cableonline.com.mx, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Oct 03 23:08:42 Proxmox-VE sshd[5460]: Invalid user support from 187.252.208.82
Oct 03 23:08:42 Proxmox-VE sshd[5460]: input_userauth_request: invalid user support [preauth]
Oct 03 23:08:42 Proxmox-VE sshd[5460]: pam_unix(sshd:auth): check pass; user unknown
Oct 03 23:08:42 Proxmox-VE sshd[5460]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.252.208.82
Oct 03 23:08:44 Proxmox-VE sshd[5460]: Failed password for invalid user support from 187.252.208.82 port 6920 ssh2
Oct 03 23:08:44 Proxmox-VE sshd[5460]: pam_unix(sshd:auth): check pass; user unknown
Oct 03 23:08:46 Proxmox-VE sshd[5460]: Failed password for invalid user support from 187.252.208.82 port 6920 ssh2
Oct 03 23:08:46 Proxmox-VE sshd[5460]: pam_unix(sshd:auth): check pass; user unknown
Oct 03 23:08:47 Proxmox-VE sshd[5460]: Failed password for invalid user support from 187.252.208.82 port 6920 ssh2
Oct 03 23:08:48 Proxmox-VE sshd[5460]: Connection closed by 187.252.208.82 [preauth]
Oct 03 23:08:48 Proxmox-VE sshd[5460]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.252.208.82
Oct 03 23:13:29 Proxmox-VE sshd[5726]: Received disconnect from 59.45.175.98: 11: [preauth]
Oct 03 23:15:18 Proxmox-VE pvedaemon[1371]: <root@pam> successful auth for user 'root@pam'
Oct 03 23:17:01 Proxmox-VE CRON[5926]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 03 23:17:01 Proxmox-VE CRON[5927]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Oct 03 23:17:01 Proxmox-VE CRON[5926]: pam_unix(cron:session): session closed for user root
Oct 03 23:20:56 Proxmox-VE sshd[6092]: Received disconnect from 221.194.47.233: 11: [preauth]
Oct 03 23:22:46 Proxmox-VE kernel: perf interrupt took too long (2510 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
Oct 03 23:24:06 Proxmox-VE smartd[1118]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 64 to 65
Oct 03 23:24:06 Proxmox-VE smartd[1118]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 36 to 35
Oct 03 23:24:07 Proxmox-VE smartd[1118]: Device: /dev/sdb [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 76 to 80
Oct 03 23:24:07 Proxmox-VE smartd[1118]: Device: /dev/sdb [SAT], SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 33 to 32
Oct 03 23:25:08 Proxmox-VE sshd[6322]: Received disconnect from 59.45.175.96: 11: [preauth]
Oct 03 23:30:18 Proxmox-VE pvedaemon[1371]: <root@pam> successful auth for user 'root@pam'
Oct 03 23:37:38 Proxmox-VE systemd-timesyncd[668]: interval/delta/delay/jitter/drift 2048s/-0.002s/0.000s/0.003s/-8ppm
Oct 03 23:40:55 Proxmox-VE sshd[7165]: Received disconnect from 121.18.238.106: 11: [preauth]
Oct 03 23:45:19 Proxmox-VE pvedaemon[1371]: <root@pam> successful auth for user 'root@pam'
Oct 03 23:50:55 Proxmox-VE sshd[7693]: Received disconnect from 221.194.47.236: 11: [preauth]
Oct 03 23:53:55 Proxmox-VE sshd[7870]: Received disconnect from 5.189.133.76: 11: Bye Bye [preauth]
Oct 03 23:54:04 Proxmox-VE rrdcached[1163]: flushing old values
Oct 03 23:54:04 Proxmox-VE rrdcached[1163]: rotating journals
Oct 03 23:54:04 Proxmox-VE rrdcached[1163]: started new journal /var/lib/rrdcached/journal/rrd.journal.1507067644.924035
Oct 03 23:54:04 Proxmox-VE rrdcached[1163]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1507052174.961719
Oct 03 23:54:04 Proxmox-VE rrdcached[1163]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1507055774.961697
Oct 03 23:54:04 Proxmox-VE rrdcached[1163]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1507059166.885596
Oct 03 23:54:04 Proxmox-VE rrdcached[1163]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1507060444.824042
Oct 03 23:54:06 Proxmox-VE smartd[1118]: Device: /dev/sdb [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 80 to 82
Oct 03 23:59:13 Proxmox-VE sshd[8151]: Received disconnect from 59.45.175.94: 11: [preauth]
Oct 04 00:00:19 Proxmox-VE pvedaemon[1372]: <root@pam> successful auth for user 'root@pam'
Oct 04 00:01:29 Proxmox-VE sshd[8248]: Invalid user admin from 202.29.233.65
Oct 04 00:01:29 Proxmox-VE sshd[8248]: input_userauth_request: invalid user admin [preauth]
Oct 04 00:01:29 Proxmox-VE sshd[8248]: pam_unix(sshd:auth): check pass; user unknown
Oct 04 00:01:29 Proxmox-VE sshd[8248]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.29.233.65
Oct 04 00:01:31 Proxmox-VE sshd[8248]: Failed password for invalid user admin from 202.29.233.65 port 6920 ssh2
Oct 04 00:01:31 Proxmox-VE sshd[8248]: pam_unix(sshd:auth): check pass; user unknown
Oct 04 00:01:33 Proxmox-VE sshd[8248]: Failed password for invalid user admin from 202.29.233.65 port 6920 ssh2
Oct 04 00:01:34 Proxmox-VE sshd[8248]: pam_unix(sshd:auth): check pass; user unknown
Oct 04 00:01:35 Proxmox-VE sshd[8248]: Failed password for invalid user admin from 202.29.233.65 port 6920 ssh2
Oct 04 00:01:36 Proxmox-VE sshd[8248]: Connection closed by 202.29.233.65 [preauth]
Oct 04 00:01:36 Proxmox-VE sshd[8248]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.29.233.65
Oct 04 00:11:46 Proxmox-VE systemd-timesyncd[668]: interval/delta/delay/jitter/drift 2048s/-0.001s/0.000s/0.004s/-8ppm
Oct 04 00:15:19 Proxmox-VE pvedaemon[1372]: <root@pam> successful auth for user 'root@pam'
Oct 04 00:17:01 Proxmox-VE CRON[9070]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 04 00:17:01 Proxmox-VE CRON[9071]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Oct 04 00:17:01 Proxmox-VE CRON[9070]: pam_unix(cron:session): session closed for user root
Oct 04 00:17:29 Proxmox-VE pveproxy[5123]: worker exit
Oct 04 00:17:29 Proxmox-VE pveproxy[1386]: worker 5123 finished
Oct 04 00:17:29 Proxmox-VE pveproxy[1386]: starting 1 worker(s)
Oct 04 00:17:29 Proxmox-VE pveproxy[1386]: worker 9095 started
Oct 04 00:21:20 Proxmox-VE pveproxy[5274]: worker exit
Oct 04 00:21:20 Proxmox-VE pveproxy[1386]: worker 5274 finished
Oct 04 00:21:20 Proxmox-VE pveproxy[1386]: starting 1 worker(s)
Oct 04 00:21:20 Proxmox-VE pveproxy[1386]: worker 9312 started
Oct 04 00:24:06 Proxmox-VE smartd[1118]: Device: /dev/sdb [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 82 to 72
Oct 04 00:24:06 Proxmox-VE smartd[1118]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 63 to 64
Oct 04 00:24:06 Proxmox-VE smartd[1118]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 37 to 36
Oct 04 00:24:06 Proxmox-VE smartd[1118]: Device: /dev/sdb [SAT], SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 32 to 33
Oct 04 00:30:20 Proxmox-VE pvedaemon[1371]: <root@pam> successful auth for user 'root@pam'
Oct 04 00:41:53 Proxmox-VE pveproxy[5408]: worker exit
Oct 04 00:41:53 Proxmox-VE pveproxy[1386]: worker 5408 finished
Oct 04 00:41:53 Proxmox-VE pveproxy[1386]: starting 1 worker(s)
Oct 04 00:41:53 Proxmox-VE pveproxy[1386]: worker 10392 started
Oct 04 00:42:20 Proxmox-VE sshd[10415]: Received disconnect from 121.18.238.119: 11: [preauth]
Oct 04 00:45:20 Proxmox-VE pvedaemon[1373]: <root@pam> successful auth for user 'root@pam'
Oct 04 00:45:31 Proxmox-VE sshd[10604]: Received disconnect from 59.45.175.98: 11: [preauth]
Oct 04 00:45:54 Proxmox-VE systemd-timesyncd[668]: interval/delta/delay/jitter/drift 2048s/-0.001s/0.000s/0.003s/-8ppm
Oct 04 00:54:04 Proxmox-VE rrdcached[1163]: flushing old values
Oct 04 00:54:04 Proxmox-VE rrdcached[1163]: rotating journals
Oct 04 00:54:04 Proxmox-VE rrdcached[1163]: started new journal /var/lib/rrdcached/journal/rrd.journal.1507071244.924031
Oct 04 00:54:04 Proxmox-VE rrdcached[1163]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1507064044.924065
Oct 04 00:54:07 Proxmox-VE smartd[1118]: Device: /dev/sdb [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 72 to 79
Oct 04 00:58:37 Proxmox-VE sshd[11279]: Received disconnect from 185.158.113.54: 11: Bye Bye [preauth]
Oct 04 01:00:21 Proxmox-VE pvedaemon[1372]: <root@pam> successful auth for user 'root@pam'
Oct 04 01:00:59 Proxmox-VE sshd[11415]: Accepted password for root from 217.83.200.166 port 57905 ssh2
Oct 04 01:00:59 Proxmox-VE sshd[11415]: pam_unix(sshd:session): session opened for user root by (uid=0)
Oct 04 01:00:59 Proxmox-VE systemd[1]: Starting Session 5 of user root.
Oct 04 01:00:59 Proxmox-VE systemd-logind[1134]: New session 5 of user root.
Oct 04 01:00:59 Proxmox-VE systemd[1]: Started Session 5 of user root.
Oct 04 01:01:55 Proxmox-VE sshd[11490]: Received disconnect from 121.18.238.106: 11: [preauth]
Oct 04 01:08:24 Proxmox-VE sshd[11829]: Received disconnect from 185.158.113.54: 11: Bye Bye [preauth]
Oct 04 01:08:53 Proxmox-VE pvedaemon[1373]: <root@pam> starting task UPID

roxmox-VE:00002E4E:0011DF2F:59D41885:vncshell::root@pam:
Oct 04 01:08:53 Proxmox-VE pvedaemon[11854]: starting vnc proxy UPID

roxmox-VE:00002E4E:0011DF2F:59D41885:vncshell::root@pam:
Oct 04 01:08:53 Proxmox-VE pvedaemon[11854]: launch command: /usr/bin/vncterm -rfbport 5900 -timeout 10 -authpath /nodes/Proxmox-VE -perm Sys.Console -notls -listen localhost -c /bin/login -f root
Oct 04 01:08:55 Proxmox-VE login[11904]: pam_unix(login:session): session opened for user root by (uid=0)
Oct 04 01:08:55 Proxmox-VE systemd[1]: Starting Session 6 of user root.
Oct 04 01:08:55 Proxmox-VE systemd-logind[1134]: New session 6 of user root.
Oct 04 01:08:55 Proxmox-VE systemd[1]: Started Session 6 of user root.
Oct 04 01:08:55 Proxmox-VE login[11907]: ROOT LOGIN on '/dev/pts/1'
Oct 04 01:08:55 Proxmox-VE pveproxy[9312]: proxy detected vanished client connection
Oct 04 01:09:15 Proxmox-VE systemd-logind[1134]: Removed session 6.
Oct 04 01:09:15 Proxmox-VE pvedaemon[1373]: <root@pam> end task UPID

roxmox-VE:00002E4E:0011DF2F:59D41885:vncshell::root@pam: OK
Oct 04 01:09:50 Proxmox-VE pvedaemon[1373]: command '/sbin/zpool list -HPLv' failed: open3: exec of /sbin/zpool list -HPLv failed at /usr/share/perl5/PVE/Tools.pm line 427.
Oct 04 01:10:06 Proxmox-VE pvedaemon[1373]: command '/sbin/zpool list -HPLv' failed: open3: exec of /sbin/zpool list -HPLv failed at /usr/share/perl5/PVE/Tools.pm line 427.
Oct 04 01:10:09 Proxmox-VE pvedaemon[1373]: command '/sbin/zpool list -HPLv' failed: open3: exec of /sbin/zpool list -HPLv failed at /usr/share/perl5/PVE/Tools.pm line 427.
Oct 04 01:12:20 Proxmox-VE pvedaemon[1371]: command '/sbin/zpool list -HPLv' failed: open3: exec of /sbin/zpool list -HPLv failed at /usr/share/perl5/PVE/Tools.pm line 427.

fireon · Oct 7, 2017

Hmm, sieht jetzt alles nicht schlecht aus. Es gibt jede Menge Fehllogins auf dem Server... ok ist wohl normal wenn der bei einem Provider steht. Ich hab da in Windows immer SCSI für Festplatten, event. hilft das schon. "ksmtuned" läuft nicht... Was sagt denn

Code:

pveperf

Und wie schaut es mit den Smartwerten aus? Gibt es Sektorenfehler oder so?
lg

Pfann · Oct 8, 2017

Also die festplatte hat keinen schaden. Dachte ich zuerst auch, dann habe ich sogar den provider beauftragt dies zu prüfen. Es liegt kein Fehler vor.

fireon · Oct 8, 2017

Huch, ok also da hats gewaltig was. Das Teil hat einfach keine Power, also von der Hardware... FSYNCs/SECOND ist zwar nur ein Richtwert, aber der sollte schon mind. auf 3000 sein.

Hab hier bei 8 SATA Platten 6981 (ZFS Raid10) sind RedPro Platten, bei einem Raid5 (ZFS) mit 3SSD's (Enterprise) sind's da 5703 und bei nem.

Und dann gibt es da noch nen Backupserver, der hat das gleiche Hardware wei der mit den 8SATA Platten und dem SSD-Raid. Der Unterschied ist das dieser aber nur 4 billigsdorfen SATA Platten hat mit 5400 Umdrehungen (WD Green) und die im Raid5 (ZFS) ohne Cache/Log. Bei der Maschine hab ich auch nur "FSYNCS/SECOND 88.14" ist aber egal da nur Backup, die Maschine mag die Last noch bewältigen.

Du siehts also den Unterschied. Fett machen's die Platten der Cache.

Pfann · Oct 8, 2017

könnte es an einer falschen installation liegen oder falschen mount? oder ist es definitiv die platte die fürn A... ist ?

Wie gesagt. Mein root läuft ohne probleme. Sobald ich jedoch größere Daten verschiebe, kopiere, packe und entpacke, hängt sich alles auf.
Auf dem Debian Vserver habe ich einen größeren Download von 30 GB gestartet. Am ende waren es nur noch 200 Kb/S und alls hing

ein kollege hat den selben Root bei Hetzner bei ihm klappt alles wunderbar

CPU BOGOMIPS: 76803.96
REGEX/SECOND: 1125349
HD SIZE: 1007.81 GB (/dev/sda3)
BUFFERED READS: 171.70 MB/sec
AVERAGE SEEK TIME: 18.47 ms
FSYNCS/SECOND: 11.19
DNS EXT: 2.94 ms

fireon · Oct 8, 2017

... das I/O ist auf jeden Fall totaler Schrott. Sieht für mich jetzt so aus. Setz da mal an. Außerdem haste zwei verschiedene Plattentypen, das ist suboptimal. Poste doch mal die Smartwerte jeder Platte. Raid ist da wohl keines oder?

Pfann · Oct 8, 2017

okay hier die log

smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.4.83-1-pve] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda XT
Device Model: ST33000651AS
Serial Number: Z290YXPQ
LU WWN Device Id: 5 000c50 03600cb6b
Firmware Version: CC45
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Sun Oct 8 20:05:42 2017 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 600) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 444) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 106 099 006 Pre-fail Always - 12234381
3 Spin_Up_Time 0x0003 090 090 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 14
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 085 060 030 Pre-fail Always - 348270498
9 Power_On_Hours 0x0032 041 041 000 Old_age Always - 52014
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 14
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 065 044 045 Old_age Always In_the_past 35 (1 51 38 26 0)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 9
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 14
194 Temperature_Celsius 0x0022 035 056 000 Old_age Always - 35 (0 19 0 0 0)
195 Hardware_ECC_Recovered 0x001a 010 005 000 Old_age Always - 12234381
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 51967 (221 63 0)
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 3138470525
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 604474556

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 51160 -
# 2 Extended offline Completed without error 00% 49587 -
# 3 Extended offline Completed without error 00% 49568 -
# 4 Extended offline Completed without error 00% 49556 -
# 5 Short offline Completed without error 00% 49545 -
# 6 Extended offline Completed: read failure 40% 49535 4060750387
# 7 Extended offline Completed: read failure 40% 49516 4060750387
# 8 Extended offline Completed without error 00% 7 -
2 of 2 failed self-tests are outdated by newer successful extended offline self-test # 2

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.4.83-1-pve] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Constellation ES.2 (SATA 6Gb/s)
Device Model: ST33000650NS
Serial Number: Z292SCCC
LU WWN Device Id: 5 000c50 04d2fa7aa
Firmware Version: 0004
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Sun Oct 8 20:07:13 2017 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 609) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 452) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x10bd) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 080 063 044 Pre-fail Always - 110844167
3 Spin_Up_Time 0x0003 093 092 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 21
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 66855761
9 Power_On_Hours 0x0032 059 059 000 Old_age Always - 36093
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 20
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 064 064 000 Old_age Always - 36
190 Airflow_Temperature_Cel 0x0022 063 047 045 Old_age Always - 37 (Min/Max 27/41)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 11
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 21
194 Temperature_Celsius 0x0022 037 053 000 Old_age Always - 37 (0 25 0 0 0)
195 Hardware_ECC_Recovered 0x001a 034 009 000 Old_age Always - 110844167
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 35239 -
# 2 Extended offline Completed without error 00% 33666 -
# 3 Extended offline Completed without error 00% 33647 -
# 4 Extended offline Completed without error 00% 33640 -
# 5 Extended offline Completed without error 00% 33621 -
# 6 Extended offline Completed without error 00% 21792 -
# 7 Extended offline Completed without error 00% 21773 -
# 8 Extended offline Completed without error 00% 12521 -

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

könnte es mit diesem beiden Bildern zusammenhängen `?

fireon · Oct 8, 2017

Wie du in deinem Output siehst hast du Fehler auf der Platte

1 Raw_Read_Error_Rate 0x000f 080 063 044 Pre-fail Always - 110844167
1 Raw_Read_Error_Rate 0x000f 106 099 006 Pre-fail Always - 12234381
# 6 Extended offline Completed: read failure 40% 49535 4060750387
# 7 Extended offline Completed: read failure 40% 49516 4060750387

CRC scheint OK zu sein... die eine Platte läuft auch schon fast 6 Jahre. Also Platten raus, was gescheites rein. Würd hier mindestens 4 Platten im Raid10 nehmen, damit was weiter geht. Und vor allem 4 gleiche, nicht verschiedene Typen.

Pfann · Oct 8, 2017

aw backe alle daten sind dann wohl weg. Naja aber besser als ein root zu haben , der nur abspackt ^^

Dann werde ich mit mit hetzner in verbindung setzen. Vielen Dank für deine Hilfe

Pfann · Oct 12, 2017

Hello again ^^

Also der Provider hat NICHTS festgestellt. Mir ist nun bei Tests aufgefallen, Dass wenn ich einen wget download direkt mit der Proxmoxmaschine durchführe, gibt es keinerlei Probleme.

jedoch mache ich es mit einen der Vserver bricht derjenige zusammen.
z.b. der Linux Vserver mit Debian8, am Anfang 100MB/s nach ca 3 minuten 2MB/s schwangend von 500 kb/s - 2 MB/s

Die Festplatte kann also kein Problem darstellen. Ich vermute es wird an irgend einer Einstellung von Proxmox liegen.

Hat jemand eine Idee?

fireon · Oct 12, 2017

Die Festplatten haben doch eindeutig Fehler. Schau dir doch deine eigenen Screenshots an. RawReadErrorrate hat 113140881 das sollte wenn möglich bei 0 sein. Also Fazit: HDD hat Fehler. Hier die Erklärung dafür: https://www.pcwelt.de/tipps/Diese_S.M.A.R.T.-Daten_sind_wichtig-Festplatten-8217564.html
Dein Wert hier ist z.B. schon gesunken von 80 auf 63. Und das war nur ein Beispiel. Solltest vielleicht den Provider wechseln

udo · Oct 12, 2017

Pfann said:
Hello again ^^

Also der Provider hat NICHTS festgestellt. Mir ist nun bei Tests aufgefallen, Dass wenn ich einen wget download direkt mit der Proxmoxmaschine durchführe, gibt es keinerlei Probleme.

jedoch mache ich es mit einen der Vserver bricht derjenige zusammen.
z.b. der Linux Vserver mit Debian8, am Anfang 100MB/s nach ca 3 minuten 2MB/s schwangend von 500 kb/s - 2 MB/s

Die Festplatte kann also kein Problem darstellen. Ich vermute es wird an irgend einer Einstellung von Proxmox liegen.

Hat jemand eine Idee?

Hi,
wenn ich es richtig sehe sind alle deine VMs auf einer Platte: sdb!
Das heisst, die stellt nur eine (kleine) Menge IO zur Verfügung. Nutzt nur eine VM IO ist alles schick - kommen andere dazu bricht die Performance ein (Kopf muss ständig hin und her).

Dein pveperf-test nutzte sinnigerweise die System-Platte; sagt also nicht viel aus.
Besser wäre ein "pveperf /mnt/media/sdb1/vz"

guck mal mit atop (apt install atop) wo der Flaschenhals im Betrieb ist - ich wette die Disk.

Udo

Pfann · Oct 12, 2017

Ja alle vserver laufen auf sdb, hatte vorher einen auf sda laufen, hatte aber auch keine grpßartige verbesserung erzielt.

CPU BOGOMIPS: 76806.00
REGEX/SECOND: 1115397
HD SIZE: 2750.54 GB (/dev/sdb1)
BUFFERED READS: 74.48 MB/sec
AVERAGE SEEK TIME: 60.72 ms
FSYNCS/SECOND: 14.54
DNS EXT: 19.58 ms
DNS INT: 81.47 ms (pfanns-gaming.de)

fireon · Oct 13, 2017

Pfann said:
FSYNCS/SECOND: 14.54

Ohne Worte

Pfann · Oct 14, 2017

-naja habs aufgegeben. bin dabei backup zu machen, nur habe ich mich aus dem linux vserver ausgesperrt der gaugelt vor er sein nicht im internet, putty geht nicht, ping google.de geht nicht apt-get install geht nicht. ^^

Sobald die
Backups fertig sind, werde ich neue festplatten einbauen lassen.

Vielen Dank für eure Hilfe.

Search

Search

Festplatten Problem.

Pfann

New Member

fireon

Distinguished Member

Pfann

New Member

Pfann

New Member

fireon

Distinguished Member

Pfann

New Member

fireon

Distinguished Member

Pfann

New Member

fireon

Distinguished Member

Pfann

New Member

fireon

Distinguished Member

Pfann

New Member

Pfann

New Member

fireon

Distinguished Member

udo

Distinguished Member

Pfann

New Member

fireon

Distinguished Member

Pfann

New Member

We value your privacy