PDA

View Full Version : [ubuntu] 12.04 & Z77 mobos



loseby
April 29th, 2012, 08:12 AM
Have a Gigabyte GA Z77X-UD5H and am thinking of using this for 12.04. At the moment I have 12.04 on another PC but this PCV will be a lot quicker. This is what I am thinking of doing :

1/ Using an old drive that I have (Samsung 500GB ) and just using this
2/ Instead of letting Ubuntu use grub to manage boots will use the F12 key ( brings up boot menu from which I can select whatever drive I want to boot from )
3/ Temporary disconnect my current win7 drives so Ubuntu doesnt touch them ( GRUB ) and then install 12.04 from an USB stick

Questions : Z77 is a very new chipset....does 12,04 support it ?

Any problems with doing what I want ?

imac_89
April 29th, 2012, 05:10 PM
According to Phoronix (http://www.phoronix.com/scan.php?page=article&item=intel_z77_chipset&num=1):


Both the DZ77GA-70K and Z77H2-A2X motherboards have been running fine under Ubuntu 12.04 LTS with a variety of processors. The stock Linux 3.2 kernel has been running without fault and the Linux 3.4 kernel is also obviously running well too. All functionality seems to be in place. Ubuntu 12.04 LTS is being used since it is the latest-and-greatest packages, but even going back to Ubuntu 11.10 those packages should have the Panther Point support in place. I also have not run into any UEFI problems on Linux with either the Intel DZ77GA-70K or ECS Z77H2-A2X.

So it seems you have the green light. Maybe another web search for compatiblity may get you a better focused answer!

loseby
April 29th, 2012, 11:47 PM
have tried it and it works ok but have problems with booting .... a new type 3D BIOS and me are the probs ...... I tried Win8 a while ago but not for long

for some reason instead of booting into win7 it looks like it starts to install win8 and when it finds the CD is not there it boots into Ubuntu............


anyway, have it on another PC and will use it there

imac_89
April 30th, 2012, 12:04 AM
That is strange. I wish I had held off building my computer until now to try out the new chipset. Overall Ubuntu runs fine then I assume?

loseby
May 1st, 2012, 02:23 AM
That is strange. I wish I had held off building my computer until now to try out the new chipset. Overall Ubuntu runs fine then I assume?

yes and a little no

It ran fine, no problems at all in that regards


the no part is I was a little bit dissapointed with the speed .......

anyway am considering putting it back on there and using GRUB to boot into windows or ubuntu....... using the f12 key and you have to be very quick as it loads in a blink of an eye on Windows

Also instead of using a seperate hard drive am thinking about putting it on a sata III ( 6GBs ).... maybe that will boost the speed

loseby
May 5th, 2012, 09:26 AM
a final update : have put it on the sata 3 drive and that has killed my windows installation

anyway am now working on how to boot to windows


BUT ... 12.04 working pretty good on my Z77 system

oldfred
May 5th, 2012, 07:03 PM
Did you install in UEFI mode or BIOS mode. Is Windows in UEFI or BIOS mode? Proably best if both are the same.

If you have gpt partitioning with an efi partition first then you have UEFI mode. If MBR partitioning and no efi partition then you are in BIOS mode.

loseby
May 6th, 2012, 12:46 AM
The brain is spinning....UEFI or BIOS mode ? Going to have to do some more research here as I am not comfortable with the new layout

anyway, from another thread I obtained a script to run to show my system



Boot Info Script 0.61 [1 April 2012]


============================= Boot Info Summary: ===============================

=> No boot loader is installed in the MBR of /dev/sda.
=> Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
for (,msdos1)/boot/grub on this drive.
=> Grub2 (v1.99) is installed in the MBR of /dev/sdc and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
for (,msdos1)/boot/grub on this drive.
=> Grub2 (v1.99) is installed in the MBR of /dev/sdd.

sda1: __________________________________________________ ________________________

File system: vfat
Boot sector type: Windows 7: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bootx64.efi

sda2: __________________________________________________ ________________________

File system:
Boot sector type: -
Boot sector info:
Mounting failed: mount: unknown filesystem type ''

sda3: __________________________________________________ ________________________

File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 7
Boot files: /Windows/System32/winload.exe

sdb1: __________________________________________________ ________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 12.04 LTS
Boot files: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

sdb2: __________________________________________________ ________________________

File system: Extended Partition
Boot sector type: -
Boot sector info:

sdb5: __________________________________________________ ________________________

File system:
Boot sector type: -
Boot sector info:
Mounting failed: mount: unknown filesystem type ''
mount: unknown filesystem type ''

sdc1: __________________________________________________ ________________________

File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

sdd1: __________________________________________________ ________________________

File system: vfat
Boot sector type: -
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

============================ Drive/Partition Info: =============================

Drive: sda __________________________________________________ ___________________

Disk /dev/sda: 256.1 GB, 256060514304 bytes
256 heads, 63 sectors/track, 31009 cylinders, total 500118192 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sda1 1 4,294,967,295 4,294,967,295 ee GPT

/dev/sda1 ends after the last sector of /dev/sda

GUID Partition Table detected.

Partition Start Sector End Sector # of Sectors System
/dev/sda1 2,048 206,847 204,800 EFI System partition
/dev/sda2 206,848 468,991 262,144 Microsoft Reserved Partition (Windows)
/dev/sda3 468,992 500,117,503 499,648,512 Data partition (Windows/Linux)

Drive: sdb __________________________________________________ ___________________

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdb1 * 2,048 1,937,215,487 1,937,213,440 83 Linux
/dev/sdb2 1,937,217,534 1,953,523,711 16,306,178 5 Extended
/dev/sdb5 1,937,217,536 1,953,523,711 16,306,176 82 Linux swap / Solaris


Drive: sdc __________________________________________________ ___________________

Disk /dev/sdc: 500.1 GB, 500106780160 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976771055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdc1 2,048 976,766,975 976,764,928 7 NTFS / exFAT / HPFS


Drive: sdd __________________________________________________ ___________________

Disk /dev/sdd: 32.3 GB, 32297189376 bytes
256 heads, 63 sectors/track, 3911 cylinders, total 63080448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdd1 * 32 63,080,447 63,080,416 b W95 FAT32


"blkid" output: __________________________________________________ ______________

Device UUID TYPE LABEL

/dev/mapper/cryptswap1 3e22616b-7bc1-4eb1-a5d5-3446c5edf74b swap
/dev/sda1 7219-1D14 vfat
/dev/sda3 F86A3C126A3BCBDE ntfs
/dev/sdb1 7e3b5297-2506-4154-9ac4-8a6dc819f9f1 ext4
/dev/sdc1 161A45461A452459 ntfs Samsung
/dev/sdd1 4ED5-7386 vfat CORSAIR

========================= "ls -R /dev/mapper/" output: =========================

/dev/mapper:
control
cryptswap1

================================ Mount points: =================================

Device Mount_Point Type Options

/dev/sdb1 / ext4 (rw,errors=remount-ro)
/dev/sdd1 /media/CORSAIR vfat (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed ,dmask=0077,utf8=1,showexec,flush,uhelper=udisks)


=========================== sdb1/boot/grub/grub.cfg: ===========================

--------------------------------------------------------------------------------
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}

