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 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.
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 have a Rad Hat 7.0 old Linux system that crashed due to power failure. On reboot the system goes to Checking Root File System and does 92.5% check and fails.
Here are the error messages I get.
I don't know what to do at this point so I say yes and it goes in some wierd mode.
SO I ran fsck manually but I get an error PARALLEIZING FSCK.
I can't fix the corrupted stuff for the system to reboot. THIS IS VITAL.
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 don't think there is a way of doing this with date or clock commands. But maybe they are writing to some file and I can take a look at the file's modification time. dmesg and /var/log/messages show nothing relevant.
View 1 Replies View RelatedI need to enlarge the root file system on a Slackware 13.0 32-bit system; it's in a simple logical partition (/dev/sda6) -- no LVM, mirroring etc. This might be a good opportunity to change from ext4 to jfs, too.Routine procedure, no? No!First off I booted Knoppix 5.31 but found it doesn't have ext4 support (no efs2ck and running fsck results in "fsck.ext4: not found").So I booted Slackware 13.0 32-bit CD-1 only to get the same as with Knoppix.I do have a GParted-liveCD 0.3.4-11 but have had mixed experiences with it so am reluctant, despite having backups.
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 get the pinkish Ubuntu screen and a message such as "checking disk 1 of 4". I assume that it is doing an fsck. However, the time it takes does not seem to relate to the time it takes if I do a manual fsck (almost instantaneous) or fsck -c (several minutes to half an hour depending on the drive). I also wonder what is counts as a "disk". I have in the system:
sda1 - / 20 GB
sda2 - /home 10 GB
sda3 - swap 4 GB
sda4 - /data 115 GB
sdb1 - /quitelarge 750 GB
sdc1 - /veryhuge 1 TB
How can I change the automatic fsck execution at boot time to be above 30 boots? I reboot the system sometimes 3 to 4 times a day. Intel 3 GHz, tower, i386 lenny vmlinuz-2.6.31-686
View 2 Replies View RelatedI have switched recently from Ubuntu to Debian and overall I am enjoying it. However I was just wondering, does Debian, like Ubuntu check the filesystem at boot periodically or if damaged, because it is doing neither in my case? How do I get it to do this
View 6 Replies View RelatedI want to create a file in the /root directory and then make sure it exists. The following code keeps telling me that the file doesn't exist even though it does.
Code:
#!/bin/bash
echo -e "username=someusername
passwordsomepassword" | sudo tee /root/.credentials
if [ -e /root/.credentials ]; then
echo "File exists!"
[Code]...
[Edit] Added second double quotation mark at the end of "somepassword"
Got tired of long waits for fsck on very large partitions.Here's a script to fsck selected partitions every 'N' shutdowns. No more boot delays for fsck (unless something is really wrong
Update1: On my system '/usr/libexec/gam_server' (gamin component used by xfce) prevented /home from being unmounted. I changed
Code:
[code]...
After creating a new JFS root file system, boot (actually /etc/rc.d/rc.S ?) fails when checking it with:
Code:
fsck 1.41.8
/sbin/e2fsck: Bad magic number in super-block while trying to open /dev/sda7:
[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.
Started slackpkg upgrade-up and went to bed. Woke up to find the power had gone out during the night. The computer booted up, but displayed a message that said something to the effect of, "Error occurred during root file system check. You will be given the option of doing maintenance......"I can get to a command prompt, but regardless of what I do a message pops saying it can't find libblkid.so.1
View 14 Replies View RelatedWhen 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 am using Gentoo Linux and for a while now, the root file system is mounted read-only on booting. For obvious reasons, this is quite annoying as most services do not start up correctly (I do not use a separate file system for /var). After the system is up, I have to log in, remount the root file system read-write, fix /etc/mtab, mount all other file systems in from /etc/fstab and then start up all the missing daemons. I know that there are ways to make a system run properly with a read-only file system, but I would rather restore the old behaviour of a writable root file system.
The strange thing is that after running mount / -o remount,rw, the file system is mounted in writable mode without any errors. I suspected some problem with fsck, but now I have disabled automatic file system checks on the partition (tune2fs -c0 -i0).When I run dmesg, only these lines mention the partition at all, although I am not sure if not something gets lost because /var/log is not writable:
EXT3-fs (sda5): mounted filesystem with writeback data mode</code>
EXT3-fs (sda5): using internal journal
The line in /etc/fstab looks like this:
[code]....
I use Redhat 2 server, the server suddenly can't boot now , it goes to the grub> mode, it can't boot to Redhat kernel
View 5 Replies View RelatedI downloaded Go-OpenOffice from SlackBuilds.org, but I can't build it. make terminates with configure error: checking for C compiler default output file name. configure: error: in `/tmp/SBo/ooo-build-3.1.1.5': configure: error: C compiler cannot create executables See `config.log' for more details.
(I can't find config.log anywhere) I use a quite 'light' installation (no xap, ap), and I suspect that I have some unmet dependencies, but the error message provides no information about what software is needed (I've installed all dependencies listed on SlackBuilds.org). I'm using Slackware64-13 with Xfce
I'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).
16GB 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 RelatedI 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 RelatedI want to make sure that all my file systems and mounted points are OK during boot time. Which log file in Slackware shows such info?
View 3 Replies View RelatedIt looks,slackware is taking too much time to boot. It's starting daemons at boot time.
What are those daemons that i can stop at boot time to increase booting time?
What's the best way to stop starting daemons at boot time?
when i reboot my computer, it goes on well and loads Ubuntu but instead of it going to the login it doesn't. instead it begins checking the file system and then completely stops at
[Code]....
i am using ubuntu 8.1, please i love that ubuntu version and it's why i haven't upgraded yet because i have tried the other versions and i didn't really like them. i have a 40GB HD and 512MB RAM, 1.8GHZ processor, i am using pentium 4.
If you have a contiguous partial piece of an ext4 file system (assuming it's perfectly clean), starting from the beginning of the partition, is there any way to check it, or to mount it to get the files whose parents, inodes and data are all completely contained inside?
Have (or maybe had) a very large 11TB RAID 6 array, filled with a single large ext4 partition. Something strange happened when a single drive failed and the array ended up failing 13 out of the 11 drives. I had trouble getting the array restarted, and got to the point where I exhausted all of the options I considered completely safe. I considered a few things that may have worked, but mdadm doesn't seem to have a definite "do not change anything" option. So I decided the only way to be absolutely safe would be to clone the disks before proceeding - then I realized how much time that would take and sent the drives off to a recovery service so they could image them and check it out.
Before doing so, I copied the first 2GB from each disk. I XORd the images from the working drives to reconstruct the data chunks that were on the failed disk, manually assembled the chunks, and am very confident that I have 22GB of "correct" data in a single file. The parity and Q syndromes all matched (with RAID 6 you can still check with only 1 missing device). I've learned the fine details of ext4 from [URL], and have looked at lots of raw data from the reconstructed partition, and it all looks good. The recovery company says that they're not finding many inodes, but I found a lot of them, exactly where they're supposed to be. I tried to mount and e2fsk, but both processes seem to be extremely unhappy that the device size doesn't match the size implied by the file system geometry.
I considered hacking the superblock to manually reduce the size, but I figure that wouldn't work because there would then be more group descriptor blocks than it would expect after the superblocks. I might try doing that and compensating by incrementing the "reserve block count" to compensate. Alternatively, if there is some way to make the file appear to be the expected size with nothing but zeroes after the end of the actual data, maybe I could mount it and not get any errors until I cause the kernel to read past the true end of the file.
When booting Fedora 11, my system hangs for a very long time on starting udev. Sometimes I get an I/O error. However, my hardware is fine. I do eventually get in to the system.
View 7 Replies View RelatedCan anybody tell me what kind of fsck errors are found on a system?
View 5 Replies View RelatedEnvironment: A 32-bit kernel RHEL5.3 system running on a virtual machine. The root(/) filesystem is on an LV.
Issue: Unable to resize the FS after extending the root LV since it is mounted. After extending the LV, online resizing of the FS was not supported and the root filesystem could not be unmounted while it was in use. On rebooting, I got a kernel panic error. In runlevel 1, I couldn't run chroot, couldn't find the /etc/fstab, root FS could not be mounted, fsck did not run (tried block 31 for second copy of superblock using dd count=1 bs=4k skip=31 seek=1 if=/dev/sda2 of=/dev/sda2), couldn't find any rpm on installation media to install unix-utils rpm. On running commands in runlevel 1,
I got the following output.