I don't know what SMART utilities are built into Mac OS X Server, but I'd check the SMART information on the drive and see if it's busting the manufacturer's highest recommended operating temperature. The drive will tell you this if it's on a native PATA or SATA or SCSI interface, and not on a bridge chipset (most of which stomp on SMART support). If those utilities on Server are inadequate, you can install smartmontools and run: diskutil list
to get a listing of all drive devices: disk0, disk1, disk2, etc. and their volumes. Find the device that contains the volume you're having problems with and then: smartctl -s on /dev/diskX And then smartctl -a /dev/diskX I'd also recommend running an extended offline test of these drives periodically and then checking the result after the estimated time has elapsed. So that's smartctl -t long /dev/diskX after some hours follow it with: smartctl -a /dev/diskX You can also set smartd as a LaunchDaemon so it's always running (if it isn't already) and use smartd.conf to configure it for various parameters. You can have it email you when issues arise, including even, I bet (haven't tried) if you are within a degree or two of manufacturer temperature tolerance for your drives. Better to shut them down than invite damage or corruption. Chris On Mar 6, 2011, at 9:44 AM, Neil Laubenthal wrote: > > On Mar 6, 2011, at 11:12 AM, Ashley Aitken wrote: > >> >> This is not a startup volume, I always have my OS and general user data on >> different volumes (and in this case disks). > > Right . . .I must have missed that. > >> >> Comparing file numbers is a good idea but not sure where I will get that >> detail from, seems to pass quickly in most tools. > > Finder's Get Info on the folder will give you # of items and size . . .that > part was just to verify that your backup copy is actually good by checking > source and destination. Won't tell you exactly . . .but I sometimes use that > as a gross verification that the copy actually has data in it. > >> >> I don't own that but I my data is obviously worth the price - I have heard >> in the past though that it takes a lot of time and is not always successful >> (I guess that's obvious). >> >>> What you have is some sort of directory damage . . .there isn't enough >>> information to tell if the CCC copy is good . . .it likely is good but one >>> or more files (the ones that have bad directory entries on the original >>> drive) may be corrupted. >> >> Yes, this is what I was thinking too. I don't mind losing a small number of >> files (I guess). Of course, it may depend on which ones they are ;-) >> > > If you've got a good copy of the data as verified with Finder sizes . . .then > reformatting the data drive should clear up whatever is wrong. DiskWarrior > (or similar) will fix any directory errors but may not be able to recover > every file. > > > > > ----------------------------------------------- > There are only three kinds of stress; your basic nuclear stress, cooking > stress, and A$$hole stress. The key to their relationship is Jello. > > neil > > > > _______________________________________________ > MacOSX-admin mailing list > [email protected] > http://www.omnigroup.com/mailman/listinfo/macosx-admin _______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
