Hi MacRumours,
Really, really odd one. We've had about 15 or so Macs where Macintosh HD would just disappear. That being: you hold 'Alt' on startup, and there's only the recovery partition there.
In all instances the SMART data for the hard-drive is absolutely fine, and it's happened on c/rMBPs, MBAs -- it's not affecting one specific model.
When accessing the hard-drives remotely through Linux or Windows, the Macintosh HD partition is either inaccessible or completely unmountable. After formatting and reimaging the systems, they're then absolutely fine.
We image our Mac systems through OS X server and the affected machines don't seem to have been imaged at a particular time; it's all random. So I'm not even sure if it's something on there that could have caused this. Therefore I was hoping to confirm the following:
- Has anybody heard of this issue?
- Could a recent OS X update potentially have caused the issue, and if so are there any documented threads on that which I can review?
- Is there something on the OS X base image that could somehow cause this down the line or with an update -- and if so, what should we review on the image?
Thank you for your time in reading this and if I can possibly clarify any points or upload logs, please do let me know.
Really, really odd one. We've had about 15 or so Macs where Macintosh HD would just disappear. That being: you hold 'Alt' on startup, and there's only the recovery partition there.
In all instances the SMART data for the hard-drive is absolutely fine, and it's happened on c/rMBPs, MBAs -- it's not affecting one specific model.
When accessing the hard-drives remotely through Linux or Windows, the Macintosh HD partition is either inaccessible or completely unmountable. After formatting and reimaging the systems, they're then absolutely fine.
We image our Mac systems through OS X server and the affected machines don't seem to have been imaged at a particular time; it's all random. So I'm not even sure if it's something on there that could have caused this. Therefore I was hoping to confirm the following:
- Has anybody heard of this issue?
- Could a recent OS X update potentially have caused the issue, and if so are there any documented threads on that which I can review?
- Is there something on the OS X base image that could somehow cause this down the line or with an update -- and if so, what should we review on the image?
Thank you for your time in reading this and if I can possibly clarify any points or upload logs, please do let me know.