Discussion:
[Grml] The installed GRML boots very slow
Hermann
2009-05-22 14:15:31 UTC
Permalink
Hi,
while checking out your list archive, I found that this was brought up
some months ago, but I repeat it:
I installed the release candidate of GRML 2008-11 on my desktop machine,
and since that I had to observe a slow boot process.
My hard drive start spinning and then stops for a long time till it
starts moving again. I guess that in the meantime there runs the
hardware detection. But why lasts this procedure so long?
Below I put the results of:
cat /proc/partitions
and
ll /sys/block

major minor #blocks name

8 0 39099375 sda
8 1 15358108 sda1
8 2 1 sda2
8 5 16386268 sda5
8 6 48163 sda6
8 7 7301511 sda7

insgesamt 0
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram0 -> ../devices/virtual/block/ram0/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram1 -> ../devices/virtual/block/ram1/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram10 -> ../devices/virtual/block/ram10/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram11 -> ../devices/virtual/block/ram11/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram12 -> ../devices/virtual/block/ram12/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram13 -> ../devices/virtual/block/ram13/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram14 -> ../devices/virtual/block/ram14/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram15 -> ../devices/virtual/block/ram15/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram16 -> ../devices/virtual/block/ram16/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram17 -> ../devices/virtual/block/ram17/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram18 -> ../devices/virtual/block/ram18/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram19 -> ../devices/virtual/block/ram19/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram2 -> ../devices/virtual/block/ram2/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram20 -> ../devices/virtual/block/ram20/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram21 -> ../devices/virtual/block/ram21/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram22 -> ../devices/virtual/block/ram22/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram23 -> ../devices/virtual/block/ram23/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram24 -> ../devices/virtual/block/ram24/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram25 -> ../devices/virtual/block/ram25/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram26 -> ../devices/virtual/block/ram26/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram27 -> ../devices/virtual/block/ram27/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram28 -> ../devices/virtual/block/ram28/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram29 -> ../devices/virtual/block/ram29/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram3 -> ../devices/virtual/block/ram3/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram30 -> ../devices/virtual/block/ram30/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram31 -> ../devices/virtual/block/ram31/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram4 -> ../devices/virtual/block/ram4/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram5 -> ../devices/virtual/block/ram5/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram6 -> ../devices/virtual/block/ram6/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram7 -> ../devices/virtual/block/ram7/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram8 -> ../devices/virtual/block/ram8/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram9 -> ../devices/virtual/block/ram9/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 sda -> ../devices/pci0000:00/0000:00:07.1/host0/target0:0:0/0:0:0:0/block/sda/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 sr0 -> ../devices/pci0000:00/0000:00:07.1/host1/target1:0:0/1:0:0:0/block/sr0/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 sr1 -> ../devices/pci0000:00/0000:00:07.1/host1/target1:0:1/1:0:1:0/block/sr1/

Anything wrong with that entries?
What can I change? I remember that deactivating udev detection is no
good idea.
Hermann

--
Hermann
2009-05-22 14:15:31 UTC
Permalink
Hi,
while checking out your list archive, I found that this was brought up
some months ago, but I repeat it:
I installed the release candidate of GRML 2008-11 on my desktop machine,
and since that I had to observe a slow boot process.
My hard drive start spinning and then stops for a long time till it
starts moving again. I guess that in the meantime there runs the
hardware detection. But why lasts this procedure so long?
Below I put the results of:
cat /proc/partitions
and
ll /sys/block

major minor #blocks name

8 0 39099375 sda
8 1 15358108 sda1
8 2 1 sda2
8 5 16386268 sda5
8 6 48163 sda6
8 7 7301511 sda7

insgesamt 0
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram0 -> ../devices/virtual/block/ram0/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram1 -> ../devices/virtual/block/ram1/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram10 -> ../devices/virtual/block/ram10/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram11 -> ../devices/virtual/block/ram11/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram12 -> ../devices/virtual/block/ram12/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram13 -> ../devices/virtual/block/ram13/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram14 -> ../devices/virtual/block/ram14/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram15 -> ../devices/virtual/block/ram15/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram16 -> ../devices/virtual/block/ram16/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram17 -> ../devices/virtual/block/ram17/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram18 -> ../devices/virtual/block/ram18/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram19 -> ../devices/virtual/block/ram19/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram2 -> ../devices/virtual/block/ram2/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram20 -> ../devices/virtual/block/ram20/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram21 -> ../devices/virtual/block/ram21/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram22 -> ../devices/virtual/block/ram22/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram23 -> ../devices/virtual/block/ram23/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram24 -> ../devices/virtual/block/ram24/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram25 -> ../devices/virtual/block/ram25/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram26 -> ../devices/virtual/block/ram26/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram27 -> ../devices/virtual/block/ram27/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram28 -> ../devices/virtual/block/ram28/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram29 -> ../devices/virtual/block/ram29/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram3 -> ../devices/virtual/block/ram3/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram30 -> ../devices/virtual/block/ram30/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram31 -> ../devices/virtual/block/ram31/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram4 -> ../devices/virtual/block/ram4/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram5 -> ../devices/virtual/block/ram5/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram6 -> ../devices/virtual/block/ram6/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram7 -> ../devices/virtual/block/ram7/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram8 -> ../devices/virtual/block/ram8/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram9 -> ../devices/virtual/block/ram9/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 sda -> ../devices/pci0000:00/0000:00:07.1/host0/target0:0:0/0:0:0:0/block/sda/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 sr0 -> ../devices/pci0000:00/0000:00:07.1/host1/target1:0:0/1:0:0:0/block/sr0/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 sr1 -> ../devices/pci0000:00/0000:00:07.1/host1/target1:0:1/1:0:1:0/block/sr1/

