I have a problem, my filesystem seems to show random corruption. For example:
[Code]....
This has happened to many files, they suddenly contain random garbage. Fsck seems to say the filesystem contains no errors I tried to run it multiple times.
I have a problem, my filesystem seems to show random corruption. For example:
[code]...
This has happened to many files, they suddenly contain random garbage. Fsck seems to say the filesystem contains no errors I tried to run it multiple times.
So I built a new system few months to act as a development/"mess around with" server with an Asus Mobo and a Q6600 processor and 8 gigs of ram. Along with file, web and app hosting, I also do some virtualization on it... or atleast I had hoped to.
Ever since the first install, I've been randomly getting crashes and lockups. Sometimes it would just dump an error to the screen but stay alive, and sometimes it would dump an error and then lock up fully. The error mentions something about "kernel not tainted" etc. I will post the detailed error once it comes up again, as I have just formatted it again.
Other problems include downloaded files becoming corrupt. Files downloaded through any means (wget, torrents, ssh, ftp etc.) seem to randomly get corrupted (ie: the hashes are wrong).
I currently have one WD 150GB raptor as my primary OS partition, and 3 WD 1TB greens as my storage in an mdadm raid 5 array. At first, I had thought it was the raid array or it's drives causing issues. After painfully transfering the data off of it, I took the drives out and tried to run ubuntu with just the OS drive for a while. This still had the same issues. I then put in only one of the 1TB greens and had the same issue...
I downloaded WD's hardware diagnostic tool and ran full scans on all the drives. They all check out fine.
I left memtest running overnight and it had no errors either.
Most recently, ubuntu would not even install. It would get stuck at the stage of partitioning, and the keyboard lights would flash. After much googling, I tried popping in "noapic nolapic" to the end of the grub string, and it managed to install.
Now, I'm in a fresh system and just wgetted vmware server. However, it wont untar, I just realized the MD5 hash doesn't match!
So definately not the memory or the hds... I'm assuming it has to do with the APIC? From what I found on google, it seems as though this is only needed for the install.
Do I really need this to be on the boot string too? From what I understand, APIC allows processes to be divided out to the least loaded CPU. Having a quad core, I'd rather leave this on since it seems somewhat beneficial... I have yet to try putting this into the grub yet since I'm offsite and need
As a side note, this latest install is using just the WD Raptor as an OS drive.
And I'll post up the dumped errors if I get them again. There were none dumped out when the vmware download corrupted. The message format is very similar to the one here: [url
However, sometimes it mentions ext3 (or one of the other filesystem types I had tried with thinking it was a problem with ext3) Again, the error message is not the EXACT same, however the format is very similar...
While trying to boot into the normal user the system aborts the login and tells me that /home does not have write permission.
The login manager gives:
Code:
If I log in as root and do a
Code:
Or to open some files, it works and no problem seems to exist.
All this happened for the first time after running luckybackup to fusion the old files of one home directory under EXT4 with the new files from my notebook (ext3, Opensuse 11.1 KDE3) in order to come to a unified home. But then the system did not boot any more. I tried to change the owner but some files did not have write access (not even as root, "the file does not exist"). So I thought I might have a a file system problem.
So I thought: unmount the /dev/sdb1 and then do a fschk on it. Runs and was perfect. So I did run it with forcing to control inode per inode.
No error.
So I thought: you screwed up the system. I then decided to reinstall OpensSuse11.3 from the scratch and create the same user for home. I formatted the rest (/swap /boot /root) and left only /home. Installation runs brilliantly, all ok, it comes to the login..................
Code:
I'm trying to RMA a month old SSD, and they're giving me a hassle about it. The drive currently seems to work just fine, but I'm 95% sure that a few blocks went bad and corrupted some data about a week ago. I was able to mostly recover the data and correct for the bad blocks, but I don't really trust the drive anymore.
I'm running an up to date Debian Squeeze install with ext4 on this drive. My system started doing some bizarre things, to the point that it was unusable, so I rebooted it. As it was booting up, it complained about needing an fsck, which found dozens of non-trivial errors that it was mostly able to fix. It then proceeded to boot normally, except the drive mounted itself as read only (due to errors). Another fsck turned up a similar number of problems. This happened a couple of times before I ran fsck with '-c', which is supposed to scan for and work around bad blocks. That seemed to fix the problem, it hasn't given any more problems since then.
The manufacturer is refusing to RMA the drive unless it's completely unmountable right now this minute, saying that it was a one time problem that could have been caused by anything. Am I right in thinking that the problem has to have been with the drive if 'fsck -c' fixed it, or could something else be going on? If it was the drive, am I somehow being unreasonable in asking for a new one while the current one is "working"?
When I rebooted my system (RHEL 5.3 x86_64), I got the following error when it was booting up:
Code:
Full screenshot of the bootup error messages here: previous bootup error
So to try and fix this, I booted from the OS disk and did a linux rescue.
Here's some of the results of the commands I did:
Code:
Here's a screenshot of the output from fsck after it's done, notice it says 0 bad blocks but the system was modified:fsck results
I then reboot but now I get the errors:
Code:
Full screenshot of the startup errors I get now here: current bootup error
Does anyone have any ideas on how I can fix this? Was the fsck I did initially the correct thing to do to fix that initial group descriptor error or did I make things worse?
I have been having problems with filesystem corruption on my eeepc 1000H for a long time now. I have tried using different filesystems, kernels and distributions (arch, slackware) to no effect. I am starting to grow suspicious that this problem lies somewhere else, as I haven't seen anyone else having similar problems in such a variety of scenarios.
I have tried testing my ram using memtest86+, didn't come up with anything after a full run through. I also have tried using e2fsck -c to check for bad blocks, it finds none. I had a go at using smartctl but wasn't really sure what I was doing. I did a long test and it came up with nothing anyway.
This problem is in addition to the problems I've been having with my intel graphics chip and KMS. A lot of the time there are lockups when booting into X, which can only be gotten out of by a hard reset. This is sometimes what causes the original filesystem errors. I've stopped messing around with KMS for now to eliminate this but my current system in unbootable. I'm guessing my disk is wrecked but have as yet seen no definitive proof. Can anyone recommend anything that I should do?
I am currently on ext4 with a custom kernel 2.6.33-rc6 (the stock kernel shipping with slackware does not have the elantech extension for psmouse included). When I was using arch, I was just using the stock kernels.
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 have openSUSE 11.3 Gnome installed. The nautilus address bar shows the "Button Bar" and if I press Ctrl+L it swaps to the "Text Location Bar". The Text Location bar is where you see the full path to the directory that you're viewing.But I can't set the default addressing to the Text Location Bar.What else should I do to get the text location bar (i.e. the full path) to be the default view in the address bar?
View 4 Replies View RelatedLast night I was working on a document on my brothers Laptop computer. While working on it however, the computer locked up hard and I had to press the power button. When I booted back up I loaded up OpenOffice.org and it offered to recover my progress as normal, so I gave it the go ahead but it gave me a blank page. No big deal, I thought, and went to load up the original document. That is when the *beep* hit the fan. The original document was corrupted. My theory was that it was saving at the time of the crash. A 50 KB document now reads as only 4 KB. I did have a backup of the document from about a month ago, but that is ten pages shorter than the document that I lost.
Is there anyway I can recover my progress on the document? The computer is my brothers Dell Latitude D600 running Fedora 12 and he is using OpenOffice.org 3. I checked the "~/.openoffice.org/3/user/backup" directory and found two documents, but those are just useless files from when we were doing Grade 10 Social Studies. I doubt the remains of the file are much use, as it has shrunk in size dramatically. So it seems I may be up a certain creek, but I thought I would ask a few of the guru's here for some advice.
I did learn how to make it automatically backup files in OpenOffice.org through. Hopefully that will help prevent these kinds of situations from occurring again.
This is a strange problem, 2 Fedora 11 machines, both Dell's. On machine A, remote desktop is okay. On Machine B, remote desktop display is corrupt/unusable.
However, prior to upgrading to Fedora 11, both machines had Fedora 10, and, remote desktop on Machine A was corrupt and Machine B was okay.
Any idea what happened? Why did the upgrade fix one and break the other? Both machines where upgraded with Pre-upgrade. The two machines are in to separate locations, un-related to each other.
If you typed it in, my fdisk -l looks like this
[Code].....
I partitioned it using the Acronis (proprietary) partitioning software. I've had to move these around a bit when I initially set it up and at one point grub didnt work anymore. It was after I had to expand my Windows (7) partition. However I'm told that most modern software dont use the same unit of measurement that fdisk still uses 'til this day. Should I even be concerned? I did have to reinstall grub after I initial set all my partitions up. This post is merely a double-check to make sure.
During a recent request to install fedora 11, I ran into an interesting problem. It seems that between fedora10 and fedora11, the developers switched from fdisk, to parted for creating the initial pre-mke2fs partition table creation.
It looks like the implementation of this is broken, as it's writing the partition table with overlapping cylinder boundaries. While this can sometimes be ignored, it can in certain cases cause significant data corruption.
On an installation I took it through, using the latest installation media, in both manual & automatic partition creation, the layout looked like this:
The last two partitions turn out fine, for some reason. However, those two partitions should not have overlapping cylinders. After my very first installation, the system was completely unbootable, and not even fsck wouldn't rescue it. If this is possible, then that means that a system that's been online for months or even years could simply drop out of functionality simply due to a byte or two of system-critical data falling on that last cylinder. Considering that a lot of the time kernel data ends up on /dev/sda1 (commonly the /boot partition), this is something that should not be ignored.
I've just installed F12 and during boot and at the desktop, the screen has an issue. I have a 9700 pro and the resolution gets detected properly (1440x900), but it's like the frequency is slightly off. I see the screen fine, but the screen looks almost as if it's underwater. My monitor accepts two freq at 1440x900, and the issue is at the 60Hz setting. If I change it to 75Hz, the screen is fine, but the corruption is still there during boot and at the login screen. Ubuntu 8.04, 9.10 and Mint 8 all work just fine at 60Hz. This is using the default driver for my ATI card. The corruption was there in anaconda when I was installing F12, but figured it would not be there after the install. Can I somehow force 75Hz to the kernel mode set? I'll try to get a video up on ..... soon as it can describe my problem perfectly without words.
View 5 Replies View RelatedI'm looking for a script that copies a random .jpg from a random folder in my ~/Pictures folder to my ~/temp folder with a standard filename. This file will then be displayed in Conky. I can fix the last part, but I cannot find a way to do the first part.
View 3 Replies View RelatedWhat is the easiest way to make it so that these transferred files will not be completely locked out and require me to go and change them one by one sohat i can access them without having to go root. Also the "apply to all subfolders and files" doesn't work. Also trying to set the SELinux rule to "userspace" doesn't do anything else. Basically i was trying to do just that transfer my $home folder over to fedora but now it's being a bit odd towards me with making everything require root access and not letting me read/write all files and folders within them.
View 3 Replies View RelatedI just installed Fedora 12. Now i've seen a few other threads but they seem to have all the conclusion that its the Nvidia drivers at fault. Well i have an ATI Mobility Radeon 3400 series. I can login, and navigate for a little bit, then it just randomly freezes. I've booted to both gnome and KDE, kde freezes almost immediately w/o letting me navigate much. Gnome takes a bit and then freezes on me. I managed to login once and go like 6 minutes then i thought it was worked out, rebooted and boom, froze up again. I can still move my mouse but can't click or use keyboard. Ctrl+Alt+Backspace doesn't work either .....
View 2 Replies View RelatedAbout a week after I installed F12 on a brand new system, a friend came over and went on to play poker on facebook. At some point he yelled that the PC froze. I was working on another machine at the time and tried to ssh to the supposedly hung system, but couldn't; Except for playing poker he had audacious open and about 3 seconds of the song that was playing at the time of the hang, kept looping. Neither Ctrl+Alt+Backspace nor any of the Alt+SysRq combos had any effect whatsoever, so I had to press the reset button (and I have to say this was the first time I had to do so in linux after almost a decade of using it, save for a hiccup with my first gentoo kernel).
The system usually freezes if there are two or more sound streams, but that is not always the case. The best way to get the system to crash is by playing something in audacious or rhythmbox while seeking through a video in mplayer or vlc or having flash content appear in firefox (I am using adobe's latest 64-bit flash plug-in and have been using it without any problems -though on other systems- since F10). Also most but not all the times the system is going to hang, there are a few skips in audacious every ~10-30 minutes. I've been getting the lock-ups with every kernel released so far.
My system logs don't contain any useful info after each hang; there are however certain problems mentioned in syslog which I thought they could be relevant, but they always appear whether the system works fine or not, namely the following:
Code:
I used to get a lot more of these with previous kernels:
Code:
Code:
This one appeared every now and then until Dec 25:
Code:
And this one is always there:
Code:
Finally, at every boot I get this from abrtd, but it doesn't seem to be related:
Code:
Yesterday, I devoted the entire day to hunting down the culprit, but I couldn't get the system to hang; I had rhytmbox, audacious, totem, vlc, mplayer and vlc all playing music and videos simultaneously from local disks, network shares and through upnp, I got myself a facebook account in order to play that zynga poker thing, I upgraded alsa-lib to 1.0.22 from updates-testing, rebooted countless times, but the system didn't hang nor did any of the above messages disappear.
Today as I was browsing through some web pages, one of which had an interactive flash ad, while listening to music and the system froze again.
System specs:
When I try to boot to OpenSUSE I get the following error during boot-up: unknown filesystem type 'reiserfs' could not mount root filesystem - exiting to /bin/sh$
This only started happening quite recently - before this I could boot to Linux quite happily.
I have a new IBM x3650 that I am trying to get installed and running. However, it seems to experience random segfaulting. The system has ECC RAM and I have taken a look at the EDAC reports from the kernel, but as far as I can tell there is no error.This is a critical system I need to bring up, so I can't have it act flaky like this. Software is up to date. [URL]
Example output:
Code:
__ratelimit: 1 callbacks suppressed
ld-linux-x86-64[7676]: segfault at b33000 ip 00000000003b557b sp 00007fff13789c18 error 6 in ld-2.9.so[39d000+20000]
ld-linux-x86-64[7699]: segfault at 62ddbb ip 000000000062ddbb sp 00007ffffa0ab520 error 15 in toc2cddb[62c000+9000]
ld-linux-x86-64[7939]: segfault at 161004011d5 ip 00000000001ea1f0 sp 00007fff1eeb14f0 error 4 in ld-2.9.so[1e2000+20000]
[code]....
I've installed fedora 11 (GNOME) on my laptop. It sometimes reboot itself. The screen goes black and reboots(sometimes just turn off!) Palimpsest Disk Utility reports HDD bad sector but when I run memtest, everything looks fine. Windows xp does not have this kind of problem before I use fedora
View 3 Replies View RelatedMy mouse still moves, but it doesn't have any effect clicked. My keyboard doesn't work. Sugar doesn't hang at all
View 1 Replies View RelatedI've installed Eclipse PDT with yum and httpd got installed as well. The problem is everytime httpd starts it chooses different (random) port and refuses connections to other ports like 80 (displays 403 forbidden error). That's really annoyng because I have to launch eclipse and open file in "PHP Browser" to get the right port. It also makes me unable to setup vhosts properly (i think). How to force apache to stick to the 80 port? Heres my httpd.conf: [URL] The only things I've changed there is added vhost
View 7 Replies View RelatedI am trying to mount a file image, like this
mount -o loop /tmp/apps.img /media/apps
But I get the following:
mount: you must specify the filesystem type
I try ext3:
mount -o loop /tmp/apps.img /media/apps -t ext3
dmesg says:
error: can't find ext3 filesystem on dev loop6.
I've also tried ext2, vfat etc. How can I detect the filesystem type of apps.img?
I have a following problem: Recently my drive with Ubuntu 9.4 has mysteriously stopped working, i.e. when I switch the computer on it informs me that GRUB didn't find the filesystem. Well, I suppose it happens.
First, I though it was due to the drive dying, but I popped it in an external enclosure and HDTune told me the drive was fine. Wanting to recover the files on the drive before reinstalling I first tried to mount it in said external enclosure under Windows (I have Win Ext2 driver installed which used to work just fine). This time, however, drive gets assigned a letter but upon opening it Windows popped up an error saying that the drive was not formatted and whether I would like to format it then.
Unfazed by this streak of failures I tried to mount it under Linux but, alas, to no avail. I might have tried every single -t operator under mount command but it still won't budge and let me mount.
I've had a look at some similar threads but as I'm very new to linux they're already a bit technical for me. Sorry, this calls for someone with patience. I gather from other threads that disconnecting an external drive without unmounting is a no-no, and this seems to be the likely cause. Now the disk is read only and I'm unable to change any settings through the usual control panel on ubuntu. I'm just not familiar with the terminal instructions. I tried to cut and past a few command lines from other threads but I got some warnings that proceding could damage data. Like this one: WARNING! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage.
View 5 Replies View RelatedIt's been freezing on me like you wouldn't believe today, and I think it has something to do with the load put on the CPU by various sites. The trouble is, I need to access a few of these sites to do my work. WordPress is one of them. I've had to restart the computer five times via SysRq keys since when these freezes happen, I can't Ctrl-Alt-Backspace out of it (even with zap enabled) and I can't bring up a terminal or Alt-F2 to kill process. I can't switch processes, windows, or anything. Firefox just sits there and laughs at me as I threaten to bust the screen in half.
And the real funny thing is, people actually say this is a better browser than IE. I never had these problems on Windows.What can I do to stop this? Do I just have to switch to another browser?
I am using Fedora 12. I am able to connect to my wireless network (95% of the time at least) on start-up automatically, however after anywhere between a few seconds to a few minutes later it cuts out and will not reconnect. It appears to be that whenever it finds next doors network it disconnects from mine! I have set the channel to 9, and my neighbor's is on 1. I have a USB N+ adapter, and a G+ MIMO PCI card, however do not know which is being used to connect with.
View 5 Replies View RelatedMy firefox (Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.6) Gecko/20091216 Fedora/3.5.6-1.fc11 Firefox/3.5.6) on Gnome 2.26.3 will randomly crash, without any errors. /var/log/messages & /var/log/Xorg.0.log doesn't show anything that caused any errors. And it doesn't matter on which website(s) I'm busy with, it will just crash.
My PC has:
Intel Pentium(R) Dual-Core E5200 CPU
4GB DDRII Corsair RAM
3x 160GB SATAII HDD
Asus Nvidia 8800GT graphics card.
I have updated to the latest nVidia drivers
[root@Rudi-PC ~]# dmesg | grep nvidia
nvidia: module license 'NVIDIA' taints kernel.
nvidia 0000:01:00.0: setting latency timer to 64
[code]....
This is on Fedora Core 12 x86 I have disabled the only 3 Firefox plug-ins that I installed yesterday, but this problem has been looming for a long time. Something interesting that I picked up is that Thunderbird will close randomly (very seldom though) as well, so I don't know if it's Firefox specific though.
I have picked up that it happens more often when my PC's memory usage is above 2GB RAM, and memtest86+ didn't indicate any memory problems. If I have less tabs open, it happens less often, but the more tabs I have open, the more often it happens. At the same time, on the same PC, when I'm in Windows XP SP3 (dual boot), I can have many more tabs open as well as Thunderbird, Quickbooks, Photoshop CS3 and some other applications, and it doesn't cash.
I just installed 64 bit Fedora 12 on a Dell Latitude E6510. When I am typing, the cursor sometimes jumps to a random place. This is very annoying, especially while coding.
This was not a problem with Fedora 11 live or Windows 7 (dual boot).