It takes a long time from startup to GRUB

English Install/Boot/Login
#1

Hi,
this happens after I suspended my pc: From fresh startup to GRUB it takes almost 4 minutes. At first I thought it is somehow related to MBR. But the problem remains after I fix the MBR.
Really need help on this.

Thanks,

#2

How much ram do you have in your system? The stage you describe is when grub is reading back your memory from disk to ram, but 4 minutes is way too long! Could also be a driver is delaying things…

Any clues in;
/var/log/messages
/var/log/pm-suspend.log
or ‘dmesg’, when you have just resumed?

-Wj

#3

Thanks for the respond,
I forgot to mention that reinstalled opensuse after the first slow boot, my bad. So the /var/log/pm-suspend.log is empty.

I looked the output from dmesg and /var/log/messages but as far as my noob eyes can see, I don’t see anything wrong. I’d like post them here, but they’re too long. And I don’t see any possibility to attach those as files in this forum, too (probably a reason to include the file-attachment function in this forum ;)).

Cheers,
T.A.

#4

BTW I have 1GB Ram-memory

#5

PS: I have 1GB ram.

#6

iamlost schrieb:
> this happens after I suspended my pc: From fresh startup to GRUB it
> takes almost 4 minutes. At first I thought it is somehow related to
> MBR. But the problem remains after I fix the MBR.

What filesystem type are your / and /boot directories on? If it’s
ReiserFS, I used to have a similar issue because suspend wouldn’t mark
the filesystem as clean, so GRUB went and replayed the transaction log,
which does take a long time.

HTH
T.

–
Tilman Schmidt t.schmidt@phoenixsoftware.de
Phoenix Software GmbH www.phoenixsoftware.de
Adolf-Hombitzer-Str. 12 Amtsgericht Bonn HRB 2934
53227 Bonn, Germany Geschäftsführer: W. Grießl

#7

Hi,
I have ext3 and swap for linux partitions and ntfs for xp. This problem isn’t really new to me. It happened before when I was using 10.3 too. But at that time the long delay at startup was somehow magically fixed. I had a normal boot speed until it came again after suspending my computer. Afterward I installed 11.0 hoping to fix it, but the problem remains

Sorry for the double post. @ Mods: how can I delete it?
Thanks,
T.A.

#8

This is from menu.lst:

Modified by YaST2. Last modification on Fri Jun 27 13:47:20 CEST 2008

default 2
timeout 8

###Don’t change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.0 - 2.6.25.5-1.1
root (hd1,0)
kernel /boot/vmlinuz-2.6.25.5-1.1-default root=/dev/disk/by-id/scsi-SATA_SAMSUNG_HD400LDS0AXJ1CPB23867-part1 resume=/dev/sdb7 splash=silent showopts
initrd /boot/initrd-2.6.25.5-1.1-default

###Don’t change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe – openSUSE 11.0 - 2.6.25.5-1.1
root (hd1,0)
kernel /boot/vmlinuz-2.6.25.5-1.1-default root=/dev/disk/by-id/scsi-SATA_SAMSUNG_HD400LDS0AXJ1CPB23867-part1 showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off x11failsafe
initrd /boot/initrd-2.6.25.5-1.1-default

###Don’t change this comment - YaST2 identifier: Original name: linux-2.6.25.5-1.1-pae###
title openSUSE 11.0
kernel (hd1,0)/boot/vmlinuz-2.6.25.5-1.1-pae root=/dev/disk/by-id/scsi-SATA_SAMSUNG_HD400LDS0AXJ1CPB23867-part1 resume=/dev/sdb7 splash=silent showopts
initrd (hd1,0)/boot/initrd-2.6.25.5-1.1-pae

###Don’t change this comment - YaST2 identifier: Original name: windows###
title Windows
rootnoverify (hd1,0)
chainloader (hd0,0)+1

###Don’t change this comment - YaST2 identifier: Original name: floppy###
title Floppy
rootnoverify (hd1,0)
chainloader (fd0)+1

###Don’t change this comment - YaST2 identifier: Original name: failsafe-2.6.25.5-1.1-pae###
title Failsafe – openSUSE 11.0
kernel (hd1,0)/boot/vmlinuz-2.6.25.5-1.1-pae root=/dev/disk/by-id/scsi-SATA_SAMSUNG_HD400LDS0AXJ1CPB23867-part1 showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off x11failsafe
initrd (hd1,0)/boot/initrd-2.6.25.5-1.1-pae

###Don’t change this comment - YaST2 identifier: Original name: Kernel-2.6.25.5-1.1-pae###
title Kernel-2.6.25.5-1.1-pae
kernel (hd1,0)/boot/vmlinuz-2.6.25.5-1.1-pae root=/dev/disk/by-id/scsi-SATA_SAMSUNG_HD400LDS0AXJ1CPB23867-part1 resume=/dev/sdb7 splash=silent showopts
initrd (hd1,0)/boot/initrd-2.6.25.5-1.1-pae

Notice the (hd1,0). Does this mean that my computer boots from hd1? If it’s true then could it be the reason to the slow boot? Because the setting from menu.lst differs from my BIOS setting, which is set to boot from hd0. Is it then safe to change the menu.lst so it conforms the boot setting from BIOS?
Anyone can help?
Thanks,
T.A

#9

You can always make a second entry by making a copy of the one you want to test using hd0.
Try to boot using it and if does (&resume) you will have an answer.

Who is /dev/sdb7? Thats the correct swap partition?

#10

Will try and report back. The /dev/sdb7 is swap partition. Is it suppose to be there?
Many thanks,
T. A.

#11

If it’s the swap… yes. Your hibernation info (memdump etc) is written to your swap partition. Bluntly said: If you want to hibernate to disk then the swap must be big enough to contain your working mem. If not hibernation will fail.

#12

Could you please help me to fix it? My last try editing the menu.lst wasn’t so helpful.
Much obliged,
T. A.