How to recover Linux after a power surge puts it in emergency mode

ebunch

New Member
Joined
Oct 18, 2020
Messages
9
Reaction score
3
Credits
82
I have an Acer computer that came with Microsoft 10 but I installed Linux Red Hat as my operating system which I used exclusively. I suffered a power surge and now when I try to boot the operating system, I receive several error messages and am left in emergency mode.
How can I get out of emergency mode and back into my computer?
 


G'day @ebunch and welcome to linux.org, albeit under trying circumstances :)

I may not be the one to help you, but a couple of questions -

  1. How are you communicating with us?
  2. Can you post eg phone pics or other information?
  3. Describe the emergency mode, including any prompt
  4. Do you have a support agreement with Red Hat, and which version?
The more you tell us, the better we may be able to assist.

Cheers

Chris Turner
wizardfromoz
 
IF you don't have hardware problems due to the surge, try logging in (in emergency mode) and entering "systemctl default" and reboot. That was needed with CentOS, so I assume it's the same with RHEL.

However, that's a guess - 'cause I don't know what your error messages are. As Wizard said, we need to know what specific errors we're working with.
 
I've had a power surge or two but my tower running Linux Mint just boots back up,so I can't help you.
My computer is plugged into a power surge protection board which might be why no damage is done. ;)
Your computer my have suffered damage that can't be fixed,I might be wrong but a small amount of static electricity can kill computer components. I always keep an Image of my Operating System on an External HDD for times just like this, so I don't loose everything and have to reinstall the OS. ;)
 
G'day @ebunch and welcome to linux.org, albeit under trying circumstances :)

I may not be the one to help you, but a couple of questions -

  1. How are you communicating with us?
  2. Can you post eg phone pics or other information?
  3. Describe the emergency mode, including any prompt
  4. Do you have a support agreement with Red Hat, and which version?
The more you tell us, the better we may be able to assist.

Cheers

Chris Turner
wizardfromoz


Hello Chris,
This is Liz and I'm communicating with you by cell phone. The following are the errors I received:
8.842578) ACPI Error: Result stack is empty! State=8888888Beba 1f 458 (281883 13/dsustate-65) 8.842574) ACPI Error: AE_AML_NO_RETURN_VALUE, Missing or null operand (2818 8313/dsutils-612) 8.8425771 ACPI Error: AE_APL_NO_RETURN_VALUE, While creating Arg 8 (2818831 3/dsutils-727) 8.842581) ACPI Error: Result stack is empty! State-88888888eba 4f 458 (281883 13/dsustate-65) 8.842584) ACPI Error: AE AM_NO_RETURN_UALUE, Missing or null operand (2018 8313/dsutils-612) 8.842586) ACPI Error: AE_AML_NO_RETURN_VALUE, While creating Arg @ (2818831 3/dsutils-727)

8.593788) tpm_crb MSFT8181:88: [Firmware Bug]: ACPI region does not cover t sponse buffer. (mea exfcd 48888-8xded 4887f flags x288) vs fed488B8 f88 8.593755) tpm_crb MSFT8181:89: [Firmware Bug): ACPI region does not cover t sponse buffer. Imem 8xded48008-8xfed4067f flags 8x288) vs fed 48888 f88

Generating "/run/Instramfs/rdsosreport.txt"

Entering emergence de Pelt the ebell

Entering emergency mode. bit the shell to continue. Type "Journalctl" to view system logs. You might want to save run/initrons/ednokreport.txt to a USB stick or Moot after mounting them and attach it to a bug report.
I do not have any agreement with Red Hat
I hope will this info you can give me direction. Thank you.

Liz
 
G'day Liz, just a holding post for now. :)


I have only had the quickest read of the above so far. I have some time up my sleeve this arvo (Aussie time), and I will digest it and see if I can help.

I see my fellow Aussie Brian @Condobloke has put a like on your Post too, which reflects that you have given us some good information under trying circumstances.

We'll see if we can get you sorted. Back as soon as I can. ;)

Cheers

Wizard
BTW you can call me Chris, Wizard, Wiz - anything but late for dinner.

BTW 2 - if you can tell us your timezone, I can try to work with that.
 
G'day Liz, just a holding post for now. :)


I have only had the quickest read of the above so far. I have some time up my sleeve this arvo (Aussie time), and I will digest it and see if I can help.

I see my fellow Aussie Brian @Condobloke has put a like on your Post too, which reflects that you have given us some good information under trying circumstances.

We'll see if we can get you sorted. Back as soon as I can. ;)

Cheers

Wizard
BTW you can call me Chris, Wizard, Wiz - anything but late for dinner.

BTW 2 - if you can tell us your timezone, I can try to work with that.

Thanks, Chris.
I'm in the Eastern Time zone.
Thanks for your help!
 
