[Resolved] CPU died, fresh install?

nixIT · 2013-10-20 12:39:11

Hey all,

My CPU died last week, and I just put together my system yesterday. for the most part Arch came right back up, had to edit NIC, but that was it. After I got back online, I did a

pacman -Syyu

And after the reboot, I am getting this during boot:

systemd-fsck[161]: /dev/sda2: clean, <files and block count>
systemd-fsck[253]: /dev/sda3: recovering journal
systemd-fsck[253]: /dev/sda3: clean, <files and block count>
systemd-fsck[258]: /dev/sdb2: recovering journal
systemd-fsck[258]: /dev/sdb2: clean, <files and block count>
systemd-fsck[253]: /dev/sdb1: recovering journal
systemd-fsck[253]: /dev/sdb1: clean, <files and block count>
Welcome to emergency mode! After loggin in type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot inot default mode.
Give root password for maintenance
(or type Control-D to continue):

Not sure what that means, or what I'm looking for in the logs.

as a result of my mobo and cpu change, has something gone fubar? Should I have done a fresh install?

--nixIT

Last edited by jasonwryan (2013-10-21 20:22:12)

drcouzelis · 2013-10-20 12:53:52

It looks like your computer experienced a hard shutdown. Does it still show that message every time you boot?

nixIT · 2013-10-20 13:49:49

yes it does, I'm not sure what to do to fix it, besides a fresh install.

anyway to get the system back to booting order?

Is there any info I can provide that can assist in this?

cfr · 2013-10-21 00:40:08

Well what do the logs say? The fact that the journal is recovered on its own is not enough to dump you in emergency mode. I've seen those messages bunches of times (my laptop had a habit of shutting off in the dirtiest possible manner on a regular basis at one point) but I never got dumped to emergency mode as a result. There must be something further wrong - maybe the journal can't be recovered, maybe other issues with the file system or something else altogether. It's giving you the command - did you run it?

nixIT · 2013-10-21 02:31:52

cfr wrote:

Well what do the logs say? The fact that the journal is recovered on its own is not enough to dump you in emergency mode. I've seen those messages bunches of times (my laptop had a habit of shutting off in the dirtiest possible manner on a regular basis at one point) but I never got dumped to emergency mode as a result. There must be something further wrong - maybe the journal can't be recovered, maybe other issues with the file system or something else altogether. It's giving you the command - did you run it?

I did, and to tell you the truth, I'm not sure what to look for.

I may just do what I normally do on a hardware swap...reinstall, just to make sure it's all clean and not lingering "ghosts"

I appreciate your help.

cfr · 2013-10-21 20:03:05

Why don't you post the output of the command, then?

nixIT · 2013-10-21 20:17:02

cfr wrote:

Why don't you post the output of the command, then?

This may be dumb, but since that system is unbootable, I'm not sure how to get the output posted.

Either way, I spent the 40 minutes over lunch re-installing Arch, so far it's working flawlessly while SSH'd in.

Thanx for your help.

--nixIT

jasonwryan · 2013-10-21 20:21:47

Please don't use [Closed], it denotes a locked thread. I have changed it to Resolved.

nixIT · 2013-10-21 20:36:56

roger that, sorry.

Arch Linux

#1 2013-10-20 12:39:11

[Resolved] CPU died, fresh install?

#2 2013-10-20 12:53:52

Re: [Resolved] CPU died, fresh install?

#3 2013-10-20 13:49:49

Re: [Resolved] CPU died, fresh install?

#4 2013-10-21 00:40:08

Re: [Resolved] CPU died, fresh install?

#5 2013-10-21 02:31:52

Re: [Resolved] CPU died, fresh install?

#6 2013-10-21 20:03:05

Re: [Resolved] CPU died, fresh install?

#7 2013-10-21 20:17:02

Re: [Resolved] CPU died, fresh install?

#8 2013-10-21 20:21:47

Re: [Resolved] CPU died, fresh install?

#9 2013-10-21 20:36:56

Re: [Resolved] CPU died, fresh install?

Board footer