DS412+ lässt Finder von Mac OS X 10.8.2 abstürzen -Hilfe-

[Darkdevil]

Habe gestern meine DS412+ in Betrieb genommen.
Allerdings wird meine Freude dadurch getrübt, dass es mir seitdem regelmäßig den Finder zerschießt und zwar so stark, dass ich diesen nicht mehr neu starten kann und das MacBook Pro neu starten muss

Ich bin wirklich ratlos.
In der linken Finder-Spalte unter "Freigaben" erscheint die DiskStation. Ich klicke ein bischen durch die Ordner. Öffne ein paar Dateien und dann auf einmal nach ca. 5-10 Min. erscheint der Sat1-Ball und
der Finder ist hinüber. cmd+alt+esc = finder reagiert nicht mehr. Also klicke ich auf Finder neu starten. Allerdings kann Mac OS X dann den Finder nicht mehr neu starten.
Ergo Neustart.

DSM ist neu installiert worden. 4.1-2668

Kann sich das jemand erklären was da los ist? Einstellungsfehler? Bug?
SO habe ich mir das ganze nicht vorgestellt.

 

[amarthius]

Verbindest du dich per AFP oder SMB? Lässt es sich auf ein bestimmten Ordner, Pfadlänge oder Datei einschränken?

 

[jiraya]

Meldungen in der Konsole (Programme / Dienstprogramme)?

 

[Darkdevil]

Die Diskstation wird in der linken Finderleiste unter "Freigaben" angezeigt. Ich vermute, dass hier das AFP-Protokoll zum Einsatz kommt.
Ich habe mich auch schon mal per SMB mit cmd+k im Finder mit der Diskstation verbunden, aber das bringt mir nicht viel, weil ich dann jeden freigegebenen Ordner auf der Diskstation erst manuel
einbinden müsste. Wenn ich aber in der Finderleiste links unter Freigaben auf die DS klicke, dann erscheinen alle freigegebenen Ordner sofort und ich kann auf jeden zugreifen.

Der Finder stürzt nicht bei bestimmten Ordnern ab, da ich in verschiedenen Verzeichnissen navigiert habe und es bisher immer an den unterschiedlichsten Stellen passiert ist.

Meldung in der Konsole unter system.log hat folgende Einträge:

