OpenSUSE Install :: EXT4 And Power Outage - No Longer Mount At Boot-up
Sep 24, 2010
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.
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.
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.
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?
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.
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.
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?
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.
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?
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.
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
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 was originally going to install debian on this old iMac G4 and everything was going well. But then I decided, hey wait one second, I could probably find a version of Ubuntu which works on this old iMac, and so... i stopped the installation and loaded the ubuntu 8.04 disc. The only problem is, it will no longer register the boot CD... because i kind of already did the partitioning and nuked the OS X... So now I just see a gray screen with a file image displayed revolving between a question mark and the file finder image.
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.
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.
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?
telling me if this behavior of my openSuSE 11.2 installation is normal? I use a 64-Bit openSuSE 11.2 with kernel 2.6.31.x with root partition ext4. After adding and updating from repository kernel:/HEAD/etc to 2.6.34-rc4 I can not boot anymore due to a lack of module ext4. I thought today ext4 is stable and fix built-in in the actual kernel releases, isn't it? The error message at boot time: FATAL: Module ext4 not found. Which is right because in /lib/modules/<kernelversion>/kernel/ there is NO 'fs' subfolder. Isn't the kernel:/HEAD/ repository the official update path to get a newer major kernel? (besides openSuSE's Updates for security reasons) Do you know how I can fix it without self-compiling?
Some times ago i add Tumbleweed repo to my Open Suse 11.3 64bit system & try to update. On every update with kernel by zypper up it make output like this
I'm trying to set up my Fedora 15 installation to automatically mount (with all privileges needed for read/write access w/o a password prompt) an ext4 partition on the same HDD. Below is the output of sudo fdisk -l.
Code:
Disk /dev/sda: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors Units = sectors of 1 * 512 = 512 bytes
[code]....
Partition table entries are not in disk order I'm trying to automount /dev/sda8, I believe. I'll check that when I've rebooted to by Ubuntu partition, 'cause that's where I know how to do it. I tried to use pysdm, since that's what I used to do the same thing in Ubuntu, but it wasn't found by the Fedora package manager.
When booting I get the following error message: Code: The disk drive for EXT4 is not ready yet or not present. Continue to wait; or press S to skip mounting or M for manual recovery.
The drive in question is SSD2, which I wanted to mount as an extended disk (non OS). This is what I did: FDISK: Code: Disk /dev/sdb: 64.0 GB, 64023257088 bytes 255 heads, 63 sectors/track, 7783 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00029baa
Device Boot Start End Blocks Id System /dev/sdb1 1 7783 62516916 85 Linux extended BLKID: Code: /dev/sdb1: LABEL="SSD2" UUID="#######" TYPE="ext4" FSTAB: Code: UUID=####### ext4 /media/mountSSD2 defaults 0 2
I've run into a strange problem recently. My primary OS right now is Windows 7, and OpenSUSE is secondary. I had GRUB as the bootloader, and everything seemed fine, but I ran into one problem in Windows 7: one program refused to work correctly with ATI forced anti-aliasing on, but it is needed by others (or else edges look jagged).So I decided to install ATI Tray Tools. But it seems that Windows 7 is being evil and won't let install drivers that their creators didn't pay Microsoft for (thank goodness that's not the case in Linux). That means I had to use a driver overrider program, and that means that it had to change the Windows 7 BCD options. And that's where bootloaders kick in. It seems that Windows 7 is too lazy to check for its BCD on other than active partitions, so it doesn't allow the overrider to function.
So what I did was change GRUB to boot Windows 7 with makeactive flag. The problem now is - it won't deactivate! I no longer get GRUB's boot screen, it just boots to BCD directly. So my question is - is there a way to deactivate (or, rather, reactivate the /boot partition) after Windows 7 shuts down or restarts automatically? Obviously I don't want to use GPartEd each time I want to boot to Linux.
I updated my GRUB config. I reordered some menu items and set openSUSE as default OS.When I boot into openSUSE, I am no longer greeted by Geeko when openSUSE is loading. I only see text from the boot procedure scroll by like it's still the 90s. While there's a certain coolness in seeing openSUSE switch to runlevel 5 and all that jazz, I want my chameleon back.A few weeks ago, I configured openSUSE to boot with flag vga=0x3ef so that it would boot with my preferred resolution immediately. This used to work fine. Since this morning, openSUSE crashes when X is attempting to start. I can still boot into openSUSE by removing that flag, but even then I still don't see the chameleon.
Everything went fine but whenever I rebooted, Ubuntu 10.10 was not an option in the boot list. However, Windows shows up and boots just fine. I am currently tri booting (not sure if that's the correct term) Windows 7, Ubuntu 10.10, and OpenSuse each on a hard drive of their own. In the dolphin file manager I can still see all the files for Ubuntu so I know it was not partitioned over or deleted.