SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
At boot time, before entering Runlevel 3 the HDD will go mad when mounting tmpfs on /dev/shm...
Code:
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
-------------------------------------------
INIT:Entering runlevel 3
...........................
It will go on and on at the tmpfs on /dev/shm type tmpfs (rw) until i press ctrl-C...
then I will stop whatever it is doing, let the hdd rest a bit, and resume normal boot...
Well after you control+c out of it and booting continues, what does the syslogs say? Also out of curiosity, what happens if you boot / with your install disk?
Messed with udev or your fstab file? I had some problems when migrating udev to '/lib64/udev' and tmpfs not being mounted at boot because, on my insanity, I forgot about the 'devices' subdir =[
Look inside rc.S, rc.M and rc.udev for some clues about how tmpfs is mounted at boot
Even with the long delay, '/dev/shm' is mounted when you boot your machine?
If not, can you mount tmpfs by hand? Type 'mount tmpfs' and look the output...
ps: when I type 'mount', mine reads 'tmpfs on /dev/shm type tmpfs (rw,noatime)'.
alex@iskandhar:~/trunk/elmerfem/trunk/ElmerGUI$ mount
/dev/cryptvg/root on / type ext3 (rw,errors=continue,data=ordered)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sdb1 on /media/KINGSTON type vfat (rw,nosuid,nodev,uhelper=hal,uid=1000,utf8,shortname=mixed,flush)
alex@iskandhar:~/trunk/elmerfem/trunk/ElmerGUI$
For reference hda_intel is the Intel ICHx sound driver module and is not related to the ata subsystem.
Yea, I thought it was the ata sys. Dopey me.
Quote:
Originally Posted by Alexvader
The issue fixed itself....
I let the activity proceed till eventually boot continued...
Next time I booted, ther was no more delay...
Strange this...
Any Idea what might have caused it...?
Unfortunately you will have to keep looking through your syslog. The reason of why is buried somewhere there. Just post whatever you find/think is relevant to your disk activity during that date/time and hopefully one of us (probably not me) can actually figure it out.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.