[solved]Emergency mode after force shutdown

Unline · 2017-08-23 16:52:29

I force shutdown my system for 2 or 3 time bcuz of freezing ui
And the last time it boot into emergency mode
And i googled it many ways and i did many of suggestions
But still no result
Any other suggestion
?
The log is 3 or 4 similar exception

Here s error part of journal log
https://ibb.co/c4LPP5

Re installing is not an option
Plz help me

Last edited by Unline (2017-08-24 13:13:36)

Slithery · 2017-08-23 16:57:40

Looks like a dead/dying hard drive.

Boot from an Arch CD/USB and run a SMART test. Post the results here.
You might want to check that your backups are OK, if it is a dead drive then you'll be needing them.

Unline · 2017-08-23 17:16:45

slithery wrote:

Looks like a dead/dying hard drive.
Boot from an Arch CD/USB and run a SMART test. Post the results here.
You might want to check that your backups are OK, if it is a dead drive then you'll be needing them.

https://ibb.co/jKuerk
Seems to be healthy hard drive any other suggestion ?

Unline · 2017-08-23 17:28:31

This is smart value
https://ibb.co/hMkoHQ

loqs · 2017-08-23 17:35:09

Unline wrote:

Re installing is not an option

Could you explain why it is not an option please.
When you boot from the live media does dmesg contain any of the errors from the screenshot from post #1?
Can you mount all the filesystems present on the system from the live media?
When you boot the system do you obtain a command prompt in rescue/emergency mode?
If you do please post the journal for that boot, you may need to transfer the journal's output to some removable media and upload it from a system with an internet connection.
Failed to complete its self-test at least the block noted 1151800432 need to be remapped by the drives firmware.
I would class the drive as failed and need replacing given the above but that is just my opinion.
Edit:
You may want to retitle the thread to something indicating the issue is device unable to read block or device unable to complete S.M.A.R.T. self-test.

Last edited by loqs (2017-08-23 17:38:21)

Unline · 2017-08-23 17:42:48

loqs wrote:

Could you explain why it is not an option please.

If i have to i will re install
I mean i want make it witouth installation

loqs wrote:

When you boot from the live media does dmesg contain any of the errors from the screenshot from post #1?

Yes one of them

loqs wrote:

Can you mount all the filesystems present on the system from the live media?

Yes i can mount all of them

loqs wrote:

When you boot the system do you obtain a command prompt in rescue/emergency mode?

Yes i have root access

loqs wrote:

If you do please post the journal for that boot, you may need to transfer the journal's output to some removable media and upload it from a system with an internet connection.

I will upload it

loqs wrote:

Failed to complete its self-test at least the block noted 1151800432 need to be remapped by the drives firmware.
I would class the drive as failed and need replacing given the above but that is just my opinion.

I didnt really understand this part

loqs · 2017-08-23 17:52:27

As you can mount the filesystems I would ensure you have backups of all your data although as the drive is producing read errors I would make these backups separate to any existing backups
as I it is highly possible the backup will fail or contain errors.
Trying to explain the last part the self-test failed but the drives assessment is healthy that to me is somewhat bizarre.
The block that can not be read is where the self-test aborted it is unknown if there are any other blocks beyond that point that can not be read.
Preferably when the firmware can not read a block it will remap that block to one of its reserve blocks it has allocated for such occasions.
You can try rerunning the self-test after trying to recover all the data you can and see if the firmware did remap that block.
Whatever filesystem is using that block if any will run into issues until the block is remapped. The same is true if there are other bad blocks beyond that location.

Unline · 2017-08-23 18:15:25

loqs wrote:

As you can mount the filesystems I would ensure you have backups of all your data although as the drive is producing read errors I would make these backups separate to any existing backups
as I it is highly possible the backup will fail or contain errors.
Trying to explain the last part the self-test failed but the drives assessment is healthy that to me is somewhat bizarre.
The block that can not be read is where the self-test aborted it is unknown if there are any other blocks beyond that point that can not be read.
Preferably when the firmware can not read a block it will remap that block to one of its reserve blocks it has allocated for such occasions.
You can try rerunning the self-test after trying to recover all the data you can and see if the firmware did remap that block.
Whatever filesystem is using that block if any will run into issues until the block is remapped. The same is true if there are other bad blocks beyond that location.

Ok now i know exactly what folder cause this problem
( And i know kinda why .. its steam library
Located in home/.local/share/common/Steam)
But when i m trying to remove that folder i got those error and exception again
Any other advice ?

Unline · 2017-08-23 18:21:55

One solution maybe is deleting that home partition and recreating it since its seperate from / partion
Beside that i m not sure if its working or not
I want to avoid that unless its last solution

loqs · 2017-08-23 18:23:01

Perhaps badblocks#read-write_Test_.28non-destructive.29

dockland · 2017-08-23 19:17:54

First of all I would have done a full backup of my /home, in the case I have anything that I want to keep there.
Then I would get rid of the drive, install a fresh Arch Linux and do a restore manually of my /home.

But do a backup. First things first.

Unline · 2017-08-24 11:59:50

Ok i scaned it completly and it had 14 error exaclty that folder ive mentioned before
So i took back up from rest of my files
And since my /home mount point was seperated from /
I made new partitiob trying to avoid that part of blocks
Made new partision and configurang fstab and ...
I fixed it finally
Thank u all guys

mrunion · 2017-08-24 12:07:08

Please edit your first post and add "[SOLVED]" to the title to indicate your issue is solved. Thanks!

Arch Linux

#1 2017-08-23 16:52:29

[solved]Emergency mode after force shutdown

#2 2017-08-23 16:57:40

Re: [solved]Emergency mode after force shutdown

#3 2017-08-23 17:16:45

Re: [solved]Emergency mode after force shutdown

#4 2017-08-23 17:28:31

Re: [solved]Emergency mode after force shutdown

#5 2017-08-23 17:35:09

Re: [solved]Emergency mode after force shutdown

#6 2017-08-23 17:42:48

Re: [solved]Emergency mode after force shutdown

#7 2017-08-23 17:52:27

Re: [solved]Emergency mode after force shutdown

#8 2017-08-23 18:15:25

Re: [solved]Emergency mode after force shutdown

#9 2017-08-23 18:21:55

Re: [solved]Emergency mode after force shutdown

#10 2017-08-23 18:23:01

Re: [solved]Emergency mode after force shutdown

#11 2017-08-23 19:17:54

Re: [solved]Emergency mode after force shutdown

#12 2017-08-24 11:59:50

Re: [solved]Emergency mode after force shutdown

#13 2017-08-24 12:07:08

Re: [solved]Emergency mode after force shutdown

Board footer