PDA

View Full Version : [SOLVED] Ubuntu 10.10 booting problem after using Gparted



sebas2831983
April 15th, 2011, 11:08 PM
Hello everyone,

Ubuntu 10.10 worked great until I created a FAT32 partition with Gparted. While booting Ubuntu, it fails with the following messages:



Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
[ 3.644823] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Begin: Running /scripts/local-bottom ... done
done.
Begin: Running /scripts/init-bottom ... done.
mount: mounting /proc on /root/proc failed: No such file or directory
init: Error while reading from descriptor: Bad file descriptor
init: hwclock main process (314) terminated with status 127
init: ureadahead main process (315) terminated with status 3
/bin/sh: Can't open /proc/self/fd/8
init: mountall main process (316) terminated with status 127


I guess (not sure, I'm a nube) mounting the hard disks goes well, however, something goes wrong with mounting /proc on /root/proc. As I understood, /proc is some kind of virtual drive kind of thingy.....

I have no idea how to solve this. For you information, I just booted Ubuntu 10.10 from the 'live cd' and navigated to the physical hard drive, where the 'installed version' of Ubuntu 10.10 is located. The identification of the devices read:



sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/sda1: UUID="9c30c37f-81ae-4423-a660-20318be12e52" TYPE="ext4"
/dev/sda3: UUID="D477-5BE7" TYPE="vfat"
/dev/sda5: UUID="b715c668-22a9-4a24-af8c-54d9d4a95e96" TYPE="swap"


Whereas the fstab file looks like:



# /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
/dev/sda1 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=b715c668-22a9-4a24-af8c-54d9d4a95e96 none swap sw 0 0


Does anyone has a suggestion to solve this booting problem?

Thanks a lot!
Kind regards, Bas

wilee-nilee
April 15th, 2011, 11:26 PM
Lets see that information and a little more click on the bootscript link in my signature and run it and post all the text from the generated file in code tags.

Did you try to resize the sda1 partition while using it? or resize it at all, and from which end the front or back?

sebas2831983
April 16th, 2011, 08:36 AM
Hi Wilee, thanks for your reply!

The txt file generated by the bootscript reads:



Boot Info Script 0.55 dated February 15th, 2010

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

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

sda1: __________________________________________________ _______________________

File system: ext4
Boot sector type: Grub 2
Boot sector info: Grub 2 is installed in the boot sector of sda1 and
looks at sector 34023240 of the same hard drive for
core.img, but core.img can not be found at this
location.
Operating System: Ubuntu 10.10
Boot files/dirs: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

sda2: __________________________________________________ _______________________

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

sda5: __________________________________________________ _______________________

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

sda3: __________________________________________________ _______________________

File system: vfat
Boot sector type: Fat32
Boot sector info: According to the info in the boot sector, sda3 starts
at sector 0. But according to the info from fdisk,
sda3 starts at sector 126431550.
Operating System:
Boot files/dirs:

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

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sda1 * 2,048 126,431,549 126,429,502 83 Linux
/dev/sda2 150,161,406 156,301,311 6,139,906 5 Extended
/dev/sda5 150,161,408 156,301,311 6,139,904 82 Linux swap / Solaris
/dev/sda3 126,431,550 150,159,554 23,728,005 b W95 FAT32


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/sda1 9c30c37f-81ae-4423-a660-20318be12e52 ext4
/dev/sda2: PTTYPE="dos"
/dev/sda3 D477-5BE7 vfat
/dev/sda5 b715c668-22a9-4a24-af8c-54d9d4a95e96 swap
/dev/sda: 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)
/dev/sda1 /media/9c30c37f-81ae-4423-a660-20318be12e52 ext4 (rw,nosuid,nodev,uhelper=udisks)
/dev/sda3 /media/D477-5BE7 vfat (rw,nosuid,nodev,uhelper=udisks,uid=999,gid=999,sh ortname=mixed,dmask=0077,utf8=1,showexec,flush)


