my Fedora 12 does fsck on boot time to time and sometimes it's really annoying having to wait for the check to complete. In Linux Mint pressing <Esc> cancelled the check; however in Fedora this does not work (nor does Ctrl+C nor anything other I've tried). What is the key to cancel the check in Fedora?
View 11 Replies
I am very new to linux, and I have a question regarding the filesystem check (fsck). The power recently went out and when I tried to restart linux the following error appears:
*/dev/sda1 contains file system w/errors, check forced it then goes on to say..
*An error occured during the file system check. Dropping you to a shell; the system will reboot when you leave the shell. Give root password for maintenance (or type Control-D to continue) I wasn't sure what to do, but checked some other online forums and they suggested running fsck manually - so I typed in the root password - and used the command, "fsck -A -V ; echo == $? ==" it then gave the following message
*WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage
*Would you like to continue (y/n)
Again, I wasn't sure what to do so i just checked no. I then manually turned off the computer and was prompted at the beginning to press Alt-3. I was brought to another screen and it informed me one of the drives was degraded and suggested rebuilding the array. I tried doing this, but it still brings me back to the original error of, "/dev/sda1 contains file system w/errors, check forced," and the process continues.
Also, when I tried to rebuild the array, I didn't backup any of the data on our home directory before doing this (which was probably a big mistake). After being prompted to type the root password, I was able to give the ls command and look at all the directories...the home directory where our data was stored was empty and I am afraid I may have lost some information. Is there a possibility that data was lost when I was trying to rebuild using the old drives?
I did the "yum update" today, the process was doing well but, the follow error appears:
Transaction Check Error:
installing package kernel-PAEdebug-2.6.31.12-174.2.3.fc12.i686 needs 9MB on the /boot filesystem
Look:
Code:
Transaction Summary
==================================
Install 10 Package(s)
Upgrade 33 Package(s)
Remove 1 Package(s)
[code]....
i was recently trying to boot my fedora 12 installation of a usb device today when i went to boot it i enter my LUKS pasfrase and it stops with an error mesege:
Code:
***an error occured during the filesystem check
***droping you to a shell; the system will rebot
[code]...
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.
View 9 Replies View RelatedA few days ago I upgraded my debian sid system, and since then systemd does a filesystem check on every boot which takes over two minutes, disobeying the existing settings I had. How can I set systemd to do a filesystem check only once every a set number of mounts, like I had set up before the upgrade?
View 5 Replies View Relatedyou 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.
View 2 Replies View RelatedI'm a bit of a Linux newbie, but I did manage to set up the following RAID-5 system:1x 500GB system drive on ATA IDE4x 1TB SATA drives in software RAIDLinux = Fedora 13So here's what happened. I set up the system to send me an email every time the mdadm stat file changed, so it would send me emails when in periodically ran a self-test. I was away and noticed that the self-test was going incredibly slow (usually took 8 hours...was on course for taking 250 days!) A colleague decided to just reboot the system.Afterwards, the system would not boot and, while all 5 drives were connected, would stop at an endlessly scrolling error message of: Code: ata4.01: exception Emask 0x0 SErr 0x0 action 0x0
ata4.01: BMDMA stay 0x64
ata4.01: failed command: READ DMA
ata4.01: (a bunch of hex numbers)
[code]....
Right now I am trying to fix the problems on my server with daemons not starting.
So I have to try different solutions and reboot.
The problem is that after 28 reboots, fsck kicks in and decides to check 2 TB of data.
Is there a way to cancel this???
It takes forever, and by the time it will be done, I will have forgotten what I was testing.
The issue of daemons not starting becomes even more frustrating when fsck decides that I must take a half an hour break.
So again, how do I cancel the fsck on Ubuntu Server?
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....
View 2 Replies View RelatedWhen I installed Debian stable on a headless machine of mine, I configured a partition with LUKS encryption (intended for swap), but told the installer not to use it. After installation, I configured that encrypted partition as swap and mounted it. I wanted my headless machine to boot all the way without manual intervention, so I can log in via ssh and mount my encrypted partitions.However, since the kernel was updated (and the initrd regenerated), the machine now waits during boot for me to enter the swap encryption password, but no others, only the swap.I have been unable to find in my searchings how the initrd is generated with that setting or how I can change it, preferably permanently so future regenerated initrd's don't try activating my encrypted swap on boot. Does anyone know how to configure a Debian style initrd generator to generate an initrd that will not try to activate swap?
View 9 Replies View RelatedI have got arch Linux dual booting with Win XP on my laptop. I have been getting a filesystem check error since yesterday and am unable to start Arch. Upon googling and searching the arch fora, I came upon some advice which I tried which has not worked yet. Hence the new post.Basically, I was attempting to print something off and accidentally chose a printer that was not connected to my laptop. After half a minute or so, it repeatedly started giving me notifications that the printer was not connected...in excess of 200 messages that the printer was not working which continued to pop up despite me canceling the print job. The whole system got really sluggish (for the first time in the last year) and I had to restart the laptop upon which the boot messages appear. It gets to the point where its loading the various filesystems. It mounts root and says it fine.
I tried fsck which tells me that home and boot are still mounted.So I booted up using an Ubuntu Live CD and checked and repaired each file system which it successfully did. Upon rebooting into Arch, I am getting the same message.I have not installed anything new and had upgraded the whole system a few days before the problem started.
Code:
fsck from util-linux-ng 2.17.2
e2fsck 1.41.11 (14-Mar-2010)
/dev/sda1 is mounted.
WARNING!!! The filesystem is mounted. If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.
Do you really want to continue (y/n)?
I don't want to cause damage, but I'd rather not go into BIOS.
write a script that will check all filesystems to see if they are read-only.
I have come up with ...
df -h > /tmp/mount.lst
awk '{print $6}' /tmp/mount.lst > /tmp/mounted_systems.lst
This gives me ..
Mounted
/
/boot
/dev/shm
/proc
So now I have ..
How do I automatically get rid of the 'Mounted' header in my /tmp/mounted_systems.lst file ?
Also, I don't want to check the /proc filesystem, so how do I remove that within the script too.
Then I will run ...
while read dir
do
touch $dir/read_only_test
done < /tmp/mounted_systems.lst
If the filesystem is read only, I want that filesystem name to be listed into another file.
how can I disable the automatic file system check after power outages or system crashes? The check sometimes prompts for a key (ignore, repair etc.) but the panels do not have a keyboard.
View 9 Replies View RelatedI'm not a complete newb, or a seasoned hacker. I can't figure out what's up with this, I keep getting this message when I try to apply updates. [('installing package kernel-2.6.35.12-88.fc14.i686 needs 17MB on the /boot filesystem', (9, '/boot', 16985088L))]
View 6 Replies View RelatedI just noticed that there is an icon on my desktop that is named Filesystem, it is the Windows XP portion of the hard drive. I don't remember seeing it on the desktop, I only noticed it 15 minutes ago after installing Adobe flash player. Is that icon supposed to be on my Fedora desktop?
View 6 Replies View RelatedThis is a Natty system. I ran update manager to update to the latest releases for Natty, and it crashed. I ran it again and it told me it could only do a partial upgrade, and that I should do apt-get install -f. I did that, but apt-get told me the system was locked by another program. Not to worry I thought, I'll just reboot. So I did that, and I think Update-Manager got a lot further through the process than I thought, because my system is borked. It'll boot into Gnome, but when booting up the Boot Screen no longer shows the pretty Ubuntu Logo, but rather a line of text that says "Ubuntu 11.04".
When it gets into Gnome the keyboard and mouse more or less don't work (although the keyboard based Fn+9 and Fn+10 brightness control still works) and there is no desktop background. After about 30 seconds something crashes but I can't click on it to find out what. Going into the recovery console doesn't help either. The latest Kernel (2.6.38-7) stops moving forwards after "Begin:Running /scripts/init-bottom...done". has occurred for the second time. Luckily I still have the previous kernel, which gets to the same spot and then tells me:
"init: udevtrigger main process (390) terminated with status 1" and then "init: udevtrigger post-stop process (394) terminated with status 1".
I then get the message
"The disc drive for / is not ready yet or not present. Continue to wait; or Press S to skip mounting or M for manual recovery". S goes back to "Begin:Running /scripts/init-bottom...done" a second time, M brings up the message:
"Root filesystem check failed. A maintenance shell will now be started"
and then it asks for the root password and gives me a terminal. Everything seems to be there, but apt-get and dpkg both can't do anything as the filesystem is read only.
My Fedora 12 System was failed when booting.The message like that : mount: wrong fs type, bad option, bad superblock on /dev/mapper/my_vol missing codepage or helper program, or other error. In some case, useful info is found in syslog - try dmesg | tail or so Can't mount at root filesystem. [drm: drm_mode_rmfb ] *ERROR* tried to remove a fb that we didn't own. Boot has failed, sleep forever. I guess something wrong with my hard disk, so the bootloader can't recognize the filesystem type.
View 2 Replies View RelatedI'm trying to partition/format a new external hard disk for backup and have run into a snag that now prevents my computer from booting. In the description below of what happened please bear with me as I do my best to remember the commands and screen output (which for obvious reasons I don't have in front of me).As root.The disk was subsequently writable. However, I then realized that the default start and end cylinders had resulted in a very small partition apparently occupying some free cyclinders in the beginning of the disk.
So next I ran fdisk again, deleting the sdc4 I had just created and creating a new one instead, this time using the cylinders at the end of the disk. When I exited fdisk I got a message something like that the new tables can only be read upon a subsequent reboot. I ran mkfs again, but not e2label. Indeed using /sbin/fdisk -l, sdc4 still had the small size as defined initially. So I rebooted.
Now when it comes up I get something like "checking filesystems. fchk.ext3: can't resolve 'LABEL=/media/LaCie2TB1'" and am prompted to login as root to correct. I tried to simply delete sdc4 again but that didn't help. I also tried to edit /etc/fstab (using vi, which I don't know at all) but it kept telling me that this is a read only file, even though permissions are rw for root.Can anyone out there help me so that (1) I can boot into my computer, and (2) I can correctly partition and format the hard drive??
In Fedora 13 64 bit, Ctrl+C does not terminate the running programing in terminal window but in Unbuntu this shortcut key works. If I hit Ctrl+Z, this makes the running program run in background which is something I definitely dont want. what is the shortcut for terminating a program in terminal window? What is the shortcut key for canceling the command I have typed but not run yet no matter where the cursor is in the command ? Ctrl+U works but only if cursor is at the last character of the command.
View 8 Replies View RelatedHaving a little issue with creating a login message banner in RHEL6 that uses two buttons. One for Accept which logs the user in. The second for Cancel which immediately logs the user out. I've modified the /etc/gdm/PostLogin/Default file to have the script, posted below, and it worked perfectly fine in RHEL5. But in 6, when you click Cancel, the user is still able to log in. It even states in the system logs that the user cancelled the login.As you can see, I have the script using the 9th field of the user's env to get the PID, and using the kill command to end the process, which should be logging the user out right away if they click the Cancel button. This works in 5 without issue (though I used -f5 in RHEL5, had to move it to -f9 for RHEL6).
View 4 Replies View RelatedI've downloaded Fedora 12 and decided to try and install it on my old laptop which is currently running Ubuntu 9.10 with no problems.
When I boot from the live cd, it starts to load with the 3 bars on the bottom, one on top of the other, one is white, one is dark blue, the other is in between those colours in the spectrum somewhere....
Anyway, the load bars complete and "Fedora 12" turns white, then the following output populates:
mount: unknown filesystem type 'DM_Snapshot_Cow' (<----- repeated a bunch of times) can't mount root filesystem Boot has failed, sleeping forever.
i am trying to compile kernel 2.6.23 on Fedora 12 After fixing a few bugs (getline error, %dil ,etc) i was able to compile the kernel made initramfs img using dracut updated grub and then booted up the new kernel 2.6.23 but it fails to boot with following error mount: unknown filesystem type 'ext4'
View 8 Replies View RelatedWhat 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 am running Fedora 13 in VMWare. I tried doing a software update and I get this error message when tring to install the updated kernel:
Test Transaction Errors: installing package kernel-PAE-2.6.33.6-147.fc13.i686 needs 6MB on the /boot filesystem
how to increase the memory space required for installation.
G'day. My distro is Fedora 13. I received the above subject error message at boot. My /etc/fstab is attached as follow:
#
# /etc/fstab
# Created by anaconda on Fri Mar 5 12:44:10 2010
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
[code].....
I have lost my ability in KDE Menus to do a shutdown or restart. My only option is to logoff or cancel. This started occurring about 2 weeks ago, possibly 2 KDE workspace updates ago. I have been assuming it would get fixed with an update but so far it has not.
I am running Fedora 10 x86_64, kernel = 2.6.27.7-134.fc10.x86_64, and the KDE version is:
kde-filesystem.noarch 4-20.fc10 installed
kde-settings.noarch 4.1-4.20081031svn.fc10 installed
kde-settings-kdm.noarch 4.1-4.20081031svn.fc10 installed
code....
I have 3 different systems all running the same OS and KDE versions and it is happening on all 3 systems. All systems have the "Offer Shutdown Options" selected in Session Manager. I have even turned this option off, rebooted, and then back on to try to jumpstart it but that did not work.
Additionally, I have tried deleting the contents of the /tmp directory while in single-user mode and also the .kde under my home directory. This made no difference.
Another symptom I am noticing is that any desktop widgets that I create all get moved to the upper left-hand corner of the display whenever I reboot and log back in. Any extra shortcut widgets that I add to the panel are also gone the next time I log in.
Again, these same symptoms are occurring on 3 different machines.
These symptom do not occur after a fresh install of FC 10. It is breaking during one of the yum updates but I have not narrowed it down yet as to which update is causing this to happen.
I edited /etc/fstab and after that the computer won't boot up. I got as far as (Repair filesystem) 32 #mount -w -o -remount / and it says already mounted or busy. I type (Repair filesystem) 32 #mount And it looks like all mount points are (rw) I try to edit /etc/fstab but when I save it I get told that the filesystem is READ ONLY.
View 4 Replies View Relatedmy partitioning layout was as follows
Vista Recovery
Windows 7
GRUB
Extended
-->Fedora 12 (ext4)
so, I shrunk my recovery in Windows 7 successfully, and booted into my Fedora 12 live cd to run Gparted, and move the partitions so that the free space could go towards fedora, I did such, and then I couldn't expand the partition to my dismay. Next, I woke up this morning, tried to boot to fedora to run SSH, grub loaded, but when I tried to boot fedora, I got the "File system check failed" error, and when I tried 7, it just went to a blank screen with a single "_" in the top left-hand corner.
