Re: Linux in an LPAR - recovery?

2007-01-12 Thread Post, Mark K
As others have found out to their dismay, no, it doesn't.  Sounds like a
good subject for an RFE to me.


Mark Post 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Tim Hare
Sent: Friday, January 12, 2007 11:00 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux in an LPAR - recovery?

Not running mkinitrd and zipl is most likely my problem...  I'm tied up
(again) with z/OS stuff but when I get a chance I'll pursue that avenue
of investigation.

I added the devices using YAST - does it not do these two steps?


Tim Hare
Senior Systems Programmer
Florida Department of Transportation

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Linux in an LPAR - recovery?

2007-01-12 Thread Tim Hare
Not running mkinitrd and zipl is most likely my problem...  I'm tied up
(again) with z/OS stuff but when I get a chance I'll pursue that avenue of
investigation.

I added the devices using YAST - does it not do these two steps?


Tim Hare
Senior Systems Programmer
Florida Department of Transportation
(850) 414-4209

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Linux in an LPAR - recovery?

2007-01-11 Thread Eric Chevalier

Tim Hare wrote:

My Linux LPAR was dormant for a couple of weeks at least, no one logging
on (since I'm the only user and I had other things to do). The guy who
does our IODF needed to make changes to make my Linux disks visible to the
z/OS LPAR (offline, but we'll need to see them to move them with FDRPAS
later this month).  Somewhere in there (I didn't do it) someone did
'Deactivate' of the Linux LPAR from the HMC and now when I try to load it,
I get messages about my filesystems having problems and it doesn't come up
normally..


We had an experience some months ago that seems seems eerily similar to
yours, but under somewhat different circumstances...

We had a z800 at the time, running a z/OS sysplex on several LPARs,
along with a VM LPAR with Debian running as a VM guest. Debian boots off
a VM Mimidisk, but we also had filesystem mounted on a dedicated drive.
For some reason I can't remember, we made some changes to the z800 that
required a power-on-reset. When the system came back up, we couldn't
boot Debian. We wound up having to reinstall Debian onto that boot
drive, but the filesystem on the dedicated drive was intact.
(Fortunately, that file system had most of our critical data!)

Eric Chevalier

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Linux in an LPAR - recovery?

2007-01-11 Thread John Schnitzler Jr
>My Linux LPAR was dormant for a couple of weeks at least, no one logging
>on (since I'm the only user and I had other things to do). The guy who
>does our IODF needed to make changes to make my Linux disks visible to the
>z/OS LPAR (offline, but we'll need to see them to move them with FDRPAS
>later this month).  Somewhere in there (I didn't do it) someone did
>'Deactivate' of the Linux LPAR from the HMC and now when I try to load it,
>I get messages about my filesystems having problems and it doesn't come up
>normally..

>Is this one of those situations where I will need to use the install CD as
>a 'recovery system'? I could just install SLES10 from scratch (this was
>SLES9) but I had such a "fun time" using my z/OS system FTP server as the
>source for the install I thought it would be nice to use the z/Linux
>system this time..

What is the actual message you are getting. With sles9 if you have added
dasd after the initial install
and you didn't run mkinitrd and zipl after adding the dasd you will a
similar error but the system will
come up. In this case go into your /etc/fstab and comment out the devices
that you can't find, reboot and if
you come up OK, go back and define the missing devices, run mkinitrd and
zipl, reboot and hope.

john

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Linux in an LPAR - recovery?

2007-01-11 Thread Post, Mark K
As Jeremy stated, we would need some more information.  If the system is
asking you to enter maintenance mode and run fsck (whether for ext2/ext3
or reiserfs), go ahead and try that first.  If the file system(s) that
is/are damaged is _not_ your root file system, you could try removing
them from /etc/fstab (make a backup first) and then rebooting.  Once
you're up, you could run the fsck, then mount them to see if you lost
anything.  (Although if you did, you'll get that clue during the fsck
itself.  Lots of ugly messages, etc.)

Also, what file system were you using?  If the system really was
dormant, and you were using a journaled file system, I would not have
expected this problem to happen.  It should have be able to replay the
journal and come right back up.


Mark Post

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Tim Hare
Sent: Thursday, January 11, 2007 11:37 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Linux in an LPAR - recovery?

My Linux LPAR was dormant for a couple of weeks at least, no one logging
on (since I'm the only user and I had other things to do). The guy who
does our IODF needed to make changes to make my Linux disks visible to
the z/OS LPAR (offline, but we'll need to see them to move them with
FDRPAS later this month).  Somewhere in there (I didn't do it) someone
did 'Deactivate' of the Linux LPAR from the HMC and now when I try to
load it, I get messages about my filesystems having problems and it
doesn't come up normally..

Is this one of those situations where I will need to use the install CD
as a 'recovery system'? I could just install SLES10 from scratch (this
was
SLES9) but I had such a "fun time" using my z/OS system FTP server as
the source for the install I thought it would be nice to use the z/Linux
system this time..

Tim Hare
Senior Systems Programmer
Florida Department of Transportation

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Linux in an LPAR - recovery?

2007-01-11 Thread Jeremy Warren
Here it comes..
Wait for it...
"It depends..."


What exactly are the messages you are getting?  Sometimes it's a simple as
letting it come up borked and then running the appropriate filesystem
repair tool (e2fsck, etc) with the right switches, rebooting again, and
all is well.





Tim Hare <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port 
01/11/2007 11:36 AM
Please respond to
Linux on 390 Port 


To
LINUX-390@VM.MARIST.EDU
cc

Subject
[LINUX-390] Linux in an LPAR - recovery?






My Linux LPAR was dormant for a couple of weeks at least, no one logging
on (since I'm the only user and I had other things to do). The guy who
does our IODF needed to make changes to make my Linux disks visible to the
z/OS LPAR (offline, but we'll need to see them to move them with FDRPAS
later this month).  Somewhere in there (I didn't do it) someone did
'Deactivate' of the Linux LPAR from the HMC and now when I try to load it,
I get messages about my filesystems having problems and it doesn't come up
normally..

Is this one of those situations where I will need to use the install CD as
a 'recovery system'? I could just install SLES10 from scratch (this was
SLES9) but I had such a "fun time" using my z/OS system FTP server as the
source for the install I thought it would be nice to use the z/Linux
system this time..

Tim Hare
Senior Systems Programmer
Florida Department of Transportation
(850) 414-4209

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Linux in an LPAR - recovery?

2007-01-11 Thread Tim Hare
My Linux LPAR was dormant for a couple of weeks at least, no one logging
on (since I'm the only user and I had other things to do). The guy who
does our IODF needed to make changes to make my Linux disks visible to the
z/OS LPAR (offline, but we'll need to see them to move them with FDRPAS
later this month).  Somewhere in there (I didn't do it) someone did
'Deactivate' of the Linux LPAR from the HMC and now when I try to load it,
I get messages about my filesystems having problems and it doesn't come up
normally..

Is this one of those situations where I will need to use the install CD as
a 'recovery system'? I could just install SLES10 from scratch (this was
SLES9) but I had such a "fun time" using my z/OS system FTP server as the
source for the install I thought it would be nice to use the z/Linux
system this time..

Tim Hare
Senior Systems Programmer
Florida Department of Transportation
(850) 414-4209

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390