function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}

insmod part_msdos
insmod ext2
set root='(hd1,msdos1)'
search --no-floppy --fs-uuid --set=root 7e3b5297-2506-4154-9ac4-8a6dc819f9f1
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=auto
load_video
insmod gfxterm
insmod part_msdos
insmod ext2
set root='(hd1,msdos1)'
search --no-floppy --fs-uuid --set=root 7e3b5297-2506-4154-9ac4-8a6dc819f9f1
set locale_dir=($root)/boot/grub/locale
set lang=en_AU
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
if background_color 44,0,30; then
clear
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="$1"
if [ "$1" = "keep" ]; then
set vt_handoff=vt.handoff=7
else
set vt_handoff=
fi
}
if [ ${recordfail} != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
if [ "$linux_gfx_mode" != "text" ]; then load_video; fi
menuentry 'Ubuntu, with Linux 3.2.0-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd1,msdos1)'
search --no-floppy --fs-uuid --set=root 7e3b5297-2506-4154-9ac4-8a6dc819f9f1
linux /boot/vmlinuz-3.2.0-24-generic root=UUID=7e3b5297-2506-4154-9ac4-8a6dc819f9f1 ro quiet splash $vt_handoff
initrd /boot/initrd.img-3.2.0-24-generic
}
menuentry 'Ubuntu, with Linux 3.2.0-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd1,msdos1)'
search --no-floppy --fs-uuid --set=root 7e3b5297-2506-4154-9ac4-8a6dc819f9f1
echo 'Loading Linux 3.2.0-24-generic ...'
linux /boot/vmlinuz-3.2.0-24-generic root=UUID=7e3b5297-2506-4154-9ac4-8a6dc819f9f1 ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-24-generic
}
submenu "Previous Linux versions" {
menuentry 'Ubuntu, with Linux 3.2.0-23-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd1,msdos1)'
search --no-floppy --fs-uuid --set=root 7e3b5297-2506-4154-9ac4-8a6dc819f9f1
linux /boot/vmlinuz-3.2.0-23-generic root=UUID=7e3b5297-2506-4154-9ac4-8a6dc819f9f1 ro quiet splash $vt_handoff
initrd /boot/initrd.img-3.2.0-23-generic
}
menuentry 'Ubuntu, with Linux 3.2.0-23-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd1,msdos1)'
search --no-floppy --fs-uuid --set=root 7e3b5297-2506-4154-9ac4-8a6dc819f9f1
echo 'Loading Linux 3.2.0-23-generic ...'
linux /boot/vmlinuz-3.2.0-23-generic root=UUID=7e3b5297-2506-4154-9ac4-8a6dc819f9f1 ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-23-generic
}
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod part_msdos
insmod ext2
set root='(hd1,msdos1)'
search --no-floppy --fs-uuid --set=root 7e3b5297-2506-4154-9ac4-8a6dc819f9f1
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(hd1,msdos1)'
search --no-floppy --fs-uuid --set=root 7e3b5297-2506-4154-9ac4-8a6dc819f9f1
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
if [ "x${timeout}" != "x-1" ]; then
if keystatus; then
if keystatus --shift; then
set timeout=-1
else
set timeout=0
fi
else
if sleep --interruptible 3 ; then
set timeout=0
fi
fi
fi
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
--------------------------------------------------------------------------------

