heimlich schon, OS X ist doch ein BSD derivat
log files liegen üblicherweise in /var/log …
entweder mal das system.log, kernel.log oder die firewall log angucken.
/var/log/mount.today (nur eine Seite, irgendwie kann ich in der Shell im WEbGUI nicht hochscrollen)
Standard 19:44:06.171849 +0100 KernelEventAgent tid 54485244 received event(s) VQ_NOTRESP (1)
Standard 19:44:06.392310 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:06.392315 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:06.392320 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:06.392324 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:06.392789 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: is alive again
Standard 19:44:06.172601 +0100 KernelEventAgent tid 54485244 received event(s) VQ_NOTRESP (1)
Standard 19:44:07.485028 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:07.264680 +0100 KernelEventAgent tid 54485244 received event(s) VQ_NOTRESP (1)
Standard 19:44:07.485411 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: is alive again
Standard 19:44:07.265339 +0100 KernelEventAgent tid 54485244 received event(s) VQ_NOTRESP (1)
Standard 19:44:07.506833 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:07.286633 +0100 KernelEventAgent tid 54485244 received event(s) VQ_NOTRESP (1)
Standard 19:44:07.506854 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:07.507483 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: is alive again
Standard 19:44:07.287182 +0100 KernelEventAgent tid 54485244 received event(s) VQ_NOTRESP (1)
Standard 19:44:07.527524 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:07.307180 +0100 KernelEventAgent tid 54485244 received event(s) VQ_NOTRESP (1)
Standard 19:44:07.527540 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:07.307379 +0100 KernelEventAgent tid 54485244 type 'nfs', mounted on '/Volumes/NAS-Bilder', from '192.168.2.100:/mnt/NAS-Bilder', not responding
Standard 19:44:07.527935 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: is alive again
Standard 19:44:07.307846 +0100 KernelEventAgent tid 54485244 found 1 filesystem(s) with problem(s)
Standard 19:44:07.307975 +0100 KernelEventAgent tid 54485244 received event(s) VQ_NOTRESP (1)
Standard 19:44:07.548863 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:07.548880 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:07.549305 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: is alive again
Standard 19:44:07.328977 +0100 KernelEventAgent tid 54485244 received event(s) VQ_NOTRESP (1)
Standard 19:44:07.329291 +0100 KernelEventAgent tid 54485244 received event(s) VQ_NOTRESP (1)
Standard 19:44:07.570187 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:07.349843 +0100 KernelEventAgent tid 54485244 received event(s) VQ_NOTRESP (1)
Standard 19:44:07.350050 +0100 KernelEventAgent tid 54485244 type 'nfs', mounted on '/Volumes/NAS-Bilder', from '192.168.2.100:/mnt/NAS-Bilder', not responding
Standard 19:44:07.570630 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: is alive again
Standard 19:44:07.350591 +0100 KernelEventAgent tid 54485244 found 1 filesystem(s) with problem(s)
Standard 19:44:07.350750 +0100 KernelEventAgent tid 54485244 received event(s) VQ_NOTRESP (1)
Standard 19:44:07.591534 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:07.371193 +0100 KernelEventAgent tid 54485244 received event(s) VQ_NOTRESP (1)
Standard 19:44:07.591548 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:07.591968 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: is alive again
Standard 19:44:07.371748 +0100 KernelEventAgent tid 54485244 received event(s) VQ_NOTRESP (1)
Standard 19:44:13.652408 +0100 opendirectoryd Client: <private>, UID: 0, EUID: 0, GID: 0, EGID: 0
Standard 19:44:13.652810 +0100 opendirectoryd Client: <private>, UID: 0, EUID: 0, GID: 20, EGID: 20
Standard 19:44:13.653675 +0100 opendirectoryd Client: <private>, UID: 502, EUID: 502, GID: 20, EGID: 20
Standard 19:44:13.669025 +0100 opendirectoryd Client: <private>, UID: 502, EUID: 502, GID: 20, EGID: 20
Standard 19:44:16.313689 +0100 CommCenter #watchdog #I Callback Watchdog: checkin 7046
Standard 19:44:16.313809 +0100 CommCenter #watchdog #I Server Watchdog: checkin 7046
Standard 19:44:18.391536 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:18.171681 +0100 KernelEventAgent tid 54485244 received event(s) VQ_NOTRESP (1)
Standard 19:44:18.391550 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:18.391555 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:18.391560 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:18.391996 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: is alive again
Standard 19:44:18.172608 +0100 KernelEventAgent tid 54485244 received event(s) VQ_NOTRESP (1)
Standard 19:44:23.681638 +0100 opendirectoryd Client: <private>, UID: 0, EUID: 0, GID: 0, EGID: 0
Standard 19:44:23.682059 +0100 opendirectoryd Client: <private>, UID: 0, EUID: 0, GID: 20, EGID: 20
Standard 19:44:23.682656 +0100 opendirectoryd Client: <private>, UID: 502, EUID: 502, GID: 20, EGID: 20
Standard 19:44:23.695596 +0100 opendirectoryd Client: <private>, UID: 502, EUID: 502, GID: 20, EGID: 20
Standard 19:44:31.314232 +0100 CommCenter #watchdog #I Callback Watchdog: checkin 7047
Standard 19:44:31.314356 +0100 CommCenter #watchdog #I Server Watchdog: checkin 7047
Standard 19:44:33.705872 +0100 opendirectoryd Client: <private>, UID: 0, EUID: 0, GID: 0, EGID: 0
Standard 19:44:33.706860 +0100 opendirectoryd Client: <private>, UID: 0, EUID: 0, GID: 20, EGID: 20
Standard 19:44:33.707697 +0100 opendirectoryd Client: <private>, UID: 502, EUID: 502, GID: 20, EGID: 20
Standard 19:44:33.720770 +0100 opendirectoryd Client: <private>, UID: 502, EUID: 502, GID: 20, EGID: 20
Standard 19:44:36.776927 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: is alive again
Standard 19:44:36.777008 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: is alive again
Standard 19:44:36.777047 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: is alive again
Standard 19:44:36.777105 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: is alive again
Standard 19:44:37.397761 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:37.398216 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: is alive again
Standard 19:44:37.179283 +0100 KernelEventAgent tid 54485244 received event(s) VQ_NOTRESP (1)
Standard 19:44:38.393015 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:38.393027 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:38.393031 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:38.393034 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:38.393038 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:38.393050 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:38.393054 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:38.393058 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:38.393062 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:38.393066 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: not responding
Standard 19:44:38.393390 +0100 kernel nfs server 192.168.2.100:/mnt/NAS-Bilder: is alive again
Standard 19:44:38.175297 +0100 KernelEventAgent tid 54485244 received event(s) VQ_NOTRESP (1)
Ich versteh das System nicht. Wenn der Mac meckert, das "192.168.2.100:/mnt/NAS-Bilder: not responding" ist, okay. Aber das der Server selbst diese Meldung in sein Protokoll schreibt, wieso? Kann das was mit geparkten HDDs zu tun haben? Wenn ja, die parken erst nach einer Stunde. Und nach dem versuchtenZugriff höre ich wie die HDD hochfährt. Dann höre ich sie steppen. Wieso dann die Meldung "not responding"?
Th.