No boot !

[sid.mallya]

Okay .. Major problem. I rebooted my computer because root terminal wasn't working .. and now I just cannot boot into my Ubuntu 10.04 .. It goes into the loading screen of Ubuntu and goes on for an eternity - Nothing happens after that.

I am on my live Ubuntu CD right now .. I need help. ASAP. Please.

[Rubi1200]

From the LiveCD, please post the results of the boot-script linked at the bottom of my post.

[sid.mallya]

There you go mate ! Thanks in advance.

[Rubi1200]

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 /boot/grub.

sda1: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 10.04.1 LTS
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:

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

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 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 964,753,407 964,751,360 83 Linux
/dev/sda2 964,755,454 976,773,119 12,017,666 5 Extended
/dev/sda5 964,755,456 976,773,119 12,017,664 82 Linux swap / Solaris


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/sda1 f2adeeb0-00e4-4006-99d2-0f5c6b2ad220 ext4
/dev/sda2: PTTYPE="dos"
/dev/sda5 b84db55f-2d6a-4afc-b4ce-80845cf5b41b swap
/dev/sda: PTTYPE="dos"
error: /dev/sdb: No medium found
error: /dev/sdc: No medium found
error: /dev/sdd: No medium found
error: /dev/sde: No medium found

============================ "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/f2adeeb0-00e4-4006-99d2-0f5c6b2ad220 ext4 (rw,nosuid,nodev,uhelper=udisks)


