Grub not showing debian partition

mrmazda · 08-07-2019, 02:37 AM

Those are Grub Legacy files.

Which Debian version do you have?

djk44883 · 08-07-2019, 05:04 PM

Ok, the lines I gave were an "overview" not exactly step. It's an option to consider... You have to be booted in to the debian system to install to it's partition! Yes it warns you - "warnings" are not failures. ext2 is most likely generic for the ext family of filesystems.

You'll need to have a grub boot menu, from install, for the debian system. In your previous post, you haven't. If you go this route, you'll then have to create, yourself, an entry in the ubuntu system for it in /etc/grub.d [menuentry setroot chainlod boot].

To go the chroot method. There are a plethora examples to restore grub with this method, I've used it several times... but there are several commands to execute to co-ordinate the systems. It should be easy to find examples.

The files you list in /boot/grub in particular menu.list and prior /boot/grub/i386-pc/legacycfg.mod leads me to believe you have (mistakenly) installed grub-legacy when you need/want to install grub-pc It allows for MBR booting or EFI and/or a combination depending you system needs.

You're getting there, despite what it may look like. You need to get everything together, not just bits. Some have given you more, I haven't dual booted for years, so I don't have any references left. When you're comfortable with a single single open OS your life will probably be a lot easier.

djk44883 · 08-08-2019, 07:10 PM

Found it!! Ok, this may not be a preferred method. I found booting mulit-linux systems, it allows each to have their own grub menus. When kernels are updated or other updates requiring 'update-grub' each system are independent of each other in this respect.

Boot the secondary system. Install grub to the partition instead of the MBR. something like grub-install /dev/sda4 you'll have to know devices and partitions a,b,c - 1,2,3 !!! and you get warnings.

Back to the primary system - the one with the grub boot menu in the first place. In /etc/grub.d open 40_custom and first thing Save As - creating a new file!! 35_debian maybe.

Code:

#!/bin/sh
exec tail -n +3 $0
menuentry 'debian 10 buster' {
	savedefault
	insmod chain
	set root=(hd0,4)
	chainloader +1
}

You'll have to tweak this to your system!! You may have have savedefault enabled, you probably have different drive/partition.
After you save it, you have to allow executing (file browser) chmod +x 35_debian -- if you didn't know to use sudo or root privileges for this you are in way over your head. Now you need to update-grub.

Now to go over the top, if you don't want grub to generate it's own entries for debian (someday)... add to /etc/default/grub

Code:

GRUB_DISABLE_OS_PROBER=true

(of course update-grub needs up be ran)

This should boot with the menu from ubuntu, when you select debian, it should bring up the menu from debian, which should be straight forward from there. (if you don't want debian to add ubuntu to it's menu, disable os_prober)

I have an idle partition with linux mint 17.3... I have a feeling I haven't had a fresh installation since at least debian 7 wheezy, not really sure if that's good or bad. This system had been with stable, so I guess it's alright.

colorpurple21859 · 08-08-2019, 08:42 PM

put this in /etc/grub.d/40_custom

Code:

menuentry Debian{
set root=(hd0,6)
Linux /vmlinuz root=/dev/sda6
initrd /initrd.img
}

run

Code:

sudo update-grub

ondoho · 08-09-2019, 01:47 AM

Quote:

Originally Posted by djk44883

Found it!! Ok, this may not be a preferred method. I found booting mulit-linux systems, it allows each to have their own grub menus. When kernels are updated or other updates requiring 'update-grub' each system are independent of each other in this respect.

Oh, multibooting! Of course! :slap_forehead:
OP didn't mention that at all...

mrmazda · 08-09-2019, 04:53 AM

Dual means exactly two. Multi means more than one. Thus, multibooting subsumes dual-booting.

djk44883 · 08-09-2019, 03:29 PM

OP's mulit-boot includes that other one, so, disableing OS_PROBBER in the primary system, ubuntu, - you'll need to create your own win entry in /etc/grub.d ...unless you find it obsolete.

djk44883 · 08-09-2019, 03:34 PM

Quote:

Originally Posted by colorpurple21859

put this in /etc/grub.d/40_custom

You may consider copying the contents of 40_custom and create another file. Don't forget to make it executable.

On occasion if/when grub updates, the process will stop, informing you the file has been changed, do you want to keep it or install the new one...

ondoho · 08-10-2019, 01:20 AM

Quote:

Originally Posted by mrmazda

Dual means exactly two. Multi means more than one. Thus, multibooting subsumes dual-booting.

No, i meant multiboot as a commonly used term for things like this.

djk44883 · 08-10-2019, 07:47 AM

Quote:

Originally Posted by ondoho

No, i meant multiboot as a commonly used term for things like this.

wait, no my multi-linux was a subsumes dual booting system.

Outside of a tech support environment (maybe studies) - that's insane.