How to disable 10.10 checks drives at every boot

I have looked in Technical Answers in case anyone else has had the same problem I have and did not find anything similar to my problem.

Can you give the output of:

gedit /etc/default/grub

Thanks

Here is my output from gedit /etc/default/grub:
---------------------------------------------------------------------
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.

GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_LINUX_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

Check the mount count parameter with tune2fs:

sudo tune2fs -l /dev/sda1

If the max mountcount has been changed to something silly you can change it with:

sudo tine2fs -c 35 /dev/sda1

which will change the maximum mount count to 35; this means that it will force a check of the drive after35 mounts. If you have multiple partitions it's nice to have different mount counts for them, so that they never have to test all at the same time.

If it's a strange cycle where the test is stuck in a loop try pressing the key to abort the test (nothing bad should happen).

If it keeps on happening then there's something else going on- either it's stuck in "check on next re-boot" mode or it's detecting a filesystem problem every time you boot.

Chris

Thanks Chris. I entered your first suggestion to get a read out and this was the output:

tune2fs 1.41.12 (17-May-2010)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: b4d96413-8afd-4edf-bf38-2f93eb468810
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: filetype sparse_super large_file
Default mount options: (none)
Filesystem state: not clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 7880704
Block count: 15743692
Reserved block count: 787184
Free blocks: 12774916
Free inodes: 7642249
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16384
Inode blocks per group: 512
Last mount time: Sun Jan 15 20:30:28 2012
Last write time: Sun Jan 15 22:54:45 2012
Mount count: 1
Maximum mount count: 30
Last checked: Sun Jan 15 22:43:46 2012
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128

I do notice that under Filesystem state it has "not clean", could this be causing the problem? I will run the same command for the other partitions and see what their output will read. Thank you for the help, I will keep you updated.

Chris, I ran your suggestions and the problem still exists. It still runs check at boot and then reboots.

I ran > System > Administration > Disk Utility and ran a file system check and repair, it returned "file system is clean" response after test. I ran it on other drives and got the same result.

Yes, your "maximum mount count" is 30 (probably default) but the "count" is only one (just checked) so that is not the cause.

The most likely cause is the "Filesystem state: not clean" you are seeing. It seems to be indicating a problem with the file system and this is probably causing the checks on every boot.

Does the system shut down by itself normally, or do you have to force power off for some reason? Is there anything else odd going on?

As a test you could try a safe reboot using the the SysRq feature. It just takes a bit of Ninja style keyboard contortion:

Hold down the <Alt> key and the <SysRq> at the same time (it's on the <Print Screen> key on a normal keyboard).
While holding down these two keys, also press the following keys, alowing a second or two between keypresses:
r e i s u b

This will do various things including flush the drive cache correctly and unmount the drives, then remount as read only (hence the completely safe part) and finally cause the computer to reboot clean. Reference is here:
http://en.wikipedia.org/wiki/Magic_SysRq_key

Does the system do a normal boot next time around?

You'll note from the reference I gave that you can also turn the system off safely with the SysRq key combination of:
r e i s u o

Try these and see if it makes a difference, but you really need to find out what is making a mess of the files system. If there's nothing obvious you might need to check the disk drive in case is failing or developing errors.

Chris

Chris, the system shuts off normally without any forced shut down procedures, so that was not a problem. I did the [Alt] [SysRq] sequence and the computer booted normally without running the file check. I have to see if after several reboots if it repeats the same problem.

Thanks Chris for the info. Have rebooted several times and it seems that the problem still occurs. I will probably need to run an industrial strength file system check and repair to fix this.