=============================== sdb1/etc/fstab: ================================

--------------------------------------------------------------------------------
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sdb1 during installation
UUID=7e3b5297-2506-4154-9ac4-8a6dc819f9f1 / ext4 errors=remount-ro 0 1
# swap was on /dev/sdb5 during installation
#UUID=926a19c1-6f05-4b14-9083-c4dc095313fd none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0
--------------------------------------------------------------------------------

=================== sdb1: Location of files loaded by Grub: ====================

GiB - GB File Fragment(s)

= boot/grub/core.img 1
= boot/grub/grub.cfg 1
= boot/initrd.img-3.2.0-23-generic 1
= boot/initrd.img-3.2.0-24-generic 2
= boot/vmlinuz-3.2.0-23-generic 1
= boot/vmlinuz-3.2.0-24-generic 1
= initrd.img 2
= initrd.img.old 1
= vmlinuz 1
= vmlinuz.old 1

=============================== StdErr Messages: ===============================

xz: (stdin): Compressed data is corrupt
xz: (stdin): Compressed data is corrupt
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in
awk: cmd. line:36: Math support is not compiled in

oldfred
May 6th, 2012, 01:04 AM
You have both BIOS/MBR and gpt/EFI, not sure how that even works? It must be interesting trying to boot.

But you also have a problem which we need to fix first.


/dev/sda1 ends after the last sector of /dev/sdaLots to tools including gparted just stop working when the partition table is corrupted.

The author of gdisk for gpt drives has a program called fixparts which works well on fixing MBR errors similar to yours, but yours is on the gpt drive.

You do not want to convert your gpt drive to MBR or else Windows will not boot. I think you need gdisk, but you can look at this.
Fixparts - Repair broken partition tables (not overlapping issues) & delete Stray gpt data from MBR drives
http://ubuntuforums.org/showthread.php?t=1705325
http://www.rodsbooks.com/fixparts/
First backup partition table, use your drive for sdX or sda, sdb etc.
sudo sfdisk -d /dev/sdX > parts.txt

But do not use gdisk on your MBR drives as it may try to convert from MBR to gpt.
repair gpt:
http://www.rodsbooks.com/gdisk/repairing.html

GPT Advantages srs5694:
http://ubuntuforums.org/showthread.php?t=1457901
GPT or MBR
http://ubuntuforums.org/showthread.php?t=1625285

GPT fdisk Tutorial -srs5694 in forums
http://ubuntuforums.org/showthread.php?t=1439794
http://www.rodsbooks.com/gdisk/

gdisk is in the repository so you can easily download it into Ubuntu.

I converted several Linux only drives to gpt and boot with BIOS, but I do not have UEFI.

loseby
May 6th, 2012, 01:46 AM
omg

A brief history:

1/ Installed win8 on the SSD just for a trial whislt waiting for new mobo etc to arrive
2/ Then installed win7 back on SSD after doing an upgrade
3/ Put 12.04 on the 500GB Samsung drive but as I had boot problems with win7 I ended up formattin it from within windows
4/ Tranfered data from the Seagate drive to the Samsung and then installed 12.04 on the current Ubuntu drive ( the Seagate )

What I would like to do is get all these drives back to near new status ie. remove all data and history of windows or ubuntu

Am going to disconnect all drives bar the SSD and then install ubuntu on that ...............

oldfred
May 6th, 2012, 02:07 AM
With a new z77 motherboard you have to decide if you want to boot in UEFI or BIOS. UEFI is the newer thing.

Also you have to decide whether to use gpt or MBR(msdos). I still have BIOS but am converting drives to gpt. You only have to have gpt for drives over 2.2GB, but gpt again is newer, and has some advantages. But Windows will only boot from gpt with UEFI.

