Thanks for your reply. No, the disk is not being used for booting at all, just data storage. The RAID capacity is about 547GB, so the 1TB limit is not an issue either. The RAID is managed using a Fibre-Channel controller (if that makes any difference).
The embedded system creates a FAT32 partition on the RAID and does not support a Solaris label in sector/block 0. When the RAID is viewed by Solaris (without the Solaris label), the disk appears to be truncated to a much smaller drive, which corresponds to Solaris defaulting it to 255 heads, 63 sectors and whatever number of cylinders it calculates by dividing tha actual number of sectors by 255 and 63 ... resulting in a value that overflows the number of cylinders variable (a 16 bit unsigned int). While trolling through OpenSolaris code, the "matching" logic to the observed behaviour was found in cmlb.c, hence the post to verify if the analysis was correct and whether the intended fix in OpenSolaris would work on a (closed) Solaris machine. So I'm not sure that either of the issues you mentioned below are applicable in this specific instance. Thank you for indicating that several other places will need fixing in addition to the one place that was identified in the post ... I guess it's time for some other workaround to be found. This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