@ebunch I can't help you with your problem but I can tell you how to protect your computer from power surges. Before I did what I'm gonna suggest to you, I had 4 motherboards fried in less than a year.
So, look for the brand Brennenstuhl - it's made in Germany and its primary purpose is exactly that: power surges protection.
First you get this and plug it into the wall plug. Then you get this by the same brand and plug it into the silver thingy. My silver thingy is pretty much the same, only mine has no screen or buttons. Sorry for the "this" and "this" words, it's just that English ain't my native language and I have no idea what these items are called in English.
With this double protection you'll forget what a power surge is, believe me! I got my things in 2015 and I'm very happy with their functioning - no more fried motherboards, no more screwed up operating system!
 
I have no idea what these items are called in English.
It's a surge protector.
So, look for the brand Brennenstuhl - it's made in Germany and its primary purpose is exactly that: power surges protection.
First you get this and plug it into the wall plug. Then you get this by the same brand and plug it into the silver thingy.
@ebunch, if you live in the Eastern United States, you may want to look for an American style plugin on your surge protector.
 
I have an Acer computer that came with Microsoft 10 but I installed Linux Red Hat as my operating system which I used exclusively. I suffered a power surge and now when I try to boot the operating system, I receive several error messages and am left in emergency mode.
How can I get out of emergency mode and back into my computer?
Before the disastre have you create un timeshift? a backup system? If yes at bootstrap you have
the alternative to repair the SO...If NO....reinstall it!
 
Seeing the content of "/run/Instramfs/rdsosreport.txt" might be helpful.

Try doing the following:
1. Boot from centos dvd.
2. Select Troubleshooting from the boot menu.
3. Select Rescue a Centos System.
4. Select continue
5. chroot /mnt/sysimage
If this does work we could try to continue from there, however I doubt it will work since my guess is your partitions are probably screwed or some other hardware problem like @KGIII already mentioned. If that doesn't work go through steps 1 through 3 again, and then this time instead of selecting Continue select 3(Skip to Shell), from there try the following.
Code:
fdisk -l
lsblk
What happens?
 
Hi Wizard,

Sorry it has been a while but I've been coping with the death of my father in upstate New York. Our IT guy placed all the Linux software in the E drive on our computer. I can boot into Windows, but not into Linux (which I had been previously set up to so). When I open the E drive on my computer I can see all the Linux files, including the BOOT file. I attempted to open the Linux BOOT file, but it says "Class not registered", as did all the files I attempted to open in that drive.

I have not attempted any of the above suggstions just yet because first I wanted to tell you what I discovered on the E drive.

Thank you for your help.
 
That's fine Liz (for the delay), and sincere condolences (lost my parents within 18 months of each other a few years ago).

Our Members above are likely of more assistance than I in this regard, but as said earlier, anything useful I find, I will report back here.

Chris

BTW our Off Topic subforum is a good place to exchange ideas and thoughts not related to Linux. Your first holiday season without Dad will be tough.

My very good friend Brian @Condobloke has this in his signature

It has been said that time heals all wounds. I don't agree. The wounds remain. Time - the mind, protecting its sanity - covers them with some scar tissue and the pain lessens, but it is never gone. Rose Kennedy

Stay safe
 
That's fine Liz (for the delay), and sincere condolences (lost my parents within 18 months of each other a few years ago).

Our Members above are likely of more assistance than I in this regard, but as said earlier, anything useful I find, I will report back here.

Chris

BTW our Off Topic subforum is a good place to exchange ideas and thoughts not related to Linux. Your first holiday season without Dad will be tough.

My very good friend Brian @Condobloke has this in his signature



Stay safe
Hi Wizard,
I've gone attempted to go through the information
Seeing the content of "/run/Instramfs/rdsosreport.txt" might be helpful.

Try doing the following:
That's fine Liz (for the delay), and sincere condolences (lost my parents within 18 months of each other a few years ago).

Our Members above are likely of more assistance than I in this regard, but as said earlier, anything useful I find, I will report back here.

Chris

BTW our Off Topic subforum is a good place to exchange ideas and thoughts not related to Linux. Your first holiday season without Dad will be tough.

My very good friend Brian @Condobloke has this in his signature



Stay safe
1. Boot from centos dvd.
2. Select Troubleshooting from the boot menu.
3. Select Rescue a Centos System.
4. Select continue
5. chroot /mnt/sysimage
If this does work we could try to continue from there, however I doubt it will work since my guess is your partitions are probably screwed or some other hardware problem like @KGIII already mentioned. If that doesn't work go through steps 1 through 3 again, and then this time instead of selecting Continue select 3(Skip to Shell), from there try the following.
Code:
fdisk -l
lsblk
What happens?
That's fine Liz (for the delay), and sincere condolences (lost my parents within 18 months of each other a few years ago).

Our Members above are likely of more assistance than I in this regard, but as said earlier, anything useful I find, I will report back here.

Chris

BTW our Off Topic subforum is a good place to exchange ideas and thoughts not related to Linux. Your first holiday season without Dad will be tough.

My very good friend Brian @Condobloke has this in his signature



Stay safe
Hi Chris or Brian,
In an attempt to recover the damaged file system, I entered "fsck" . The response was

fsck from util-linux 2.30.2

Okay, what does this mean???

