Like I mentioned earlier this is not production system that is down. It is just a lab system that can be re-installed easily. It would be nice to have some idea of what killed it in the first place. Using DITTO I was visually trying to compare the DASD from the working and nonworking systems, but that was inconclusive. If I get a chance later I'll write a quick PIPE to do trackreads and compare the two disks, maybe that'll show something. Thanks for all of the tips and comments. Tom
On Thu, Dec 17, 2015 at 6:14 AM, Jonathan Quay <jonathan.q...@ihg.com> wrote: > Isn't it complaining about not finding the root filesystem, not about not > finding the /boot filesystem? I would take a look at that partition in > question that it can't find. > > ---------------------------------------------------------------------- > 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/