Anything wrong with that entries?
What can I change? I remember that deactivating udev detection is no
good idea.
Hermann

--
Hermann
2009-05-22 14:15:31 UTC
Permalink
Hi,
while checking out your list archive, I found that this was brought up
some months ago, but I repeat it:
I installed the release candidate of GRML 2008-11 on my desktop machine,
and since that I had to observe a slow boot process.
My hard drive start spinning and then stops for a long time till it
starts moving again. I guess that in the meantime there runs the
hardware detection. But why lasts this procedure so long?
Below I put the results of:
cat /proc/partitions
and
ll /sys/block

major minor #blocks name

8 0 39099375 sda
8 1 15358108 sda1
8 2 1 sda2
8 5 16386268 sda5
8 6 48163 sda6
8 7 7301511 sda7

insgesamt 0
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram0 -> ../devices/virtual/block/ram0/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram1 -> ../devices/virtual/block/ram1/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram10 -> ../devices/virtual/block/ram10/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram11 -> ../devices/virtual/block/ram11/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram12 -> ../devices/virtual/block/ram12/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram13 -> ../devices/virtual/block/ram13/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram14 -> ../devices/virtual/block/ram14/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram15 -> ../devices/virtual/block/ram15/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram16 -> ../devices/virtual/block/ram16/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram17 -> ../devices/virtual/block/ram17/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram18 -> ../devices/virtual/block/ram18/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram19 -> ../devices/virtual/block/ram19/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram2 -> ../devices/virtual/block/ram2/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram20 -> ../devices/virtual/block/ram20/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram21 -> ../devices/virtual/block/ram21/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram22 -> ../devices/virtual/block/ram22/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram23 -> ../devices/virtual/block/ram23/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram24 -> ../devices/virtual/block/ram24/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram25 -> ../devices/virtual/block/ram25/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram26 -> ../devices/virtual/block/ram26/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram27 -> ../devices/virtual/block/ram27/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram28 -> ../devices/virtual/block/ram28/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram29 -> ../devices/virtual/block/ram29/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram3 -> ../devices/virtual/block/ram3/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram30 -> ../devices/virtual/block/ram30/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram31 -> ../devices/virtual/block/ram31/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram4 -> ../devices/virtual/block/ram4/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram5 -> ../devices/virtual/block/ram5/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram6 -> ../devices/virtual/block/ram6/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram7 -> ../devices/virtual/block/ram7/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram8 -> ../devices/virtual/block/ram8/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 ram9 -> ../devices/virtual/block/ram9/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 sda -> ../devices/pci0000:00/0000:00:07.1/host0/target0:0:0/0:0:0:0/block/sda/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 sr0 -> ../devices/pci0000:00/0000:00:07.1/host1/target1:0:0/1:0:0:0/block/sr0/
lrwxrwxrwx 1 root root 0 22. Mai 15:15 sr1 -> ../devices/pci0000:00/0000:00:07.1/host1/target1:0:1/1:0:1:0/block/sr1/

Anything wrong with that entries?
What can I change? I remember that deactivating udev detection is no
good idea.
Hermann

--
Michael Prokop
2009-06-01 21:59:41 UTC
Permalink
Post by Hermann
while checking out your list archive, I found that this was brought up
I installed the release candidate of GRML 2008-11 on my desktop machine,
and since that I had to observe a slow boot process.
My hard drive start spinning and then stops for a long time till it
starts moving again. I guess that in the meantime there runs the
hardware detection. But why lasts this procedure so long?
[...]
Post by Hermann
Anything wrong with that entries?
What can I change? I remember that deactivating udev detection is no
good idea.
When booting with noudev the problem isn't visible?
If so try finding out which driver takes so long to initialize.
Look at output of lsmod of a system running without the use of
noudev and manually load the drivers. Also check out dmesg and the
timing information at the beginning of each line.

