Take too much time to scan file system while booting

Please open a terminal and type:
df -h

Post the output here. (highlight the output and paste it with middle mouse)

Next, type:
sudo fdisk -l

## where l is lower case of L

Post the output also. Thanks.

There is a bug which incl. a possible workaround.

Here is output of both commands df -h and fdisk -l :-

root@sharedata:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sdc1 229G 197G 21G 91% /
varrun 1.5G 148K 1.5G 1% /var/run
varlock 1.5G 0 1.5G 0% /var/lock
udev 1.5G 52K 1.5G 1% /dev
devshm 1.5G 24K 1.5G 1% /dev/shm
lrm 1.5G 40M 1.5G 3% /lib/modules/2.6.24-28-generic/volatile
/dev/md0 925G 495G 383G 57% /root/raid

root@sharedata:~# sudo fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/sda doesn't contain a valid partition table

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/sdc: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00074c5a

   Device Boot Start End Blocks Id System
/dev/sdc1 * 1 30028 241199878+ 83 Linux
/dev/sdc2 30029 30401 2996122+ 5 Extended
/dev/sdc5 30029 30401 2996091 82 Linux swap / Solaris

Disk /dev/md0: 1000.2 GB, 1000204795904 bytes
2 heads, 4 sectors/track, 244190624 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md0 doesn't contain a valid partition table.
--
But This problem is not only for one system. it's appearing several systems.
I have around 50 systems in my comp. which all are managed by me .

please let me know if you need more information regarding this.

Thanks
Gokendra

> /dev/sdc1 229G 197G 21G 91% /
> /dev/sdc1 * 1 30028 241199878+ 83 Linux

As you may see yourself you need to free some space.
Clean up package cache.
CLI:
sudo apt-get autoremove && sudo apt-get clean && sudo apt-get autoclean

Verify how many kernel images are installed and in case remove one or two, since they take lots of disk space.
Make sure not to remove the current kernel image you're booting with.

Find out currently booted image:
uname -r

Find installed images:
dpkg -l linux-image* |grep ii

## Example output (short):
ii linux-image-2.6.35-22-generic
ii linux-image-2.6.35-23-generic
ii linux-image-2.6.35-24-generic
ii linux-image-2.6.35-25-generic

## Lets say I'd like to remove -22 and -23.
sudo apt-get purge linux-image-2.6.35-22-generic
sudo apt-get purge linux-image-2.6.35-23-generic

## I'd keep two images, current and previous, just in case one fails to boot.

https://help.ubuntu.com/community/AptGet/Howto

If nothing helps
- join bug report by click on 'Does this bug affect you?'
- wait until it's fixed
- report a new one (maybe your issue concerns raid architecture)
CLI:
LANG=C ubuntu-bug mountall
https://help.ubuntu.com/community/ReportingBugs

- You may also test if boot is faster when plymouth (fancy splash on boot) is deactivated.
For this you need to edit Grub. Backup the file first, choose whatever ending you prefer.
CLI:
sudo cp /etc/default/grub /etc/default/grub-backup

Open the file:
gksudo gedit /etc/default/grub

## Search the line
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

## change it to
GRUB_CMDLINE_LINUX_DEFAULT=""

save the file and run:
sudo update-grub

## Alternative: Change the line to
GRUB_CMDLINE_LINUX_DEFAULT="noplymouth"

https://help.ubuntu.com/community/Grub2#/etc/default/grub%20%28file%29

- upgrade to Maverick 10.10
https://wiki.ubuntu.com/MaverickMeerkat/ReleaseNotes