=========================== sda1/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='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
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='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
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/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.35-28-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
linux /boot/vmlinuz-2.6.35-28-generic root=UUID=9c30c37f-81ae-4423-a660-20318be12e52 ro quiet splash
initrd /boot/initrd.img-2.6.35-28-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-28-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
echo 'Loading Linux 2.6.35-28-generic ...'
linux /boot/vmlinuz-2.6.35-28-generic root=UUID=9c30c37f-81ae-4423-a660-20318be12e52 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.35-28-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-27-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
linux /boot/vmlinuz-2.6.35-27-generic root=UUID=9c30c37f-81ae-4423-a660-20318be12e52 ro quiet splash
initrd /boot/initrd.img-2.6.35-27-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-27-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
echo 'Loading Linux 2.6.35-27-generic ...'
linux /boot/vmlinuz-2.6.35-27-generic root=UUID=9c30c37f-81ae-4423-a660-20318be12e52 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.35-27-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-25-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
linux /boot/vmlinuz-2.6.35-25-generic root=UUID=9c30c37f-81ae-4423-a660-20318be12e52 ro quiet splash
initrd /boot/initrd.img-2.6.35-25-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-25-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
echo 'Loading Linux 2.6.35-25-generic ...'
linux /boot/vmlinuz-2.6.35-25-generic root=UUID=9c30c37f-81ae-4423-a660-20318be12e52 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.35-25-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
linux /boot/vmlinuz-2.6.35-22-generic root=UUID=9c30c37f-81ae-4423-a660-20318be12e52 ro quiet splash
initrd /boot/initrd.img-2.6.35-22-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
echo 'Loading Linux 2.6.35-22-generic ...'
linux /boot/vmlinuz-2.6.35-22-generic root=UUID=9c30c37f-81ae-4423-a660-20318be12e52 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.35-22-generic
}
### END /etc/grub.d/10_linux ###

### 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,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
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 ###

=============================== sda1/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
/dev/sda1 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=b715c668-22a9-4a24-af8c-54d9d4a95e96 none swap sw 0 0

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


17.4GB: boot/grub/core.img
52.0GB: boot/grub/grub.cfg
52.2GB: boot/initrd.img-2.6.35-22-generic
52.2GB: boot/initrd.img-2.6.35-25-generic
.9GB: boot/initrd.img-2.6.35-27-generic
1.5GB: boot/initrd.img-2.6.35-28-generic
17.4GB: boot/vmlinuz-2.6.35-22-generic
17.4GB: boot/vmlinuz-2.6.35-25-generic
17.4GB: boot/vmlinuz-2.6.35-27-generic
17.4GB: boot/vmlinuz-2.6.35-28-generic
1.5GB: initrd.img
.9GB: initrd.img.old
17.4GB: vmlinuz
17.4GB: vmlinuz.old


Considering your last question, I booted from a Gparted cd, so I guess I did not using sda1 at that time. Then I resized the partition from the back. With that appearing space, a FAT 32 was created.

Hope this gives you enough information. Anyways, thanks again!

Cheers, Bas

wilee-nilee
April 16th, 2011, 08:49 AM
You have no bootloader in the mbr, this link will give you the two commands to fix this.
https://help.ubuntu.com/community/Grub2#Reinstalling%20GRUB%202

The only other thing I see with a quick look is this.
sda1: __________________________________________________ _______________________

File system: ext4
Boot sector type: Grub 2
Boot sector info: Grub 2 is installed in the boot sector of sda1 and
looks at sector 34023240 of the same hard drive for
core.img, but core.img can not be found at this
location.
Operating System: Ubuntu 10.10
Boot files/dirs: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

Fixing this part if needed is a little beyond my area of help.

Rubi1200
April 16th, 2011, 09:07 AM
You have no bootloader in the mbr, this link will give you the two commands to fix this.
https://help.ubuntu.com/community/Grub2#Reinstalling%20GRUB%202

The only other thing I see with a quick look is this.
sda1: __________________________________________________ _______________________

