LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices



Reply
 
Search this Thread
Old 12-11-2011, 04:21 PM   #46
sdfi
Member
 
Registered: Oct 2011
Distribution: debian
Posts: 107

Original Poster
Rep: Reputation: Disabled

I thought i'd given the relevant information from df -h but here is exactly what it says, when i have mounted both sda1 and sda5
Code:
Filesystem	Size	Used	Available	Use%	Mounted on
tmpfs		124.7M	32.0K	124.7M		0%	/dev
/dev/sr0	648.0M	648.0M	0		100%	/cdrom
/dev/sda5	27.0G	664.6M	25.0G		3%	/mnt/sda5
/dev/sda1	9.2G	2.9G	5.8G		33%	/mnt/sda1
Quote:
rerun the boot script again.
How?

Last edited by sdfi; 12-11-2011 at 04:22 PM.
 
Old 12-11-2011, 05:08 PM   #47
widget
Senior Member
 
Registered: Oct 2008
Location: S.E. Montana
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,350

Rep: Reputation: 402Reputation: 402Reputation: 402Reputation: 402Reputation: 402
Use this link from a Live Session and post the results.text completely.
http://bootinfoscript.sourceforge.net/
 
Old 12-11-2011, 06:54 PM   #48
sdfi
Member
 
Registered: Oct 2011
Distribution: debian
Posts: 107

Original Poster
Rep: Reputation: Disabled
results.txt

Edit: done the rest of post #45.. the 40_custom file was printed, but i saw no recognition of /dev/sda5 containing linux.
Quote:
They should be below the entry that you currently see on your menu screen.
Just to make it clear (again) I do NOT see any menu screen on booting the HDD. Grub does NOT load.
Attached Files
File Type: txt RESULTS.txt (30.5 KB, 6 views)

Last edited by sdfi; 12-11-2011 at 07:18 PM.
 
Old 12-12-2011, 02:56 AM   #49
widget
Senior Member
 
Registered: Oct 2008
Location: S.E. Montana
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,350

Rep: Reputation: 402Reputation: 402Reputation: 402Reputation: 402Reputation: 402
I am about knackered.

As far as the boot info script goes in section one. Grub should load.

Have you had Voyage on there a long time? There seems to be a lot of kernels for it installed.

How are you using the internet? Are you on a different box or using a Live CD?

Sdb claims to have grub legacy installed on the MBR but no files to go to. Where is it getting this idea from, any idea? Was Voyage handling the MS boot?

Back to sda there is no mention of MS in the grub.cfg file (grub) or for that matter in your menu.lst (grub-legacy). Boot info script makes no real sense of either Debian or Voyage grub files. They appear to be faulty as hell.

I thought about trying to restore the grub-legacy from Voyage to the MBR but I think that is a waste of time as it doesn't look at all healthy either.

I have seen a lot of boot info script results. Even, ineptly, helped folks get MS to boot even though I don't use it and don't like it a bit. I have never seen a script result like this.

I really think this one has me whipped. Have no real idea at all where to go with this one.

The only thing I can think of is, if you are using or have a Debian Live CD you could boot to it, us apt to install "testdisk" on the live session and use it. May straighten your drive out, I just do not know.

Other wise I would back up your data from sda, format the bugger and start over.

Hopefully someone will jump in here with a lot better idea and we will both learn something.

Sorry, I am just out of options.
 
Old 12-12-2011, 09:31 AM   #50
hurry_hui
Member
 
Registered: Oct 2008
Location: Near Jakarta
Distribution: Slackware, Arch, Slax, Porteus, Tiny Core, Slitaz
Posts: 355
Blog Entries: 1

Rep: Reputation: 51
Quote:
Originally Posted by sdfi View Post
results.txt

Edit: done the rest of post #45.. the 40_custom file was printed, but i saw no recognition of /dev/sda5 containing linux.Just to make it clear (again) I do NOT see any menu screen on booting the HDD. Grub does NOT load.
Grub (both grub) does not load because it cannot find certain files.

We need to use manual check whether grub can see files it need to load.

We also need supergrub disk.

I will use grub2 to detect and boot manually via grub prompt (to access, on grub menu press C to enter command-line); hence we need supergrub disk or any bootable cd which boots grub2 (usually they boot isolinux). We only use device (hd0,1) and (hd0,5).

