We are sitting here in front of an ubuntu 10.04 server who insists doing a lengthy checkdisk during reboot.
We see one option to edit the kernel boot options line in grub to skip the check.
What would be the parmater, something like --skip-fsck maybe?
I am also trying google and docs and could not find it so far. Still searching...
With Mat's help (googling for fsck not chkdsk) i found the parameter, it is probably "fastboot", tried to edit grub during boot with that... still not found the right way to do it. Does it need -- in front? which line?
The boot process on ubuntu 10.04 is not like traditionally on linux, some things have changed to "speed up" the boot process. Obviously this results in the fact that fsck is no longer a foreground process that could be aborted with ctrl-c. There is pressing "C" mentioned, but this does not work, no reaction.
This is an Ubuntu 10.04 Server. I found this:
https: //wiki.ubuntu.com/LucidLynx/ReleaseNotes#Changes in boot-time output on Ubuntu Server
Quote: "Changes in boot-time output on Ubuntu Server
With the introduction of plymouth, boot-time messages from startup scripts are no longer displayed above the login prompt on tty1. Instead, they are all output to tty7 and on Ubuntu Server, can be viewed after boot by pressing Alt+F7. On all systems the boot output can also be found in /var/log/boot.log.
[...] Hotkeys for interacting with mountall will still work without the splash screen, but are not discoverable: C to cancel a running fsck; M to request a maintenance shell; S to skip an unavailable mount; and F to try to fix errors found by a fsck."
I tried c, C, m, M and Ctrl-C with no result. Alt-F7 sends me to a different boot log than Alt-F1, but both do not reaction, still fsck-ing.
I have the impression that the checking is done absolutely in the background. (upstart?) Cannot get control of that process. In the foreground the boot process continued to the other disks (which are clean) but stops then, but no ctrl-c accepted. Also no loging consoles available (alt-f2,...), only boot logs.
EDIT4: Maybe this is related information: