Getting the error that you cannot import a foreign disk? Looked in the Event Viewer’s System Log to find: “A disk group with the specified name already exists”? Not to worry! There is a solution, it just isn’t obvious.
This requires some general comfort with regedt32.exe, and I have only done this under Windows XP Pro.
Fire Up regedt32.exe.
Navigate to : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\dmio\Boot Info
Right-mouse click on “Primary Disk Group” and select “delete” to remove it.
Quit the registry editor.
Reboot the machine.
Once the machine comes back up, you can go in to “Disk management” and successfully import the foreign disk.
Hit a peculiar problem today with a new Solaris 10 T2000 and our NetApp FAS3020. While the right users had the right access to the volumes mounted from the NetApp, directory listings showed the directories and files owned by “nobody” with the group “nobody”.
With older version of NFS, this usually meant that the filesystem was not exported with read/write access to the host, but, since this had already been done quite some time ago, it looked like the problem was related to NFSv4.  Some quick investigation showed this to be the case.
The resolution was two fold:
 On the Netapp, I make sure that “nfs.v4.id.domain” was set to the domain name. It defaults to nothing “”.
Again, on the Netapp, since we are not using a centralized location for accounts (we have < 12 accounts across all of the systems), I had to populate /etc/passwd with all of the accounts on the rest of the systems and /etc/group with all of the groups defined on the rest of the systems.
That brought the behavior back to what was expected.
Having had past success with yum upgrades for Fedora under the i386 install, I thought I would give it a whirl with my x86_64 installations. The YumUpgradeFaq points out that the yum upgrade process is very straight forward, and this was, indeed, what I followed before.
I ran in to the problem where the elfutils package came up as a conflict, as outlined in the comments here, here (post #5), and here. The last link had a “hackish” way of making it work, but, after some fighting and a little bit of panic, I can say that it doesn’t really work and it just isn’t worth the hassle.
It seems that the only sure-fire way to perform an upgrade would be to use the DVD or CD set to upgrade. Yum still hasn’t caught up to the x86_64 world just yet.
Be aware, though, that an upgrade will take a very long time. Seriously consider the idea of backing up your important configuration files and just performing a clean install.