You are not logged in.

#1 2011-06-30 02:37:23

yvonney
Member
Registered: 2008-06-11
Posts: 671

systemd + systemd-arch-units massive fsck errors BROKEN after all fix

should I just go ahead and reinstall my entire system?
Don't know which logs to post or if I've simply wrecked the system while fsck fixing hundred of errors.
I'm ok with redoing it all as it's been brilliant running full testing for many seasons.


[errors after massive fsck errors all fixed with tons of lost files]
happens just after grub menu: 1 second flash of 2 lines:
"error: out of partition"
"error: no suitable command found"

happens  bootup: unable to do much at prompt
"unknown teminal "linux"

happens during bootup after udev rules loading

"syslog-ng line 7 command not found"

Figuring it's to do with today's systemd and systemd-arch-units and my particular system.

I posted here which may have been the wrong spot anyways.
https://bbs.archlinux.org/viewtopic.php?id=96316&p=33
so real sorry about what may constitute poor posting judgment. Just a bit desperate
for then next hour until I wipe my system if I can't hobble back to being able to run.

won't do much now except boot up with errors note above.

Last edited by yvonney (2011-06-30 02:37:58)

Offline

#2 2011-06-30 02:42:33

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,111
Website

Re: systemd + systemd-arch-units massive fsck errors BROKEN after all fix

There was no systemd update today. syslog-ng and a new units package were pushed from testing into core. I tested them on multiple machines before they even went into testing.

I don't mean this to be a copout, but this sounds unrelated to any updates at all. Your hard drive is barfing, hard.

Offline

#3 2011-06-30 03:25:05

yvonney
Member
Registered: 2008-06-11
Posts: 671

Re: systemd + systemd-arch-units massive fsck errors BROKEN after all fix

thanks! um, reading this from the dev feed.
maybe I'm not running this testing package.
errr, perhaps if I could find it and install it (though I tried to reinstall systemd and it complained about another package.. pls I seem to not 'quite be able to startx due to my keymap being manged.


All good really as the last TWO times I moved my system I literally simply copied all the files from one volume to another then tweeked and added a few folders, like the ones that are created upon boot like /dev and voila!  no probs...


though I always knew that my mediocraty would get me eventually!


woohoo!


ok, so no easy fix?  that would allow my to save some databases better than simple copies.

thanks again. 

On Tue, Jun 28, 2011 at 11:08 AM, Andreas Radke <a.radke@arcor.de> wrote:
> Am Tue, 28 Jun 2011 10:33:19 -0400
> schrieb Dave Reisner <d@falconindy.com>:
>
>> syslog-ng 3.2.4-2 is in [testing]. It's a rebuild with the following
>> changes:
>>
>> * add --enable-systemd flag to ./configure
>> * add upstream patch to fix socket acitvation for systemd
>> * package upstream syslog-ng.service
>>

Offline

Board footer

Powered by FluxBB