Hello Andrew,
Thank you for your reply, please see my comments below.
On Tue, Aug 5, 2008 at 6:11 PM, andrew <andrum04 at gmail.com> wrote:
> Solaris can only use 1 FDISK partition per disk. The reason for this is
> that on SPARC there are no FDISK partitions - only slices. When Solaris was
> ported to x86, the solution was to make one big Solaris FDISK partition and
> put all Solaris slices inside it.
>
Maybe I was not clear in my description. There will only be one Solaris
fdisk partition. This will only have a single slice, which I tried to
create and this is where I am stuck at present. As you describe below,
Solaris can in fact see multiple fdisk partitions.
Just to be 100% clear: There will be only on type 0xbf fdisk partition, and
this should have slice 2 and slice 0, as well as the standard slice 8 and 8
for boot block and alternates, with 2 being the whole fdisk partition and 0
being everything excluding what is blocked out by 8 and 9. Currently those
are missing and when I try to create the partition using all-free-hog it
hogs the entire physical disk, in other words it is created larger than the
Solaris fdisk partition.
>
> Also, Solaris currently doesn't understand extended partitions, so anything
> you put in there won't be accessible from within Solaris.
>
This is exactly why I put Linux into an extended partition.
a) It hides the Linux swap fdisk partition, which has got type 0x82 and is
confusing Solaris.
b) Solaris does not need access to the Linux partitions.
c) I have the flexibility to change the Linux partitioning layout in the
extended partition should I wish to do so, without affecting the existing
fdisk partitions.
> What you really want is this:
>
> Partition 1: Solaris (with a root pool and data pool as seperate slices)
> Partition 2: Linux
> Partition 3: Linux Swap
> Partition 4: Windows
>
That would work but I would not be able to easily share the ZFS data pool
between Solaris and Linux, something I currently do and very much depend on
(half of my Linux software is installed on the ZFS pool).
In addition I *still* cannot create the slices in the Solaris fdisk
partition.
My existing hard drive has got a similar layout, being the following:
Total disk size is 12161 cylinders
Cylinder size is 16065 (512 byte) blocks
Cylinders
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1 EXT-DOS 0 1337 1338 11
2 Active Solaris 1338 4027 2690 22
3 Win95 FAT32 4028 12160 8133 67
SELECT ONE OF THE FOLLOWING:
1. Create a partition
2. Specify the active partition
3. Delete a partition
4. Change between Solaris and Solaris2 Partition IDs
5. Exit (update disk configuration and exit)
6. Cancel (exit without updating disk configuration)
Enter Selection:
Current partition table (original):
Total disk cylinders available: 2688 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 root wm 3 - 2687 20.57GB (2685/0/0) 43134525
1 unassigned wu 0 0 (0/0/0) 0
2 backup wm 0 - 2687 20.59GB (2688/0/0) 43182720
3 unassigned wu 0 0 (0/0/0) 0
4 unassigned wu 0 0 (0/0/0) 0
5 unassigned wu 0 0 (0/0/0) 0
6 unassigned wu 0 0 (0/0/0) 0
7 unassigned wu 0 0 (0/0/0) 0
8 boot wu 0 - 0 7.84MB (1/0/0) 16065
9 alternates wu 1 - 2 15.69MB (2/0/0) 32130
So the desired outcome is to have the same, except for three minor
variations:
1) Part 3 should have a more appropriate type, maybe EFI. This is where my
ZFS data pool resides.
2) I am considering to have an extra partition for NTFS
3) The order of the partitions is maybe not perfect, I would ideally like to
have them ordered like I described in my initial post.
Thanx!
_Johan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/opensolaris-help/attachments/20080806/30c3ede0/attachment.html>
