Disk

Warning: Nerd Content ahead...

If you go to http://dsstos.blogspot.com/ there’s an excellent presentation on data storage concepts and recommendations. It’s HDS AMS focused, but the majority of the presentation relates to general data storage. Great stuff!

This is a marketing video from HP simulating a datacenter disaster causing a fail over to a backup datacenter. People often ask me what I do for a living and for most of the time the answer I usually give doesn’t help. If the conversation continues with printer driver questions in Vista I know I failed to describe what I do. So in short, I help companies with the design, build, and implementation of large storage arrays that are designed to minimize application downtime due to hardware failures. These same storage arrays also have extended capabilities and features that help customers create enire copies of their datacenters in case thier primary datacenter gets “blowed up”. In this video, I would be one of the goofy white coat guys. Enjoy!

Today I experienced a firewire drive failure on my mini. To determine which drive was bad was a bit difficult since the apple profiler does not show serial number information about the drives and the firewire id can change depending on which drive was ready first, etc. After the experience I now have the following steps to take to make this easier in the future. The follow was done after I replaced the bad drive – There also appears to be a Disk Utility issue with disk replacements do I went the terminal window instead. mini:~ sean$ sudo su - Password: mini:~ root# diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *74.5 Gi disk0 1: EFI 200.0 Mi disk0s1 2: Apple_HFS Macintosh HD 74.2 Gi disk0s2 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *465.8 Gi disk1 1: DOS_FAT_32 SPAREY 465.6 Gi disk1s1 /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *279.5 Gi disk2 1: EFI 200.0 Mi disk2s1 2: Apple_HFS Timie 279.2 Gi disk2s2 /dev/disk3 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *931.5 Gi disk3 1: EFI 200.0 Mi disk3s1 2: Apple_RAID 931.2 Gi disk3s2 3: Apple_Boot Boot OSX 128.0 Mi disk3s3 /dev/disk4 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *931.5 Gi disk4 1: EFI 200.0 Mi disk4s1 2: Apple_HFS Untitled 1 931.2 Gi disk4s2 /dev/disk5 #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFS Hugie *931.2 Gi disk5 mini:~ root# diskutil checkraid RAID SETS ================================================================= Name: Hugie Disk Unique ID: EAA0BF40-5431-4DBF-B280-5D96983C4C18 Type: Mirror Status: Degraded Size: 999860862976 B Rebuild: automatic Device Node: disk5 Apple RAID Version: 2 Device Node UUID Status 0 disk3s2 BCE5791A-9FBC-471F-BCCB-AB0B9DB0A81E Online 0 -none- FC7931AC-A4F3-468F-AC75-F48C60EABFEF Missing/Damaged mini:~ root# diskutil repairmirror /Volume/Hugie disk4 Could not find the RAID set device node mini:~ root# diskutil repairmirror /Volumes/Hugie disk4 Note: Syncing data between mirror partitions can take a very long time. Note: The mirror should now be repairing itself. You can check its status using ‘diskutil listRAID’. mini:~ root# diskutil checkraid RAID SETS ================================================================== Name: Hugie Disk Unique ID: EAA0BF40-5431-4DBF-B280-5D96983C4C18 Type: Mirror Status: Degraded Size: 999860862976 B Rebuild: automatic Device Node: disk5 Apple RAID Version: 2 Device Node UUID Status 0 disk3s2 BCE5791A-9FBC-471F-BCCB-AB0B9DB0A81E Online 1 disk4s2 21FA4F0B-7637-40CD-B396-A2C7D64589DA 0% (Rebuilding) mini:~ root#