weird hard disk error - ideas?

b0fh666

macrumors 6502a
Original poster
Oct 12, 2012
903
647
south
first time this happens - 2012 15" CMBP, disk is in the optibay (for years).

2/20/15 8:08:51.000 PM kernel[0]: disk4: no such device.
2/20/15 8:08:51.000 PM kernel[0]: disk4: no such device.
2/20/15 8:08:51.000 PM kernel[0]: jnl: disk4: do_jnl_io: strategy err 0x6
2/20/15 8:08:51.000 PM kernel[0]: jnl: disk4: write_journal_header: error writing the journal header!
2/20/15 8:08:51.000 PM kernel[0]: disk4: media is not present.

lots of repeated media not present messages then finally

2/20/15 8:08:52.000 PM kernel[0]: hfs: unmount initiated on Diamond XD on device disk4
2/20/15 8:08:52.000 PM kernel[0]: jnl: disk4: close: journal 0xffffff8042b3aa80, is invalid. aborting outstanding transactions


and the 'disk not ejected properly' message.

ideas? I was backing up a bunch of VMs to an external disk, but the failure was in the internal one.

failing HD, probably... how to check for that? working just fine after a reboot.
 

Bomb Bloke

macrumors regular
Feb 12, 2015
222
6
Tasmania (AU)
Quite simply, the system is saying that it could no longer physically locate the drive holding the "Diamond XD" volume.

This could indicate a problem with the drive, or the cable connecting it, or the connectors attaching it, or the BUS... Usually a failing drive will start to generate I/O errors rather than simply "disappearing entirely", so I'd be more inclined to blame the leads.
 

b0fh666

macrumors 6502a
Original poster
Oct 12, 2012
903
647
south
banged up the laptop around, no issues. never had a prob with this optibay in years, so... dunno.

wondering if it is another yo-seh-mite bug, as the disks were transferring @ 60mbps-ish at the time it failed.
 

yjchua95

macrumors 604
Apr 23, 2011
6,725
230
GVA, KUL, MEL (current), ZQN
banged up the laptop around, no issues. never had a prob with this optibay in years, so... dunno.

wondering if it is another yo-seh-mite bug, as the disks were transferring @ 60mbps-ish at the time it failed.
Nah, it just happened to fail.

Such failures can have no symptoms, like your case. They just happen out of the blue.
 

b0fh666

macrumors 6502a
Original poster
Oct 12, 2012
903
647
south
oddly, it did not ever happened again. quite sure it was a software glitch.

yose mite eh.