> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
> Mark Post
> Sent: Tuesday, April 15, 2008 10:18 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: CentOS 4.4 kernel panic on boot s390x
>
> >>> On Tue, Apr 15, 2008
>>> On Tue, Apr 15, 2008 at 11:03 AM, in message
<[EMAIL PROTECTED]>, "Kelly F.
Hickel" <[EMAIL PROTECTED]> wrote:
-snip-
> That explains something, although fdasd doesn't think there are
> partition tables either, I just tried again though, and I can still do a
> "normal" load from DASD address D
> >>> On Tue, Apr 15, 2008 at 7:55 AM, in message
> <[EMAIL PROTECTED]>,
> "Kelly F.
> Hickel" <[EMAIL PROTECTED]> wrote:
> > Well, I guess that I'm out of luck. It says that there are no valid
> > partition tables on any of my devices, I have no idea how that could
> > have possibly happened, but
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
> Brad Hinson
> Sent: Tuesday, April 15, 2008 8:52 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: CentOS 4.4 kernel panic on boot s390x
>
> I think that message may be mislea
>>> On Tue, Apr 15, 2008 at 7:55 AM, in message
<[EMAIL PROTECTED]>, "Kelly F.
Hickel" <[EMAIL PROTECTED]> wrote:
> Well, I guess that I'm out of luck. It says that there are no valid
> partition tables on any of my devices, I have no idea how that could
> have possibly happened, but I seem to ha
; > 952-345-8677 Office
> > 952-345-8721 Fax
> > [EMAIL PROTECTED]
> > www.mqsoftware.com
> > SEE BUSINESS WORK
> >
> > > -Original Message-
> > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf
> Of
> > > Brad Hins
elly F. Hickel
> Sent: Tuesday, April 15, 2008 6:14 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: RE: CentOS 4.4 kernel panic on boot s390x
>
> Brad,
> That sounds like a great tip, I'll give it a try. I hadn't gone
> past the initial "choose a language" s
TECTED]
www.mqsoftware.com
SEE BUSINESS WORK
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
> Brad Hinson
> Sent: Monday, April 14, 2008 5:10 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: CentOS 4.4 kernel panic on boot s390x
>
>
K
>
>
> > -Original Message-
> > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
> > Justin Payne
> > Sent: Monday, April 14, 2008 3:28 PM
> > To: LINUX-390@VM.MARIST.EDU
> > Subject: Re: CentOS 4.4 kernel panic on boot s390x
> >
alf Of
> Justin Payne
> Sent: Monday, April 14, 2008 3:28 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: CentOS 4.4 kernel panic on boot s390x
>
> Do you see lvm in /usr/sbin?
>
> ~Justin
>
> Kelly F. Hickel wrote:
> > Brad,
> > I don't have any of th
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Brad Hinson
Sent: Monday, April 14, 2008 3:05 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: CentOS 4.4 kernel panic on boot s390x
When inside the rescue environment, run 'lvm'. This is an LVM "shell"
with all the comma
Looks like I was slow on the draw.
Brad++
Brad Hinson wrote:
When inside the rescue environment, run 'lvm'. This is an LVM "shell"
with all the commands you need (pvcreate, vgscan, etc). At the very
least, you can run:
lvm
vgscan
vgchange -a y
to activate the LVM. The vgscan creates the /
half Of
> Brad Hinson
> Sent: Monday, April 14, 2008 3:05 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: CentOS 4.4 kernel panic on boot s390x
>
> When inside the rescue environment, run 'lvm'. This is an LVM "shell"
> with all the commands you need (pvcre
Kelly F. Hickel wrote:
So, I've got this zlinux LPAR on a z9BC, and it's been running CentOS
4.4 for a year or so, and recently it failed to reboot after an IPL.
It lists all the dasd, then says "Activating logical volumes" then
panics with "Kernel panic - not syncing: Attempted to kill init!".
When inside the rescue environment, run 'lvm'. This is an LVM "shell"
with all the commands you need (pvcreate, vgscan, etc). At the very
least, you can run:
lvm
vgscan
vgchange -a y
to activate the LVM. The vgscan creates the /dev nodes, so you don't
need to do that manually. After you exit
So, I've got this zlinux LPAR on a z9BC, and it's been running CentOS
4.4 for a year or so, and recently it failed to reboot after an IPL.
It lists all the dasd, then says "Activating logical volumes" then
panics with "Kernel panic - not syncing: Attempted to kill init!".
I've been able to boot f
16 matches
Mail list logo
