En un sistema Mac OS X 10.7.5 (Lion) con dos unidades SATA internas, las unidades internas se conectan mediante un controlador Highpoint Rocketraid y se configuran sin ningún RAID, por lo que funcionan en modo heredado.
Las dos unidades de disco duro SATA conectadas localmente no se montan después de que el Mac se enciende después de un corte / interrupción de la alimentación (apagado impuro). En el siguiente reinicio limpio, se montan los dos volúmenes locales.
Cuando la unidad / volumen no tiene actividad de lectura / escritura, el volumen no se monta. En caso de que no haya actividad de E / S en la unidad / volumen, la unidad / volumen se montará.
Ambos volúmenes locales son idénticos:
$ diskutil info disk2s1
Device Identifier: disk2s1
Device Node: /dev/disk2s1
Part of Whole: disk2
Device / Media Name: Untitled 1
Volume Name: A
Escaped with Unicode: A
Mounted: Yes
Mount Point: /Volumes/A
Escaped with Unicode: /Volumes/A
File System Personality: HFS+
Type (Bundle): hfs
Name (User Visible): Mac OS Extended
Owners: Enabled
Partition Type: Apple_HFS
OS Can Be Installed: No
Media Type: Generic
Protocol: SCSI
SMART Status: Not Supported
Volume UUID: 45D248ED-29E3-3344-8B62-4E43499568CE
Total Size: 3.0 TB (3000592979456 Bytes) (exactly 5860533163 512-Byte-Blocks)
Volume Free Space: 3.0 TB (2997719433216 Bytes) (exactly 5854920768 512-Byte-Blocks)
Device Block Size: 512 Bytes
Read-Only Media: No
Read-Only Volume: No
Ejectable: Yes
Whole: No
Internal: No
Registro parcial:
Jul 12 10:32:48 nl3 kernel[0]: jnl: disk3s2: replay_journal: from: 4367872 to: 5375488 (joffset 0x1c3000)
Jul 12 10:32:48 nl3 kernel[0]: jnl: disk3s2: journal replay done.
Jul 12 10:32:49 nl3 kernel[0]: hfs: Removed 0 orphaned / unlinked files and 329 directories
Jul 12 15:26:15 nl3 kernel[0]: disk3s2: device/channel is not attached.
Jul 12 15:26:15 nl3 kernel[0]: /Volumes/Time Machine] [FSLogMsgID 381179371] [FSLogMsgOrder Last]
Jul 12 15:26:15 nl3 kernel[0]: disk3s2: device/channel is not attached.
Jul 12 15:26:15: --- last message repeated 10 times ---
Jul 12 15:26:15 nl3 kernel[0]: jnl: disk3s2: do_jnl_io: strategy err 0x6
Jul 12 15:26:15 nl3 kernel[0]: jnl: disk3s2: write_journal_header: error writing the journal header!
Jul 12 15:26:15 nl3 kernel[0]: disk3s2: device/channel is not attached.
Jul 12 15:26:15: --- last message repeated 48 times ---
Jul 12 15:26:15 nl3 kernel[0]: 2309.inProgress/.Backup.363792189.590451.log] [FSLogMsgID 662186116] [FSLogMsgOrder Last]
Jul 12 15:26:15 nl3 kernel[0]: disk3s2: device/channel is not attached.
Jul 12 15:26:16: --- last message repeated 76 times ---
Jul 12 15:26:16 nl3 kernel[0]: 0451.log] [FSLogMsgID 860380055] [FSLogMsgOrder Last]
Jul 12 15:26:16 nl3 kernel[0]: disk3s2: device/channel is not attached.
Jul 12 15:26:20: --- last message repeated 56 times ---
Jul 12 15:26:20 nl3 kernel[0]: disk3s2: media is not present.
Jul 12 15:26:20: --- last message repeated 7 times ---
Jul 12 15:26:20 nl3 kernel[0]: jnl: disk3s2: close: journal 0x602ed30, is invalid. aborting outstanding transactions
Jul 12 15:29:00 nl3 kernel[0]: jnl: disk3s2: replay_journal: from: 4588544 to: 4118528 (joffset 0x1d9000)
Jul 12 15:29:01 nl3 kernel[0]: jnl: disk3s2: journal replay done.
Jul 12 15:47:16 nl3 kernel[0]: jnl: disk3s2: do_jnl_io: strategy err 0xdisk3s2: device/channel is not attached.
Jul 12 15:47:16 nl3 kernel[0]: 6
Jul 12 15:47:16 nl3 kernel[0]: jnl: disk3s2: write_journal_header: error writing the journal header!
Jul 12 15:47:16 nl3 kernel[0]: disk3s2: device/channel is not attached.
Jul 12 15:47:24: --- last message repeated 15 times ---
Jul 12 15:47:24 nl3 kernel[0]: disk3s2: media is not present.
Jul 12 15:47:24: --- last message repeated 18 times ---
Jul 12 15:47:24 nl3 kernel[0]: jnl: disk3s2: close: journal 0x602ed30, is invalid. aborting outstanding transactions
/dev/rdisk3s2: fsck_hfs run at Thu Jul 12 15:55:59 2012
/dev/rdisk3s2: ** /dev/rdisk3s2 (NO WRITE)
/dev/rdisk3s2: Executing fsck_hfs (version diskdev_cmds-540.1~25).
QUICKCHECK ONLY; FILESYSTEM DIRTY
/dev/rdisk3s2: fsck_hfs run at Thu Jul 12 15:55:59 2012
/dev/rdisk3s2: ** /dev/rdisk3s2
/dev/rdisk3s2: Executing fsck_hfs (version diskdev_cmds-540.1~25).
/dev/rdisk3s1: fsck_hfs run at Thu Jul 12 16:01:55 2012
/dev/rdisk3s1: ** /dev/rdisk3s1 (NO WRITE)
/dev/rdisk3s1: Executing fsck_hfs (version diskdev_cmds-540.1~25).
QUICKCHECK ONLY; FILESYSTEM CLEAN
Y ambas unidades tienen un esquema de partición GUID y un sistema de archivos HFS + idénticos:
$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
...
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *3.0 TB disk1
1: Apple_HFS J 3.0 TB disk1s1
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *3.0 TB disk2
1: Apple_HFS A 3.0 TB disk2s1
¿Cómo montar automáticamente estos discos duros automáticamente después de un cierre impuro?