Originally Posted By: Virtual1
Interesting my vsdbutil crc is different than yours. I wonder if apple bundled a bad build with server?

apple:~ virtual1 $ md5 -q /Volumes/Service\ Snow/usr/sbin/vsdbutil
6a1a6785606dbe0ac6981f4667a182af

or yours is different wink 10.6.3 here.

Mine is from a very recent Macbook Pro (core i7).
sw_vers
ProductName: Mac OS X
ProductVersion: 10.6.3
BuildVersion: 10D2094


Those two vsdbutil binaries seem nearly identical, but mine is almost a day newer:

-r-xr-xr-x 1 root wheel 76528 Feb 10 23:41 /usr/sbin/vsdbutil <--- yours
-r-xr-xr-x 1 root wheel 76528 Feb 11 17:05 /usr/sbin/vsdbutil <--- mine



Originally Posted By: Virtual1
Since the checksums are the same in server and client, it's not the binary. It works on all the clients, and does NOT work on hard drives attached to server (so no db issue?), and this is the only server I have to test so maybe this server install is broken? Anyone else with SL server? Either that or a framework in server is broken?

Okay yes, that suggests the binary can be ruled out then maybe (though our differing checksums remain a curiosity).

I'm not so sure your db there is in perfect shape though. Note the empty line #1 :
Code:
apple:~ virtual1 $ cat -ntv /var/db/volinfo.database
     1	
     2	D7365339BB07C1C3: 00000001
     3	EB0C229CE388595C: 00000001
     4	54DCC8B44C0DB324: 00000001

No biggie perhaps... i just never seen line #1 blank like that before.

It may be worth it to erase (rm) that /var/db/volinfo.database file completely, and then fully reinitialize it via:

sudo vsdbutil -i

[if that fails... we gain another "clue" wink and you can always resort to the diskutil method to rebuild it.]

Last edited by Hal Itosis; 05/22/10 11:10 PM.