Hello all,

This is kind of a strange one but we've about run out of things to look
at.  The two servers having boot problems are:

Psuedo Name: SUSE Linux Enterprise Server 10 (s390x)
Rev: 4
Kernel 2.6.16.60-0.103.1-default
Machine: s390x

and we have the disks being SRDF'd to a remote datacenter.  We have
hundreds of servers that we are SRDF'g too and they have not seen this
issue.

SRDF is suspended and the remote disks are R/W to the host.

When the server starts up in the remote side, we see the usual preamble of:

15:36:14 Starting
udevd

Creating
devices

15:36:14 Loading
scsi_mod

SCSI subsystem
initialized

Loading
sd_mod

Loading
dasd_mod

15:36:14 Loading
dasd_diag_mod

Loading
dasd_fba_mod

Loading
dasd_eckd_mod

Loading
scsi_transport_fc

Loading
qdio

15:36:14 qdio: loading QDIO base support version
2
Loading
zfcp

Activating DASDs: 0.0.01b0:0dasd(eckd): 0.0.01b0: PSF-SSC on storage
subsystem EMC.080000000AGRDK.ca01 returned rc=0
dasd(eckd): 0.0.01b0: 3390/0C(CU:3990/01) Cyl:150 Head:15
Sec:224
dasd(eckd): 0.0.01b0: (4kB blks): 108000kB at 48kB/trk compatible disk
layout
 dasda:VOL1/  0X01B0:
dasda1

 0.0.01b1:0dasd(eckd): 0.0.01b1: PSF-SSC on storage subsystem
EMC.080000000AGRDK.c001 returned rc=0
dasd(eckd): 0.0.01b1: 3390/0C(CU:3990/01) Cyl:730 Head:15
Sec:224
dasd(eckd): 0.0.01b1: (4kB blks): 525600kB at 48kB/trk compatible disk
layout
 dasdb:VOL1/  0XDA11:
dasdb1


.... more ...
.... goes into zfcp configuration ...
.... then ...

Loading jbd
Loading
ext3
Waiting for device /dev/disk/by-path/ccw-0.0.01b1-part1 to appear:
ok
rootfs: major=94 minor=5
devn=24069
/dev/disk/by-path/ccw-0.0.01b1-part1: unknown volume
type
invalid root filesystem -- exiting to /bin/sh

We have no clue how/why this 1b1 disk (which is root) will simply not
work.  Some things we've tried:

- Mount the disk on another server; looks fine, files/directories all
there; fsck clean
- Created a new disk, dasdfmt/fdasd/mkfs ext3, then copied all the files
from the orig disk to the new disk - still FAILED
- Used PIPEDDR to copy the original system's 1b1 disk to the remote system
- still FAILED
- Tried booting from a working server's 1b0 - still FAILED
- Tried booting using the working server's 1b1 - WORKED

Something is up with that 1b1 but I can't even begin to know what to look
for.  It seems like it has to be some file on the disk b/c creating a brand
new disk didn't help any.

Anyone have any ideas?  THANKS!


-- *James Vincent*

----------------------------------------------------------------------
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 more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to