File system: ext4
Boot sector type: Grub 2
Boot sector info: Grub 2 is installed in the boot sector of sda1 and
looks at sector 34023240 of the same hard drive for
core.img, but core.img can not be found at this
location.
Operating System: Ubuntu 10.10
Boot files/dirs: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

Fixing this part if needed is a little beyond my area of help.
This should be taken care of with a reinstall to the MBR of the drive. That message usually appears when GRUB is installed to the partition rather than the drive.

wilee-nilee
April 16th, 2011, 09:12 AM
This should be taken care of with a reinstall to the MBR of the drive. That message usually appears when GRUB is installed to the partition rather than the drive.

Thanks I wondered about that.

Rubi1200
April 16th, 2011, 09:23 AM
No problem, wilee, you are welcome.

Just want to clarify my previous comment; when one attempts to install to the partition.

sebas2831983
April 16th, 2011, 11:27 AM
Thanks a lot guys, I'll have look at it this afternoon. I'll keep you informed.
Thanks, Bas

sebas2831983
April 16th, 2011, 06:24 PM
So I've been working for a while on the suggestions above. Grub was installed by the following commands:



sudo mount /dev/sda1 /mnt
sudo grub-install --root-directory=/mnt /dev/sda
After rebooting, I still get these messages:



Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
[ 3.644823] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Begin: Running /scripts/local-bottom ... done
done.
Begin: Running /scripts/init-bottom ... done.
mount: mounting /proc on /root/proc failed: No such file or directory
init: Error while reading from descriptor: Bad file descriptor
init: hwclock main process (320) terminated with status 127
init: ureadahead main process (321) terminated with status 3
/bin/sh: Can't open /proc/self/fd/8
init: mountall main process (322) terminated with status 127
Let me show you the novel boot info summary:



Boot Info Script 0.55 dated February 15th, 2010

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

=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in
partition #1 for (,msdos1)/boot/grub.

sda1: __________________________________________________ _______________________

File system: ext4
Boot sector type: Grub 2
Boot sector info: Grub 2 is installed in the boot sector of sda1 and
looks at sector 34023240 of the same hard drive for
core.img, but core.img can not be found at this
location.
Operating System: Ubuntu 10.10
Boot files/dirs: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

sda2: __________________________________________________ _______________________

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

sda5: __________________________________________________ _______________________

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

sda3: __________________________________________________ _______________________

File system: vfat
Boot sector type: Fat32
Boot sector info: According to the info in the boot sector, sda3 starts
at sector 0. But according to the info from fdisk,
sda3 starts at sector 126431550.
Operating System:
Boot files/dirs:

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

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sda1 * 2,048 126,431,549 126,429,502 83 Linux
/dev/sda2 150,161,406 156,301,311 6,139,906 5 Extended
/dev/sda5 150,161,408 156,301,311 6,139,904 82 Linux swap / Solaris
/dev/sda3 126,431,550 150,159,554 23,728,005 b W95 FAT32


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/sda1 9c30c37f-81ae-4423-a660-20318be12e52 ext4
/dev/sda2: PTTYPE="dos"
/dev/sda3 D477-5BE7 vfat
/dev/sda5 b715c668-22a9-4a24-af8c-54d9d4a95e96 swap
/dev/sda: 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)
/dev/sda1 /media/9c30c37f-81ae-4423-a660-20318be12e52 ext4 (rw,nosuid,nodev,uhelper=udisks)
/dev/sda3 /media/D477-5BE7 vfat (rw,nosuid,nodev,uhelper=udisks,uid=999,gid=999,sh ortname=mixed,dmask=0077,utf8=1,showexec,flush)