First we need to find files needed by (hd0,1)/boot/grub/menu.lst

Code:
ls (hd0,1)/
expected results vmlinuz, initrd.img

Code:
ls (hd0,1)/boot/
expected results vmlinuz-2.6.38-voyage, initrd.img-2.6.38-voyage (+ several vmlinuz and initrd.img)

Code:
ls (hd0,1)/boot/grub/
expected results stage2, menu.lst

----------------------------------------------

you can do similarly with (hd0,5)
directory we need to check:
(hd0,5)/boot/ ---> vmlinuz-2.6.32-5-686, initrd.img-2.6.32-5-686
(hd0,5)/boot/grub/ ---> core.img, grub.cfg

----------------------------------------------

having found expected files we need to type following line by line followed by ENTER and pay attention to output before executing next line

Code:
set root=(hd0,1)
linux /boot/vmlinuz-2.6.38-voyage root=/dev/sda1 ro
initrd /boot/initrd.img-2.6.38-voyage
boot
likewise you can do above for (hd0,5) and change parameter as necessary.

HTH
 
Old 12-12-2011, 09:46 AM   #51
sdfi
Member
 
Registered: Oct 2011
Distribution: debian
Posts: 107

Original Poster
Rep: Reputation: Disabled
i guess i should be using 'super grub2 disk', right?
 
Old 12-12-2011, 10:26 AM   #52
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,393

Rep: Reputation: 187Reputation: 187
The only issue I see is that
Quote:
Filesystem Size Used Available Use% Mounted on
tmpfs 124.7M 32.0K 124.7M 0% /dev
/dev/sr0 648.0M 648.0M 0 100% /cdrom
/dev/sda5 27.0G 664.6M 25.0G 3% /mnt/sda5
/dev/sda1 9.2G 2.9G 5.8G 33% /mnt/sda1
if debian a full install on sda5 and voyager on sda1, if so then there is something wrong with the debian install with only 644m of hardrive space being used for a full install of debian on /dev/sda5 as the root partition. Something isn't right there.

Last edited by colorpurple21859; 12-12-2011 at 10:36 AM.
 
Old 12-12-2011, 11:28 AM   #53
sdfi
Member
 
Registered: Oct 2011
Distribution: debian
Posts: 107

Original Poster
Rep: Reputation: Disabled
It does not have the GUI, that would probably be why it is so small.

Also, I have been able to get into both installs (booting from external floppy) using smartbootmanager.

edit: it seems smartbootmanager should be ok as a replacement for supergrub disk as it has grub 1.98

update: all files found (plus many more).. also entering commands returned nothing.. it started the boot process.. currently thrashing the floppy drive. It seems you are trying to boot into an old voyage kernel, fwiw. I stopped it after about 5 minutes. [but as above, i can boot them w/ smartbootmanager]

Last edited by sdfi; 12-12-2011 at 12:04 PM.
 
Old 12-12-2011, 11:35 AM   #54
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,393

Rep: Reputation: 187Reputation: 187
okay, I understand now. It was just something I notice out of the ordinary.
 
Old 12-12-2011, 11:37 AM   #55
odiseo77
Senior Member
 
Registered: Dec 2004
Location: Caracas, Venezuela
Distribution: Debian Sid, OpenSUSE 13.1
Posts: 1,022

Rep: Reputation: 315Reputation: 315Reputation: 315Reputation: 315
Quote:
Originally Posted by sdfi View Post
Also, I have been able to get into both installs (booting from external floppy) using smartbootmanager.
What happens if you try to reinstall grub from the debian install?:

Code:
update-grub
grub-install /dev/sda
 
Old 12-12-2011, 11:53 AM   #56
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,393

Rep: Reputation: 187Reputation: 187
wouldn't it be easier to reinstall grub legacy from voyager to the mbr edit /boot/grub/menu.lst to add the following
Quote:
menu Debian on sda5
root=(hd0,5)
kernel /vmlinuz root=/dev/sda5 ro quiet
initrd /initrd.img
to boot into debian. That way if debian still don't boot you can at least boot into your voyager distro, untill debian is fixed. If you want to use grub2, install it to debian's partition and chainload from grub legacy. I know grub 2 is the up and coming thing, but in my opinion grub legacy is easier to use.

