Peter Bell
November 19th, 2010, 06:48 AM
I'm running ubuntu on an i5-650, Intel H55 mobo system. I have 4GB RAM.
I was running Lucid (AMD64) very happily, but then had a severe failure of the Samsung HD502HJ hdd (the smart report is showing more than 1000 bad sectors, increasing everytime I try to access the disk).
I have replaced that drive with a Seagate ST3500418AS. Using ddrescue I was able to recover all but 9MB of the drive content. However, with my /etc, /proc and /opt directories having gone missing, I decided that attempting to recover the installation was a lost cause so I went ahead and installed Maverick onto the new drive. As part of this process I created a separate partition for my /home directory (recovered from the old drive).
Now, having installed only a few 'essential' packages (eg autofs5), I've realised that a lot of actions are taking well in excess of a minute to take effect. For instance, clicking on 'Places->Computer', it takes approximately 100 seconds before the Nautilus window appears.
According to System Monitor, there is nothing using any significant resource during this time - it's as though something is waiting for a timeout to complete before actioning my command.
If I look at the processes in System Monitor during this time, I can see that the Nautilus process is showing 'autofs4_wait'.
Is anyone able to suggest what is likely to be causing this, and how can I fix it.
I was running Lucid (AMD64) very happily, but then had a severe failure of the Samsung HD502HJ hdd (the smart report is showing more than 1000 bad sectors, increasing everytime I try to access the disk).
I have replaced that drive with a Seagate ST3500418AS. Using ddrescue I was able to recover all but 9MB of the drive content. However, with my /etc, /proc and /opt directories having gone missing, I decided that attempting to recover the installation was a lost cause so I went ahead and installed Maverick onto the new drive. As part of this process I created a separate partition for my /home directory (recovered from the old drive).
Now, having installed only a few 'essential' packages (eg autofs5), I've realised that a lot of actions are taking well in excess of a minute to take effect. For instance, clicking on 'Places->Computer', it takes approximately 100 seconds before the Nautilus window appears.
According to System Monitor, there is nothing using any significant resource during this time - it's as though something is waiting for a timeout to complete before actioning my command.
If I look at the processes in System Monitor during this time, I can see that the Nautilus process is showing 'autofs4_wait'.
Is anyone able to suggest what is likely to be causing this, and how can I fix it.