Is it possible to run fsck on the root file system?
My Ubuntu 10.04 seems to be checking it's fs at boot...
It shows that the file system is in use and can get severely damaged!
Or the only possibility is to run it from a live CD?
I would like to know if there is a way to do an unattended check on the root file system on my servers, *and* send emails in case of errors.
I know you can schedule a root file system fsck during boot time - but the root file system will be mounted read-only - so if fsck finds any problems - it can't email away a warning, or write the result to a file - or can it?
Essentially I would like my servers to do a self-check of the root file system periodically - and to email me if it fails. I just can't think of a way to get it done.
Fsck is not check any file system which are not root file system at boot time.
Normally it run: /sbin/fsck -A -R -C -a
But this command doesn't do anything.
I've tried to strace it, and looks like this:
Code:
I've got a system that has given me problems since day one. It's my oldest kids computer and she seems to open about twenty tabs in Firefox. The computer will freeze and she'll manually hold down the switch to reset. I've instructed her to please stop shutting it down manually but kids never listen.So anyway the thing reboots into initramfs. Seems unable to do anything with the hard disk. Now heres where I run into problems. In the past I've removed the drive and put it into one of my other Ubuntu boxes then ran fsck. fsck always recovers the journel quickly and I pop it back in and all is well.First question or situation if you will. I have tried left and right to get fsck to work from the livecd. If I let the livecd boot up and open a terminal fsck /dev/sda1 comes back with device or resource busy. Apparently the livecd get stuck automounting and causes problems.
I'm really tired of putting this thing in another box. I tried downloading knoppix but it wouldn't burn off for some reason. I've tried booting into rescue mode, but that seems to be missing from the livecd these days?Can I boot into single user mode somehow? Kill off some process that is causing the resource to be busy? I'm thinking once I maybe flagged the drive as dirty and had it clean itself on reboot.. will the livecd pick up on that?ok.. so thats the first situation.. second is upon recently fsck doesn't fix the problem. The drive recovers just fine, but after using the computer for a short while the drive will somehow magically mount as read only.. and then programs will freeze and shutting down is hard to do.
I have a 2TB file-system and when the machine reboots it fails the fsck, halts and goes into maintenance mode.Stats: I have have RHEL 5, 2.6.18 kernel, the file-system is an ext3. The file-system is on an EMC AX4 connected with fiber channel HBA.So far my reading tells me this should work because under 2.6 4TB is OK. Any ideas why this fails?If I take it out of the fstab file and mount it manually the boot is OK and the file-system behaves well. I can change the fsck check option in the fstab to 0 but I don't think I should have too. Everything I read says that 2TB ext3 file-systems are OK.
View 5 Replies View RelatedI'm running an Acer Aspire 1830T-3721 dual-booting Windows 7 with Ubuntu 10.10 (Desktop).
Background: So first I dropped my laptop a couple feet while Windows was running. The laptop immediately shut off and then tried to boot. Booting Windows results in an unfortunate "Windows has encountered a problem communicating with a device connected to your computer. The error can be caused by ... faulty hardware ... Status: Oxc00000e9 Info: An unexpected I/O error has occurred." But Ubuntu booted fine, and could access my NTFS files fine, so I was trying to work on the problem from there. I try a few utilities, looking at the partition table, etc without actually applying any changes.
Then I run a fsck on the drive. It loudly warns me that if I continue on a mounted drive, then I'm going to mess things up. In a moment of stupidity I push on, thinking that surely it would ask me for more configuration, or confirmation, before actually starting. The fsck runs for about 1 second before I Ctrl-C it, running some preliminary stuff and then just starting pass 1.
After this, Ubuntu won't boot anymore. Instead, it hangs just after the init-bottom script runs. If I boot with init=/bin/bash, I can get to a shell, and see that my file system is still there, but not sure what else to do.
I've been running off of a SysRescCD LiveCD, from which I've looked at the drive with testdisk. Testdisk reports that "the hard disk seems too small" while showing me the partition table.
I ran a fsck on the Linux partition; it fixed a bunch of things. There has been no apparent effect on the boot behavior.
I can access all my files, back them up, and reinstall Ubuntu, but I'm hoping there's a better solution, perhaps one that will also help me repair my Windows installation (but I'm looking at one problem at a time here).
When I do a forced fsck, I would like to have a log file to look at after boot.
When I check /var/log/ there are no files there with fsck output
I've run force fsck in these ways:
shutdown -rF now
-and-
touch /forcefsck
I have Ubuntu 9.10 installed on my HP desktop, but I'm running an older version (8.10) on a live CD so I can at least get online to ask for some When I tried to log on earlier it went to a command prompt and said the 'file system check failed' and to run fsck manually. I entered 'sudo fsck' at the prompt and I selected "y" to fix all the bad inodes, when it was complete it told me to restart, I then entered 'sudo restart' at the prompt and it said 'sudo uuid unknown'. I have not installed anything recently and I'm not sure what to do.
View 3 Replies View Related16GB RAI've been running the Debian-based Proxmox VE on it for six months or so with no problems.Today I loaded Centos 5.5 x64. During a reboot, the file system crashed and fsck couldn't repair.I loaded it again, did all the updates, and loaded my applications. On about the third reboot, it crashed again and fsck couldn't fix it.I don't really know where to begin. I doubt seriously that any hardware has went bad since yesterday.
View 1 Replies View RelatedCan anybody tell me what kind of fsck errors are found on a system?
View 5 Replies View Relatedjust start Ubuntu 9.04 said: File system chek failed a long is beging saved /var/long/fsck/checkfs if that location is writable Please repair the file systmen manually A maintenance shell will now be started Ctr+ D terminate this shell and resume system boot. Give root password for maintenance or type Control +D to continue. I did Ctr+D , and after login said , that can not find /home. I starte with the live cd:
[Code]....
Can I do fsck on my root File system (/ ) from linux rescue on RHEL 5 ?
View 1 Replies View RelatedI work for a company that makes portable devices running Linux and I was recently asked to make the underlying file system read-only for "security" purposes. Since the distribution is based on LinuxFromScratch, I know that very little writing happens at run time. So, even if the device runs on a usb flash device, I doubt that putting the root file system RO will be that beneficial. I am actually more concerned about a process actually breaking because it cannot open a file in RW mode than a process going rogue and filling the root file system with log files, etc. I'd really like to ear what kind of advantages disadvantages there really is with read-only file-systems.
View 6 Replies View RelatedI got 2 HDDs, I had created LVM by two of them. When I was trying to install quota it was saying it is better if you run fsck first message. When I tried to run fsck. It warned me that I could lose some of my data. So it happened. Actually it is worse: I can't boot my Fedora 11. When I try to run installer in rescue mode, it says no linux partition find. When I try to install (just to see partitions) it shows LVM volumes of hdds are ok but the partition which is / (root)partition seems in unknown format. How can I save my datas? Or can i restore my partitions, LVM?
View 11 Replies View RelatedUPDATE: This is a bug: [URL] Evidently the problem is with plymouth because a workaround is to add "rd_NO_PLYMOUTH" to the kernel boot options. I don't get a prompt for my disk encyrption pass phrase---just a flashing cursor---but that's a small price to pay for being able to run fsck when the root filesystem wasn't umounted properly.
I have fully updated f13 (as of today) on a laptop with all ext2 file systems (It has nothing but flash memory.) If it's shut down without unmounting all file systems, it drops to a shell and asks for the root password to run fsck when it's rebooted. Every key press is treated as though it were <enter>, with a response to the effect that the password is incorrect.
I have pc/os linux 2009 installed and I recently got the following message while trying to boot up my system:
*checking root file system...fsck 1.41.4 (27-Jan-2009) dev/sda1 contains a file system with errors, check forced. /dev/sda1:Inodes that were part of a corrupted orphan linked list found. /dev/sda1:Unexpected inconsistency;run fsck manually. (i.e., without -a or -p options) fsck died with exit status 4
*An automatic file system check (fsck) of the root filesystem failed. A manual fsck must be performed, then the system restarted. The fsck should be performed in maintenance mode with the root filesystem mounted in read-only mode.
*The root filesystem is currently mounted in read-only mode. A maintenance shell will now be started. after performing system maintenance press Control-D to terminate the maintenance shell and restart the system.
Give root password for maintenance:
The problem is, when I enter my password I get an incorrect password prompt. How can I change my password so that a manual fsck can start? Why did this message error message appear in the first place?
We have a server for which the root password had been lost, and there were no other user accounts set up. Yesterday evening I attempted to reset the root password by booting from the install CD and using VI to clear the root password in the passwd and shadow files. I then rebooted, and the system has halted with an 'FSCK failed. Please repair manually and reboot' error, with a prompt to 'Enter root password' below. But of course the root password isn't known (I had expected it to blank after editing the passwd and shadow files, but it doesn't work), so I have no way of logging on.
View 6 Replies View RelatedTrying to install from netbootin...gives me that error.
View 4 Replies View RelatedI have been using Ubuntu 9.10 Desktop version for around 1 month then i stoped using after installing windows 7, as I knew that there were the 10.04 version coming. So when it was released i went to torrent download the file and burned it on a cd. After that i insert the cd and use the wubi installer in there as i want to install them side by side. so after installing ubuntu i restarted the system and got into it. After a few minutes it appeared this error message "Not root file system is defined. Please correct this from the partitioning menu." So i was expecting it to be downloading problems. I went on to ubuntu website requested for a CD and it came today. So i inserted the cd did the same thing again.
View 9 Replies View RelatedMy current installation setup has a separate partition for /, /boot, /home, /tmp, /usr, and /var. The problem I have is the root partition / is 98% full (4.3GB full). Cleaning temp files and log files won't help since they are on their own partition (and clean). I've removed all but two linux-images. Linux images seem to run at a size of roughly 105M. My root partition is 4.6GB. I can't seem to find any other options for cleaning up space on this partition. I have no idea what is taking up 4.6GB of space.
Disk Usage Analyzer has not been helpful since I have not been able to reconcile 4.6GB of memory with what it claims the total size of the remaining directories occupy. I've tried localepurge, gtkorphan, apt-get clean, apt-get autoclean, apt-get autoremove. I've removed all packages listed under Status -> Not Installed in the package manager. My root file system is still 98% full (4.3GB full).
Classic partition problem apparently. What do I do? the 11.04 wubi doesn't give a lot of installation options, so i just selected C drive, and gave it 10GB of space. instilled it, and when it goes to the desktop menu, that pop up appears saying No root file system is defined. Please correct this from the partitioning menu
In dual booting with XP. what do I do?
I'm trying to install 11.04 and get the error warning in the title. It says "Please correct this from the partitioning menu."How do I do that?I don't see any options for that.Puppy will already boot from that device and has grub installed.
View 9 Replies View RelatedI have had this problem since yesterday, I've looked around at previous archives, but I can't seem to find anything that works. When I boot up, the screen gives me the following prompt:
Code:
Mount of root filesystem failed.
A maintenance shel will now be started.
CONTROL-D will terminate this shell and reboot the system.
Give root password for maintenance:
[Code]....
So I have an external hard drive (wd passport) that I want to install ubuntu on. I created 100gb partition via diskutility (fat32) and it seems I can't install ubuntu on this partition.
View 3 Replies View RelatedI would like to start off by saying this: I am very new to Linux, and this is my first time installing it, therefor I am having some very newb-like issues. Please bear with me.I am currently at step five of the installation process of Ubuntu, and I clicked on the partition which I have set aside to install Ubuntu onto, but when I proceed by hitting forward, I get the following error message:"No root file system is defined.Please correct this from the partitioning menu."My question to the community is, how would I correct that? How do I turn my 20GB partition into the root file system?P.S. I searched the forum for this issue, and being that it sounds so simple, yet I found nothing about it being previously asked, I feel sort of dumb....
View 9 Replies View RelatedWhen I tried to install 10.10 'side by side' with 10.04 and OpenArtist for triple booting I get the messageQuote:No root file system is defined. Please correct this from the partitioning menu.I don't have the screen in front of me now but what5 does it want me to do and how do I do it?
View 9 Replies View RelatedI'm having a problem and it seems like partitions during the dual boot install.
Here's EXACTLY what I get...
Menu: Allocate drive space
Erase and use entire disk
X Specify partitions manually (advanced) [X denotes I chose this option]
I have 3 partitions on my gateway laptop...
[graphical bar across the top]
sda1 NTFS - 10g - weird partition w/recovery software or something from Vista
sda2 NTFS - 140g - Windows Vista
47g FREE SPACE [this is where I want ubuntu]
[Code].....
I click "Install Now" and I get this error:
"No root file system is defined. Please correct this from the partitioning menu."
I am running a RAID0 array, with Windows 7 Ultimate x64 installed.
When i install LL10.04 through Wubi, it installs fine, reboots, continues the installation procedure, then it gives me an error box "No root file system is defined".
I have attempted pressing the "OK" button 10 or 15 times, however it does not progress. The box just keeps on popping up. My only option is a hard reset.
I've tried downloading the latest version of Wubi from the official website, and allowing Wubi to download ubuntu itself, and still nothing.
I do not want to create a new partition for Ubuntu and use the GRUB loader. I have a multi boot system and would like to stick to the windows boot loader.
I have a 9.04 64bit Ubuntu server that I use for a home file server and for downloading duties, every few days the root filesystem gets remounted as read only, usually requiring a reboot and fsck to get everything running again. The box is tucked away in the roof space to keep the noise down so it's a bit of a pain to keep pulling it out to get console access.troubleshoot what might be causing this?/ is on a raid 1 array on 2 8GB usb sticks last few lines of DMESG EXT3-fs error (device md3): ext3_journal_start_sb: Detected aborted journal
Code:
[632280.290419] journal_bmap: journal block not found at offset 23180 on md3
[632280.290470] Aborting journal on device md3.
[code]....
I am pondering a reinstall of a freshly installed Ubuntu; I may or may not take that drastic step.However, I have partitioned my drive to include a 16-GB partition labelled "Ubuntu-tmp", in my case /dev/sda7, with the intent of mounting that file system as /tmp. Depending on how I decide to go about the reinstall I need an answer to these questions:If I reinstall: Is it possible to designate /dev/sda7 to mount as /tmp during the installation process?If I cannot designate the mounts at install time, or if I opt not to reinstall: I can't really empty the /tmp directory in the root in order to properly use it as a mount point for [the file system on] /dev/sda7; many files in there are still in use by running processes. So how can I clear the /-mounted /tmp directory and assign it to /dev/sda7?
I have attached a screen shot of gparted to illustrate my layout scheme.The gparted manual suggests I select the partition, click [Partition]->[Mount]. Of course, my gparted drops a menu with [Mount] is absent and an [Unmount] option is greyed out.This raises a question of how I am going to mount /users and /var in their intended file systems (/dev/sda8 and /dev/sda9, respectively), because the [partition] menu looks the same for these partitions as well.