Can't reboot server - not repsonding

[phreaq]

I did a yum update, in hopes of fixing an issue I am having, and one of the updates failed along the way.

It rebooted the server, and now I can't get the HDA Dashboard, or log in thru WinSCP or putty.

Connecting a monitor gives me the following:

Links removed

During reboot I can go into Fedora 19, or an emergency mode, but I don't know what o do there.

Links Removed

any help?

[phreaq]

my pics have been deleted, and I can't upload them as attachments. Not sure what to do here.

[phreaq]

here's my pics again

[phreaq]

what will happen If i run the install cd again?

Will it stomp over all my settings? (fstab, greyhole, installed apps etc.) or will it keep all that?

[bigfoot65]

Yes it will likely make things worse.

Best to try and resolve the current issue.

Have you tried checking the internet? I did a quick search and see this is something that has happened to others with updates. Not specific to Amahi, but the same general principle.

[phreaq]

I can only get into the ...recovery boot option. is that where I should go? (I do see my edited fstab when I go this route)

I've tried:

Code: Select all

yum clean all rpm --rebuilddb

those run without error

Code: Select all

package-cleanup

returns an error

Code: Select all

package-cleanup: command not found

and

Code: Select all

yum check

gives me a few screens worth of items; package_123 is a duplicate with package_123... etc


what else did you see?

[phreaq]

I tried selecting the second entry in the grub menu, and once it boots into emergency mode I tried:

Code: Select all

yum history undo last

it seemed to undo most of it, but fails with:

Code: Select all

Failure: repodata/repomd.xml from amahi...

I suspect it's due to no network connections

[bigfoot65]

Yes that would be the result of no network.

I was going to suggest you check out this article:
http://forums.fedoraforum.org/showthread.php?t=299624

Not sure if it would be helpful, but thought I'd share.

[phreaq]

I don't believe that helped, thanks though.

Do you know how to make the second grub entry the default? it will allow me to boot into it, but only as emergency

[bigfoot65]

I don't, but I do recall seeing something on the internet. Might try there.

Sounds like you might have some real issues that may not be resolvable.

Not sure if booting with a Live CD and disabling extra drives in the /etc/fstab would help.

Maybe use the Live CD to check if the disk needs repair. Just a thought.

Sorry I am not much help.