The SAN's working now. The SAN guys had to grant us access. sciload was putting out the 'unknown partition table' but there was no way for us to re-partition it as you suggest. We still had no access. For what it's worth we did attempt to run fdisk but fdisk did not put out any error messages. The SAN guys gave us a brand new LUN. They wouldn't let us share. Fear of Linux. In their defense the True 64 boxes can't share and Linux is still an unknown to them. Thanks to all for their input!
> >We are attempting have LINUX/390 use an EMC SAN. > >scsiload puts out a message about an 'unknown partition table' > >Are other folks using EMC SYMMETRIC successfully? Is there doc anywhere > >on > >how to configure the EMC SAN for LINUX/390? > > Unknown partition table simply means that your kernel was unable to > recognize any partitions on the disk. Usually means that you did not > build the kernel with the partition scheme found on the disk. For > example, the disk may have been formerly used on SUN or IA64 system and > could contain a Solaris or GPT partition scheme. Happens when you get > drives that have not been wiped clean. Fdisk only understands a few > partition schemes. I can probably tell you what is on the disk if you > send me some of the first tracks of the disk ... > > Lets see ... fdisk said ... > > >Disk /dev/sda: 1 heads, 15 sectors, 1024 cylinders > >Units = cylinders of 15 * 512 bytes > > Weird ... 1 head ... must be the emc controller producing a contrived track > geometry ... you would ... dd if=/dev/sda of=sda.tracks bs=512 > count=60 ... this will give you the 1st 4 tracks which you can send the > file sda.tracks to [EMAIL PROTECTED] > > In the meantime ... if you don't care about what is on this disk ... then > ... just go ahead and repartition it. > > -Don