Last edited by colorpurple21859; 12-12-2011 at 12:22 PM.
 
Old 12-12-2011, 11:59 AM   #57
sdfi
Member
 
Registered: Oct 2011
Distribution: debian
Posts: 107

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by odiseo77 View Post
What happens if you try to reinstall grub from the debian install?:

Code:
update-grub
grub-install /dev/sda
Same as when i've done it before. complains
Code:
grub-setup: warn: This msdos-style partition label has no post-MBR gap; embedding won't be possible!
grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists.
            However, blocklists are UNRELIABLE and its use is discouraged.
grub-setup: error: If you really want blocklists, use --force.
using --force it says the same but 'Installation finished. No error reported' in the last line, instead. No change in terms of the actual booting.
 
Old 12-12-2011, 03:37 PM   #58
odiseo77
Senior Member
 
Registered: Dec 2004
Location: Caracas, Venezuela
Distribution: Debian Sid, OpenSUSE 13.1
Posts: 1,022

Rep: Reputation: 315Reputation: 315Reputation: 315Reputation: 315
Quote:
Originally Posted by sdfi View Post
Same as when i've done it before. complains
Code:
grub-setup: warn: This msdos-style partition label has no post-MBR gap; embedding won't be possible!
grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists.
            However, blocklists are UNRELIABLE and its use is discouraged.
grub-setup: error: If you really want blocklists, use --force.
using --force it says the same but 'Installation finished. No error reported' in the last line, instead. No change in terms of the actual booting.
That's what I feared. According to the Archlinux wiki, this error message happens when there is not a necessary 1 mb gap between the MBR and the first partition, so Grub2 can't store the core.img file there. The strange thing is that the boot info script doesn't seem to show this problem. Apparently, one way to fix it is to repartition the hard drive (note that this will destroy everything you have in this drive, so you would have to backup your data somewhere else first). Another possibility, is restoring the old grub from your Voyage partition to the MBR as suggested by colorpurple21859 on post #56, since the old grub doesn't seem to have this issue. For this, you can either try Rescatux, or booting into Voyage, editing your menu.lst (as suggested by colorpurple21859), and then issuing these commands as root:

Code:
grub
root (hd0,0)
setup (hd0)
quit
Hope it works. However, if it does work, you will still have the 1 mb gap missing between your MBR and the first partition, and this could cause problems in the future when you upgrade to grub2, so maybe it would be better to repartition, just to be safe.

(More information about your problem here).
 
Old 12-12-2011, 04:23 PM   #59
widget
Senior Member
 
Registered: Oct 2008
Location: S.E. Montana
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,350

Rep: Reputation: 402Reputation: 402Reputation: 402Reputation: 402Reputation: 402
This is very interesting. It has been a while sense I last used grub-legacy but during that transition I never had trouble with the size of the MBR at all, still haven't either.

I had Ubuntu 9.04 on here installed with the default grub-legacy before grub-pc came on the scene. Decided I preferred grub-pc and installed it from the 9.10 repo. No problem.

I thought the 1Mb size was standard on the dos partition scheme.
 
Old 12-12-2011, 04:25 PM   #60
sdfi
Member
 
Registered: Oct 2011
Distribution: debian
Posts: 107

Original Poster
Rep: Reputation: Disabled
SO.. i did that. With voyage. old grub definitely installed.. because now smartbootmanager loads it. but still no change from boot.
 
  


Reply

Tags
grub, install, mbr


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] cannot install grub (grub-probe says 'unknown fs' with ext4 and md raid) cusco Linux - Software 3 03-15-2011 02:58 AM
Grub - Does fedora automatically install a bootloader like grub? or... mitchell7man Linux - Software 10 05-09-2007 11:49 AM
Booting my new ubuntu install = "GRUB GRUB GRUB GRUB GRUB" etc. dissolved soul Ubuntu 2 01-13-2007 01:55 PM
Need to (re)install GRUB: fedora c4 rescue cd (and GRUB) unable to see the harddisk whencat Fedora 4 03-05-2006 03:01 PM
Grub 0.97 issues on slackware - grub-install is very slow, & updating menu.lst fails dieyouspammer Linux - Software 1 02-27-2006 02:06 PM


All times are GMT -5. The time now is 05:15 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration