I experience a couple of problems, when this one is sorted out, I'll start on the next one!
The problem is a 75 second boot time and after investigation have found that, at 8. 5 seconds the 2nd internal HDD (sbd5) is mounted, this is the HDD that hosts the OS. Then everything goes into a state of limbo and finally, at 36.5 seconds in to boot-up sequence, with nothing happening in between, it is re-mounted
I may be going senile, but I can not for the life of me work out why this is happening.
The two consecutive lines from the boot log sequence look like this:
[ 8.428310] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Opts: (null) [ 36.611892] EXT4-fs (sdb5): re-mounted. Opts: errors=remount-ro
My grub file looks like this:
GRUB_DEFAULT="0" #GRUB_HIDDEN_TIMEOUT="0" GRUB_HIDDEN_TIMEOUT_QUIET="true" GRUB_TIMEOUT="3" GRUB_DISTRIBUTOR="`lsb_release -i -s 2> /dev/null || echo Debian`" GRUB_CMDLINE_LINUX_DEFAULT="quiet profile splash nomodeset video=uvesafb:mode_option=1280x1024-24,mtrr=3,scroll=ywrap" GRUB_CMDLINE_LINUX=""
I have the mount option for the drive set at: Mount at Startup
I do not have a swap file as I have 4GiB SDRAM.
- Processor - Intel® Core™2 Duo CPU T5450 @ 1.66GHz × 2
- Graphics - GeForce 8400M GT/PCIe/SSE2
- OS - Ubuntu 13.04 64-bit
- Memory - 3.9 GiB
HDD 1 (sda)
- FUJITSU MHY2250BH 250GiB
- running at 38°C/100°F
- This is the Windows 7 disk which I use to run iTunes on (damn Apple!!!)
- sda1, HPFS/NTFS (Bootable), 105 MB
- sda2, HPFS/NTFS, 250 GB
HDD 2 (sdb)
- FUJITSU MHY2200BH 200GiB
- running at 44°C/111°F
- 196611 bad sectors on it this has
- sdb1 Extended Partition 194 GB
- sdb2 Linux, Ext2 (version 1.0), 5.9 GB
- sdb5 Linux, Ext4 (version 1.0), 194 GB
If you have any ideas how to stop this long delay in my boot time, I would appreciate hearing from you.
UPDATE Thursday 6th June 16:15
[ 9.443273] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Opts: (null) [ 37.837711] EXT4-fs (sdb5): re-mounted. Opts: errors=remount-ro
on a previous boot, the message included a bit where a repair of the read only part of the disk was required, it was fixed 2 seconds later.
Could the answer be in the 196611 bad sectors?