Some light reading:

Grub2 efi info ArchLinux - Arch but grub2 is grub2 with maybe minor differences by distribution
https://wiki.archlinux.org/index.php/GRUB2#Bootloader_Installation_for_UEFI_systems

https://wiki.archlinux.org/index.php/UEFI
https://wiki.archlinux.org/index.php/GPT
https://wiki.archlinux.org/index.php/Grub2

https://help.ubuntu.com/community/UEFIBooting#UEFI%20Shell
Recompiling GRUB not required with newest versions of grub.
Creating efi partition & folders in advance works.

GUIDE: (U)EFI installation Also full install post *52 superfreak
http://ubuntuforums.org/showthread.php?t=1958383
Asus UEFI instructions (except efi should be first partition, but must not have to be)
http://ubuntuforums.org/showthread.php?p=11842855
Examples that worked, format in advanced with gparted, gpt with find efi output & demesg
http://ubuntuforums.org/showthread.php?t=1954716&highlight=efi
http://ubuntuforums.org/showthread.php?t=1939094
How to install Ubuntu 11.10 on a Lenovo (U)EFI system (tested on S205, B570)
http://ubuntuforums.org/showthread.php?t=1867367

If drive is only going to be Ubuntu (never Windows), I would suggest using gpt not MBR as the partitioning scheme. You then do not have any logical partitions, they are all primary and it has a backup in case of problems. You do have to create a tiny bios_grub partition to correctly install grub2's boot loader to the drive.
If using gpt with BIOS create a 1MB bios_grub partition with no format. I used gparted and selected gpt under device, advanced & select gpt over msdos(MBR) default partitioning....

But since you can boot with UEFI, you can also boot Windows from gpt.

Even if you want to stay with BIOS & MBR, I would create the efi & bios_grub partitions. The efi has to be first so it would be difficult to change later unless you create it when you format drive.

Since the BIOS Boot Partition ("bios_grub" flag set in GNU Parted) is used without a filesystem for storing GRUB 2 boot code, and since the EFI System Partition (ESP) is used by EFI with a FAT-32 filesystem for storing EFI files, the two cannot be the same partition.
If you're using UEFI mode to boot, you don't need a BIOS Boot Partition, but you do need an EFI System Partition (ESP)
If a new drive, to be safe, create both of these partitions, in addition to your regular Linux partitions. But the efi partition has to be first. Do not configure Linux to use either the ESP or the BIOS Boot Partition; they'll be used automatically by GRUB, if necessary.

If you're using UEFI mode to boot, you don't need a BIOS Boot Partition with gpt partitions (only for BIOS), but you do need an EFI System Partition (ESP). This is entirely different; it should be a 200-300 MiB FAT32 partition that's flagged as an ESP and must be the first partition. In libparted-based tools, you'd give it a "boot" flag (which is entirely unrelated to the MBR boot/active flag, although libparted makes them look the same). In gdisk, you'd give it a type code of EF00.
An EFI System Partition EF00 (~100 to -256MiB, FAT32) for UEFI, a BIOS Boot Partition EF02 (~1MiB, no filesystem) for BIOS, and whatever partitions you want for Linux. You must set the partition type codes correctly, but how you do this depends on the utility you use to create them. Also, you should be sure to create a GUID Partition Table (GPT) on the disk, not a Master Boot Record (MBR) partition table. In BIOS mode, Ubuntu's installer defaults to creating MBR partitions, at least on sub-1TB disks, so you may need to use another utility to do the partitioning. You do not need both but it does not hurt as both are small, and then you can configure easily to boot with either UEFI or BIOS. You can boot via bios AND efi (after setting up your efi boot entry using efibootmgr or via efi shell and running the efi binary)
AsRock calls BIOS mode AHCI.

loseby
May 6th, 2012, 03:35 AM
all done .. I hope this looks better


=========================== Drive/Partition Info: =============================

Drive: sda __________________________________________________ ___________________

Disk /dev/sda: 256.1 GB, 256060514304 bytes
255 heads, 63 sectors/track, 31130 cylinders, total 500118192 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sda1 * 63 466,623,989 466,623,927 83 Linux
/dev/sda2 466,623,990 500,103,449 33,479,460 5 Extended
/dev/sda5 466,624,053 500,103,449 33,479,397 82 Linux swap / Solaris

oldfred
May 6th, 2012, 04:26 AM
That will only boot in BIOS mode. It is ok, I do prefer smaller / (root) partitions and large /home or even data partitions. All my / are about 25GB with data in other partitions.

There is or was a bug in grub that very large ( on 1 or 2TB drives) / partitions would not boot. Plus it is not efficient on those very large drives to have the boot files located across the drive and make it search the whole thing.