=========================== sda1/boot/grub/grub.cfg: ===========================

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/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
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
}
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set f2adeeb0-00e4-4006-99d2-0f5c6b2ad220
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set f2adeeb0-00e4-4006-99d2-0f5c6b2ad220
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.32-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set f2adeeb0-00e4-4006-99d2-0f5c6b2ad220
linux /boot/vmlinuz-2.6.32-24-generic root=UUID=f2adeeb0-00e4-4006-99d2-0f5c6b2ad220 ro quiet splash
initrd /boot/initrd.img-2.6.32-24-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set f2adeeb0-00e4-4006-99d2-0f5c6b2ad220
echo 'Loading Linux 2.6.32-24-generic ...'
linux /boot/vmlinuz-2.6.32-24-generic root=UUID=f2adeeb0-00e4-4006-99d2-0f5c6b2ad220 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-24-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-21-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set f2adeeb0-00e4-4006-99d2-0f5c6b2ad220
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=f2adeeb0-00e4-4006-99d2-0f5c6b2ad220 ro quiet splash
initrd /boot/initrd.img-2.6.32-21-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-21-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set f2adeeb0-00e4-4006-99d2-0f5c6b2ad220
echo 'Loading Linux 2.6.32-21-generic ...'
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=f2adeeb0-00e4-4006-99d2-0f5c6b2ad220 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-21-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set f2adeeb0-00e4-4006-99d2-0f5c6b2ad220
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set f2adeeb0-00e4-4006-99d2-0f5c6b2ad220
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
if [ ${timeout} != -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 ###

=============================== 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=b84db55f-2d6a-4afc-b4ce-80845cf5b41b none swap sw 0 0

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


339.4GB: boot/grub/core.img
389.1GB: boot/grub/grub.cfg
339.4GB: boot/initrd.img-2.6.32-21-generic
339.5GB: boot/initrd.img-2.6.32-24-generic
339.4GB: boot/vmlinuz-2.6.32-21-generic
339.5GB: boot/vmlinuz-2.6.32-24-generic
339.5GB: initrd.img
339.4GB: initrd.img.old
339.5GB: vmlinuz
339.4GB: vmlinuz.old
=======Devices which don't seem to have a corresponding hard drive==============

sdb sdc sdd sde

I do not see any obvious errors here.

When the computer starts hold down Shift to bring up the GRUB menu. Are you then able to boot the computer with one of the kernel images?

[wilee-nilee]

The script looks correct basically although I see the UUID missing for sda1 the Ubuntu OS in fstab.

Try reloading grub here is a link.
https://help.ubuntu.com/community/Grub2#Reinstalling%20from%20LiveCD

Not sure why you were using the root terminal, especially if you are not a experienced user, all of what you need to do can be do with a regular terminal and a sudo command. I suspect that something has been done in tweaking the OS that will make a fix unlikely, without you remembering what you have done.

[sid.mallya]

R u saying I should try booting from Initrd.img.old ?

[sid.mallya]

Okay .. I couldn't get the grub menu to come up even when I changed the grub.cfg file's 'default="2" ' ..

Secondly .. When I press the direction keys when the loading screen comes up .. I see that the boot is clean but it is getting stuck at "Checking batter state".

Does this help at all ?

[sid.mallya]

Not sure why you were using the root terminal, especially if you are not a experienced user, all of what you need to do can be do with a regular terminal and a sudo command. I suspect that something has been done in tweaking the OS that will make a fix unlikely, without you remembering what you have done.

Actually I was trying to install a driver for my Canon PIXMA MP250 (I have posted a thread on this forum itself) and also trying to configure VirtualBox .. Both of which required my being the root (or atleast that's what I thought)

All I remember was simply this .. The printer driver wouldn't work, and when I tried opening the root terminal, it wouldn't. I thought a simple restart would sort matters but it apparently made them worse. :(

[sid.mallya]

Okay .. The GRUB screen came up .. When I tried logging in using the "Recovery" mode, I could log in perfectly albeit in the tty1 terminal screen. The normal mode is still the same; and the UUID is present when I press "e" ..

Is there any way of repairing Ubuntu - or, in Windows terms, do a system recovery ? I cannot lose this data, nor is it currently possible for me to back it up someplace .. :(

[wilee-nilee]

Actually I was trying to install a driver for my Canon PIXMA MP250 (I have posted a thread on this forum itself) and also trying to configure VirtualBox .. Both of which required my being the root (or atleast that's what I thought)

All I remember was simply this .. The printer driver wouldn't work, and when I tried opening the root terminal, it wouldn't. I thought a simple restart would sort matters but it apparently made them worse. :(

If you need root approval for a installation, don't use the root terminal, use sudo. In virtualbox if your doing a regular install from synaptic or the web version you are asked for your pass word, the guest editions can be run several different ways. I might suggest being careful that your sure of what your doing. There are good reasons why root and user accounts are separate. If you mistakenly run something in root with a incorrect method you risk breaking the OS, making it unstable, and being exposed in ways you shouldn't be.

Get back into Ubuntu from the recovery and run

sudo update-grub

This might straighten out the grub.cfg file.

[Rubi1200]

Right now I can suggest you edit the fstab file and enter the missing UUID as pointed out by wilee-nilee previously.

Your fstab needs a line that looks something like this:

# / was on /dev/sda1 during installation
UUID=xxxxxxxxxxxxxxx / ext4 errors=remount-ro 0 1
where xxxx etc. is the UUID on your machine.

Save and reboot.

[sid.mallya]

Okay so .. the "sudo update-grub" didn't quite work. Still the same problem, goes on loading forever.

@Rubi,

My fstab (found in "/media/<filesystem name>/etc") doesn't have the things which were present in the RESULTS.txt file .. :confused: ..This is what I found -->


aufs / aufs rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0
/dev/sda5 swap swap defaults 0 0

I am a newbie, so go easy on me. :P

One last option, should I repartition my HDD (I have 280Gig free there) and try to reinstall Ubuntu in the primary one ?

[sid.mallya]

^ Alright that was kinda stupid. I think this was the fstab of my liveCD. I tried the


gksudo nautilus

and now I see the proper fstab file. Lemme see if this works ..

[sid.mallya]

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 /boot/grub.

sda1: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 10.04.1 LTS
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:

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

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 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 964,753,407 964,751,360 83 Linux
/dev/sda2 964,755,454 976,773,119 12,017,666 5 Extended
/dev/sda5 964,755,456 976,773,119 12,017,664 82 Linux swap / Solaris


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/sda1 f2adeeb0-00e4-4006-99d2-0f5c6b2ad220 ext4
/dev/sda2: PTTYPE="dos"
/dev/sda5 b84db55f-2d6a-4afc-b4ce-80845cf5b41b swap
/dev/sda: PTTYPE="dos"
error: /dev/sdb: No medium found
error: /dev/sdc: No medium found
error: /dev/sdd: No medium found
error: /dev/sde: No medium found

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

Device Mount_Point Type Options

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


=========================== sda1/boot/grub/grub.cfg: ===========================

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/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
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
}
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set f2adeeb0-00e4-4006-99d2-0f5c6b2ad220
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set f2adeeb0-00e4-4006-99d2-0f5c6b2ad220
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.32-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set f2adeeb0-00e4-4006-99d2-0f5c6b2ad220
linux /boot/vmlinuz-2.6.32-24-generic root=UUID=f2adeeb0-00e4-4006-99d2-0f5c6b2ad220 ro quiet splash
initrd /boot/initrd.img-2.6.32-24-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set f2adeeb0-00e4-4006-99d2-0f5c6b2ad220
echo 'Loading Linux 2.6.32-24-generic ...'
linux /boot/vmlinuz-2.6.32-24-generic root=UUID=f2adeeb0-00e4-4006-99d2-0f5c6b2ad220 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-24-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-21-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set f2adeeb0-00e4-4006-99d2-0f5c6b2ad220
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=f2adeeb0-00e4-4006-99d2-0f5c6b2ad220 ro quiet splash
initrd /boot/initrd.img-2.6.32-21-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-21-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set f2adeeb0-00e4-4006-99d2-0f5c6b2ad220
echo 'Loading Linux 2.6.32-21-generic ...'
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=f2adeeb0-00e4-4006-99d2-0f5c6b2ad220 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-21-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set f2adeeb0-00e4-4006-99d2-0f5c6b2ad220
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set f2adeeb0-00e4-4006-99d2-0f5c6b2ad220
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
if [ ${timeout} != -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 ###

=============================== 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
UUID=f2adeeb0-00e4-4006-99d2-0f5c6b2ad220 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=b84db55f-2d6a-4afc-b4ce-80845cf5b41b none swap sw 0 0

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


339.4GB: boot/grub/core.img
339.5GB: boot/grub/grub.cfg
339.4GB: boot/initrd.img-2.6.32-21-generic
339.5GB: boot/initrd.img-2.6.32-24-generic
339.4GB: boot/vmlinuz-2.6.32-21-generic
339.5GB: boot/vmlinuz-2.6.32-24-generic
339.5GB: initrd.img
339.4GB: initrd.img.old
339.5GB: vmlinuz
339.4GB: vmlinuz.old
=======Devices which don't seem to have a corresponding hard drive==============

sdb sdc sdd sde

This is the new RESULTS.txt file generated by the bash script. Please check and inform me if its correct.

(Also, there is no change to the booting even after editing the fstab.)

[Rubi1200]

If that is the correct UUID for the Ubuntu partition (which you can get by right-clicking on the partition in GParted and find it under Information) then okay, but the line needs to look like this:


# / was on /dev/sda1 during installationthen a new line and then the rest of it as you have in the script. Save and reboot and let's see if it makes a difference.

In other words, fstab should look like this:

# / was on /dev/sda1 during installation
UUID=f2adeeb0-00e4-4006-99d2-0f5c6b2ad220 / ext4 errors=remount-ro 0 1

The entry for swap looks okay.

[sid.mallya]

@Rubi,

I see. Will make the changes. Although, just for general knowledge, how does an commented statement like the one u've asked me to type make a difference to the execution ?

[Rubi1200]

@Rubi,

I see. Will make the changes. Although, just for general knowledge, how does an commented statement like the one u've asked me to type make a difference to the execution ?
In order for the system to know what to mount at boot it needs to know where to look. Possibly the UUID is more important, but most fstab files I have seen have the line with where / was at installation.

[sid.mallya]

=============================== 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
# / was on /dev/sda1 during installation
UUID=f2adeeb0-00e4-4006-99d2-0f5c6b2ad220 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=b84db55f-2d6a-4afc-b4ce-80845cf5b41b none swap sw 0 0


From Results.txt .. Going to try to restart my computer now .. Hopefully it works .. :(

[sid.mallya]

Nope. No change.

Btw I just realised this .. If I press Ctrl+Alt+F1/F2, etc. I am able to log into the tty terminals; meaning the OS is booting properly, just there is something wrong with the GUI. I tried "startx" and "INIT 5" commands (yes, I know Debian has the same run levels for 2-5, still) but it fails some operation. In my opinion, it is the GUI which has got disabled for some reason .. Any thoughts ?

[sid.mallya]

Wait .. Isn't the Debian command "telinit" instead of just "init" ?

[Rubi1200]

When you get to the console try this command and see if it helps:


sudo /etc/init.d/gdm start

[sid.mallya]

@Rubi,

It didn't. This is beginning to get very annoying .. :(