LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux Mint (https://www.linuxquestions.org/questions/linux-mint-84/)
-   -   Boot problems after installing Mint 12 (https://www.linuxquestions.org/questions/linux-mint-84/boot-problems-after-installing-mint-12-a-4175431283/)

Steve W 10-09-2012 03:57 AM

Boot problems after installing Mint 12
 
I installed Mint 12 as a dual boot on my laptop, which already has Windows XP.

However, when I switch on and it presents the usual Grub boot screen, I press the default first option to boot up Mint, but the screen goes blank, the HDD light goes off and nothing happens. I have to hold down the power button to get the laptop to switch off.

Windows XP has broken, and upon selecting this option I get a blank screen with a flashing cursor in the top left hand corner.

The only way it will boot into Mint is if I select the Safe boot (2nd option on the list), then select "Normal boot" at the next menu. It does pop up a message while loading in this mode, that says (from the brief glimpse I got of it) "initclr event failed" or similar.

After Googling this problem, I found a similar one where the advice was to do sudo update-grub, but this didn't work for them, or me.

I have only used Ubuntu before, and I have never had an unsuccessful dual-boot install like this; even though Mint and Ubuntu seem to use much the same installer.

Can anyone suggest how I revive my Windows XP, and get Mint starting properly? The Windows XP files are still intact in sda1, as I can see them when accessing that partition from within Mint.

Thank you for any advice you can give.

syg00 10-09-2012 06:23 AM

Go here, do as it says - post the RESULTS.txt
With luck Mint may install it by default - been a while since I last installed it.

Steve W 10-09-2012 10:40 AM

Okay, thanks.

I downloaded and ran bootinfoscript and the results file is as follows:

Boot Info Script 0.61 [1 April 2012]


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

=> Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
for (,msdos5)/boot/grub on this drive.

sda1: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows XP: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows XP
Boot files: /boot.ini /ntldr /NTDETECT.COM

sda2: __________________________________________________________________________

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

sda5: __________________________________________________________________________

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

sda6: __________________________________________________________________________

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

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

Drive: sda _____________________________________________________________________

Disk /dev/sda: 40.0 GB, 40007761920 bytes
255 heads, 63 sectors/track, 4864 cylinders, total 78140160 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sda1 * 63 39,062,551 39,062,489 7 NTFS / exFAT / HPFS
/dev/sda2 39,063,550 78,139,391 39,075,842 5 Extended
/dev/sda5 39,063,552 76,599,295 37,535,744 83 Linux
/dev/sda6 76,601,344 78,139,391 1,538,048 82 Linux swap / Solaris


"blkid" output: ________________________________________________________________

Device UUID TYPE LABEL

/dev/sda1 BC605C58605C1C08 ntfs
/dev/sda5 61f4a608-43cb-45b3-99fc-0152e964f378 ext4
/dev/sda6 3c7b46b9-1019-46a0-b0c1-423fda8df328 swap

================================ Mount points: =================================

Device Mount_Point Type Options

/dev/sda5 / ext4 (rw,errors=remount-ro,commit=0)


================================ sda1/boot.ini: ================================

--------------------------------------------------------------------------------
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
--------------------------------------------------------------------------------

=========================== sda5/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 video_bochs
insmod video_cirrus
}

insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 61f4a608-43cb-45b3-99fc-0152e964f378
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=auto
load_video
insmod gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 61f4a608-43cb-45b3-99fc-0152e964f378
set locale_dir=($root)/boot/grub/locale
set lang=en_GB
insmod gettext
fi
terminal_output gfxterm
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
if background_color 0,0,0; then
clear
fi
### END /etc/grub.d/05_debian_theme ###

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

### BEGIN /etc/grub.d/10_linux ###
if [ ${recordfail} != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
if [ "$linux_gfx_mode" != "text" ]; then load_video; fi
menuentry 'Linux Mint 12 LXDE, 3.0.0-12-generic (/dev/sda5)' --class linuxmint --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 61f4a608-43cb-45b3-99fc-0152e964f378
linux /boot/vmlinuz-3.0.0-12-generic root=UUID=61f4a608-43cb-45b3-99fc-0152e964f378 ro quiet splash vt.handoff=7
initrd /boot/initrd.img-3.0.0-12-generic
}
menuentry 'Linux Mint 12 LXDE, 3.0.0-12-generic (/dev/sda5) -- recovery mode' --class linuxmint --class gnu-linux --class gnu --class os {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 61f4a608-43cb-45b3-99fc-0152e964f378
echo 'Loading Linux 3.0.0-12-generic ...'
linux /boot/vmlinuz-3.0.0-12-generic root=UUID=61f4a608-43cb-45b3-99fc-0152e964f378 ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.0.0-12-generic
}
### 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='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 61f4a608-43cb-45b3-99fc-0152e964f378
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 61f4a608-43cb-45b3-99fc-0152e964f378
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Microsoft Windows XP Professional (on /dev/sda1)" --class windows --class os {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root BC605C58605C1C08
drivemap -s (hd0) ${root}
chainloader +1
}
### 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 ###
--------------------------------------------------------------------------------

