>>> On 12/16/2015 at 10:35 PM, Thomas Anderson <tp...@speakeasy.net> wrote: > 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>
If there wasn't a kernel and initrd on the 100 disk at the expected location, he wouldn't have gotten nearly as far as he did. Mark Post ---------------------------------------------------------------------- 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/
