[opensuse] Power failed, won't boot up to desktop
Hi, my friends suffered a power failure at their farm while their computer was running opensuse 11.4. When the power came back on, opensuse won't boot back up. When they try to boot the computer, they get to a screen that says FAILED:module ata_piix not found I tried putting the computer in text mode (level 3) to see if I could do a zypper up or zypper dup in the hopes that that would repair the problem. But it didn't work, what came up was a notice in red that says something like REPAIR FILE SYSTEM. Can someone on the list help me to correct this problem? Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Mark Misulich wrote:
Hi, my friends suffered a power failure at their farm while their computer was running opensuse 11.4. When the power came back on, opensuse won't boot back up.
When they try to boot the computer, they get to a screen that says
FAILED:module ata_piix not found
I tried putting the computer in text mode (level 3) to see if I could do a zypper up or zypper dup in the hopes that that would repair the problem. But it didn't work, what came up was a notice in red that says something like REPAIR FILE SYSTEM.
Can someone on the list help me to correct this problem?
Thanks.
What happens if you boot from a rescue disc and run fsck? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 2012-07-05 at 14:03 -0400, James Knott wrote:
Mark Misulich wrote:
Hi, my friends suffered a power failure at their farm while their computer was running opensuse 11.4. When the power came back on, opensuse won't boot back up.
When they try to boot the computer, they get to a screen that says
FAILED:module ata_piix not found
I tried putting the computer in text mode (level 3) to see if I could do a zypper up or zypper dup in the hopes that that would repair the problem. But it didn't work, what came up was a notice in red that says something like REPAIR FILE SYSTEM.
Can someone on the list help me to correct this problem?
Thanks.
What happens if you boot from a rescue disc and run fsck?
I tried to have them boot to runlevel 3 and from command prompt run fsck -p, and then fsck -y to see if I could correct the problem. But it didn't work. They can't find the install disk that I left at their house, so I can't get them to use repair disk. I am away on a business trip and won't get home for another week. I have been trying to help them by phone. So unless someone has a better idea, I will have to wait till I get home and can bring the install disk with me to their house to try fsck with the disk in the cd drive. Thanks -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012/07/05 14:32 (GMT-0400) Mark Misulich composed:
What happens if you boot from a rescue disc and run fsck?
I tried to have them boot to runlevel 3 and from command prompt run fsck -p, and then fsck -y to see if I could correct the problem. But it didn't work. They can't find the install disk that I left at their house, so I can't get them to use repair disk.
I am away on a business trip and won't get home for another week. I have been trying to help them by phone. So unless someone has a better idea, I will have to wait till I get home and can bring the install disk with me to their house to try fsck with the disk in the cd drive.
Any bootable Linux media that isn't too old to support the / filesystem can be used to run fsck. Usually the auto fsck that runs after such an irreverent shutdown will automatically fix the problem, so don't count on a novice to be able to do manually what didn't work automatically. Before next time, get that system hooked up to a UPS. Power failures are inevitable, not mere possibilities. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/07/12 03:49, Mark Misulich wrote:
Hi, my friends suffered a power failure at their farm while their computer was running opensuse 11.4. When the power came back on, opensuse won't boot back up.
When they try to boot the computer, they get to a screen that says
FAILED:module ata_piix not found
I tried putting the computer in text mode (level 3) to see if I could do a zypper up or zypper dup in the hopes that that would repair the problem. But it didn't work, what came up was a notice in red that says something like REPAIR FILE SYSTEM.
Can someone on the list help me to correct this problem?
Thanks.
The assumption to what I write is that the file system being used is one of the ext fs - ext2, ext3, ext4. If it is reiserfs then slightly different instructions will apply. At the grub boot menu, type in 'init 1' (without the quotes). Login as root at the prompt. type 'fdisk -l' <ENTER> to get the listing of the HDD/HDDs being used - the idea here is to find which partition contains the '/root' or the operating system. Let's say that this found to be 'sda2'. Once you know what this partition is, type this: mount -o remount,ro /dev/sda2 [The 'o' here is the letter 'o' and not zero '0' - right? :-) ] then type in e2fsck /dev/sda2 and answer the questions which come up (in all cases the answer would probably be "yes"). HOWEVER, note here that you do NOT use the "-p" parameter when executing the above: you do NOT want automatic fixes to be done by e2fsck because you want to see what the information about what the corruptions were. After the error fixing has been done, type a slightly modified version of the command above: remount -o remount,rw /dev/sda2 <ENTER> Type in 'init 5' - or simply reboot - to boot into the system. BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.4.4.2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 2012-07-06 at 16:14 +1000, Basil Chupin wrote:
On 06/07/12 03:49, Mark Misulich wrote:
Hi, my friends suffered a power failure at their farm while their computer was running opensuse 11.4. When the power came back on, opensuse won't boot back up.
When they try to boot the computer, they get to a screen that says
FAILED:module ata_piix not found
I tried putting the computer in text mode (level 3) to see if I could do a zypper up or zypper dup in the hopes that that would repair the problem. But it didn't work, what came up was a notice in red that says something like REPAIR FILE SYSTEM.
Can someone on the list help me to correct this problem?
Thanks.
The assumption to what I write is that the file system being used is one of the ext fs - ext2, ext3, ext4. If it is reiserfs then slightly different instructions will apply.
At the grub boot menu, type in 'init 1' (without the quotes).
Login as root at the prompt.
type 'fdisk -l' <ENTER> to get the listing of the HDD/HDDs being used - the idea here is to find which partition contains the '/root' or the operating system. Let's say that this found to be 'sda2'. Once you know what this partition is, type this:
mount -o remount,ro /dev/sda2 [The 'o' here is the letter 'o' and not zero '0' - right? :-) ]
then type in
e2fsck /dev/sda2
and answer the questions which come up (in all cases the answer would probably be "yes"). HOWEVER, note here that you do NOT use the "-p" parameter when executing the above: you do NOT want automatic fixes to be done by e2fsck because you want to see what the information about what the corruptions were.
After the error fixing has been done, type a slightly modified version of the command above:
remount -o remount,rw /dev/sda2 <ENTER>
Type in 'init 5' - or simply reboot - to boot into the system.
BC
Thanks Basil, that fixed the problem. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/07/12 12:43, Mark Misulich wrote:
On Fri, 2012-07-06 at 16:14 +1000, Basil Chupin wrote:
[.........]
mount -o remount,ro /dev/sda2 [The 'o' here is the letter 'o' and not zero '0' - right? :-) ]
then type in
e2fsck /dev/sda2
and answer the questions which come up (in all cases the answer would probably be "yes"). HOWEVER, note here that you do NOT use the "-p" parameter when executing the above: you do NOT want automatic fixes to be done by e2fsck because you want to see what the information about what the corruptions were.
After the error fixing has been done, type a slightly modified version of the command above:
remount -o remount,rw /dev/sda2 <ENTER>
Type in 'init 5' - or simply reboot - to boot into the system.
BC
Thanks Basil, that fixed the problem.
Good! :-) If you suffer power failures or notice that the system is not behaving normally then I suggest you run the above 'fix'. Can't do any harm but could do a lot of good :-) . BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.4.4.2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Basil Chupin -
Felix Miata -
James Knott -
Mark Misulich