Siduction Forum
Siduction Forum => Software - Support => Topic started by: vilde on 2018/01/03, 19:39:26
-
Installed the new xfce iso instead of old instalation. One hd with siduction another hd with windowz. The installer prompted me to create a efi partition, I did so and after installation grub will not find the windowz installation.
No other change have been done on the hard disks than the new efi partition on the siduction hd.
-
Did you run os-prober?
-
Did you run os-prober?
No, never herd about that, is it in the installer?
Edit: I tried to read about os-prober and I also installed it but it gives nothing out when running it.
Edit 2:
Looks like this running os-prober and then update-grub, not finding any windows partition:
root@vilde-T420:/home/vilde# os-prober
root@vilde-T420:/home/vilde# update-grub
Generera konfigurationsfil för grub …
Hittade tema: /usr/share/grub/themes/patience/theme.txt
Hittade linux-avbildning: /boot/vmlinuz-4.14.11-towo.1-siduction-amd64
Hittade initrd-avbildning: /boot/initrd.img-4.14.11-towo.1-siduction-amd64
Hittade linux-avbildning: /boot/vmlinuz-4.14.10-towo.1-siduction-amd64
Hittade initrd-avbildning: /boot/initrd.img-4.14.10-towo.1-siduction-amd64
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
färdigt
-
I started the computer from usb-stick and are now running live from latest xfce iso.
siducer@siduction:~$ su
root@siduction:/home/siducer# os-prober
/dev/sda4:Debian GNU/Linux buster/sid:Debian:linux
root@siduction:/home/siducer#
No windows hd/partition found now either. Is this a bug in the iso?
-
How would that be a bug in the iso-image?
-
How would that be a bug in the iso-image?
I have no idea. So far I have always only installed siduction on a hd and the last couple of years it (Grub) has always found all my other os on the computer, this time it fails and I don't know why.
This computer has exactly the same setup as before with siduction, this time the installer told me to create an efi partition, at first I didn't do it and installed anyway but then on boot it left me with grub rescue or whatever it is called, I installed again, made an efi partition in the beginning of the hd and then this happened. The only difference from before is a new iso and that I did change the former siduction partition to an efi partition and the rest as ext4.
So for me it's a bug or a regression or whatever.
-
Maybe this (https://wiki.siduction.de/index.php?title=Probleme_mit_UEFI_l%C3%B6sen) helps after running it through deepl
-
Are you shure that windows is installed with uefi too? The windows-drive shows no fat-partition, so maybe you installed windows in legacy-mode.
-
Maybe this (https://wiki.siduction.de/index.php?title=Probleme_mit_UEFI_l%C3%B6sen) helps after running it through deepl
I will have a look at that
Are you shure that windows is installed with uefi too? The windows-drive shows no fat-partition, so maybe you installed windows in legacy-mode.
I have no idea about that either, can be that it is so, I have never really dealt with uefi, I just install with the installer.
-
Maybe this (https://wiki.siduction.de/index.php?title=Probleme_mit_UEFI_l%C3%B6sen) helps after running it through deepl
This is to much for me to understand, I did translate to English but then it's not so good, for example in the
-
Maybe this (https://wiki.siduction.de/index.php?title=Probleme_mit_UEFI_l%C3%B6sen) helps after running it through deepl
I tried to read this, to much over my head. I translated to English and for example the translated text says that I shall make an efi partition in the Bios, that's a wrong translation. This together makes it to hard to follow and understand.
I did gdisk -l /dev/sdX to check and it's not the output that is in the text, maybe this can help somebody to help me.
root@vilde-T420:/home/vilde# gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.3
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************
Disk /dev/sda: 234441648 sectors, 111.8 GiB
Model: INTEL SSDSC2BW12
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): CE862E8A-47B7-4D07-AF0F-C9E6600C31ED
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 234441614
Partitions will be aligned on 2048-sector boundaries
Total free space is 2925 sectors (1.4 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 526335 256.0 MiB EF00 EFI System
2 226052096 234440703 4.0 GiB 8200 Linux swap
3 183554048 226052095 20.3 GiB 8300 Linux filesystem
4 526336 183554047 87.3 GiB 8300 Linux filesystem
root@vilde-T420:/home/vilde# gdisk -l /dev/sdb
GPT fdisk (gdisk) version 1.0.3
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************
Disk /dev/sdb: 312581808 sectors, 149.0 GiB
Model: INTEL SSDSA2BW16
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 921B6789-19E3-4E3A-9E5A-C89BF655389A
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 312581774
Partitions will be aligned on 2048-sector boundaries
Total free space is 3693 sectors (1.8 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 1126399 549.0 MiB EF00 EFI System
2 1126400 122882047 58.1 GiB 0700 Microsoft basic data
3 122882048 312580095 90.5 GiB 8300 Linux filesystem
root@vilde-T420:/home/vilde#
If not I can live with the setup I have, to start win (like once a month or so) I just press F12 on boot and chose the other hd to boot from, that works.
-
First, after switching to UEFI in the BIOS a UEFI partition must be created
that`s exact the same as in the german version and means that YOU have to create a UEFI partition on your hdd (NOT in the BIOS) from at least 100 MB up to 500 MB formatted with FAT32.
-
First, after switching to UEFI in the BIOS a UEFI partition must be created
that`s exact the same as in the german version and means that YOU have to create a UEFI partition on your hdd (NOT in the BIOS) from at least 100 MB up to 500 MB formatted with FAT32.
I know that and I did that, when I did the install.
I mentioned that wrong translation as an example, I have very difficult to understand what's written even if it was in English because I understand to little of the vocabulary about whats under the hood in linux to be able to understand if it's also wrong translated.
-
I wonder all the time why the box with MBR has the EFI. ???
In my opinion, the problem arises because os-prober has not recognized the existing on sda/sdb.
The solution should be to install grub on both plates.
-
I wonder all the time why the box with MBR has the EFI. ???
In my opinion, the problem arises because os-prober has not recognized the existing on sda/sdb.
The solution should be to install grub on both plates.
Can bee a solution?
Anyway I just changed the settings in BIOS from where it has always been Legacy or UEFI? have been BOTH, now I changed it to only UEFI and then win is not starting, when telling bios to start from sdb.
That probably means that win is installed legacy mode just that Geier0815 asked before.
Can that be changed or shall I someway install Grub on sdb also as unklarer suggest?
-
that means that windows will only be found _and_ can only start in legacy mode - so i would suggest to switch to "legacy first" and modify the system that way
-
that means that windows will only be found _and_ can only start in legacy mode - so i would suggest to switch to "legacy first" and modify the system that way
Yes, I did change to only UEFI just to test. But can it not be "Both" as it has been before?
-
the problem is that the stick with that you can fix the installation must be started in legacy mode - and that means that you will run both linux and windows in legacy
-
the problem is that the stick with that you can fix the installation must be started in legacy mode - and that means that you will run both linux and windows in legacy
So would this be a solution?
Boot with a linux-usb stick that boots in legacy mode. Checkroot in to my installed siduction and reinstall Grub?
-
I have fixed the issue ie, it's not solved really. Couldn't find a solution to start legacy win from uefi grub.
I did a new win install with win uefi.
Then win allways started first and I had to use "f12" to start grub and siduction, the option in bios to choose boot order is gone. After update-grub , grub found my win install but win started anyway first on boot.
I tried to reinstall grub on siduction disc and yes now grub is starting when starting computer and I can use it as I want, multoboot with grub.
-
You solved your problem, not only fixed it. There is no way to use uefi and legay os the same time with the same setting in bios/uefi.