regards,
-mika-
--
http://grml.org/ # Linux for texttool-users and sysadmins
http://wiki.grml.org/ # share your knowledge
http://grml.supersized.org/ # the grml development weblog
#grml @ irc.freenode.org # meet us on irc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.mur.at/pipermail/grml/attachments/20090601/e19b843a/attachment.pgp
Hermann
2009-06-02 08:42:35 UTC
Permalink
Post by Michael Prokop
Post by Hermann
while checking out your list archive, I found that this was brought up
I installed the release candidate of GRML 2008-11 on my desktop machine,
and since that I had to observe a slow boot process.
My hard drive start spinning and then stops for a long time till it
starts moving again. I guess that in the meantime there runs the
hardware detection. But why lasts this procedure so long?
[...]
Post by Hermann
Anything wrong with that entries?
What can I change? I remember that deactivating udev detection is no
good idea.
When booting with noudev the problem isn't visible?
If so try finding out which driver takes so long to initialize.
How can I change boot options on an installed system?
Post by Michael Prokop
Look at output of lsmod of a system running without the use of
noudev and manually load the drivers. Also check out dmesg and the
timing information at the beginning of each line.
I've checked taht, but I don't really understand what all the entries
mean?
May I send you the output?
Hermann
Hermann
2009-06-02 08:42:35 UTC
Permalink
Post by Michael Prokop
Post by Hermann
while checking out your list archive, I found that this was brought up
I installed the release candidate of GRML 2008-11 on my desktop machine,
and since that I had to observe a slow boot process.
My hard drive start spinning and then stops for a long time till it
starts moving again. I guess that in the meantime there runs the
hardware detection. But why lasts this procedure so long?
[...]
Post by Hermann
Anything wrong with that entries?
What can I change? I remember that deactivating udev detection is no
good idea.
When booting with noudev the problem isn't visible?
If so try finding out which driver takes so long to initialize.
How can I change boot options on an installed system?
Post by Michael Prokop
Look at output of lsmod of a system running without the use of
noudev and manually load the drivers. Also check out dmesg and the
timing information at the beginning of each line.
I've checked taht, but I don't really understand what all the entries
mean?
May I send you the output?
Hermann
Hermann
2009-06-02 08:42:35 UTC
Permalink
Post by Michael Prokop
Post by Hermann
while checking out your list archive, I found that this was brought up
I installed the release candidate of GRML 2008-11 on my desktop machine,
and since that I had to observe a slow boot process.
My hard drive start spinning and then stops for a long time till it
starts moving again. I guess that in the meantime there runs the
hardware detection. But why lasts this procedure so long?
[...]
Post by Hermann
Anything wrong with that entries?
What can I change? I remember that deactivating udev detection is no
good idea.
When booting with noudev the problem isn't visible?
If so try finding out which driver takes so long to initialize.
How can I change boot options on an installed system?
Post by Michael Prokop
Look at output of lsmod of a system running without the use of
noudev and manually load the drivers. Also check out dmesg and the
timing information at the beginning of each line.
I've checked taht, but I don't really understand what all the entries
mean?
May I send you the output?
Hermann

Michael Prokop
2009-06-01 21:59:41 UTC
Permalink
Post by Hermann
while checking out your list archive, I found that this was brought up
I installed the release candidate of GRML 2008-11 on my desktop machine,
and since that I had to observe a slow boot process.
My hard drive start spinning and then stops for a long time till it
starts moving again. I guess that in the meantime there runs the
hardware detection. But why lasts this procedure so long?
[...]
Post by Hermann
Anything wrong with that entries?
What can I change? I remember that deactivating udev detection is no
good idea.
When booting with noudev the problem isn't visible?
If so try finding out which driver takes so long to initialize.
Look at output of lsmod of a system running without the use of
noudev and manually load the drivers. Also check out dmesg and the
timing information at the beginning of each line.

regards,
-mika-
--
http://grml.org/ # Linux for texttool-users and sysadmins
http://wiki.grml.org/ # share your knowledge
http://grml.supersized.org/ # the grml development weblog
#grml @ irc.freenode.org # meet us on irc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://ml.grml.org/pipermail/grml/attachments/20090601/e19b843a/attachment-0002.pgp>
Michael Prokop
2009-06-01 21:59:41 UTC
Permalink
Post by Hermann
while checking out your list archive, I found that this was brought up
I installed the release candidate of GRML 2008-11 on my desktop machine,
and since that I had to observe a slow boot process.
My hard drive start spinning and then stops for a long time till it
starts moving again. I guess that in the meantime there runs the
hardware detection. But why lasts this procedure so long?
[...]
Post by Hermann
Anything wrong with that entries?
What can I change? I remember that deactivating udev detection is no
good idea.
When booting with noudev the problem isn't visible?
If so try finding out which driver takes so long to initialize.
Look at output of lsmod of a system running without the use of
noudev and manually load the drivers. Also check out dmesg and the
timing information at the beginning of each line.

regards,
-mika-
--
http://grml.org/ # Linux for texttool-users and sysadmins
http://wiki.grml.org/ # share your knowledge
http://grml.supersized.org/ # the grml development weblog
#grml @ irc.freenode.org # meet us on irc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://ml.grml.org/pipermail/grml/attachments/20090601/e19b843a/attachment-0003.pgp>
Loading...