Ubuntu :: How To Stop Disk Check Every Time On Boot Up
Dec 19, 2010
Every time I boot up I have to go through a disk check and then restart, how do I stop it from happening? When the disk checks happening I press escape and it usually says its deleted inode something because it has zero Dtime or some thing similar and also a paragraph of repeated lines saying something like all system files need alsa base.cnfg it will be ignored in a future release then the disk check completes and it restarts and is fine then, also sometimes it says dev/sda5 (my ubuntu partition) was not cleanly unmounted check forces. Is their a way to stop this happening as it ends up taking ages just to login.
When I start the computer I receive the message that the drive that contains the /home partition has an error. If I press "F" the screen says that the drive is no ready, that I can wait, cancel or manually recovery. If I wait, in about 1 minute, the system starts normally. If I press "M" to repair manually, then I press fsck to repair the disk and apparently repairs the disk. But everytime I start (power on) the computer, Ubuntu always checks the disk and gives a dialog where I can: press F to attempt to fix the errors, I to ignore, S to skip mounting or M for manual recovery
I'm very new to linux and running debian 4.0. On boot got an error:
I did a ghost image of drive before I do any more damage and when performing the ghost, ghost stated I need to run fsck. I created the image and noticed that a lot of folders were missing (bin, boot and others).
1. How do I run check disk from an boot disk? 2. Is there something else I should consider?
What are others' views and experience regarding automatically checking filesystems (running fsck) at boot time?To be more clear, I have left the ext3 filesystems on this machine set to require checking after a fixed number of mounts by using tune2fs with the '-c' option. I've done this mainly because of the following (from the tune2fs man page):
Code:Youshould strongly consider the consequences of disabling mount-count-dependentchecking entirely. Bad disk drives, cables, memory, and kernel bugs could all corrupta filesystem without marking the filesystem dirty or in error.e using journalingon your filesystem, your filesystem will never be marked dirty, so it will not normallybe checked. A filesystem error detected by the kernel will still force an fsck on the nextreboot, but it may already be too late to prevent data loss at that pointBut what does anyone else do? Is there really much risk to disabling this automatic checking
I have updated from Karmic to Lucid not long ago, and everything went smooth and my system is been working like a charm for about a month. And it still does, with the only issue being that every time I restart my system, one of my partitions is checked.
My disk is split into 4 partitions: sda1, NTFS for windows sda2, ext4 for "/" sda3, ext2 for /home sda4, swap
Now what seems to happen is that sda3 is being marked as "not clean" on every shutdown, which makes me assume that is not being umounted at all.
I've been reading logs, commenting network drives out on fstab.. nothing does the trick.
I've booted into single mode and run e2fsck (which doesn't find anything wrong, and marks the FS as "clean") and then rebooted. The result is: if the FS wasn't mounted when I restart, then I get a clean boot once, but it is checked on the following one; if it was mounted then it is again checked at start-up.
Again, all points to the problem being that the FS is not cleanly umounted on shut-down.
I could not find any log with info of the processes killed and FS umounted at shut-down, so if anybody knows where to look, it could be a good start.
I applying changes through update manager in ubuntu 10.04 then my computer froze. So I had to restart it manually. Now I can't boot ubuntu normal or recovery mode.I get an error message saying 'the disk drive / is not ready yet or blah blah'.I don't have a livecd to fix it this with... but here is my 'cat /etc/fstab' relevant output
I have a custom modified Ubuntu LiveCD. Sometimes when I boot from the CD, after it detects the HDDs it starts automatically scanning and repairing them even if the partitions are windows partitions. What do I need to modify to make it not scan/repair any partitions/drives at boot?
you can refer to this ubuntu thread for context, but i'll sum up what i'm trying to do here to spare the reading. basically i want to be able to schedule a filesystem check with automatic repairs at the next boot time. but i'm not sure if this will try to automatically fix errors which is what i want to do. the reason i want to do this is because i experienced a power outage (the machine was not plugged into an UPS) and i want to make sure everything is ok.
These days I see the disk check that is popping up when my Ubuntu is booting up quite frequently. It says 'press C to cancel' but C (or Shift C or CTRL C or CTRL ALT C) does not have any effect. Pressing CTRL+ALT+DELETE reboots but again ends up in the vicious loop of disk check. How to bypass it? When I need to critically enter the desktop for an urgent pressing info waiting for 20 to 25 minutes disk check is kind of difficult.
i'm trying to get everything working ok. i have installed ubuntu using wubi and i've found that i can access my files on my windows partition from ubuntu. to do this i have to mount the disk and enter the password each time i boot up, and i would like this to be done automatically. i was wondering if this was possible? i put in a link directly to the music folder on windows into my 'places' but it only appears once i have put the password in. its not a huge thing, but its one of those things which would make starting up my ubuntu a lot more conveniant.
I'm using Fedora 12 since 2 years lately, I really enjoy this S.O., it's quite robust and wonderful, but a couple of months ago it is really slow to boot up when startup the computer, I've checked everything, but seems to be ok, I had a partition lost arround that date, but recover successfully, it happens when I run gparted that It cannot see partition on my 500 GB disk, but still boots up. When running Mandriva live cd, it can see (?) all partitions on that disk, even with Fedora Dolphin I can access this partitions. What could it be?
My laptop boot up time increased considerably (10 seconds) after allocating a virtual drive for virtualbox guest. The guest installation did not work so i removed it along with the virtual disk. Now everytime when i boot to ubuntu, after inputting my password in the login screen, it takes much longer to load the system. And during the loading time the disk activity indicator light blinks indicating the harddisk is actually busy loading the system.
I decided to search around for a possible answer and force reprofiling ureadahead does the trick Now boot time is back to what it used to be
as far as i know Debian "Squeeze" has a disk check utility, but you can't run this on a mounted filesystem. Is there a way to trigger this during boot (before filesystem is mounted) ? I can run this once a month to keep filesystem healthy....
I think I selected the wrong time during the installation and now at the top right corner, my time keeps changing back to one hour ahead. Not sure why.I've went into the Preferences of the Time/Date > Time Settings > and set an hour back manually. I check back in 30-45 minutes, it's back another hour ahead. I'm on a Dell Inspiron 1545.
i recently switched to ubuntu 9.10 from win vista, i am having a problem... in ubuntu when ever i do any changes it asks me for my password, i know that its for my own PC's securiety but now i am really annoyed with this.
I recently bought a Shuttle XS-35 Mini-Barebone-PC and filled it with a 2GB Corsair RAM and a 1 TB WD Scorpion Blue Drive.After assembling all the parts I simply wanted to install Ubuntu but it simply doesn't work. However then I had the idea it would be good to kinda get the drive to a completely clean state and used the tools to safely wipe the whole HDD (by writing zeros everywhere as the tool tells me). The tool ran good for around 30 minutes but suddenly the write speed showing in the console window would go down to 0B/s (meaning basically nothing at all I suppose). I tried it 2 more times and it always came to a halt at the 10-20GB mark.
So this lead me to belief that that is also the problem while installing, that my drive doesn't want to wark anymore but rather just sleep a bit.What could be the problem? Is it a hardware error? Is there some linux system setting that could whip my HDD whenever it gets lazy? Did I do something else wrong?
I'm trying to develop a system that records different desktops at the same time. I have developed a audio-videochat system and I want to be able to record what happens in every room, so my starting idea was:
1) Open a graphic terminal for each room. I have succeeded using vncserver :NumberDisplay. 2) In each terminal, run firefox at each URL. I succeeded too because firefox lets me specify in wich NumberDisplay I want it to be open 3) In each terminal, run recordmydesktop to record. It allows too to specify the NumberDisplay.
My problem now is that it seems that the sound card is "shared", so the sounds recorded in the display 1 includes the sound generated in all others firefox windows. I havnt found an analogy for the sound as the display is for the graphics.
I have thought some ideas but I havnt been able to materialize anyone. Im tried to create virtual sound cards and specify one for each vncserver, I tried to redirect the sound of each firefox window to one "channel" (read firefox delegates the sound so that might not be an option), I read many things about pulseaudio, jack and several stuff that I just havnt been able to work.
I was using Terminal and browsing a directory in my home folder. My "home" directory is located on "/dev/sdb1". When in Terminal I typed "ls" in one of my directories and the output was garbage. The output didn't show the files in the directory. I think it said something like, "input/output error". Unfortunately, I didn't write the exact error down. Instead I rebooted.The hard disk with the problem is:
Code: $ sudo hdparm -I /dev/sdb [sudo] password for brian: