Reindl Harald wrote (on Fri 07-Apr-2012 at 18:51 +0100):
> Am 07.04.2012 19:45, schrieb 'Chris Hall':
> > Unfortunately, this has not helped. The /dev/md0 came up with
> > just one half running. All the stuff in the /var/log/messages which
> > appears rel
T.C. Hollingsworth wrote (on Sat 07-Apr-2012 at 18:02 +0100):
> > Can anybody point be in the direction of what is going on here,
> > and how I may be able to restore some stability to my Fedora 16
> > installation, which is currently falling over about once a day at
> > random.
> Well, the r
Reindl Harald wrote (on Sat 07-Apr-2012 at 16:22 +0100):
> Am 07.04.2012 17:10, schrieb 'Chris Hall':
> >
> > I have a /home partition which is set up as a Software RAID1,
> > using /dev/md0.
> >
> > When I reboot the /dev/md0 fails to come up cleanly.
So the dbus daemon appears to be a busy little bee... but the buzzing noise is
getting on my nerves. I see a lot of this stuff in /var/log/messages:
Apr 7 15:49:49 hestia dbus[1024]: [system] Activating service
name='org.freedesktop.PackageKit' (using servicehelper)
Apr 7 15:49:49 hestia dbu
I have a /home partition which is set up as a Software RAID1, using /dev/md0.
When I reboot the /dev/md0 fails to come up cleanly. So far it has come back
each time, but nearly every time it comes up with one of the two members of the
RAID array missing. I can mdadm /dev/md0 --re-add /dev/sdb
Having recently installed Fedora 16, replacing Fedora 14, I am now plagued by
the thing spontaneously falling into "Emergency Mode"... "Welcome to Emergency
Mode" ha ha !
The last things in /var/log/messages are:
Apr 7 14:55:54 hestia systemd[1]: Job dev-sdb5.device/start timed out.
Apr 7 14:
Tom Horsley wrote (on Wed 04-Apr-2012 at 12:57 +0100):
> On Wed, 4 Apr 2012 12:41:59 +0100 'Chris Hall' wrote:
>
> > There is clearly a mechanism for this, since an upgrade (rather
> > than a clean install) appears to do it. But it seems to be
> > buried many l
Andrew Haley wrote (on 04-Apr-2012 at 09:55 +0100):
...
> It's because in the old scheme when a machine had several ports the
> mapping between the physical hardware and the dev nodes was not
> fixed:
> the kernel would just assign names as it found interfaces. This
> caused a fair bit of inconven
Tom Horsley wrote (on 03-Apr-2012 at 22:15 +0100):
> On Tue, 3 Apr 2012 21:48:49 +0100 'Chris Hall' wrote:
>
> > More important. Somebody has killed my eth0. It's gone. "Device
> > eth0 does not seem to be present..." I cannot find it anywhere.
&
Once upon a time I was happy with Fedora 14.
Then my hard disc crashed, and I thought that was an opportune moment to move
up to Fedora 16.
Big mistake. Huge.
Cannot stand the new Gnome. So I'm trying KDE.
More important. Somebody has killed my eth0. It's gone. "Device eth0 does
not seem
10 matches
Mail list logo
