Not to state the obvious, but the “kernel command line”  is telling the kernel 
loader that it will find a root file system and a loadable kernel image at
"/dev/disk/by-path/ccw-0.0.0100-part2” 
However when it tries to read it, either it can’t access the device or it isn’t 
finding the “IPLTEXT” (for want of a better term).

> Kernel command line: root=/dev/disk/by-path/ccw-0.0.0100-part2 rd_NO_LUKS
> LANG=en_US.UTF-8  KEYTABLE=us rd_NO_MD SYSFONT=latarcyrheb
> -sun16  rd_DASD=0.0.0100 rd_NO_LVM rd_NO_DM
> BOOT_IMAGE=0

Blah, blah, blah…

> 
> VFS: Cannot open root device "disk/by-path/ccw-0.0.0100-part2" or
> unknown-block(0,0)
blah, blah, blah, 

Kind of like you told CP to “ipl <address>” and there was nothing “ipl-able” at 
<address>

WAGs:
Transitory disk error or pregnant pause while trying to read the device?  (Try 
re-booting a couple of more times, keeping an eye out for DASD errors??  “Thank 
you for calling Microsoft support…")
Somebody sharing the device that is supposed to hold your kernel?  (oh were YOU 
using that disk?, I saved my grandma’s fruitcake recipe there)
Something “interesting” happened during the “yum update” and the kernel image 
wasn’t properly updated.   
        “Just check the yum logs”
        “If the system would boot so I could see the logs, I wouldn’t need to 
check the yum logs, now would I?”
        “Thank you for calling Linux support, is there anything else I can help 
you with today?”
        <click>

Actually you COULD allocate the disk that is supposed to contain the root file 
system on the failing system to the instance that is working, mount it and poke 
around,
but it doesn’t sound like this system is worth that much work and your time 
would be better spent on last minute Christmas shopping. :O


Tom Anderson
Ex ignorantia ad sapientiam
e tenebris ad lucem!

> On Dec 16, 2015, at 7:44 AM, Tom Huegel <tehue...@gmail.com> wrote:
> 
> Here is the whole console log.
> In the mean time I am attributing it to global warming.
> 
> 
> 
> CP I
> 100
> 
> Booting default
> (2.6.32-573.8.1.el6.s390x)
> 
> Initializing cgroup subsys
> cpuset
> 
> Initializing cgroup subsys
> cpu
> 
> Linux version 2.6.32-573.8.1.el6.s390x (
> mockbu...@s390-003.build.bos.redhat.com) (gcc version 4.4.7 20120313 (Red
> Hat 4.4.7-16) (GCC
> ) ) #1 SMP Fri Sep 25 19:21:49 EDT
> 2015
> 
> setup: Linux is running as a z/VM guest operating system in 64-bit
> mode
> crashkernel=auto resulted in zero bytes of reserved
> memory.
> 
> Zone PFN
> ranges:
> 
>  DMA      0x00000000 ->
> 0x00080000
> 
>  Normal   0x00080000 ->
> 0x00080000
> 
> Movable zone start PFN for each
> node
> 
> early_node_map[1] active PFN
> ranges
> 
>    0: 0x00000000 ->
> 0x00080000
> 
> PERCPU: Embedded 12 pages/cpu @0000000002b00000 s19456 r8192 d21504
> u65536
> pcpu-alloc: s19456 r8192 d21504 u65536
> alloc=16*4096
> 
> pcpu-alloc: [0] 00 [0] 01 [0] 02 [0] 03 [0] 04 [0] 05 [0] 06 [0]
> 07
> pcpu-alloc: [0] 08 [0] 09 [0] 10 [0] 11 [0] 12 [0] 13 [0] 14 [0]
> 15
> pcpu-alloc: [0] 16 [0] 17 [0] 18 [0] 19 [0] 20 [0] 21 [0] 22 [0]
> 23
> pcpu-alloc: [0] 24 [0] 25 [0] 26 [0] 27 [0] 28 [0] 29 [0] 30 [0]
> 31
> pcpu-alloc: [0] 32 [0] 33 [0] 34 [0] 35 [0] 36 [0] 37 [0] 38 [0]
> 39
> pcpu-alloc: [0] 40 [0] 41 [0] 42 [0] 43 [0] 44 [0] 45 [0] 46 [0]
> 47
> pcpu-alloc: [0] 48 [0] 49 [0] 50 [0] 51 [0] 52 [0] 53 [0] 54 [0]
> 55
> pcpu-alloc: [0] 56 [0] 57 [0] 58 [0] 59 [0] 60 [0] 61 [0] 62 [0]
> 63
> 
> 
> 
> HOLDING   SCZVMLX2
> Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
> 517120
> Kernel command line: root=/dev/disk/by-path/ccw-0.0.0100-part2 rd_NO_LUKS
> LANG=en_US.UTF-8  KEYTABLE=us rd_NO_MD SYSFONT=latarcyrheb
> -sun16  rd_DASD=0.0.0100 rd_NO_LVM rd_NO_DM
> BOOT_IMAGE=0
> 
> PID hash table entries: 4096 (order: 3, 32768
> bytes)
> 
> Dentry cache hash table entries: 262144 (order: 9, 2097152
> bytes)
> Inode-cache hash table entries: 131072 (order: 8, 1048576
> bytes)
> Memory: 2048224k/2097152k available (5118k kernel code, 0k reserved, 3531k
> data, 260k init)
> Write protected kernel read-only data: 0x100000 -
> 0x7fffff
> 
> Hierarchical RCU
> implementation.
> 
> console [ttyS0]
> enabled
> 
> allocated 8388608 bytes of
> page_cgroup
> 
> please try 'cgroup_disable=memory' option if you don't want memory
> cgroups
> pid_max: default: 65536 minimum:
> 512
> 
> Security Framework
> initialized
> 
> SELinux:
> Initializing.
> 
> Mount-cache hash table entries:
> 256
> 
> Initializing cgroup subsys
> ns
> 
> Initializing cgroup subsys
> cpuacct
> 
> Initializing cgroup subsys
> memory
> 
> Initializing cgroup subsys
> devices
> 
> Initializing cgroup subsys
> freezer
> 
> Initializing cgroup subsys
> net_cls
> 
> Initializing cgroup subsys
> blkio
> 
> Initializing cgroup subsys
> perf_event
> 
> Initializing cgroup subsys
> net_prio
> 
> 
> 
> 
> HOLDING   SCZVMLX2
> cpu: 1 configured CPUs, 0 standby
> CPUs
> 
> cpu: Processor 0 started, address 0, identification
> 1B6ED6
> 
> Brought up 1
> CPUs
> 
> devtmpfs:
> initialized
> 
> regulator: core version
> 0.5
> 
> NET: Registered protocol family
> 16
> 
> bio: create slab <bio-0> at
> 0
> 
> NetLabel:
> Initializing
> 
> NetLabel:  domain hash size =
> 128
> 
> NetLabel:  protocols = UNLABELED
> CIPSOv4
> 
> NetLabel:  unlabeled traffic allowed by
> default
> 
> Switching to clocksource
> tod
> 
> NET: Registered protocol family
> 2
> 
> IP route cache hash table entries: 65536 (order: 7, 524288
> bytes)
> TCP established hash table entries: 65536 (order: 8, 1048576
> bytes)
> TCP bind hash table entries: 65536 (order: 8, 1048576
> bytes)
> 
> TCP: Hash tables configured (established 65536 bind
> 65536)
> 
> TCP reno
> registered
> 
> NET: Registered protocol family
> 1
> 
> futex hash table entries: 4096 (order: 8, 1048576
> bytes)
> 
> audit: initializing netlink socket
> (disabled)
> 
> type=2000 audit(1450280489.672:1):
> initialized
> 
> HugeTLB registered 1 MB page size, pre-allocated 0
> pages
> 
> VFS: Disk quotas
> dquot_6.5.2
> 
> Dquot-cache hash table entries: 512 (order 0, 4096
> bytes)
> 
> 
> 
> 
> HOLDING   SCZVMLX2
> msgmni has been set to
> 4001
> 
> ksign: Installing public key
> data
> 
> Loading
> keyring
> 
> - Added public key
> E5A322A2BCB59BD8
> 
> - User ID: Red Hat, Inc. (Kernel Module GPG
> key)
> 
> - Added public key
> D4A26C9CCD09BEDA
> 
> - User ID: Red Hat Enterprise Linux Driver Update Program <
> secal...@redhat.com>
> - Added public key
> CB445E0DA3EA1F65
> 
> - User ID: Red Hat Enterprise Linux Driver Update Program (key 4) <
> secal...@redhat.com>
> Block layer SCSI generic (bsg) driver version 0.4 loaded (major
> 253)
> io scheduler noop
> registered
> 
> io scheduler anticipatory
> registered
> 
> io scheduler deadline
> registered
> 
> io scheduler cfq registered
> (default)
> 
> brd: module
> loaded
> 
> loop: module
> loaded
> 
> cio: Channel measurement facility initialized using format extended (mode
> autodetected)
> GRE over IPv4 demultiplexor
> driver
> 
> TCP cubic
> registered
> 
> Initializing XFRM netlink
> socket
> 
> NET: Registered protocol family
> 17
> 
> registered taskstats version
> 1
> 
> Initalizing network drop monitor
> service
> 
> md: Waiting for all devices to be available before
> autodetect
> 
> md: If you don't use raid, use
> raid=noautodetect
> 
> 
> 
> 
> HOLDING   SCZVMLX2
> md: Autodetecting RAID
> arrays.
> 
> md: Scanned 0 and added 0
> devices.
> 
> md: autorun
> ...
> 
> md: ... autorun
> DONE.
> 
> VFS: Cannot open root device "disk/by-path/ccw-0.0.0100-part2" or
> unknown-block(0,0)
> Please append a correct "root=" boot option; here are the available
> partitions:
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
> CPU: 0 Not tainted 2.6.32-573.8.1.el6.s390x
> #1
> 
> Process swapper (pid: 1, task: 000000007fe83370, ksp:
> 000000007fe8b958)
> 
> 000000007fe8bd20 000000007fe8bca0 0000000000000002
> 0000000000000000
> 
>       000000007fe8bd40 000000007fe8bcb8 000000007fe8bcb8
> 00000000004f7108
>       0000000000000011 0000000000000000 000000007eb63000
> 000003d281bb7da8
>       000000000000000d 000000000000000c 000000007fe8bd10
> 0000000000000000
>       0000000000000000 000000000010582c 000000007fe8bca0
> 000000007fe8bce0
> Call
> Trace:
> 
> ([<000000000010572c>]
> show_trace+0xe8/0x138)
> 
> [<00000000004f6f42>]
> panic+0xde/0x250
> 
> [<00000000008744c2>]
> mount_block_root+0x292/0x33c
> 
> [<00000000008747d6>]
> prepare_namespace+0x1e2/0x220
> 
> [<0000000000873890>]
> kernel_init+0x464/0x47c
> 
> [<000000000010a746>]
> kernel_thread_starter+0x6/0xc
> 
> [<000000000010a740>]
> kernel_thread_starter+0x0/0xc
> 
> HCPGIR450W CP entered; disabled wait PSW 00020001 80000000 00000000
> 001156BA
> 
> 
> 
> 
> 
> 
> 
> RUNNING   SCZVMLX2
> 
> 
> On Wed, Dec 16, 2015 at 7:35 AM, Gregg Levine <gregg.drw...@gmail.com>
> wrote:
> 
>> Hello!
>> Actually Alan you're thinking of why hundreds of satellites ignored
>> yesterday.
>> 
>> Actually it looks like that penguin ignored the root setting for
>> things. First time I've seen one that revolting.
>> 
>> Is it possible to see the log entries before that first line?
>> -----
>> Gregg C Levine gregg.drw...@gmail.com
>> "This signature fought the Time Wars, time and again."
>> 
>> 
>> On Wed, Dec 16, 2015 at 10:19 AM, Alan Altmark <alan_altm...@us.ibm.com>
>> wrote:
>>> On Wednesday, 12/16/2015 at 02:48 GMT, Tom Huegel <tehue...@gmail.com>
>>> wrote:
>>>> Now the registered machine fails to boot, the other one works fine.
>>> 
>>> A gamma ray collided with a 1 and knocked it over, turning it into a 0.
>>> That's the only explanation I can think of.  I used to think it was
>>> sunspots or coronal mass ejections, but I've moved on.
>>> 
>>> Alan Altmark
>>> 
>>> Senior Managing z/VM and Linux Consultant
>>> Lab Services System z Delivery Practice
>>> IBM Systems & Technology Group
>>> ibm.com/systems/services/labservices
>>> office: 607.429.3323
>>> mobile; 607.321.7556
>>> alan_altm...@us.ibm.com
>>> IBM Endicott
>>> 
>>> ----------------------------------------------------------------------
>>> For LINUX-390 subscribe / signoff / archive access instructions,
>>> send email to lists...@vm.marist.edu 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/
>> 
>> ----------------------------------------------------------------------
>> For LINUX-390 subscribe / signoff / archive access instructions,
>> send email to lists...@vm.marist.edu 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/
>> 
> 
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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/
> 

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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