Installing Open Solaris and Open Suse 10.2 on same disk problem
Solaris / OpenSolarisThis forum is for the discussion of Solaris, OpenSolaris, OpenIndiana, and illumos.
General Sun, SunOS and Sparc related questions also go here. Any Solaris fork or distribution is welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Installing Open Solaris and Open Suse 10.2 on same disk problem
Hi,
I am in the trouble of installing Open Solaris and Open Suse on same disk. My PC arch is as follows:
- Intel Pentium D (2.8 GHz)
- 1 GB DDR2 RAM
- 230 GB SATA and 78 GB SATA HDD
- 1 DVD writer and a CD Writer on same IDE
I have installed WinXP on the primary HDD (230 GB) and Open Solaris on the secondary (78 GB). I gave 35 GB to Solaris and remaining space is actually free, where I want to install Suse. But in the installation procedure for Suse, it doesn't show the free space, rather the entire hard drive, i.e. 78 GB. I am not partitioning it from Suse, cause I dont wanna lose Solaris. And I dont want to touch my primary HDD. I know that Solaris points the entire disk on slice 2 (eg c0t0d0s2) as its entire disk.
Is there any way I can get Solaris not point entire disk on slice 2. I guess that would sort the problem. I have not tried anything with format and resizing yet.
And here is my format partition output:
Distribution: Solaris 11.4, Oracle Linux, Mint, Debian/WSL
Posts: 9,789
Rep:
Quote:
Originally Posted by devn
I gave 35 GB to Solaris and remaining space is actually free
Actually, you gave Solaris the whole disk, or more precisely, a partition spanning the whole disk.
Quote:
But in the installation procedure for Suse, it doesn't show the free space, rather the entire hard drive, i.e. 78 GB.
Suse correctly detects your disk has no spare space.
Quote:
I am not partitioning it from Suse, cause I dont wanna lose Solaris.
Yes, any action from Suse would made your Solaris filesystems unreachable.
Quote:
I know that Solaris points the entire disk on slice 2 (eg c0t0d0s2) as its entire disk.
This the case on SPARC hardware only. With x86 H/W, the whole disk is c0t0d0p0.
Quote:
Is there any way I can get Solaris not point entire disk on slice 2.
Yes, you can have slice 2 not to point to the entire Solaris partition as it is just a convention, but that wouldn't be enough to recover some disk space.
Quote:
I guess that would sort the problem. I have not tried anything with format and resizing yet.
The main issue is your Solaris partition isn't used contiguously, so you can't shrink it from one end or the other.
Cylinders 0 to 133 are used by the boot and the swap areas while cylinders from 5263 to 9725 are used by your filesystems.
The solution would be to move these 2 last partions (0 and 7) to the free area starting from slice 134 and then shrink s2 and p1 but as there are no tools to automatize the process, you would have to edit by hand the partition and slice table, I'm afraid it would be extremely difficult to achieve the task without loosing all the data.
You may wan't to try that if you have enough space on another disk to store the whole disk image (78 GB) thus to rollback to the initial situation should something goes wrong.
Thanks for the quick reply. Well, moving slices to make my disk contiguous for solaris looks a lot of backup and restoration job to do. Well, I could attempt that provided the backup slice actually releases the free space. Is there any way I can do that while I am installing a fresh copy of Solaris? I mean is there a way to slide cylinders to point only the part of disk I want it to while I am partitioning disk from installation menu?
Or should I install Suse first then?
If possible, could you give me specific suggestions on how to format filesystem (the free space after done installing Suse) so that Solaris finds it for installing itself after I install Suse. And is it possible to have the same swap for Suse and Solaris? I did it for Linux (two different distros) before.
I am attempting to shift my slices. Here is what I am going to do. Correct my steps if wrong:
Well, from the calculations, I am going to do this new cylinder struct:
root = 134 - 2047 (cylinders)
home = 2048 - 4598 (cylinders)
backup = 0 - 4598 (cylinders)
create filesystem and mount them with different names e.g / as /root_bck and so for home.
My vfstab contains the following entries:
But the problem is, how to copy slice 0 exactly to slice 3? And same for slice 7?
After reboot, system should now be booted with mounted filesystems from slice 3 and 4.
Should I then change backup slice (slice 2) to 4598 and remove slice 0 and 7?
How risky is that?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.