hi thanks for the prompt reply
On Wed, Dec 23, 2015 at 6:32 AM, maderios maderios@gmail.com wrote:
Hi Why an extended partitition?
I just marked the normal partition flag instead of LVM, is there any practical and related issue with my problem in this?
It should a gpt partitioning with efi. Your 'Dell Precision m6800' uses uefi but you have not any efi partition http://www.manualslib.com/manual/563583/Dell-Precision-M6800.html?page=58 For me, your install is wrong. First, You have to disable uefi secure boot in your bios, then install F23. Installer has to detect an efi partition like '/boot/efi'
uhm, I' ve checked and in what should be the /boot dir I' ve
efi |-->EFI |-->BOOT |-->BOOTX64.EFI |-->fallback.efi |-->fedora |-->BOOT.CSV |-->fonts |-->unicode.pf2 |-->gcdx64.efi |-->grubx64.efi |-->MokManager.efi |-->shim.efi |-->shim-fedora.efi |-->mach_kernel |-->System |-->Library |-->CoreServices |-->SystemVersion.plist
as far as I know everything is there or is it not?
I've also checked the options related to UEFI in my BIOS and seems that UEFI and Secure boot are both disabled. This are the related options: General Boot Sequence Legacy (this flagged) UEFI (this is not flagged) Advanced Boot Options Enable Legacy Option ROMS (this is selected and the note says "This option is not allowed if secure boot is enabled") System Configuration Integrated NIC Enabled UEFI Network Stack (this is not flagged) Enabled w/PXE (this is flagged) Secure Boot Disabled (flagged)
Could be that I missed something? Any other idea?
Walter
--
On Wed, 2015-12-23 at 09:20 -0500, Walter Cazzola wrote:
This are the related options: General Boot Sequence Legacy (this flagged)
In that case, I think your first post indicated that the boot flag was not set for your new /boot partition. From your post, with lots of snipping:
Device Boot Start End Sectors Size Id Type /dev/sda2 * 81920 25710591 25628672 12.2G 27 Hidden NTFS /dev/sda5 201410560 202776575 1366016 667M 83 Linux
where sda1-3 are the original windows partitions, sda5 is /boot and sda6 is /
On Wed, Dec 23, 2015 at 9:34 AM, Doug H. fedoraproject.org@wombatz.com wrote:
On Wed, 2015-12-23 at 09:20 -0500, Walter Cazzola wrote:
This are the related options: General Boot Sequence Legacy (this flagged)
In that case, I think your first post indicated that the boot flag was not set for your new /boot partition. From your post, with lots of snipping:
Device Boot Start End Sectors Size Id Type /dev/sda2 * 81920 25710591 25628672 12.2G 27 Hidden NTFS /dev/sda5 201410560 202776575 1366016 667M 83 Linux
where sda1-3 are the original windows partitions, sda5 is /boot and sda6 is /
Indeed you could be right. How I can change such a flag?
Second question: the error message said that no /boot/grub2/i386-pc/normal.mod file is available and effectively I don' t have such a file in that position but only it is in /usr/lib/grub/i386-pc/. So changing the boot flag would be enough to solve the problem?
Walter
--
On Wed, 2015-12-23 at 09:54 -0500, Walter Cazzola wrote:
On Wed, Dec 23, 2015 at 9:34 AM, Doug H. <fedoraproject.org@wombatz.c om> wrote:
On Wed, 2015-12-23 at 09:20 -0500, Walter Cazzola wrote:
This are the related options: General Boot Sequence Legacy (this flagged)
In that case, I think your first post indicated that the boot flag was not set for your new /boot partition. From your post, with lots of snipping:
Device Boot Start End Sectors Size Id Type /dev/sda2 * 81920 25710591 25628672 12.2G 27 Hidden NTFS /dev/sda5 201410560 202776575 1366016 667M 83 Linux
where sda1-3 are the original windows partitions, sda5 is /boot and sda6 is /
Indeed you could be right. How I can change such a flag?
Second question: the error message said that no /boot/grub2/i386- pc/normal.mod file is available and effectively I don' t have such a file in that position but only it is in /usr/lib/grub/i386-pc/. So changing the boot flag would be enough to solve the problem?
Please don't try this unless others reply to support this, but...
If you can boot to a Fedora CD/DVD which is able to detect your Fedora install then I think it should be something like this...
chroot /mnt/sysimage
fdisk /dev/sda Command (m for help): a Partition number ([snip] default x): 5 Command (m for help): w The partition table has been altered. Calling ioctl() to re-read partition table.
grub2-install /dev/sda
Hi few more questions inline with your reply.
On Wed, Dec 23, 2015 at 10:12 AM, Doug H. fedoraproject.org@wombatz.com wrote:
On Wed, 2015-12-23 at 09:54 -0500, Walter Cazzola wrote:
On Wed, Dec 23, 2015 at 9:34 AM, Doug H. <fedoraproject.org@wombatz.c om> wrote:
On Wed, 2015-12-23 at 09:20 -0500, Walter Cazzola wrote:
This are the related options: General Boot Sequence Legacy (this flagged)
In that case, I think your first post indicated that the boot flag was not set for your new /boot partition. From your post, with lots of snipping:
Device Boot Start End Sectors Size Id Type /dev/sda2 * 81920 25710591 25628672 12.2G 27 Hidden NTFS /dev/sda5 201410560 202776575 1366016 667M 83 Linux
where sda1-3 are the original windows partitions, sda5 is /boot and sda6 is /
Indeed you could be right. How I can change such a flag?
Second question: the error message said that no /boot/grub2/i386- pc/normal.mod file is available and effectively I don' t have such a file in that position but only it is in /usr/lib/grub/i386-pc/. So changing the boot flag would be enough to solve the problem?
Please don't try this unless others reply to support this, but...
ok I will wait
If you can boot to a Fedora CD/DVD which is able to detect your Fedora install then I think it should be something like this..
what do you mean by " is able to detect your Fedora install"? I can boot with the live cd and mount all the partitions but nothing is automatically done.
chroot /mnt/sysimage
what should sysimage be? is this a file in the /boot partition? I don' t have any file with this name in /boot
fdisk /dev/sda Command (m for help): a Partition number ([snip] default x): 5 Command (m for help): w The partition table has been altered. Calling ioctl() to re-read partition table.
do the numbers already refer to my partitions or I' ve to change something? what should this do?
grub2-install /dev/sda
if this doesn't work can I go back to the previous situation? if yes how?
thanks for the help Walter
--
I don't know if it was a rogue update or something but I had the same (or similar) problem. Booting dropped me to the grub rescue prompt and my i386-pc folder was also empty.
Only strange part of my setup is the main drive is GPT partitioned with regular BIOS so I have a small bios_grub partition at the beginning of the drive for the stage 2 bootloader.
Somehow my /boot filesystem got corrupted and after a fsck and copying the files from /usr/lib/grub2/i386-pc to /boot/grub2/i386-pc I was able to boot again.
Thanks, Richard
On Wed, Dec 23, 2015 at 11:58 AM, Richard Shaw hobbes1069@gmail.com wrote:
I don't know if it was a rogue update or something but I had the same (or similar) problem. Booting dropped me to the grub rescue prompt and my i386-pc folder was also empty.
Only strange part of my setup is the main drive is GPT partitioned with regular BIOS so I have a small bios_grub partition at the beginning of the drive for the stage 2 bootloader.
Somehow my /boot filesystem got corrupted and after a fsck and copying the files from /usr/lib/grub2/i386-pc to /boot/grub2/i386-pc I was able to boot again.
I' ve tried to copy from /usr/lib/grub (I don' t have grub2 dir but just grub) but the only result was to boot to the grub shell instead of the grub rescue shell.
Can this help?
Walter
--
On Wed, 2015-12-23 at 11:48 -0500, Walter Cazzola wrote:
Hi few more questions inline with your reply.
chroot /mnt/sysimage what should sysimage be? is this a file in the /boot partition? I don't have any file with this name in /boot
Historically (and currently I think), the rescue/repair option for the Fedora CD & DVD is to look for a Fedora install and then mount it in /mnt/sysimage. So there would be a /mnt/sysimage/boot for example. Thus you can do `chroot /mnt/sysimage` and the shell will act like you are simply logged into the Fedora system. Things would work as if you had booted normally into the Fedora system. That allows you to do maintenance using the same full paths as "normal".
fdisk /dev/sda Command (m for help): a Partition number ([snip] default x): 5 Command (m for help): w The partition table has been altered. Calling ioctl() to re-read partition table.
do the numbers already refer to my partitions or I've to change something? what should this do?
I ran an fdisk on a temp loopfile and then altered the output to show "5" since I think that is the partition that I think might need to be bootable. What that does is to make partition 5 the boot/bootable partition. I don't really know how that works at a deeper level and I have little experience with efi so far. My suggestions are based on the idea that your bios setup is presenting a traditional/older system type.
grub2-install /dev/sda
if this doesn't work can I go back to the previous situation? if yes how?
The above assumes that your Windows boot utility has already been messed with and is not usable at the moment. If that is true then I am not even sure you need to do the grub2-install but it seems like it would not make it worse.
But again I don't feel comfortable suggesting these actions unless we get some community support for it.
Hi. I've done some attempts and following a guide for ubunto I got some improvements.
At the moment the normal.mod is in the boot partition and I'm not starting with the grub2 rescue terminal but with still the selection menu doesn' t appear and the system doesn' t boot.
At the moment the system get stuck on: grub2> prompt.
I dug a littel in the system and - the boot flag still points to the sda2 (the dell recopvery partition) instead of the one with /boot partition (sda5) - in /etc there is a grub2.cfg file that it is a dangling link to /boot/grub2/grub.cfg probably both of these points are part of the problem.
Looking around I found some guides about ubunto (e.g., https://www.linux.com/learn/tutorials/776643-how-to-rescue-a-non-booting-gru...) that uses an update-grub command to create the boot loader but I can' t find anything like that for fedora. What I'm I doing wrong now?
Walter
On Wed, Dec 23, 2015 at 1:08 PM, Doug H. fedoraproject.org@wombatz.com wrote:
On Wed, 2015-12-23 at 11:48 -0500, Walter Cazzola wrote:
Hi few more questions inline with your reply.
chroot /mnt/sysimage what should sysimage be? is this a file in the /boot partition? I don't have any file with this name in /boot
Historically (and currently I think), the rescue/repair option for the Fedora CD & DVD is to look for a Fedora install and then mount it in /mnt/sysimage. So there would be a /mnt/sysimage/boot for example. Thus you can do `chroot /mnt/sysimage` and the shell will act like you are simply logged into the Fedora system. Things would work as if you had booted normally into the Fedora system. That allows you to do maintenance using the same full paths as "normal".
fdisk /dev/sda Command (m for help): a Partition number ([snip] default x): 5 Command (m for help): w The partition table has been altered. Calling ioctl() to re-read partition table.
do the numbers already refer to my partitions or I've to change something? what should this do?
I ran an fdisk on a temp loopfile and then altered the output to show "5" since I think that is the partition that I think might need to be bootable. What that does is to make partition 5 the boot/bootable partition. I don't really know how that works at a deeper level and I have little experience with efi so far. My suggestions are based on the idea that your bios setup is presenting a traditional/older system type.
grub2-install /dev/sda
if this doesn't work can I go back to the previous situation? if yes how?
The above assumes that your Windows boot utility has already been messed with and is not usable at the moment. If that is true then I am not even sure you need to do the grub2-install but it seems like it would not make it worse.
But again I don't feel comfortable suggesting these actions unless we get some community support for it.
-- Doug H.
--
Sorry for the flooding but my investigations is goin' further into the problem.
Looking at the content of /boot -rw-r--r--. 1 root root 160270 Oct 5 11:58 config-4.2.3-300.fc23.x86_64 drwxr-xr-x. 4 root root 4096 Oct 29 17:26 efi -rw-r--r--. 1 root root 184380 Oct 21 2014 elf-memtest86+-5.01 drwxr-xr-x. 2 root root 4096 Oct 29 17:23 extlinux drwxr-xr-x. 6 root root 4096 Dec 23 15:18 grub2 -rw-rw-r--. 1 root root 52373550 Dec 22 23:07 initramfs-0-rescue-4f585391395b40e3823bebd86a3e6c01.img -rw-rw-r--. 1 root root 17771095 Dec 22 23:07 initramfs-4.2.3-300.fc23.x86_64.img -rw-r--r--. 1 root root 571817 Oct 29 17:27 initrd-plymouth.img drwx------. 2 root root 16384 Dec 22 23:01 lost+found -rw-r--r--. 1 root root 182704 Oct 21 2014 memtest86+-5.01 -rw-------. 1 root root 3152021 Oct 5 11:58 System.map-4.2.3-300.fc23.x86_64 -rwxr-xr-x. 1 root root 5977368 Dec 22 23:07 vmlinuz-0-rescue-4f585391395b40e3823bebd86a3e6c01 -rwxr-xr-x. 1 root root 5977368 Oct 5 11:59 vmlinuz-4.2.3-300.fc23.x86_64
it seems that initrd for tmy kernel is missing and also tryin' to manually boot from the grub menu let the system fail.
My impression is that the whole fedora installation tool failed and I' ve a partial system but I can' t find more on this. I' m quite ready to give up and try to install a different flavor of linux.
Walter
On Wed, Dec 23, 2015 at 4:05 PM, Walter Cazzola cazzola@di.unimi.it wrote:
Hi. I've done some attempts and following a guide for ubunto I got some improvements.
At the moment the normal.mod is in the boot partition and I'm not starting with the grub2 rescue terminal but with still the selection menu doesn' t appear and the system doesn' t boot.
At the moment the system get stuck on: grub2> prompt.
I dug a littel in the system and
- the boot flag still points to the sda2 (the dell recopvery partition)
instead of the one with /boot partition (sda5)
- in /etc there is a grub2.cfg file that it is a dangling link to
/boot/grub2/grub.cfg probably both of these points are part of the problem.
Looking around I found some guides about ubunto (e.g., https://www.linux.com/learn/tutorials/776643-how-to-rescue-a-non-booting-gru...) that uses an update-grub command to create the boot loader but I can' t find anything like that for fedora. What I'm I doing wrong now?
Walter
On Wed, Dec 23, 2015 at 1:08 PM, Doug H. fedoraproject.org@wombatz.com wrote:
On Wed, 2015-12-23 at 11:48 -0500, Walter Cazzola wrote:
Hi few more questions inline with your reply.
chroot /mnt/sysimage what should sysimage be? is this a file in the /boot partition? I don't have any file with this name in /boot
Historically (and currently I think), the rescue/repair option for the Fedora CD & DVD is to look for a Fedora install and then mount it in /mnt/sysimage. So there would be a /mnt/sysimage/boot for example. Thus you can do `chroot /mnt/sysimage` and the shell will act like you are simply logged into the Fedora system. Things would work as if you had booted normally into the Fedora system. That allows you to do maintenance using the same full paths as "normal".
fdisk /dev/sda Command (m for help): a Partition number ([snip] default x): 5 Command (m for help): w The partition table has been altered. Calling ioctl() to re-read partition table.
do the numbers already refer to my partitions or I've to change something? what should this do?
I ran an fdisk on a temp loopfile and then altered the output to show "5" since I think that is the partition that I think might need to be bootable. What that does is to make partition 5 the boot/bootable partition. I don't really know how that works at a deeper level and I have little experience with efi so far. My suggestions are based on the idea that your bios setup is presenting a traditional/older system type.
grub2-install /dev/sda
if this doesn't work can I go back to the previous situation? if yes how?
The above assumes that your Windows boot utility has already been messed with and is not usable at the moment. If that is true then I am not even sure you need to do the grub2-install but it seems like it would not make it worse.
But again I don't feel comfortable suggesting these actions unless we get some community support for it.
-- Doug H.
--
--
On 12/23/2015 10:33 PM, Walter Cazzola wrote:
My impression is that the whole fedora installation tool failed and I' ve a partial system but I can' t find more on this. I' m quite ready to give up and try to install a different flavor of linux.
I told you the base, your disk partitioning, is bad. A new/good fresh install avoid wasting time... Normally, it takes only about 20 mn. Dont forget efi partition. Good luck
On Wed, 2015-12-23 at 16:33 -0500, Walter Cazzola wrote:
Sorry for the flooding but my investigations is goin' further into the problem.
Looking at the content of /boot -rw-r--r--. 1 root root 160270 Oct 5 11:58 config-4.2.3- 300.fc23.x86_64 drwxr-xr-x. 4 root root 4096 Oct 29 17:26 efi -rw-r--r--. 1 root root 184380 Oct 21 2014 elf-memtest86+-5.01 drwxr-xr-x. 2 root root 4096 Oct 29 17:23 extlinux drwxr-xr-x. 6 root root 4096 Dec 23 15:18 grub2 -rw-rw-r--. 1 root root 52373550 Dec 22 23:07 initramfs-0-rescue- 4f585391395b40e3823bebd86a3e6c01.img -rw-rw-r--. 1 root root 17771095 Dec 22 23:07 initramfs-4.2.3- 300.fc23.x86_64.img -rw-r--r--. 1 root root 571817 Oct 29 17:27 initrd-plymouth.img drwx------. 2 root root 16384 Dec 22 23:01 lost+found -rw-r--r--. 1 root root 182704 Oct 21 2014 memtest86+-5.01 -rw-------. 1 root root 3152021 Oct 5 11:58 System.map-4.2.3- 300.fc23.x86_64 -rwxr-xr-x. 1 root root 5977368 Dec 22 23:07 vmlinuz-0-rescue- 4f585391395b40e3823bebd86a3e6c01 -rwxr-xr-x. 1 root root 5977368 Oct 5 11:59 vmlinuz-4.2.3- 300.fc23.x86_64
it seems that initrd for tmy kernel is missing and also tryin' to manually boot from the grub menu let the system fail.
My impression is that the whole fedora installation tool failed and I've a partial system but I can' t find more on this. I' m quite ready to give up and try to install a different flavor of linux.
Re-install, Fedora or otherwise, might be the quick fix. But I don't see that initrd is missing. My current top level for boot is:
ls -1 /boot
config-4.2.6-301.fc23.x86_64 config-4.2.7-300.fc23.x86_64 config-4.2.8-300.fc23.x86_64 elf-memtest86+-5.01 extlinux grub2 initramfs-0-rescue-c10a26eb97b3451f95a20a792c5a897d.img initramfs-4.1.7-200.fc22.x86_64.img initramfs-4.2.6-301.fc23.x86_64.img initramfs-4.2.7-300.fc23.x86_64.img initramfs-4.2.8-300.fc23.x86_64.img initrd-plymouth.img lost+found memtest86+-5.01 System.map-4.2.6-301.fc23.x86_64 System.map-4.2.7-300.fc23.x86_64 System.map-4.2.8-300.fc23.x86_64 vmlinuz-0-rescue-c10a26eb97b3451f95a20a792c5a897d vmlinuz-4.2.6-301.fc23.x86_64 vmlinuz-4.2.7-300.fc23.x86_64 vmlinuz-4.2.8-300.fc23.x86_64
Notice that the init fs files are named as yours is.
On Wed, 2015-12-23 at 07:12 -0800, Doug H. wrote:
Please don't try this unless others reply to support this, but...
If you can boot to a Fedora CD/DVD which is able to detect your Fedora install then I think it should be something like this...
chroot /mnt/sysimage
fdisk /dev/sda Command (m for help): a Partition number ([snip] default x): 5 Command (m for help): w The partition table has been altered. Calling ioctl() to re-read partition table.
grub2-install /dev/sda
As maderios has pointed out, this partitioning does not look workable. I don't think you can toggle the boot flag on for an extended partition.
On Dec 23, 2015 11:34 PM, "Doug H." fedoraproject.org@wombatz.com wrote:
As maderios has pointed out, this partitioning does not look workable. I don't think you can toggle the boot flag on for an extended partition.
Ok tomorrow I'll redo the installation.
But just to do the right thing since the beginning how should the the disk be partitioned?
Considering that the windows installation is split over three partitions (sda1-3) that I won't touch and I would like to have -/var -/tmp -/ -/home - swap -/opt -/boot - and a vfat partition to exchange data with Windows On separate partitions.
Also I don't know what this efi partition (that maderios is mentioning) is and is for. And how I should create it.
Any help would be really appreciated on this matter.
Thank you Walter
On 12/23/2015 11:58 PM, Walter Cazzola wrote:
On Dec 23, 2015 11:34 PM, "Doug H." <fedoraproject.org@wombatz.com mailto:fedoraproject.org@wombatz.com> wrote:
As maderios has pointed out, this partitioning does not look workable. I don't think you can toggle the boot flag on for an extended partition.
Ok tomorrow I'll redo the installation.
But just to do the right thing since the beginning how should the the disk be partitioned?
Considering that the windows installation is split over three partitions (sda1-3) that I won't touch and I would like to have -/var -/tmp -/ -/home
- swap
-/opt -/boot
- and a vfat partition to exchange data with Windows
On separate partitions.
Also I don't know what this efi partition (that maderios is mentioning) is and is for. And how I should create it.
If you want only one system, F23, installed on hour hd, I suggest simple partitionning /dev/sda1 /boot/efi /dev/sda2 swap /dev/sda3 / /dev/sda4 /home
If you want dual boot F23 + Windows, example /dev/sda1 /boot/efi /dev/sda2 W$ /dev/sda3 W$ /dev/sda4 swap /dev/sda5 / /dev/sda6 /home
Hi, thanks all for the help at end I missed to create a bootbios partion of 2MiB once I added that the system booted. The strange point is that I didn't find it explained in any tutorial but thanks to your advice I noticed that entry in the filesystem menu.
Walter
On Thu, Dec 24, 2015 at 2:04 PM, maderios maderios@gmail.com wrote:
On 12/23/2015 11:58 PM, Walter Cazzola wrote:
On Dec 23, 2015 11:34 PM, "Doug H." <fedoraproject.org@wombatz.com mailto:fedoraproject.org@wombatz.com> wrote:
As maderios has pointed out, this partitioning does not look workable. I don't think you can toggle the boot flag on for an extended partition.
Ok tomorrow I'll redo the installation.
But just to do the right thing since the beginning how should the the disk be partitioned?
Considering that the windows installation is split over three partitions (sda1-3) that I won't touch and I would like to have -/var -/tmp -/ -/home
- swap
-/opt -/boot
- and a vfat partition to exchange data with Windows
On separate partitions.
Also I don't know what this efi partition (that maderios is mentioning) is and is for. And how I should create it.
If you want only one system, F23, installed on hour hd, I suggest simple partitionning /dev/sda1 /boot/efi /dev/sda2 swap /dev/sda3 / /dev/sda4 /home
If you want dual boot F23 + Windows, example /dev/sda1 /boot/efi /dev/sda2 W$ /dev/sda3 W$ /dev/sda4 swap /dev/sda5 / /dev/sda6 /home
--
On Thu, Dec 24, 2015 at 3:15 PM, Walter Cazzola cazzola@di.unimi.it wrote:
Hi, thanks all for the help at end I missed to create a bootbios partion of 2MiB once I added that the system booted. The strange point is that I didn't find it explained in any tutorial but thanks to your advice I noticed that entry in the filesystem menu.
This is unexpected because BIOSBoot only exists on GPT. But Windows requires MBR on BIOS (legacy) systems, and GPT on UEFI systems. It's not possible to get it to do anything different. So if the installation is GPT, that suggests UEFI installation, and there should be an EFI System partition rather than BIOSBoot.
The fact there is an extended partition, and boot flags in earlier reports, shows this is an MBR partitioned drive. Those things don't exist with GPT drives.
On Thu, Dec 24, 2015 at 11:30 PM, Chris Murphy lists@colorremedies.com wrote:
On Thu, Dec 24, 2015 at 3:15 PM, Walter Cazzola cazzola@di.unimi.it wrote:
Hi, thanks all for the help at end I missed to create a bootbios partion of
2MiB
once I added that the system booted. The strange point is that I didn't
find
it explained in any tutorial but thanks to your advice I noticed that
entry
in the filesystem menu.
This is unexpected because BIOSBoot only exists on GPT. But Windows requires MBR on BIOS (legacy) systems, and GPT on UEFI systems. It's not possible to get it to do anything different. So if the installation is GPT, that suggests UEFI installation, and there should be an EFI System partition rather than BIOSBoot.
The fact there is an extended partition, and boot flags in earlier reports, shows this is an MBR partitioned drive. Those things don't exist with GPT drives.
I don't know what to say, this is my current configuration:
/dev/sda1 63 80324 80262 39.2M de Dell Utility /dev/sda2 * 81920 25710591 25628672 12.2G 27 Hidden NTFS WinRE /dev/sda3 25710592 201408511 175697920 83.8G 7 HPFS/NTFS/exFAT /dev/sda4 201408512 1953523711 1752115200 835.5G 5 Extended /dev/sda5 201410560 201414655 4096 2M 83 Linux /dev/sda6 201416704 202883071 1466368 716M 83 Linux /dev/sda7 202885120 307742719 104857600 50G 83 Linux /dev/sda8 307744768 358076415 50331648 24G 82 Linux swap / Sola /dev/sda9 358078464 372758527 14680064 7G 83 Linux /dev/sda10 372760576 383246335 10485760 5G 83 Linux /dev/sda11 383248384 393734143 10485760 5G 83 Linux /dev/sda12 393736192 396881919 3145728 1.5G 6 FAT16 /dev/sda13 396883968 1953523711 1556639744 742.3G 83 Linux
and for now the system boots correctly
Walter --
On Thu, Dec 24, 2015 at 4:21 PM, Walter Cazzola cazzola@di.unimi.it wrote:
On Thu, Dec 24, 2015 at 11:30 PM, Chris Murphy lists@colorremedies.com wrote:
On Thu, Dec 24, 2015 at 3:15 PM, Walter Cazzola cazzola@di.unimi.it wrote:
Hi, thanks all for the help at end I missed to create a bootbios partion of 2MiB once I added that the system booted. The strange point is that I didn't find it explained in any tutorial but thanks to your advice I noticed that entry in the filesystem menu.
This is unexpected because BIOSBoot only exists on GPT. But Windows requires MBR on BIOS (legacy) systems, and GPT on UEFI systems. It's not possible to get it to do anything different. So if the installation is GPT, that suggests UEFI installation, and there should be an EFI System partition rather than BIOSBoot.
The fact there is an extended partition, and boot flags in earlier reports, shows this is an MBR partitioned drive. Those things don't exist with GPT drives.
I don't know what to say, this is my current configuration:
/dev/sda1 63 80324 80262 39.2M de Dell Utility /dev/sda2 * 81920 25710591 25628672 12.2G 27 Hidden NTFS WinRE /dev/sda3 25710592 201408511 175697920 83.8G 7 HPFS/NTFS/exFAT /dev/sda4 201408512 1953523711 1752115200 835.5G 5 Extended /dev/sda5 201410560 201414655 4096 2M 83 Linux /dev/sda6 201416704 202883071 1466368 716M 83 Linux /dev/sda7 202885120 307742719 104857600 50G 83 Linux /dev/sda8 307744768 358076415 50331648 24G 82 Linux swap / Sola /dev/sda9 358078464 372758527 14680064 7G 83 Linux /dev/sda10 372760576 383246335 10485760 5G 83 Linux /dev/sda11 383248384 393734143 10485760 5G 83 Linux /dev/sda12 393736192 396881919 3145728 1.5G 6 FAT16 /dev/sda13 396883968 1953523711 1556639744 742.3G 83 Linux
and for now the system boots correctly
There is no BIOSBoot in that list though. And that list is using MBR type codes. I'd say this listing is unreliable, I don't know the source. Please post the complete, unedited listing from:
# parted /dev/sda u s p
That'll provide better info.
-
Chris Murphy -
Doug H. -
maderios -
Richard Shaw -
Walter Cazzola