Ubuntu :: File System Check Failed A Long Is Being Saved /var/long/fsck/checkfs
Jan 9, 2010
just 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:
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.
I have created a CD-Rom with pictures with long file names, up to 120 characters, using Brasero disk burner supplied with Ubu 10.10. I need Win XP to accept the long file names from the CD made in Ubuntu without truncating them. The WinXP HD is formatted NTFS.1) When I look at the CD made in Ubuntu with long file names,in Win XP, it shows the file names only in the 8.3 (DOS) format. When I open in Irfanview, the file names are also truncated. 2) When I email the pictures (with long file names) from Ubuntu and accept in XP, the photo file names (long) are seen unaltered. They can be stored, managed and used by viewing applications with the long file names.note: in XP, a short file name for a photo can be made to be very long, say 150 characters, and there seems to be no problem in manipulating it or viewing it
I have SLES10-SP3 running on an Intel SR1600URHS board with 3 hot-swap SATA disks configured using mdadm as Raid1 with hot spare. If I pull one of the active disks, all file i/o will stop for about 2.5 minutes after which it will start again and the raid array will be rebuilt using the spare disk. Is there any way I can reduce this 2.5 minutes of inactivity? I've tried setting /sys/block/sdX/device/timeout and /sys/block/sdX/device/retries to 1 for all disks, but this hasn't made any difference. The output from messages is:
12:11:56: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen 12:11:56: ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x1e data 0 12:11:56: res 40/00:03:00:00:20/00:00:00:00:00/b0 Emask 0x4 (timeout)
I am running Centos 5.3. I ran no updates, performed no installs, nor changed any configuration immediately prior to this issue. My problem is this: when I run the command startx (default runlevel 3), it is a long time (5-10 minutes) before Gnome startx, and once it does start applications will not run. Also, when I try to use sudo (from any environment, even ssh), it is a long time (5-10) before the command is executed.
I cannot say for sure, but it seems like this is an intermittent problem. Sometimes X takes a long time to start, but once it starts it will launch programs. Sometimes X takes a long time to launch, but once it starts it will only launch certain programs. Though presently X always takes a long time to start, and I cannot successfully launch any programs.
A while back a had a similar problem to this (x taking long time to start, sudo taking long time to execute) and it ended up being a DNS problem. Unfortunately, I cannot remember exactly what it was and I stupidly did not document it. Maybe this is also DNS related, I don't know.
I don't know what log files to look at for problems with X, Gnome, and sudo taking a long time to start.
I've been stupid, and used kleansweep, which deleted a load of files and in the process killed everything. When I boot I get "file system check failed". Then it gives me a command prompt. I really don't want to have to reinstall ubuntu as I have a lot of stuff installed on it.
I have a Hp Netbook, and my friend installed Ubuntu to my computer. Everything was going fine, until one day my battery died while I was searching the web. I turned it back on and It started checking files and then it took me to a black screen with white letters saying "File System check failed".
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.
My hard drive all of a sudden starts to read and write all on its own for around 15 seconds at a time while at idle or while I am just browsing the net. At first I thought it was from cron running but I have that disabled.
I changed to the kde desktop environment. I logged in as a normal user, and left the computer running for a few hours. when I came back the screen was turned off and the system does not respond to mouse movement, pressing the keyboard, or any combination thereof. I tried
Code: Select allCtr+Alt+F1, CapsLock
First time i touched keyboard the led of numlock turned off, and never back. Blanking the screen itself does not cause a system crash, this occurs after several hours of inactivity.
.xsession-errors Code: Select all/etc/gdm3/Xsession: Beginning session setup... localuser:bartek being added to access control list openConnection: connect: Nie ma takiego pliku ani katalogu cannot connect to brltty at :0 Failed to connect to the VirtualBox kernel service
I have a newly installed Kubuntu 10.04 running here, works fine except for one thing.
I have a kind of "fileserver" and it has a samba share that I have mounted in the home folder of my desktop computer ("/home/xxx/fileserver", the server is running an older version of Ubuntu, can't exactly remember what it is but the filesystem is ext2, if that's of any importance).
I have large files on the server, mostly video. When I use Dolphin (or Konqueror, doesn't make any difference) and right click one of these large files and choose Properties, it takes a LONG time to load the properties window. As if it copies the file to local hd before opening properties, or something.
The reason why I posted here and not in the networking section is, that I had the exact same setup with my previous installation which was Kubuntu 8.04, and also at least three different Ubuntu's before that. Never had this problem before, so I think my server and networking thingies are okay.
I need to make an ISO9660 file from a directory, but some of the files have names that are logner than 37 characters. I could not find a way to get the long names preserved. I've tried various ways but in vain. "genisoimage -J -R -U -max-iso9660-names -o tst.iso cdroot" gets most close to the end, but not close enough!
I'm trying to do a find /photos/* -type f -mtime +365 to find all my pictures that are over a year old, but I keep getting argument list too long. How can I view what all the results are, even if it just dumps it to a file that I have to open?
For reasons I won't get into, I need to copy directories so long as the average system load is low. Can someone help me write a BASH script that will copy the contents of a directory, but check to make sure the average system load is below X before copying each file, and if not, wait Y seconds and try again?
I need to delete all *.trc files that are older than 30 days and I am getting a "Argument list too long" error. There are other files that should not be deleted which is why I am using the "*.trc" and newer files need to be kept as well. I have seen other postings but they do not cover both of the conditions. Below are 2 of the many attempts at doing this but I cannot get this to work.
Problems with Bluetooth. The dongle appears to be working, but then it craps out on me after only a few minutes!
I'm using the blueman-manager GUI to connect to my cell phone. If I load blueman-manager almost immediately after connecting my dongle, I can use it for a few minutes, but only long enough to add my phone, pair it and mark it as trusted. Certainly not long enough to send or receive a single file, though. Eventually and inevitably, the connection breaks, blueman-manager hangs/freezes up, and I start getting errors in dmesg.
Here's all the relevant diagnostic stuff...
I added the MARK myself to separate where the dmesg output stops immediately after plugging in the dongle from what appears after the connection is broken. It's right when that timeout error happens that the connection severs itself, and the error usually repeats itself several times.
Even if I just connect the dongle and not do anything except wait a few minutes, after a few minutes that timeout error will still happen. I'm running fluxbox and I don't believe I have any automounting programs, so there wouldn't be any interference from something like that.
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'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 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.
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.
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).