Raid on a raid issue

[Jamie Fargen]

Margaret,
You mentioned you had to remove the four original portions from being
mounted  in /etc/fstab? I imagine you did that so the system would start?

Could it just be that the system was in a bad state when you tried to
connect?

On Jul 24, 2014 3:49 PM, "Doll, Margaret Ann" <margaret_doll at brown.edu>
wrote:
>
> The missing network route would be a good guess except that last week,
> samba, ping and ssh were working across from one subnet to another.
>
> I did ask the networking group whether there seemed to be some block
> between the rask, the new computer and my desktop.  Network said there
were
> no blocks.  The connection into rask was just timing out.
>
>
> On Thu, Jul 24, 2014 at 3:43 PM, Jonathan Billings <jsbillin at umich.edu>
> wrote:
>
> > On Thu, Jul 24, 2014 at 11:53 AM, Doll, Margaret Ann <
> > margaret_doll at brown.edu> wrote:
> > >
> > > Is the ssh timeout problem, ping problem and samba problem all caused
by
> > > the raid on raid creation?  The timing of the creation of the new raid
> > > indicates that it is.
> > >
> >
> > Not directly.  Most likely, something else was broken at the same time.
> >  The RAID issue is a red herring.  It sounds to me like your system is
> > reachable from the local subnet but not from other subnets?  That sounds
> > like a missing network route to me.
> >
> >
> > --
> > Jonathan Billings <jsbillin at umich.edu>
> > --
> > redhat-list mailing list
> > unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> > https://www.redhat.com/mailman/listinfo/redhat-list
> >
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list