Ubuntu :: 10.04: File System Failure After Power Outage
Jun 8, 2010
I recently installed Lynx 10.04 amd64. Twice now, my entire file system has become unusable -- each time after a short power outage (2 seconds).
In the first setup, I had two primary partitions: 1) / that was ext4; 2) /home that was ext4.
In the second setup, I changed the /home to ext3.
Both times, after booting up following the power outage, I received a message saying that "serious errors" were found in /home. But, after several reboots, I was able to login and use the system. Then, some time later, I would started getting "Read Only" messages when trying to write to the file system.
fsck gave the following message: "/home terminated with status 4". I received numerous "I/O error" on sda messages.
My question: Is this vulnerability due to using ext4 or is it related more to something else in Lynx 10.04? Further, what can I do (other than buying a power backup device) to avoid my file system becoming unusable after a power outage?
A 2sec service interruption was enough to cold-crash my PC and its given me a few issues, most I have solved but Synaptic is freezing up. I can get into Synaptic if I go to the terminal and become root with sudo -i If I do it through Gnome it show a frozen-screen version of synaptic like the image I posted with this. Right after the outage (it cold-crashed my PC) I used to get a message box that would pop up when I tried to shut off the PC (I have enclosed images to illustrate) but I have since overcame that problem.
So the power went out at my house recently, and my home theater PC seems to have taken a blow. We had it on a surge protector, which didn't blow so that's fine, but it keeps telling me its in low graphics mode, and I can't seem to fix it for the life of me. I could reinstall ubuntu, but I have a bunch of movies and music on that drive that I want to keep.
My computer was on when the power went out. I am not able to boot into ubuntu 11.4 install since that happened. I also have debian 6 and ubuntu 11.10 installed on the same machine and both boot just fine.
The machine boots as normal but stops with the line "disconnected from Plymouth". After the machine just sits there with a blinking cursor. I cannot start another terminal. Is my only option to reinstall.
the power on my street went out overnight, and I came home to a rebooted computer at the command line. I shut it down and rebooted again, also tried the failsafe mode, but it keeps going to the command line. Looked in the BIOS and it didn't see my hard drive settings. But I can see the HD fine when I booted using the live CD (that's how I am able to post here
I'm trying to come up with a startup init script that will check to see if the system was shut down gracefully, or if it is rebooting from a poweroff or something similar?Anyone know of a way to check for this condition with the least amount of room for false positives or vice versa?My intial thought is just a startup script that will will check for a file on startup, and on a proper reboot/shutdown just touch the file. But id like to avoid that type of script if possible,
I have a slackware 12.2 server. We had some really rough storms this weekend that took the power out for many hours. The UPS that it was connect to gave up the ghost and the server went down hard. I powered up the unit and it some up fine but with no network. Ifconfig -a shows that it only knows about the lo interface. Both integrated gig ethernet ports are missing. I am not a slackware expert. Need to figure out what is needed to get it back on the network. dmesg | grep eth0 shows nothing. Nor eth1. ifconfig eth0 returns no such device.
I come with questions to try out the wonderful forum support I keep hearing Ubuntu has! I figure this is a convenient time to ask, since I am soon to swap the UPS on my Ubuntu box. This all refers to Ubuntu 9.04. You see, not too long ago, I had a couple of power outages, and suffice to say, despite the efforts of my UPS, I didn't get to shut down my Ubuntu box properly on either occasion. After the first one, when I powered the computer back on it failed to boot. Some googling of the error message led me to find that the UUIDs Ubuntu assigns to things like hard drives, which are not SUPPOSED to change, had in fact changed. From an archived thread here I found out how to find out what the new ones were, and slapped them into my FSTAB hoping that'd be the end of it.
(Partitions/Drives affected: hda2, hdb) It wasn't. Ubuntu came up with new errors to throw at me. This time, it threw the "bad superblock/wrong fs type" error that I'm used to seeing when I fudge a mount command. It appeared to be the same anyway, it went by so fast I couldn't really read it, sure wish the pause button worked. The gui did finally load, but showed no sign of the affected drives.
I found that if I commented out the affected drives in the fstab, they would appear in the gui, ready and mountable and apparently just fine. I've double-checked the UUIDs. The new UUIDs I put in fstab match the new UUIDs that the vol_id command reports. What is wrong with my fstab? Why won't it mount them automatically? (I'll post both versions as an attachment)
Another minor problem is for some reason I can't get privoxy running anymore. I've temporarily taken to running the Windows version in wine. I seem to remember I had a helluva time getting the linux version to work in the first place anyway, so I think I'll just keep running the windows version in wine. Most importantly, what can I do to prevent this happening again? Debian Sarge never gave me such trouble (and my deb box suffered quite a few improper shutdowns too). Ubuntu's based on Debian. What gives?
I am using ubuntu 9.10. in my area there are frequent power outage. So my wifi get disonnected as the router stops. And it asks for security code. So when power comes the router starts but i have to manually write the security code and connect to wifi again. how i can make the computer to auto connect to wifi after power comes.
My computer is running really slow after a power outage. It was fine, then the power went out. Now it's *unabably* slow. The OS takes a long time to load, the simple calculator takes a few minutes to show up, Firefox doesn't even load at all before I give up. And it won't shut down normally. I have to use the power button.
So did the power outage fry somthing on my PC. Do I have ot replace RAM or the processor? Or is it a software issue? Do I have to do something as drastic as a reimage?
Installed new APC Back-UPS CS 350 on single server running openSUSE 11.2 64-bit and configured NUT 2.4.1 (SUSE package) according to instructions. When testing, NUT shuts down the server correctly and instructs the UPS to power down. UPS does so after some 20s delay, everything without errors. But after restoring main power, even after waiting for 1/2h UPS does not by itself turn on again, all LEDs are dark. One has to manually press the UPS's power button, which makes server and monitor run again immediately. What could be wrong that prevents UPS from turning itself on again?
When power was restored after an outage, my server (running Ubuntu server 9.10) started back up & got stuck in the GRUB menu ("Version 1.97~beta 4" I think) - it didn't do that countdown & auto-select the top item like I'm used to. Just stayed there, and since the server is headless, I had to dig out my monitor & hook it up to see what was wrong.
So yesterday, I my power went out on my desktop and when I rebooted, the screen resolution was stuck at 640x480. When I go to the display settings, no other higher options are available. Any suggestions?
did an update from ubuntu 8 to 10.04, this has failed. At boot there is initramfs error with prior message saying.
Code: alert /dev/disk/by-uuid/-the_uuid does not exist dropping to shell (initramfs) I boot to livecd and check disk uuid and compared it to the fstab and it is correct, is there anywhere else this uuid but have been corrupted or any issue that may cause this issue. note there was power cut during upgrade but this occurred when upgrade should have finished.
I have thought about it many times but just never found enough guts to attempt using it before..but necessity is the mother of invention so here I am.
I have a Dell PC with windows Xp that failed to restart after a power outage it went into auto restart and caught itself in a loop of restarts and wont see the hard drive so therefore will not start up in windows at all I downloaded feather Linux onto a cd and it does start the PC In Linux but I cant seem to figure out how to find the hard drives in the pc to get the info off of it
Sometimes either due to a power outage or due to lightning I turn off my Wimax modem and continue to use my laptop on the battery.Then when I turn the modem back on, there is no internet connection.Here's what I've tried:
1. turn off and on the network connections - right-clicking on the icon on the bar on top of my screen.
2. turn off and on the dsl-provider connection - no effect.
3. When I tried to re-do pppoeconf, it says that there's no response from the concentrator.
This has happened a few times in the past and the only thing I can do to go online again is restart the computer. And it works.Now on Windows, the double-computer icon showing a network indicates connectivity AND data movement. Unfortunately we don't have this on Ubuntu.I'm just after a restart and I'm online now. But I'd like to know if there's a way around this without having to restart.
We got a power outage yesterday. When my PC went back on, I noticed the Date and Time display disappeared along with the System Tray. How do I get these back? By the way, I only see the icons for printer, networkmanager and pulseaudio applet on the Taskbar at the bottom.
Due to a power outage, my EXT4 file systems (which contain /usr and /opt) no longer mount at boot-up. They are, however, seen by disk utility in Knoppix, so I assume the data is still there and that it's just matter of making a connection to it.
I setup a mythbuntu pc with an onboard card (eth0) so I could watch and listen to movies and music stored on my other pc in the basement. Everything worked fine until we had a power outage. I turned on the pc after the outage and had no networking.
I looked and saw no link lights. I verified the network port but plugging in a laptop. I got an ip and able to connect to the internet so the port is not the issue. I plugged in a pci 10/100 card (eth1) and booted up, got link lights, but no networking and not able to even ping the gateway. I setup a static ip in /etc/network/interfaces and added a route to the gateway/router. Still nothing.
Our Sled 10.1 server is running as a VM on VSpher 4. After a power outage we can not log into the server we get the Error in Module message. I can however disable the nic card for the server in the vm console and the system logs in with no problem.
I have a small problem on my Compaq Evo Centos 5.4 web server. The web server runs just fine, the problem is it fails to restart from a power outage. Simple edit the BIOS. No! For a reason I can't think of the keyboard stops working after a few key strokes following the F10 to enter BIOS setup. Then its a power cycle. If left to BOOT the PC and keyboard are fine. After hearing about viruses which get to the BIOS I will ask can NIX get that far so I can adjust the Power ON?
I've had a 4x 400Gb Raid 5 running for exactly 3 years now. There's been plenty of power outages in that time and lots of resyncing afterwards but all has been good afterwards with no issues. Last week after a power outage and reboot I went to check the status of the resync and it only listed 3 hdds.
I'm going to reformat my external drives to get rid of the crud that I've built up. (Crud being incremental backups, windows software, and similar things.)(I also want to get rid of the FAT32 file system that they use.) These are USB 1TB drives. The theory is that data is written to it once, but read back a number of times. (I also burn that data to DVD. If there was software that could organize 5TB of data on DVDs, I'd be using them.)
I"m trying to decide whether to use ReiserFS, Ext4, or another file system. Basically, I want something that:
* Won't get corrupted when the power fails; * Can handle files that are 4+GB in size; * Uses extends --- preferably without user intervention;
While I was installing some packages, the power in my street went out (uncleanly killing my system) ... unfortunately Kpackage was open at the time of the power outage. Now when I try to use KPackage, I get "Login Problem, Please Login Manually" ... which does not allow me to login using either the root or user's password. I have rebooted my computer many times and have even run a 'reiserfsck /dev/*** --fix-fixable' on my system, which did not repair the problem.
I have researched this error, but have only found responses that people suggest changing the KPackage behaviour from 'su' to 'sudo' ... ; while this does work, it feels like a 'putting-a-band-aid-over-a-warning-light-so-I-can't-see-the-warning-light-anymore' kind of 'fix?' which isn't good as it would enable anyone using the system to add or remove packages without thought or consequence. What I would prefer to do is actually fix the problem so that proper root password entering is again required to add or remove packages, so my question is:
1. Does anyone know if KPackage 'locks' out a file(s) on the system which may be preventing me from logging into the program correctly, and if so what and where the file(s) may be?
2. Can I delete any kpackage (profile?) file to gain normal login behaviour again?
3. Is this a permissions error?, has something in users/groups? been broken that I can look into?
4. how I may be able to properly repair this KPackage login problem on my system?
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 was upgrading my ubuntu(9.10)/xp machine to ubuntu(10.4)/xp . but there was a power failure and was running in backup for 15 min. But after that the system shutdown automatically. Now when i boot, grub appears and after selecting the ubuntu partition i get a error saying cannot find device.
While using my computer the other day (I was sending an email) it suddenly turned off. I didn't get any low power warning, but I was running on battery and had my iphone charging from a USB port.
As I didn't think there was low battery, I just turned it back on again. As it was booting I saw the battery light flashing, indicating low power. I went to get the charger, but before I got it, mid boot-up it turned off again.
This seemingly damaged something hard-disk-wise.
Upon turning it on again it dropped into busy box with some message similar to this:
No init fount. Try passing init= bootarg.
BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu7) built in shell (ash) Enter 'help' for a list of build in commands
That's not the actual message (copy pasted from another post) but the message is VERY similar to that.
If I "exit" busy box, I get a load of message about "kernel panic" before it freezes up.
I have booted a live USB (what I am using now). I thought since it wasn't cleanly unmounted, simply mounting and unmounting would do the trick. I was wrong.
Code: ubuntu@ubuntu:~$ sudo fdisk -l Disk /dev/sda: 250.1 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
I had previously ran e2fsck (after checking it was unmounted) but it wouldn't run also because it was reporting that the device was already mounted, busy, or being exclusively used by a process.
I don't want to do any more for fear of causing further damage.
I am astounded that such damage can be caused so easily!
Running 10.10 After a main power failure I can't boot.
It says: ........... [sdb] Attached SCSI removable disk [sdc] Attached SCSI removable disk [sdd] Attached SCSI removable disk [sde] Attached SCSI removable disk and stops.
I get a (initramfs) prompt and have no idea what to do with it.
Allready tried to install 10.10 again from a CD. But it also hangs immediately when it starts to install. The liveCD feature works OK and I can access the hard disk. I tried to update the initramfs with the liveCD but it says I can't write since I have only "read-only" access. But if I do "sudo nautilus" I have full access to the disk.