=========================== sda1/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='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
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='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
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/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.35-28-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
linux /boot/vmlinuz-2.6.35-28-generic root=UUID=9c30c37f-81ae-4423-a660-20318be12e52 ro quiet splash
initrd /boot/initrd.img-2.6.35-28-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-28-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
echo 'Loading Linux 2.6.35-28-generic ...'
linux /boot/vmlinuz-2.6.35-28-generic root=UUID=9c30c37f-81ae-4423-a660-20318be12e52 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.35-28-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-27-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
linux /boot/vmlinuz-2.6.35-27-generic root=UUID=9c30c37f-81ae-4423-a660-20318be12e52 ro quiet splash
initrd /boot/initrd.img-2.6.35-27-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-27-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
echo 'Loading Linux 2.6.35-27-generic ...'
linux /boot/vmlinuz-2.6.35-27-generic root=UUID=9c30c37f-81ae-4423-a660-20318be12e52 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.35-27-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-25-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
linux /boot/vmlinuz-2.6.35-25-generic root=UUID=9c30c37f-81ae-4423-a660-20318be12e52 ro quiet splash
initrd /boot/initrd.img-2.6.35-25-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-25-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
echo 'Loading Linux 2.6.35-25-generic ...'
linux /boot/vmlinuz-2.6.35-25-generic root=UUID=9c30c37f-81ae-4423-a660-20318be12e52 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.35-25-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
linux /boot/vmlinuz-2.6.35-22-generic root=UUID=9c30c37f-81ae-4423-a660-20318be12e52 ro quiet splash
initrd /boot/initrd.img-2.6.35-22-generic
}
menuentry 'Ubuntu, with Linux 2.6.35-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
echo 'Loading Linux 2.6.35-22-generic ...'
linux /boot/vmlinuz-2.6.35-22-generic root=UUID=9c30c37f-81ae-4423-a660-20318be12e52 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.35-22-generic
}
### END /etc/grub.d/10_linux ###

### 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,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9c30c37f-81ae-4423-a660-20318be12e52
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 ###

=============================== sda1/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
/dev/sda1 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
/dev/sda5 none swap sw 0 0

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


