On Thu, 06 Aug 2015 15:04:10 -0400 (EDT), Cameron Seay wrote:
I have attached 3 mod-9s to a guest where Debian is the OS. Q DASD sees
the new dasd, but of course Debian can't see it until it's in a Linux
filesystem. We don't know how to format it while in Debian.
Any suggestions?
All steps
in debian as far as I remember it was just a matter of adding a new dasd to
zipl.conf , running zipl and that’s it.
Gregory Powiedziuk
On Aug 6, 2015, at 3:17 PM, Mark Post mp...@suse.com wrote:
On 8/6/2015 at 03:04 PM, Cameron Seay cws...@gmail.com wrote:
I have attached 3 mod-9s to a
On 8/6/2015 at 03:04 PM, Cameron Seay cws...@gmail.com wrote:
I have attached 3 mod-9s to a guest where Debian is the OS. Q DASD sees
the new dasd, but of course Debian can't see it until it's in a Linux
filesystem. We don't know how to format it while in Debian.
The same as any other
Isn't dasdfmt, lsdasd, et al there? How did you install Debian? Are
the ibm driver tools installed?Linux should be able to see it as soon
as it's online. You may have to issue chccwdev -e for the disk if it
doesn't happen automatically. cat /proc/partitions should give you some
I have attached 3 mod-9s to a guest where Debian is the OS. Q DASD sees
the new dasd, but of course Debian can't see it until it's in a Linux
filesystem. We don't know how to format it while in Debian.
Any suggestions?
--
For
Can you see them when you do
cat /proc/dasd/devices ?
If not than first bring them online (chccwdev -e 0.0.) and then check
again.
If they are there, than you are ready to do a low level format with dasdfmt
/dev/dasdX (/proc/dasd/devices will tell you which dasdX is that).
After
