Ubuntu :: Each Time Start The Computer - Have To Check The Disk
May 19, 2011
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
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 my computer sometimes I get an error that my floppy drive isn't working and the boot process is halted. So I disabled the floppy disk seek. But Once in a while (sometimes almost every time I start) the BIOS settings are reset and I have to disable floppy disk seek and reorder boot device list again. I have checked the battery and it's fine. What else can be the problem?
For like windows you can resore your os to a state of peace kind of. If you messed up your vital files you could go back in time and restore you computer to a selected time. I was wondering if you could do that for ubuntu
My computer has different time when booting to linux or Windows.How to make the time the same?My computer time is 10:57pm Apr 14 when booting to linux.My computer time is 2:57am Apr 14 when booting to Windows Vista Home Premimum SP2.Both OS are set to the same time zone (GMT-5. Eastern Time US & Canada).
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?
I did a clean install of Ubuntu 11.04 64bit and the start up time is abnormally slow. If I start up the computer and don't press anything, the start up time is 30 minutes but it usually doesn't start up at all. It just boots into a purple screen, no splash, then it sits there and the computer doesn't have any loading lights flashing.
I had a similar problem with 10.10, but I assumed it would go away when I did a clean install of 11.04.
I can't get a read out of what's going wrong because when I press Esc it doesn't display anything, though weirdly it can sometimes get the start up process moving. I have also found that pressing enter really fast can sometimes help and something that seems completely oxymoronic, if I press the power button while it's starting up that can make it work, but nothing works every time.
I'm trying to find how to schedule a process to start at a specific time (not on start up). How would I schedule a process/application to start at a specific time (if it matters, it will be a background process). For instance, have process abc start every weekday at 5am. I've done this for windows many times though have only been using linux regularly for a few months and haven't figured out the best way of doing this.
So far the best solution I have is to create a program that will start on boot and have it check the time and sleep until the required time and then start the required process(es) at the required time(s). But this seems more of a hack since I'd expect there to be a proper way of doing this.
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:
This has probably been answered elsewhere, but I could not see it - how can I check which version of Ubunbtu I have installed and whether it is 32 or 64 bit?
I suspect one of my hard disks is faulty and I need to run a check on them. I have seen the documentation about 'e2fsck' but this states that this is unsafe if the filesystem is mounted. Unfortunately the device in question mounted on the root filesystem, so unmounting it is likely to create problems.
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 a machine that experienced some troubles with some of the real time stuff that I'm running. One lead that I have is that NTP daemon may have moved the time, causing false timeouts.
How do I find out if NTP daemon did indeed move time at all? Any logs? I do see NTP daemon restart in /var/log/messages, but I don't know if time adjustment should be there as well. to clarify: I need to understand it from the logs, after the event. May be 2 days after the time was adjusted. Running commands to see the current status doesn't help.
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.
Ubuntu has got this build-in check for errors which starts every 30 startups (if I remember well ) but my one gone missing... Strange. How can I turn it back on ?ound in the forum some information about Bonager, but is this original automatic disk check software shipped with Ubuntu or another piece of software ?
my comp hangs when disk check reaches 91% and pressing C to cancel does nothing. from irc-#ubuntu i was given this "sudo tune2fs -c 0" to cancel all future disk checking but it did not work. my drive is 2 months old.
I had it in mind that Ubuntu ran disk checks every 30 boots, but mine are more frequent - running between 10 & 25, which is an irritation. Records show checks after: 12-21-10-20-10-20-13-25-16-21 boots. Should I worry about either the frequency or the variability? I found threads suggesting how to change the frequency using tune2fs, so I suppose I can try that to stretch the interval to maybe 50 or weekly? Will it have any effect, since there is so much variation already? Is there a GUI for setting this frequency, instead of fiddling in terminal?
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?
It frozen up occasionally, when that happens, usually the harddisk light lights up continuously. So I suspect some process is writing to the disk, which prevent other process to go on. how do I find out who's using a lot of IO?
want to know enable 32-bit IO-support on my hard driveusing hdparm . But before I enable 32-bit support , I want to knowwhether my hard drive supports 32-bit IO or not. I tried the -I option with hdparm , but it is not telling clearlywhether it supports 32-bit or not. The following is the output from the hard drive of my system (hdparm -I ) .
I am dual booting XP and ubuntu, and everytime i want to go to XP through GRUB, and every time a Windows Disk Check apears. How can i stop this? I've set my hard drive partions to 50/50 (20GB on each side)so could that be the problem?
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.
I'm trying to check my server's bandwidth usage in real time, installed the following programs but none worked so far.
Iptraf - No results even when using iptraf -u Tcptrack - Error : pcap_loop: cooked-mode frame doesn't have room for sll header Iftop - No results, everything 0b
Are there any programs that displays bandwidth usage in real time and actually works on VPSes? Or getting real time bandwidth usage on a VPS is simply impossible?
