[10.10 Yosemite] Bug mit eSATA?

[Wuchtbrumme]

Hallo, seit gestern (=seit 10.10.3) unmountet sich eine externe Festplatte ständig. Ist natürlich auch möglich, dass sie in just diesem Augenblick über den Jordan gegangen ist, aber das halte ich zumindest für unwahrscheinlich. Angeschlossen war sie mittels eSATA an einem CalDigit Thunderbolt 2 Dock (meine Bezeichnung). Jetzt habe ich sie probeweise mittels FW800 angeschlossen, das scheint bis jetzt zu gehen.

11.04.15 01:00:15,000 kernel[0]: hfs: mounted MyBook on device disk3s2
11.04.15 01:00:15,850 fseventsd[61]: event logs in /Volumes/MyBook/.fseventsd out of sync with volume.  destroying old logs. (1841884 2 1841884)
11.04.15 01:00:15,877 fseventsd[61]: log dir: /Volumes/MyBook/.fseventsd getting new uuid: DA38F7EF-431C-4709-AF73-476C12AA3792
11.04.15 03:08:57,000 kernel[0]: hfs: err 6 reading VH blk (vol=MyBook)
11.04.15 03:08:57,000 kernel[0]: hfs: err 6 reading VH blk (vol=MyBook)
11.04.15 03:08:57,000 kernel[0]: hfs: unmount initiated on MyBook on device disk3s2
11.04.15 03:08:57,000 kernel[0]: hfs: err 6 reading VH blk (vol=MyBook)
11.04.15 03:08:57,000 kernel[0]: disk3s2: media is not present.
11.04.15 03:08:57,000 kernel[0]: disk3s2: media is not present.
11.04.15 03:08:57,000 kernel[0]: disk3s2: media is not present.
11.04.15 03:08:57,000 kernel[0]: disk3s2: media is not present.
11.04.15 03:08:57,000 kernel[0]: disk3s2: media is not present.
11.04.15 03:08:57,000 kernel[0]: hfs: unmount initiated on MyBook on device disk3s2
11.04.15 03:08:57,000 kernel[0]: disk3s2: media is not present.
11.04.15 03:08:57,000 kernel[0]: hfs: err 6 reading VH blk (vol=MyBook)
11.04.15 03:08:57,000 kernel[0]: disk3s2: media is not present.
11.04.15 03:08:57,000 kernel[0]: jnl: disk3s2: do_jnl_io: strategy err 0x6
11.04.15 03:08:57,000 kernel[0]: jnl: disk3s2: write_journal_header: error writing the journal header!
11.04.15 03:08:57,580 fseventsd[61]: disk logger: failed to open output file /Volumes/MyBook/.fseventsd/00000000003769f0 (No such file or directory). mount point /Volumes/MyBook/.fseventsd
11.04.15 03:08:57,580 fseventsd[61]: disk logger: failed to open output file /Volumes/MyBook/.fseventsd/00000000003769f0 (No such file or directory). mount point /Volumes/MyBook/.fseventsd
/Volumes/MyBook/.fseventsd/00000000003769f0 (No such file or directory). mount point /Volumes/MyBook/.fseventsd
11.04.15 03:08:57,580 fseventsd[61]: disk logger: failed to open output file /Volumes/MyBook/.fseventsd/00000000003769f0 (No such file or directory). mount point /Volumes/MyBook/.fseventsd
11.04.15 03:08:58,979 sandboxd[361]: ([248]) mds_stores(248) deny file-read-data /Volumes/MyBook/.Spotlight-V100/Store-V2
11.04.15 03:08:59,135 sandboxd[361]: ([248]) mds_stores(248) deny file-read-data /Volumes/MyBook/.Spotlight-V100/Store-V2
11.04.15 03:08:59,312 sandboxd[361]: ([248]) mds_stores(248) deny file-read-data /Volumes/MyBook/.Spotlight-V100/Store-V2
11.04.15 03:08:59,465 sandboxd[361]: ([248]) mds_stores(248) deny file-read-data /Volumes/MyBook/.Spotlight-V100/Store-V2