I have Linux on a thumb drive my computer yet I cannot access it. This is nuts!!

Thank you guys for any help you can give me!
 
fsck from util-linux 2.30.2

Okay, what does this mean???


it at least means that fsck is available. I can only really talk about power surges and how it affected my Slackware Linux. Currently im in Africa and often in the past i got half current and complete power off. I found that power surge did affect the file system because i used fsck and that put it right. I've done it 2 ways; you should not use fsck on a mounted file system i.e one that is in use, as it would be if you tried to use it from a booted up system. IN slackware i could get around that by dropping to run level 1 and that was ok.

I've also done it by booting Linux from a usb from the PC with a problem and then just running fsck from the Linux on usb on the PC with a problem.

For verbose use you can try :

fsck --help

from the usb live OS first confirm the root partition of the PC with problem maybe use gParted , say it was /dev/sda3

then from usb I've used with fingers crossed:

fsck /dev/sda3 -v -y

you can run fsck as scan without doing anything to see what it finds and what would be done -N on mine


to get info if you've got fsck on usb live you can use:
Code:
cd /sbin

ls fsck*



eg on slackware:

[CODE]
ash-5.0# cd /sbin
bash-5.0# ls fsck*
fsck        fsck.cramfs  fsck.ext4       fsck.fat    fsck.msdos     fsck.xfs
fsck-e2fsprogs    fsck.ext2    fsck.ext4dev  fsck.jfs    fsck.reiserfs
fsck.btrfs    fsck.ext3    fsck.f2fs       fsck.minix  fsck.vfat
bash-5.0#
 
it at least means that fsck is available. I can only really talk about power surges and how it affected my Slackware Linux. Currently im in Africa and often in the past i got half current and complete power off. I found that power surge did affect the file system because i used fsck and that put it right. I've done it 2 ways; you should not use fsck on a mounted file system i.e one that is in use, as it would be if you tried to use it from a booted up system. IN slackware i could get around that by dropping to run level 1 and that was ok.

I've also done it by booting Linux from a usb from the PC with a problem and then just running fsck from the Linux on usb on the PC with a problem.

For verbose use you can try :

fsck --help

from the usb live OS first confirm the root partition of the PC with problem maybe use gParted , say it was /dev/sda3

then from usb I've used with fingers crossed:

fsck /dev/sda3 -v -y

you can run fsck as scan without doing anything to see what it finds and what would be done -N on mine


to get info if you've got fsck on usb live you can use:
Code:
cd /sbin

ls fsck*



eg on slackware:

[CODE]
ash-5.0# cd /sbin
bash-5.0# ls fsck*
fsck        fsck.cramfs  fsck.ext4       fsck.fat    fsck.msdos     fsck.xfs
fsck-e2fsprogs    fsck.ext2    fsck.ext4dev  fsck.jfs    fsck.reiserfs
fsck.btrfs    fsck.ext3    fsck.f2fs       fsck.minix  fsck.vfat
bash-5.0#
it at least means that fsck is available. I can only really talk about power surges and how it affected my Slackware Linux. Currently im in Africa and often in the past i got half current and complete power off. I found that power surge did affect the file system because i used fsck and that put it right. I've done it 2 ways; you should not use fsck on a mounted file system i.e one that is in use, as it would be if you tried to use it from a booted up system. IN slackware i could get around that by dropping to run level 1 and that was ok.

I've also done it by booting Linux from a usb from the PC with a problem and then just running fsck from the Linux on usb on the PC with a problem.

For verbose use you can try :

fsck --help

from the usb live OS first confirm the root partition of the PC with problem maybe use gParted , say it was /dev/sda3

then from usb I've used with fingers crossed:

fsck /dev/sda3 -v -y

you can run fsck as scan without doing anything to see what it finds and what would be done -N on mine


to get info if you've got fsck on usb live you can use:
Code:
cd /sbin

ls fsck*



eg on slackware:

[CODE]
ash-5.0# cd /sbin
bash-5.0# ls fsck*
fsck        fsck.cramfs  fsck.ext4       fsck.fat    fsck.msdos     fsck.xfs
fsck-e2fsprogs    fsck.ext2    fsck.ext4dev  fsck.jfs    fsck.reiserfs
fsck.btrfs    fsck.ext3    fsck.f2fs       fsck.minix  fsck.vfat
bash-5.0#
I feel I need to fully disclose that I am truly a novice when it comes to computing. I can use the software system for business and individual purposes but when it comes to coding or fixings errors I'm at a loss.
With respect to my Linux software, it is on a separate usb drive. It was installed so thst the computer would boot up into Linux. Now, after the surge, everything else on the computer works instead of the Linux software on the thumb drive.
Do I remove the thumb drive and then insert it again with the hope that works?! Please let me know your thoughts. Thanks.
Liz Bunch
 
That sounds like the thumb drive is unmounted.

Can you 'see' the thumb drive .....if so....right click on the thumb drive and select 'mount'

If you cannot see it, take the thumb drive out, and then reinsert it.
 

Members online


Latest posts

Top