Code: Select all
Executing 'grub-install /dev/sda' failed
I would be really grateful for beginner friendly assistance to get my laptop to (dual) boot again.error: unknown filesystem.
Entering rescue mode...
grub rescue> _
Code: Select all
Executing 'grub-install /dev/sda' failed
I would be really grateful for beginner friendly assistance to get my laptop to (dual) boot again.error: unknown filesystem.
Entering rescue mode...
grub rescue> _
msdos
or UEFI
. What are results for the next questions:
Code: Select all
sudo parted -l
Code: Select all
inxi -po
Code: Select all
[ -d /sys/firmware/efi ] && echo "EFI mode" || echo "Legacy Bios mode"
Code: Select all
sudo os-prober
Code: Select all
sudo parted -l
Code: Select all
Model: ATA ST1750LM000 HN-M (scsi)
Disk /dev/sda: 1750GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 17.4kB 134MB 134MB Microsoft reserved partition msftres
2 134MB 128GB 128GB ntfs msftdata
3 129GB 1239GB 1110GB ntfs Basic data partition msftdata
4 1239GB 1750GB 511GB ext4
Model: ATA SAMSUNG MZ7PC128 (scsi)
Disk /dev/sdb: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 106MB 105MB primary ntfs boot
2 106MB 94.0GB 93.9GB primary ntfs
3 94.0GB 128GB 34.0GB extended
5 94.0GB 117GB 23.1GB logical fat32
6 117GB 128GB 10.9GB logical ext4
Model: Lexar USB Flash Drive (scsi)
Disk /dev/sdc: 64.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 64.0GB 64.0GB primary fat32 boot
Code: Select all
inxi -po
Code: Select all
Partition: ID-1: /cdrom size: 60G used: 2.8G (5%) fs: vfat dev: /dev/sdc1
ID-2: / size: 969M used: 295M (33%) fs: overlay dev: N/A
Unmounted: ID-1: /dev/sda1 size: 0.13G label: N/A uuid: N/A
ID-2: /dev/sda2 size: 127.93G fs: NTFS label: Samsung 830 uuid: 5CF83049F83023A4
ID-3: /dev/sda3 size: 1110.25G fs: NTFS label: Major uuid: 384EB1AD4EB16472
ID-4: /dev/sda4 size: 511.11G fs: ext4 label: Mint_Data uuid: b02f5948-b0d1-4b22-9a42-bbd88bd9949e
ID-5: /dev/sdb1 size: 0.10G fs: NTFS label: System Reserved uuid: 1A042EB2042E9135
ID-6: /dev/sdb2 size: 93.89G fs: NTFS label: N/A uuid: N/A
ID-7: /dev/sdb5 size: 23.14G fs: FAT (32 bit) label: LM uuid: 827A-5730
ID-8: /dev/sdb6 size: 10.90G fs: ext4 label: N/A uuid: c5a5d6a8-417e-435e-b9ff-68dafaf8ad75
Code: Select all
[ -d /sys/firmware/efi ] && echo "EFI mode" || echo "Legacy Bios mode"
Code: Select all
Legacy Bios mode
Code: Select all
sudo os-prober
Code: Select all
/dev/sdb1:Windows 7:Windows:chain
/dev/sdb6:Linux Mint 19 Tara (19):LinuxMint:linux
Code: Select all
GNU GRUB version 2.02
Linux Mint 19 Xfce
Advanced options for Linux Mint 19 Xfce
Memory test (memtest86+)
Memory test (memtest86+, serial console 115200)
*Windows 7 (on /dev/sdb1)
Linux Mint 19 Tara (19) (on /dev/sdb6)
Advanced options for Linux Mint 19 Tara (19) (on /dev/sdb6)
The problem is that grub is installed into windows-partition, which makes Windows unbootable. The fix is to use Windows´ repair or installation disk and runFrederick Turner wrote: ⤴Fri Oct 12, 2018 7:52 am Okay, I think I have made some progress. I installed LM to sdb5. I installed GRUB to sdb1. I left the previous install of LM on sdb6 untouched. I can now boot into LM on sdb5. However, I cannot boot into Windows 7. The W7-OS shows up in the GRUB bootloader but when I select it nothing happens. What can I do to correct this?
Code: Select all
bootrec /fixboot
bootrec /fixmbr
because it makes linux unbootable.Code: Select all
sudo fdisk -l 2>/dev/null | egrep "Disk /|/dev/" | sed "s#^/dev/#Part /dev/#" | awk '{print $2}' | sed 's/://' | xargs -n1 -iX sudo sh -c "dd if=X count=1 2>/dev/null | grep GRUB > /dev/null && echo Grub found: X || echo no Grub: X"
Code: Select all
no Grub: /dev/sda
no Grub: /dev/sda1
no Grub: /dev/sda2
no Grub: /dev/sda3
no Grub: /dev/sda4
Grub found: /dev/sdb
no Grub: /dev/sdb1
no Grub: /dev/sdb2
no Grub: /dev/sdb3
no Grub: /dev/sdb5
no Grub: /dev/sdb6
That idea seems to have worked. I now most certainly have a working dual boot system again. I really wonder what went wrong to start with.Frederick Turner wrote: ⤴Fri Oct 12, 2018 4:08 pm One idea would be to actually use the fix "bootrec /fixmbr" and then start a live LM USB instance and use boot-repair to re-install GRUB. However, I am not sure whether this is a good idea or whether it will create more harm than good. So, it would be great to get your counsel and advice.
Code: Select all
Model: ATA SAMSUNG MZ7PC128 (scsi)
Disk /dev/sdb: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 106MB 105MB primary
2 106MB 94,0GB 93,9GB primary ntfs boot
3 94,0GB 128GB 34,0GB extended lba
5 94,0GB 117GB 23,1GB logical ext4
6 117GB 128GB 10,9GB logical fat32
Code: Select all
Partition: ID-1: / size: 22G used: 7.5G (38%) fs: ext4 dev: /dev/sdb5
Unmounted: ID-1: /dev/sda1 size: 0.13G label: N/A uuid: N/A
ID-2: /dev/sda2 size: 127.93G fs: NTFS
label: Samsung 830 uuid: 5CF83049F83023A4
ID-3: /dev/sda3 size: 1110.25G fs: NTFS
label: Major uuid: 384EB1AD4EB16472
ID-4: /dev/sda4 size: 511.11G fs: ext4
label: Mint_Data uuid: b02f5948-b0d1-4b22-9a42-bbd88bd9949e
ID-5: /dev/sdb1 size: 0.10G label: N/A uuid: N/A
ID-6: /dev/sdb2 size: 93.89G fs: NTFS label: N/A uuid: N/A
ID-7: /dev/sdb6 size: 10.90G fs: FAT (32 bit)
Absolutely a good idea, because you have a very small linux-partition.Frederick Turner wrote: ⤴Fri Oct 12, 2018 5:51 pm I wonder whether it would be sensible to merge former sdb6 with the current LM partition sdb5 to create more space so that I shall never ever run into "no space" problems during OS upgrades. What are your thoughts? Is my system now OK or do I need to do a bit more tidying to prevent troubles ahead?
Done. Thanks for the reassurance and overall guidance.administrollaattori wrote: ⤴Sat Oct 13, 2018 2:06 pm Absolutely a good idea, because you have a very small linux-partition.