11.04.15 03:08:58,979 sandboxd[361]: ([248]) mds_stores(248) deny file-read-data /Volumes/MyBook/.Spotlight-V100/Store-V2
11.04.15 03:08:59,135 sandboxd[361]: ([248]) mds_stores(248) deny file-read-data /Volumes/MyBook/.Spotlight-V100/Store-V2
11.04.15 03:08:59,312 sandboxd[361]: ([248]) mds_stores(248) deny file-read-data /Volumes/MyBook/.Spotlight-V100/Store-V2
11.04.15 03:08:59,465 sandboxd[361]: ([248]) mds_stores(248) deny file-read-data /Volumes/MyBook/.Spotlight-V100/Store-V2
11.04.15 07:11:44,000 kernel[0]: hfs: mounted MyBook on device disk3s2
11.04.15 07:11:44,817 fseventsd[61]: event logs in /Volumes/MyBook/.fseventsd out of sync with volume.  destroying old logs. (3618 0 22289)
11.04.15 07:11:46,613 fseventsd[61]: log dir: /Volumes/MyBook/.fseventsd getting new uuid: A3273D5C-EA4B-4483-823C-2820A1880082
11.04.15 07:12:27,000 kernel[0]: hfs: unmount initiated on MyBook on device disk3s2
11.04.15 07:12:39,000 kernel[0]: hfs: mounted MyBook on device disk3s2
11.04.15 07:12:44,000 kernel[0]: hfs: unmount initiated on MyBook on device disk3s2
11.04.15 07:12:57,000 kernel[0]: hfs: mounted MyBook on device disk3s2
11.04.15 07:12:57,442 fseventsd[61]: Events arrived for /Volumes/MyBook after an unmount request! Re-initializing.
11.04.15 07:12:57,442 fseventsd[61]: creating a dls for /Volumes/MyBook but it already has one...
11.04.15 07:13:00,000 kernel[0]: hfs: unmount initiated on MyBook on device disk3s2
11.04.15 07:13:01,053 fseventsd[61]: disk logger: failed to open output file /Volumes/MyBook/.fseventsd/000000000040d1e8 (No such file or directory). mount point /Volumes/MyBook/.fseventsd
11.04.15 07:13:01,053 fseventsd[61]: disk logger: failed to open output file /Volumes/MyBook/.fseventsd/000000000040d1e8 (No such file or directory). mount point /Volumes/MyBook/.fseventsd
11.04.15 07:13:01,000 kernel[0]: hfs: mounted MyBook on device disk3s2
11.04.15 09:00:34,000 kernel[0]: hfs: err 6 reading VH blk (vol=MyBook)
11.04.15 09:00:34,000 kernel[0]: hfs: err 6 reading VH blk (vol=MyBook)
11.04.15 09:00:34,000 kernel[0]: hfs: err 6 reading VH blk (vol=MyBook)
11.04.15 09:00:34,000 kernel[0]: hfs: err 6 reading VH blk (vol=MyBook)
11.04.15 09:00:35,000 kernel[0]: hfs: unmount initiated on MyBook on device disk3s2
11.04.15 09:04:04,000 kernel[0]: hfs: mounted MyBook on device disk3s2
11.04.15 09:04:04,795 fseventsd[61]: event logs in /Volumes/MyBook/.fseventsd out of sync with volume.  destroying old logs. (5041 0 6665)
11.04.15 09:04:06,413 fseventsd[61]: log dir: /Volumes/MyBook/.fseventsd getting new uuid: 7DC3F8D6-E87B-4D7B-8386-337EA2BEAC09
11.04.15 09:04:52,000 kernel[0]: hfs: unmount initiated on MyBook on device disk3s2
11.04.15 09:04:52,956 fseventsd[61]: disk logger: failed to open output file /Volumes/MyBook/.fseventsd/000000000043bd21 (No such file or directory). mount point /Volumes/MyBook/.fseventsd
11.04.15 09:04:52,956 fseventsd[61]: disk logger: failed to open output file /Volumes/MyBook/.fseventsd/000000000043bd21 (No such file or directory). mount point /Volumes/MyBook/.fseventsd
11.04.15 09:04:57,000 kernel[0]: hfs: mounted MyBook on device disk3s2
11.04.15 09:04:59,000 kernel[0]: hfs: unmount initiated on MyBook on device disk3s2
11.04.15 09:04:59,910 fseventsd[61]: disk logger: failed to open output file /Volumes/MyBook/.fseventsd/000000000043bdf5 (No such file or directory). mount point /Volumes/MyBook/.fseventsd
11.04.15 09:04:59,910 fseventsd[61]: disk logger: failed to open output file /Volumes/MyBook/.fseventsd/000000000043bdf5 (No such file or directory). mount point /Volumes/MyBook/.fseventsd
11.04.15 09:05:30,000 kernel[0]: hfs: mounted MyBook on device disk3s2
11.04.15 09:05:53,000 kernel[0]: hfs: unmount initiated on MyBook on device disk3s2
11.04.15 09:06:11,000 kernel[0]: hfs: mounted MyBook on device disk3s2
11.04.15 09:06:11,488 fseventsd[61]: Events arrived for /Volumes/MyBook after an unmount request! Re-initializing.
11.04.15 09:06:11,489 fseventsd[61]: creating a dls for /Volumes/MyBook but it already has one...
11.04.15 09:06:14,000 kernel[0]: hfs: unmount initiated on MyBook on device disk3s2
11.04.15 09:06:14,472 fseventsd[61]: disk logger: failed to open output file /Volumes/MyBook/.fseventsd/000000000043cd96 (No such file or directory). mount point /Volumes/MyBook/.fseventsd
11.04.15 09:06:14,473 fseventsd[61]: disk logger: failed to open output file /Volumes/MyBook/.fseventsd/000000000043cd96 (No such file or directory). mount point /Volumes/MyBook/.fseventsd
11.04.15 09:06:14,000 kernel[0]: hfs: mounted MyBook on device disk3s2

Test mit dem Festplattendienstprogramm ergab nichts. Hat jemand zufällig dasselbe Verhalten am eSATA-Anschlusss des CalDigit-Docks unter 10.10.3?

 

[markthenerd]

11.04.15 03:08:57,000 kernel[0]: hfs: err 6 reading VH blk (vol=MyBook)

11.04.15 03:08:57,000 kernel[0]: hfs: unmount initiated on MyBook on device disk3s2

11.04.15 03:08:57,580 fseventsd[61]: disk logger: failed to open output file /Volumes/MyBook/.fseventsd/00000000003769f0 (No such file or directory). mount point /Volumes/MyBook/.fseventsd

U. s. w.

Sind das die Fehlermeldungen des sich "unmountenden" Gerätes? Falls ja würde ich unsere Meinungsdifferenzen betreffend WD Komplettprodukten nachvollziehen können.

Weitere Mutmassungen: Dass eine Schnittstelle eines Gerätes mit mehreren unterschiedlichen Probleme macht, kommt nach meinem Wissensstand vor allem bei Komplettprodukten immer mal wieder vor.

OS X würde ich die Schuld nicht zuzuweisen. Höchstens sekundär.

 

[Wuchtbrumme]

ok, mir ist noch aufgefallen, dass ich im Energiesparen "Festplatten ausschalten wenn möglich" angetickert hatte, das habe ich mal rausgenommen, weil sich die Kröte eh selbst ausschaltet.