Hi,
I formatted my disk, and installed Windows first (i prefered waiting to make a fresh OpenSuse 13.2 instead of upgrading), and then, using Minitool Parition Wizard, i made a partition formatted as EXT4, so i kept it for opensuse,
but here i am, i just installed the ISO, and i choosed the default parameters (it dident gave me the EXT4 as default, so i dident choosed it), and i get the error at the end, that cant install bootloader, so my machine now, loads normally like in the past: directly to windows.
On Wed 05 Nov 2014 11:46:01 PM CST, abdelouahab wrote:
Hi,
I formatted my disk, and installed Windows first (i prefered waiting to
make a fresh OpenSuse 13.2 instead of upgrading), and then, using
Minitool Parition Wizard, i made a partition formatted as EXT4, so i
kept it for opensuse,
but here i am, i just installed the ISO, and i choosed the default
parameters (it dident gave me the EXT4 as default, so i dident choosed
it), and i get the error at the end, that cant install bootloader, so my
machine now, loads normally like in the past: directly to windows.
And by the way, i have to rename the ISO file to RAW so the image writer
can find it, i think it should add the *. or the ISO
Hi
If you accepted the defaults then it created as btrfs, which you need a
separate /boot of say ext4.
Your a bit light on the size as well… if you only want to use 20 odd
GB, then you need to ensure you use the expert partitioner during
install to select ext4.
With ext4 you could use you current setup but probably easier to just
use a / and a swap.
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Hi
Yes, assuming it would all fit… are you using a light weight desktop? I would also imagine copying large files would be an issue with not much of a /tmp.
If your just trying things out, I would use your allocated space for /boot a / and a swap partition.
On Thu 06 Nov 2014 01:16:03 AM CST, abdelouahab wrote:
malcolmlewis;2673259 Wrote:
> Hi
> Yes, assuming it would all fit… are you using a light weight
> desktop? I would also imagine copying large files would be an issue
> with not much of a /tmp.
>
> If your just trying things out, I would use your allocated space for
> /boot a / and a swap partition.
so the parition for /boot is a must in the new grub?
Hi
AFAIK if you are using btrfs for / else shouldn’t be needed (I always
use one, old habits…)
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
For BTRFS it depends on the hardware and if you plan to hibernate if you truly “need” a separate boot. But it is recommended at least here that you do. It will give less trouble in the long run. But with the small sizes you are allotting you should probably stick to ext4 .BTRFS is a bit of a memory hog because of the default snapper snapshot feature
Also at the partition scheme section of the installer you can modify the scheme and assign what ever partitions you want.
By default 13.2 has a BTRFS root and a XFS home and a swap. You don’t have to accept any of that.
You don’t “need” a separate /boot at all with btrfs.
But grub2’s btrfs support is not 100% complete. In particular if you set a specific boot menu entry to be used on the next boot (via KDE’s Restart menu e.g.), grub2 cannot reset it and will continue to boot this without ever showing the menu again.
But, as mentioned in other threads already, this is not a problem any more for hibernating, as the resume script takes care of that.
AFAIK, this is the only limitation (in practice), unless there are bugs in grub2’s btrfs support.
This doesn’t mean of course that you should not have a separate /boot. It’s just not needed.
And it’s your decision.
BTRFS is a bit of a memory hog because of the default snapper snapshot feature
I suppose you mean hard disk space, not memory?
The snapshots can be turned off of course though. There’s even a prominent checkbox in the installer.
Hi Abdel, I had similar problems.
It turned out that all was correct, BUT the “boot” flag was still on the “Win**” partition.
Setting the “boot” flag to the partition where GRUB2 was installed (sda8 in my case) restored everything.
My setup on this test box:
linux-a2yg:/home/etabeta # fdisk -l
Disk /dev/sda: 111,8 GiB, 120034123776 bytes, 234441648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x8e35bb07
Device Boot Start End Sectors Size Id Type
/dev/sda1 63 127684682 127684620 60,9G 7 HPFS/NTFS/exFAT
/dev/sda2 127700685 215046089 87345405 41,7G f W95 Ext'd (LBA)
/dev/sda3 215109632 231176191 16066560 7,7G 7 HPFS/NTFS/exFAT
/dev/sda4 231184384 234438655 3254272 1,6G 7 HPFS/NTFS/exFAT
/dev/sda5 127700748 131911678 4210931 2G 82 Linux swap / Solaris
/dev/sda6 152906733 190097144 37190412 17,8G 83 Linux
/dev/sda7 190097208 215046089 24948882 11,9G 83 Linux
/dev/sda8 * 131911680 152905727 20994048 10G 83 Linux
Partition table entries are not in disk order.
sda8 is my /root with btrfs, sda6 my /home with ext3, NO separate /boot.
Looking at your screenshot I notice:
the “boot” flag seems still on the “Win” partition; maybe setting it to where GRUB was actually installed will help;
your disk shows 9 partitions on a msdos partition table AND only ONE extended partition:
as I understand it, on a msdos partition table you can put 3 primary partitions, 1 extended, another 4 primaries within the extended, so maximum 8 partitions with that setup, as my “full” disk confirms.
That is the problem, it is like a 180° switch! making them as default and not as choice was weird for me (as a beginner), it should be made as default for release 14.x and not as a 13.x upgrade?
Ah, thank you for clarification, because so much debates is made about btrfs!
Yesterday night, i almost broke my hard disk! i tried to merge them with a free windows software, and instead of mergin the small (tiny) parition to the bigger one, the inverse happened! making the laptop stop, and after the operation was stopped, the sizes changed, and bad sectors showed up, hopefully chkdsk /f /r on windows repaired them (lost some data, but at least, not the whole disk), so i am going to make it again with the ext4 values, and installing the grub as you suggested, thank you
There are no “13.x upgrades”. Each release is completely independent of the previous one. The version number has absolutely no relevance.
It’s just that a few years ago it was decided to use version numbers like this: 12.1, 12.2, 12.3, 13.1, 13.2, 13.3, 14.1, … (there was a vote)
They could have just as well used 12, 13, 14, 15, …
I suppose the current scheme has been elected because it’s more consistent with how it was done before.
You can have 4 Primary partitions on an MSDOS partition scheme. Note that an Extended partition is a special case Primary partition, so as outlined above, it is the 4th Primary partition.
Inside of an Extended partition, you do not have Primary partitions. Instead, you have Logical partitions. You are not limited to 4 Logical partitions in an Extended partition, you can have several Logical partitions in the Extended. The number of Logical partitions allowed is so many that you are unlikely to reach the limit.
Please ignore notice 2) from my post #10, sorry.
Note that it is always best to resize partitions “within” each OS, for instance:
resize NTFS partitions WITHIN “Win**” with its administration tools to free space for Linux;
create, format, resize etc. Linux partitions with Linux tools (e.g. PartedMagic, Gparted from LiveCD etc.).
Note also that, if possible, when Linux is installed within an extended partition like in your case, it is best to place the root/ (or /boot partition if any) as the first logical partition of the extended partition.
That way, you may be able to boot at least in rescue mode (thanks to the MBR partition table) even if other partitions get corrupt.
This is not the case in my setup, at the moment.
Yast2/Bootloader in OpenSUSE has some problems when installing on a “non-clean” disk.
An option I use when everything else fails is:
preparing the partitions first (with GParted or other tool);
installing openSUSE with NO bootloader (Yast complains, but I ignore the warning);
installing the bootloader manually with other tools (SuperGrub2Disk, PartedMagic…);
boot OpenSUSE and, if needed, edit the bootloader menu with Yast.
@ Fraser_Bell
Sorry for misreading information and the concept of chaining EBRs, e.g. from the sfdisk manpage:
“…(`extended partition’) the starting sector of the partition again contains 4 partition descriptors…”
I should doublecheck old assumptions from time to time… >:(
I make all the partition from windows to be sure that i dont mess with something
i use free partition manager, for example AOMEI Partition Assistant Standard Edition 5.5 make a good job, and then i format in EXT3 so the linux can find it and make its job there
in the past i was using Easuse partition manager, it is good too, but i almost broke my partition table because it tried to merge a big partition to a small one!
