Siduction Forum
Siduction Forum => Software - Support => Topic started by: turborat on 2021/03/05, 17:48:12
-
I installed siduction (5.10.20-towo.1-siduction-amd64 cinnamon) on ssd BEFORE installing windows 10 (on a 3rd partition) and lost my grub bootloader. Can someone please help me restore it so I can boot both operating systems?
-
A little "old" :D https://manual.siduction.org/sys-admin-grub2#mbr-over-grub2
-
Thanks unklarer,
but I have no idea how to enter those commands and I’m afraid of screwing up the whole thing
again. Maybe someone can help me?
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 206847 204800 100M EFI System
/dev/nvme0n1p2 206848 233471999 233265152 111.2G Linux filesystem
/dev/nvme0n1p3 233472000 233504767 32768 16M Microsoft reserved
/dev/nvme0n1p4 233504768 468860927 235356160 112.2G Microsoft basic data
GPT PMBR size mismatch (5048543 != 15138815) will be corrected by write.
Disk /dev/sda: 7.22 GiB, 7751073792 bytes, 15138816 sectors
Disk model: DataTraveler 3.0
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: gpt
Disk identifier: 261A12F6-64B4-4F4C-B124-562F2C3A0166
Device Start End Sectors Size Type
/dev/sda1 64 371 308 154K Microsoft basic data
/dev/sda2 372 6131 5760 2.8M EFI System
/dev/sda3 6132 5048479 5042348 2.4G Microsoft basic data
# /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>
UUID=5A39-A83B /boot/efi vfat umask=0077 0 2
UUID=a1ccf49c-1604-4e11-a021-10038782b7c8 / ext4 defaults,noatime 0 1
root@tuf:/home/rp#
-
^I'm sorry if you don't know how to enter the commands.
In any case, you would have to chroot into the siduction system to restore the bootloader.
My suggestion:
Install the Cinnamon with this https://news.siduction.org/ new. I think it is the shortest way for you. ;)
Remember, you can't install $M-Windows after LINUX if you don't know how to fix the Linux bootloader. :)
-
Remember, you can't install $M-Windows after LINUX if you don't know how to fix the Linux bootloader. :)
This^!
If you don't have any personal data on the disk, start again and install Windows first, then install siduction. siduction install should detect Windows and automatically include it in GRUB.
If you do have data you could back it up to an external drive and restore it afterward.
Another option could be to boot into siduction from your system Boot Select menu and reinstall GRUB. Yet another option could be to boot siduction from a USB key with rEFInd and reinstall GRUB.
-
Thank you for replies.
I found that a program that I need to run in windows10 can be installed on linux now, so I zero wrote the ssd and (fresh) installed siduction kde.
Now I will no longer have any windows related dual-bootloader type computer problems!