Feb 9 00:50:20 Alexanders-MacBook-Pro.local ReportCrash[3512]: Saved crash report for WebProcess[3236] version 8536 (8536.26.17) to /Users/rothlicht/Library/Logs/DiagnosticReports/WebProcess_2013-02-09-005020_Alexanders-MacBook-Pro.crash
Feb 9 00:50:25 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime[3522]): Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
Feb 9 00:50:25 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime[3522]): Job failed to exec(3) for weird reason: 2
Feb 9 00:50:25 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime): Job should be able to exec(3) now.
Feb 9 00:50:25 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime): Throttling respawn: Will start in 10 seconds
Feb 9 00:50:33 Alexanders-MacBook-Pro.local WebProcess[3521]: objc[3521]: Object 0x7f9351c1caf0 of class NSUserDefaults autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
Feb 9 00:50:36 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime[3523]): Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
Feb 9 00:50:36 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime[3523]): Job failed to exec(3) for weird reason: 2
Feb 9 00:50:36 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime): Job should be able to exec(3) now.
Feb 9 00:50:36 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime): Throttling respawn: Will start in 10 seconds
Feb 9 00:50:39 Alexanders-MacBook-Pro.local ReportCrash[3512]: Saved crash report for WebProcess[3521] version 8536 (8536.26.17) to /Users/rothlicht/Library/Logs/DiagnosticReports/WebProcess_2013-02-09-005039_Alexanders-MacBook-Pro.crash
Feb 9 00:50:42 Alexanders-MacBook-Pro.local com.apple.usbmuxd[649]: stopping.
Feb 9 00:50:42 Alexanders-MacBook-Pro.local com.apple.usbmuxd[3524]: usbmuxd-296.3 on Jul 25 2012 at 00:28:37, running 64 bit
Feb 9 00:50:43 Alexanders-MacBook-Pro.local NasNaviHelper[202]: execute: <NASListModeCommand: 0x4183e0> start
Feb 9 00:50:43 Alexanders-MacBook-Pro.local NasNaviHelper[202]: execute: <NASListModeCommandPrepare: 0x438eb0> start
Feb 9 00:50:43 Alexanders-MacBook-Pro.local NasNaviHelper[202]: execute: <NASListModeCommandPrepare: 0x438eb0> end
Feb 9 00:50:43 Alexanders-MacBook-Pro.local NasNaviHelper[202]: execute: <NASListModeCommandMain: 0x43a220> start
Feb 9 00:50:43 Alexanders-MacBook-Pro.local NasNaviHelper[202]: 00:1D:73:A3:33:7B
Feb 9 00:50:43 Alexanders-MacBook-Pro.local NasNaviHelper[202]: execute: <NASListModeCommandMain: 0x43a220> end
Feb 9 00:50:43 Alexanders-MacBook-Pro.local NasNaviHelper[202]: execute: <NASListModeCommandAfter: 0x439ad0> start
Feb 9 00:50:46 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime[3528]): Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
Feb 9 00:50:46 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime[3528]): Job failed to exec(3) for weird reason: 2
Feb 9 00:50:46 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime): Job should be able to exec(3) now.
Feb 9 00:50:46 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime): Throttling respawn: Will start in 10 seconds
Feb 9 00:50:46 Alexanders-MacBook-Pro.local WebProcess[3527]: objc[3527]: Object 0x7fd57841caf0 of class NSUserDefaults autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
Feb 9 00:50:53 Alexanders-MacBook-Pro.local NasNaviHelper[202]: OK. Complete to scan drives.
Feb 9 00:50:53 Alexanders-MacBook-Pro.local NasNaviHelper[202]: execute: <NASListModeCommandAfter: 0x439ad0> end
Feb 9 00:50:53 Alexanders-MacBook-Pro.local NasNaviHelper[202]: execute: <NASListModeCommand: 0x4183e0> end
Feb 9 00:50:56 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime[3534]): Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
Feb 9 00:50:56 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime[3534]): Job failed to exec(3) for weird reason: 2
Feb 9 00:50:56 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime): Job should be able to exec(3) now.
Feb 9 00:50:56 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime): Throttling respawn: Will start in 10 seconds
Feb 9 00:51:06 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime[3538]): Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
Feb 9 00:51:06 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime[3538]): Job failed to exec(3) for weird reason: 2
Feb 9 00:51:06 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime): Job should be able to exec(3) now.
Feb 9 00:51:06 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime): Throttling respawn: Will start in 10 seconds
Feb 9 00:51:13 Alexanders-MacBook-Pro.local com.apple.usbmuxd[3524]: _handle_timer heartbeat detected detach for device 0x1-192.168.1.7:0!
Feb 9 00:51:16 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime[3539]): Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
Feb 9 00:51:16 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime[3539]): Job failed to exec(3) for weird reason: 2
Feb 9 00:51:16 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime): Job should be able to exec(3) now.
Feb 9 00:51:16 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime): Throttling respawn: Will start in 10 seconds
Feb 9 00:51:26 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime[3541]): Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
Feb 9 00:51:26 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime[3541]): Job failed to exec(3) for weird reason: 2
Feb 9 00:51:26 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime): Job should be able to exec(3) now.
Feb 9 00:51:26 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime): Throttling respawn: Will start in 10 seconds
Feb 9 00:51:32 Alexanders-MacBook-Pro kernel[0]: ASP_TCP asp_tcp_usr_control: invalid kernelUseCount 0
Feb 9 00:51:32 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime): Throttling respawn: Will start in 4 seconds
Feb 9 00:51:33 Alexanders-MacBook-Pro kernel[0]: AFP_VFS afpfs_mount: /Volumes/Downloads, pid 3251
Feb 9 00:51:33 Alexanders-MacBook-Pro kernel[0]: AFP_VFS afpfs_mount : succeeded on volume 0xffffff80ff499008 /Volumes/Downloads (error = 0, retval = 0)
Feb 9 00:51:36 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime[3546]): Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
Feb 9 00:51:36 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime[3546]): Job failed to exec(3) for weird reason: 2
Feb 9 00:51:36 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime): Job should be able to exec(3) now.
Feb 9 00:51:36 Alexanders-MacBook-Pro com.apple.launchd.peruser.501[144] (filled during runtime): Throttling respawn: Will start in 10 seconds
Feb 9 00:51:43 Alexanders-MacBook-Pro.local NasNaviHelper[202]: execute: <NASListModeCommand: 0x12ada0> start
Feb 9 00:51:43 Alexanders-MacBook-Pro.local NasNaviHelper[202]: execute: <NASListModeCommandPrepare: 0x123c40> start
Feb 9 00:51:43 Alexanders-MacBook-Pro.local NasNaviHelper[202]: execute: <NASListModeCommandPrepare: 0x123c40> end
Feb 9 00:51:43 Alexanders-MacBook-Pro.local NasNaviHelper[202]: execute: <NASListModeCommandMain: 0x12a380> start
Feb 9 00:51:43 Alexanders-MacBook-Pro.local NasNaviHelper[202]: 00:1D:73:A3:33:7B
Feb 9 00:51:43 Alexanders-MacBook-Pro.local NasNaviHelper[202]: execute: <NASListModeCommandMain: 0x12a380> end
Feb 9 00:51:43 Alexanders-MacBook-Pro.local NasNaviHelper[202]: execute: <NASListModeCommandAfter: 0x12acf0> start

 

[amarthius]

Leider habe ich keine Lösung. Melde es auf jedenfall mal Synology.

Vll kannst du mal Alternativen zum Finder testen. PathFinder oder auch Fork Lift. Ich nutze mittlerweile nur noch Path Finder. Eine Demo gibts auf der Herstellerseite.

 

[Darkdevil]

Habe heute früh die DS mal neu gestartet. Seitdem hatte ich bis jetzt keinen Finder Absturz mehr. Mal sehen, ob sich nach dem DSM-Update hier etwas verhakt hatte.

 

[amarthius]

Es ist immer die Lösung die man nicht nennt Freut mich das nun wohl funktioniert.

 

[Darkdevil]

Ich nochmal,
wollte nur kurz Bescheid geben, dass es seit dem Neustart keine Finder-Abstürze mehr gegeben hat.
Da hätte ich auch früher drauf kommen können, nach dem DSM Update neu zu starten ;-)
Trotzdem danke für die Unterstützung!