[Presario C500] Delayed bootup on dual-boot system

Output of mount:
==============
/dev/sda5 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
/dev/sda1 on /media/sda1 type fuseblk (rw,nosuid,nodev,allow_other,default_permissions,blksize=4096)
/dev/sda7 on /media/Datos type fuseblk (rw,nosuid,nodev,allow_other,default_permissions,blksize=4096)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw)
gvfs-fuse-daemon on /home/luis/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=luis)

Configs of /etc/fstab
================
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda5 during installation
UUID=c016a54f-5b56-4f36-adcc-a8cb375febe5 / ext3 errors=remount-ro 0 1
/dev/sda6 none swap sw 0 0
/dev/sda1 /media/sda1 ntfs nls=iso8859-1,umask=000 0 0
/dev/sda7 /media/Datos ntfs nls=iso8859-1,umask=000,owner,uid=luis 0 0
#192.168.1.15:/home/rodrigo/Música /mnt/musicas nfs defaults 0 0

* Additional tests:
RAM test showed no errors and fsck also showed a clean

* Here's one of the gaps on dmesg:
[ 28.971126] cfg80211: Updating information on frequency 2484 MHz for a 20 MHz width channel with regulatory rule:
[ 28.971131] cfg80211: 2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 28.971136] cfg80211: World regulatory domain updated:
[ 28.971139] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 28.971144] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 28.971148] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 28.971152] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 28.971157] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 28.971161] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 32.876296] init: ufw pre-start process (673) terminated with status 1
[ 271.823913] EXT3-fs (sda5): using internal journal
[ 272.856389] RPC: Registered named UNIX socket transport module.
[ 272.856397] RPC: Registered udp transport module.
[ 272.856400] RPC: Registered tcp transport module.
[ 272.856403] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 272.930834] FS-Cache: Loaded
[ 273.120082] init: ufw pre-start process (1148) terminated with status 1
[ 273.245387] init: failsafe main process (1329) killed by TERM signal
[...

Also noted (thanks to ubuntu forum's staffer papibe suggestion) that turning of the wifi antenna by the hardware switch reduces bootup by 50 seconds.