Why these LINUX machines are setup the way they are is a mystery to me. As part of the lab exercise I used XCAT to provision the machines..
Following what Rick said I was able to boot the failing machine.. I don't know what to do next, but it is booted. On Mon, Dec 21, 2015 at 6:45 PM, Rick Troth <r...@casita.net> wrote: > On 12/16/2015 09:45 AM, Tom Huegel wrote: > > 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: > > Nothin. > No partitions. (More significantly, no disks at all.) > > I didn't see it mentioned, but if the two systems use the same device > addresses then you might be able to boot from the good system. > Guessing that the INITRD is shot. So ... > > #cp link good 100 500 rr > #cp ipl 500 clear > > ... and the INITRD there will have the needed modules and startup magic > to "see" your 100 disk. You do not need R/W access to the link. It > should not try to mount that disk (or a partition thereof) as root. > You're only using the bootstrap, the IPL text. > > -- R; <>< > > ---------------------------------------------------------------------- > 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/