17.4GB: boot/grub/core.img
17.4GB: boot/grub/grub.cfg
52.2GB: boot/initrd.img-2.6.35-22-generic
52.2GB: boot/initrd.img-2.6.35-25-generic
.9GB: boot/initrd.img-2.6.35-27-generic
1.5GB: boot/initrd.img-2.6.35-28-generic
17.4GB: boot/vmlinuz-2.6.35-22-generic
17.4GB: boot/vmlinuz-2.6.35-25-generic
17.4GB: boot/vmlinuz-2.6.35-27-generic
17.4GB: boot/vmlinuz-2.6.35-28-generic
1.5GB: initrd.img
.9GB: initrd.img.old
17.4GB: vmlinuz
17.4GB: vmlinuz.old
So, it reads that Grub 2 is now installed in the MBR. After checking several times (adding some commented (#) text lines to the grub.cfg file), the grub.cfg file has not been updated during the installation of grub. (You may find the grub.cfg file in above displayed boot info summary.) Is this normal?

I also wonder about these lines in the grub.cfg file:


insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
Why does it consider ext2? Since the partition with Ubuntu deals with ext4, right?

I hope this gives some new insights. I would be very happy to hear from you guys.
Thanks!
bas

Dutch70
April 16th, 2011, 07:21 PM
Hi & welcome to UF

The core image thing not being found is what concerns me. It may help if you edit your fstab like this...

Change this line...

/dev/sda1 / ext4 errors=remount-ro 0 1
To this...

# /dev/sda1
UUID=9c30c37f-81ae-4423-a660-20318be12e52 / ext4 errors=remount-ro 0 1

wilee-nilee
April 16th, 2011, 07:38 PM
You don't run the update grub until you're back in the install.

In these sort of circumstances I generally use supergrub2 to get in then just reload grub from the booted install.
http://www.bootproblems.com/

commands once in would be..
sudo grub-install /dev/sda
then
sudo update-grub

Not sure what you mean by "(adding some commented (#) text lines to the grub.cfg file)" you might want to elaborate on that as grub2 has a specific editing protocol.

There is also this thread on purging all of grub and reinstalling it.
http://ubuntuforums.org/showthread.php?t=1581099

sebas2831983
April 16th, 2011, 08:23 PM
Hi Dutch70 (somehow related to the dutch language :) ?),

THanks for your suggestion. I changed it into your recommended UUID. Nevertheless, similar error message about /proc while trying to boot .

What to do?
Bas

Dutch70
April 16th, 2011, 08:43 PM
Hahaa, not related to the dutch language. Just a nickname.

I think your problem is related to this line in your boot info script, but after that, it's beyond me.

Grub 2 is installed in the boot sector of sda1 and
looks at sector 34023240 of the same hard drive for
core.img, but core.img can not be found at this
location.

I would take a look at wilee nilee's link to purging and reinstalling grub2 first. Seems that would be easiest, for me anyway, b/c I have no idea about supergrub2.

Btw, these are not a problem.
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'

sebas2831983
April 16th, 2011, 09:33 PM
Hi wilee-nilee,

I tried supergrub2 serveral times, it finds grub stuff, but in all options booting fails with the same /proc mounting error as mentioned before.

Then I tried to follow the "HOWTO: Purge and Reinstall Grub 2 from the Live CD" guide, following the steps related to 'chroot', namely trying to chroot-ing stuff into the installed OS, while being into the 'live-ubuntu-system'. So, I followed step 1C, something with mounting stuff temporarily. The line


for i in /dev /dev/pts /proc /sys; do sudo mount -B $i /mnt/temp$i; done
is equivalent to:


sudo mount --bind /dev /mnt/temp/dev
sudo mount --bind /dev/pts /mnt/temp/dev/pts
sudo mount --bind /proc /mnt/temp/proc
sudo mount --bind /sys /mnt/temp/sys
But here, again problems with mounting /proc , namely:


mount: mount point /mnt/temp/proc does not exist
The other three mount commands work fine I guess... when I run the command, I get no responses:


ubuntu@ubuntu:~$ sudo mount --bind /dev /mnt/temp/dev
ubuntu@ubuntu:~$ sudo mount --bind /dev/pts /mnt/temp/dev/pts
ubuntu@ubuntu:~$ sudo mount --bind /proc /mnt/temp/proc
mount: mount point /mnt/temp/proc does not exist
ubuntu@ubuntu:~$ sudo mount --bind /sys /mnt/temp/sys
ubuntu@ubuntu:~$

... guess that's alright?

I'll try to find a topic on this specific mounting of /proc . It's all new to me, so I doubt it to find a solution.

Guys, any thoughts are most welcome!

Cheers, bas

sebas2831983
April 17th, 2011, 09:07 AM
So there is probably no /proc directory.... how come? When I browse through the files of the installed system via the live-system, I just can't find the /proc directory. Well, reinstalling sounds like the best option, isnt it?
Bas

sebas2831983
April 17th, 2011, 12:29 PM
Hello all, after manually making a /proc directory I managed to boot ubuntu. I could log on, but then autohority warnings appeared and nautilus could not be loaded. From here, I decided to do a new clean install of Ubuntu, since further editing file permissions is somewhat tricky for me. Besides, I dont trust the system security anymore in that case.

I've learned lots of new stuff this weekend, with the help of you guys. Again, thanks for your help! I appreciatie it!

Best regards, Bas

Rubi1200
April 17th, 2011, 02:22 PM
It's a pity you needed to do a clean install, but in this case it was probably the right thing to do.

Good luck and enjoy the experience :-)

Dutch70
April 17th, 2011, 04:43 PM
I just want to add that now may be a good time to create a /home partition if you don't already have one. Then you'll be able to reinstall without losing your data or settings, and you won't have to worry about upgrading anymore.

Also, please mark this thread [Solved] with Thread Tools at the top of the page.

sebas2831983
April 19th, 2011, 07:58 PM
Okay, thanks for the /home suggestion. Everything is running well again guys, thanks again!
Cheers, Bas