The embedded platform is having problems recognising the drive when a Solaris label is written to sector 0, so having control over the label is somewhat moot.
The "ideal" solution that we are aiming for is to have the embedded platform treat the entire physical drive as a single FAT32 partition, without any MBR overhead ... i.e. sector 0 of the disk holds the EBR and boot block code of the FAT32 partition itself (this is how the embedded system is currently working). Access from Solaris would not employ any of the usual slice definitions, but would simply access the whole disk as a raw device ... but in doing so the disk capacity truncation is encountered. We'd just like Solaris to allows LBA access to the full number of sectors that the drive controller is reporting, without Solaris faking some derived C/H/S geometry that cuts out 500GB of actual storage. This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