=============================== sda5/etc/fstab: ================================

--------------------------------------------------------------------------------
# /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>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda5 during installation
UUID=61f4a608-43cb-45b3-99fc-0152e964f378 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda6 during installation
UUID=3c7b46b9-1019-46a0-b0c1-423fda8df328 none swap sw 0 0
--------------------------------------------------------------------------------

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

GiB - GB File Fragment(s)

22.959411621 = 24.652480512 boot/grub/core.img 1
30.966804504 = 33.250353152 boot/grub/grub.cfg 1
21.322265625 = 22.894608384 boot/initrd.img-3.0.0-12-generic 2
30.759414673 = 33.027670016 boot/vmlinuz-3.0.0-12-generic 1
21.322265625 = 22.894608384 initrd.img 2
30.759414673 = 33.027670016 vmlinuz 1

=============================== StdErr Messages: ===============================

xz: (stdin): Compressed data is corrupt

syg00 10-09-2012 03:46 PM

That all looks pretty standard. I'd be guessing a video card that's no longer supported (by default - in Mint at least).
Doesn't explain the failure to boot in XP.

- do you know how to edit the boot line in grub2 ?. If not I'll find a link for you.
- do you have your XP install CD (or got mate who has one) ?

Steve W 10-10-2012 01:12 AM

I don't think it's a video card or other hardware issue, because XP booted okay right before I installed Mint, and Mint booted okay from the live CD. The files in the Windows partition are still there, because I can see them from Mint. Mint also boots okay as long as I go through the Safe mode, but still choose "Normal boot" from the Safe mode menu.

It seems to be a problem with Grub booting from sda1. I note the final line of results.txt about "xz: (stdin): Compressed data is corrupt". Could it be that the Windows partition was encrypted, or does that never apply?

As for editing boot lines, I have edited /etc/fstab for my desktop PC before. Hang on.... I've just viewed fstab as a result of you mentioning editing boot files. I don't know much about them, but shouldn't the Windows partition be mentioned somewhere?

Have I got the wrong file here, or is there meant to be a reference to sda1 in there somewhere? Or do things work differently under Mint (I'm only used to setting up dual-boots in Ubuntu, although I did think the installer took care of that itself...)

With regard to XP disks, I have a copy of XP Pro but not for that laptop. It's registered to my desktop.

I'm currently Googling to see if anyone else has experienced similar difficulties with dual booting and Mint 12.

Could it be the hardware specification of the laptop that is incompatible with the way Grub works? All I know is:

* XP booted before I installed Mint
* Mint booted okay in Live mode
* Mint still boots okay, as long as I use Safe mode/Normal. What's the machine doing, or not doing, in Safe mode different from what it does when I use the normal boot option on the Grub screen?

syg00 10-10-2012 05:04 AM

The (video) hardware will still be okay - no Linux driver; at least with Mint apparently like I said. The recovery mode (for Mint) is disabling kernel mode setting for the video, bypassing the issue.
fstab is for mounting files, not booting. I'm sure Mint will have some doco for grub2, but here is one for Ubuntu, but is generally applicable for derivatives like Mint.

As for XP, it won't matter that the disk is registered to another system - you only want to get into Recovery Console from a boot from that CD and run fixboot. here is a technet article that walks you through the process. Click through "Start the Computer and use the Recovery COnsole" to commands to get to how to use fixboot. There will be other similar articles there as well.

Steve W 10-10-2012 05:29 AM

Quote:

The (video) hardware will still be okay - no Linux driver; at least with Mint apparently like I said. The recovery mode (for Mint) is disabling kernel mode setting for the video, bypassing the issue.
Does that mean, on this laptop, I start off in Safe mode every time then? Is there any output from a running system I can give you that will enable me to find out where I can download the correct driver for the laptop's video hardware, if is exists?

Quote:

You only want to get into Recovery Console from a boot from that CD and run fixboot.
If I run my XP disc and restore the Windows MBR, does that mean I'll go straight into XP when I boot up again? If so, do I need to run the Mint CD again and re-install Grub? Won't that take me back to square one again?

Steve W 10-15-2012 03:25 AM

Is there a config file I can edit, so that reference to any unsupported video card is removed from the standard bootup, and I can start Mint from the standard Grub menu option, rather than going through Safe mode every time?

tomking 10-16-2012 07:16 AM

I have same problem with Mint 13 Maya 32 bit.
Use GRUB to boot to (Recovery) and then you have to log in a terminal screen which appears. When logged in do a 'sudo reboot' and you can/will boot into Mint ok.
Do not ask me why because I only use Mint to see what it is all about; I suggest Ubuntu 11.10 and back as the best and most stable OS with all (more if you want) the bells and whistles Mint has. I like Mint running from a USB stick; super fast and portale.


All times are GMT -5. The time now is 10:17 AM.