Thanks everybody for the swift response! I didn't consider (or know) that there was any limitations to fdisk labels. Armed with this knowledge I did some more thinking and testing and it now works. This is probably what happened:
The disk group in the disk system (a el-cheapo four years old EasyRaid X12P that we use for experiments like this) was previously configured with a 800 GB LUN at the beginning of the underlying RAID data. The disk system supports dynamic resizing so it won't destroy any data meaning that the fdisk label would be untouched. When we resized it beyond 1 TB the disk label was still there and Solaris got confused and the "cannot open" problem starts. If we resized it to less than 1 TB and rebooted, fdisk would complain that the disk geometry didn't match the disk label and would correct that. Conclusion: If there is a fdisk label on the disk Solaris will attempt to use it but if the disk is larger than 1TB it will get confused. The solution was to: 1. Resize the LUN to less than 1 TB and reboot 2. Write a bunch of NULs to the beginning of the p0 partition 3. Resize the LUN to full size 4. Reboot. Hey presto - Solaris can use the 1.4 TB LUN. Related question: Right now, when I run format I can set up a solaris disk label on my empty LUN. Does this mean that Solaris puts the Sun label directly on "the metal" like it was done on SPARCs or did it create a EFI partiton for me automatically? Which are the tools that manipulate EFI labels? Regards, /Erik -- This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
