New Julia install won't boot

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
wesk

New Julia install won't boot

Post by wesk »

I've just recently tried installing Jullia 32 bit. prior to this install i had ubuntu maverick meerkat 64 bit installed and working normally. i installed julia from a live dvd. the problem is: when i try to boot, the computer just hangs when it gets past the bios screen. i've tried reinstalling at least 7 times. there is no problem with the dvd. the md5sum matches up with the posted value. incidentally, i also tried installing maverick meerkat 32 bit and got the same result. i'm an absolute newb when it comes to linux and i've tried to solve this on my own but am not having much luck. thanks for any help.

i'm posting the results of my Boot Info script here:

Code: Select all

                Boot Info Script 0.55    dated February 15th, 2010                    

============================= Boot Info Summary: ==============================

 => No boot loader is installed in the MBR of /dev/sdb

sdb1: _________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info:  
    Operating System:  Linux Mint 10 Julia
    Boot files/dirs:   /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

sdb2: _________________________________________________________________________

    File system:       Extended Partition
    Boot sector type:  -
    Boot sector info:  

sdb5: _________________________________________________________________________

    File system:       swap
    Boot sector type:  -
    Boot sector info:  

sda: _________________________________________________________________________

    File system:       vfat
    Boot sector type:  Grub 2
    Boot sector info:  Grub 2 is installed in the boot sector of sda and 
                       looks at sector 48002072 of the same hard drive for 
                       core.img, but core.img can not be found at this 
                       location. According to the info in the boot sector, 
                       sda has -1364690128 sectors.. But according to the 
                       info from the partition table , it has 2930277168 
                       sectors.
    Operating System:  
    Boot files/dirs:   

=========================== Drive/Partition Info: =============================

Drive: sdb ___________________ _____________________________________________________

Disk /dev/sdb: 40.0 GB, 40018599936 bytes
255 heads, 63 sectors/track, 4865 cylinders, total 78161328 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition  Boot         Start           End          Size  Id System

/dev/sdb1               2,048    74,860,543    74,858,496  83 Linux
/dev/sdb2          74,862,590    78,159,871     3,297,282   5 Extended
/dev/sdb5          74,862,592    78,159,871     3,297,280  82 Linux swap / Solaris


blkid -c /dev/null: ____________________________________________________________

Device           UUID                                   TYPE       LABEL                         

/dev/loop0                                              squashfs                                 
/dev/sda         4983-5E35                              vfat       Data                          
/dev/sdb1        ee5f3917-d06e-4263-8850-2ae079ef0ddd   ext4                                     
/dev/sdb2: PTTYPE="dos" 
/dev/sdb5        588b97d4-abe7-44f3-91ee-9d9eeb457848   swap                                     
/dev/sdb: PTTYPE="dos" 

============================ "mount | grep ^/dev  output: ===========================

Device           Mount_Point              Type       Options

aufs             /                        aufs       (rw)
/dev/sr0         /cdrom                   iso9660    (ro,noatime)
/dev/loop0       /rofs                    squashfs   (ro,noatime)


=========================== sdb1/boot/grub/grub.cfg: ===========================

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function recordfail {
  set recordfail=1
  if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}

function load_video {
  insmod vbe
  insmod vga
}

insmod part_msdos
insmod ext2
set root='(hd1,msdos1)'
search --no-floppy --fs-uuid --set ee5f3917-d06e-4263-8850-2ae079ef0ddd
if loadfont /usr/share/grub/unicode.pf2 ; then
  set gfxmode=640x480
  load_video
  insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd1,msdos1)'
search --no-floppy --fs-uuid --set ee5f3917-d06e-4263-8850-2ae079ef0ddd
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
if [ "${recordfail}" = 1 ]; then
  set timeout=-1
else
  set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/06_mint_theme ###
insmod part_msdos
insmod ext2
set root='(hd1,msdos1)'
search --no-floppy --fs-uuid --set ee5f3917-d06e-4263-8850-2ae079ef0ddd
insmod png
if background_image /boot/grub/linuxmint.png ; then
  set color_normal=white/black
  set color_highlight=white/light-gray
else
  set menu_color_normal=white/black
  set menu_color_highlight=white/light-gray
fi
### END /etc/grub.d/06_mint_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Linux Mint 10, 2.6.35-22-generic-pae (/dev/sdb1)' --class linuxmint --class gnu-linux --class gnu --class os {
	recordfail
	insmod part_msdos
	insmod ext2
	set root='(hd1,msdos1)'
	search --no-floppy --fs-uuid --set ee5f3917-d06e-4263-8850-2ae079ef0ddd
	linux	/boot/vmlinuz-2.6.35-22-generic-pae root=UUID=ee5f3917-d06e-4263-8850-2ae079ef0ddd ro   quiet splash
	initrd	/boot/initrd.img-2.6.35-22-generic-pae
}
menuentry 'Linux Mint 10, 2.6.35-22-generic-pae (/dev/sdb1) -- recovery mode' --class linuxmint --class gnu-linux --class gnu --class os {
	recordfail
	insmod part_msdos
	insmod ext2
	set root='(hd1,msdos1)'
	search --no-floppy --fs-uuid --set ee5f3917-d06e-4263-8850-2ae079ef0ddd
	echo	'Loading Linux 2.6.35-22-generic-pae ...'
	linux	/boot/vmlinuz-2.6.35-22-generic-pae root=UUID=ee5f3917-d06e-4263-8850-2ae079ef0ddd ro single 
	echo	'Loading initial ramdisk ...'
	initrd	/boot/initrd.img-2.6.35-22-generic-pae
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/10_lupin ###
### END /etc/grub.d/10_lupin ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
	insmod part_msdos
	insmod ext2
	set root='(hd1,msdos1)'
	search --no-floppy --fs-uuid --set ee5f3917-d06e-4263-8850-2ae079ef0ddd
	linux16	/boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
	insmod part_msdos
	insmod ext2
	set root='(hd1,msdos1)'
	search --no-floppy --fs-uuid --set ee5f3917-d06e-4263-8850-2ae079ef0ddd
	linux16	/boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
if [ "x${timeout}" != "x-1" ]; then
  if keystatus; then
    if keystatus --shift; then
      set timeout=-1
    else
      set timeout=0
    fi
  else
    if sleep --interruptible 3 ; then
      set timeout=0
    fi
  fi
fi
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

=============================== sdb1/etc/fstab: ===============================

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' 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>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sdb1 during installation
UUID=ee5f3917-d06e-4263-8850-2ae079ef0ddd /               ext4    errors=remount-ro 0       1
# swap was on /dev/sdb5 during installation
UUID=588b97d4-abe7-44f3-91ee-9d9eeb457848 none            swap    sw              0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0

=================== sdb1: Location of files loaded by Grub: ===================


  24.5GB: boot/grub/core.img
  21.7GB: boot/grub/grub.cfg
  22.0GB: boot/initrd.img-2.6.35-22-generic-pae
  24.5GB: boot/vmlinuz-2.6.35-22-generic-pae
  22.0GB: initrd.img
  24.5GB: vmlinuz
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
dawgdoc

Re: New Julia install won't boot

Post by dawgdoc »

I can see a little of what is causing the problem from the your Boot Info Script printout.

Your bootloader is installed on the MBR of sda
It is looking to sda for the files needed to boot.
These files are on sdb
There is no bootloader in the MBR of sdb.

Did you initially have Meerkat on sda? Did you install LM10 without installing Grub2? Was the Mint installation performed prior to removing Meerkat?
This set or circumstances might explain why the bootloader is looking on sda for the boot files.

At the moment I am still trying to think what the best solution would be. Your sda has a Label of Data and the file system is vfat, I guess this means it is fat32 or fat16. As far as I can tell there is no OS on it. The script reported a discrepancy in the number of sectors on sda. I can think of a couple of solutions, but the best depends on what you have on the disks, if they are SATA or ATA/IDE and if you wish to reinstall or not.

I have never worked on a system with more than one SATA drive. I believe you could designate in the bios for the 2nd drive (Currently sdb) to be the boot drive. And then you could reinstall Mint on it, with the MBR also being on it. Then your former sda would be a secondary drive. You may still need to recover the file allocation table on it. (I think that was the correct terminology.) I hope the data has been backed up.
wesk

Re: New Julia install won't boot

Post by wesk »

you're right. sda is a data drive only (wd 1.5tb). there is not and has never been an OS on it. meerkat was installed on the 40gb drive that is designated as sdb here. when i did the mint install, i specified that i wanted to erase and use the entire disk that meerkat was on (sdb). both disks are SATA and i have no issues with doing what needs to be done to get the install working. there is absolutely no data on this system. it's a new build.

my bios doesn't even give me the option of designating more than one hard disk as the boot drive. it only lists the one that is designated as disk 1and i have the 40gb designated as disk 1.
wayne128

Re: New Julia install won't boot

Post by wayne128 »

wesk wrote:you're right. sda is a data drive only (wd 1.5tb). there is not and has never been an OS on it. meerkat was installed on the 40gb drive that is designated as sdb here. when i did the mint install, i specified that i wanted to erase and use the entire disk that meerkat was on (sdb). both disks are SATA and i have no issues with doing what needs to be done to get the install working. there is absolutely no data on this system. it's a new build.

my bios doesn't even give me the option of designating more than one hard disk as the boot drive. it only lists the one that is designated as disk 1and i have the 40gb designated as disk 1.

Without messing around two MBRs ( one on each hard disk), grub-install, update-grub etc, I would think since you have install so many times and each time run into the same problem, I believe I would be looking it at hardware and Bios level first.

I would just swap the SATA cable so that the OS drive become the 'first boot device' all the time when computer boots up. Bios must consistently see the 40G drive as first boot drive.

When Bios is settled, then you install Mint ( or any Linux OS), let installer wipe whole drive and install boot loader on MBR.
wesk

Re: New Julia install won't boot

Post by wesk »

wayne128 wrote:
Without messing around two MBRs ( one on each hard disk), grub-install, update-grub etc, I would think since you have install so many times and each time run into the same problem, I believe I would be looking it at hardware and Bios level first.

I would just swap the SATA cable so that the OS drive become the 'first boot device' all the time when computer boots up. Bios must consistently see the 40G drive as first boot drive.

When Bios is settled, then you install Mint ( or any Linux OS), let installer wipe whole drive and install boot loader on MBR.

i guess i don't really understand what you mean here. my bios recognizes the 40gb drive as the boot drive as it is. what would i accomplish by swapping the SATA cables? also, the original ubuntu install was working fine and i've made no changes at all to the hardware configuration or the bios since then. from what i can gather - the linux installer, for some reason, is placing the bootloader on the 1.5tb drive when the main OS install is on the 40gb drive.

i've read something about installing grub2 from the live dvd. is this something that might fix my particular issue?
wayne128

Re: New Julia install won't boot

Post by wayne128 »

Your information and output of scripts suggest some kind of BIOS/kernel inconsistency on designating drive boot order and /dev/sda , /dev/sdb. That is the reason I suspect BIOS/hardware kind of issue. My thinking could be totally wrong, however, I had that issue some time ago mixing with IDE and two SATA drives, all kind of boot issues ( which made me learn a lots on multi booting, thanks to these problems that channeled me to learn deeper on booting , eventually I took out the IDE drive, confirming that both SATA drives are consistently detected by BIOS each time computer boot up, and all LInux OS see them consistently, that is, first drive is 100% as /dev/sda and second drive is 100% as /dev/sdb.

May be you can simplify the issue by just doing it with one OS drive, says you choose your 40G as OS drive, unplug the 1T drive, install the Linux OS onto 40G drive, it should just work.

Once that is done plug in your data drive, retest to be sure booting is consistently working and second data drive is consistently seen by OS as /dev/sdb.


If you are very keen to know what is the root of the problem, here is my suggestion:

1. Test to be sure BIOS see all internal drives.
your info saying that BIOS only see 40G drive is quite unusual, in all my computers, Bios always see all internal drives and external USB drives and very consistent when CMOS setting is not changed.

2. Your computer / mother board might have updated BIOS, try to upgrade it.
You need to achieve consistency on BIOS seeing all internal and external drives for each boot up

3. Test to be sure ubuntu-32, ubuntu-64, julia-32 all see the same , consistently, drive designations,
that is 40G always seen as /dev/sdx, and 1T always seen as /dev/sdy.
If they differ, then some kind of BIOS/kernel inconsistency exist...well, lets hope not the case.
wesk

Re: New Julia install won't boot

Post by wesk »

i'll give it a try. but just to be clear - my bios does actually see the 1.5tb drive. it just doesn't offer it as a boot device. i haven't tested to see whether that is because it is designated as drive 2 or what but it will only let me select the 40gb drive as the boot device.
wesk

Re: New Julia install won't boot

Post by wesk »

Well, let's call this one solved. Unplugging the second Sata drive for the install did the trick. I still have no idea why, though.
wayne128

Re: New Julia install won't boot

Post by wayne128 »

wesk wrote:Well, let's call this one solved. Unplugging the second Sata drive for the install did the trick. I still have no idea why, though.

Glad you have it working.

At times we do not understand the puzzle.
In your case it is near the areas of BIOS/ BIOS settings/Sata chip/ Sata cable and jumpers/Mobo jumper/kernel

It takes much time to troubleshoot step by step and will eventually find out.
Meanwhile just enjoy Mint.
User avatar
Oscar799
Level 20
Level 20
Posts: 10411
Joined: Tue Aug 11, 2009 9:21 am
Location: United Kingdom

Re: New Julia install won't boot

Post by Oscar799 »

Moved here from Newbie Questions
Image
Locked

Return to “Installation & Boot”