Folks, I'm installing SLES9 under z/VM 4.4. When transfering the Installation System via FTP, I don't get what I would expect or what the SuSE doc seems to indicate I should get for byte counts.
I ftp from a VM Linux guest to other which has copies the SLES9 ISOs. A dir of boot/ shows: dir >>>PORT 10,100,4,13,4,84 200 PORT command successful. Consider using PASV. >>>LIST 150 Here comes the directory listing. -r--r--r-- 1 0 0 77 Jul 06 2004 directory.yast -r--r--r-- 1 0 0 12361298 Jul 06 2004 initrd -r--r--r-- 1 0 0 4 Jul 06 2004 initrd.siz dr-xr-xr-x 2 0 0 2048 Jul 06 2004 loader -r--r--r-- 1 0 0 62 Jul 06 2004 parmfile -r--r--r-- 1 0 0 16898549 Jun 21 2004 rescue -r--r--r-- 1 0 0 54779904 Jul 06 2004 root -r--r--r-- 1 0 0 143 Jul 06 2004 suse.ins -r--r--r-- 1 0 0 4556148 Jul 06 2004 tapeipl.ikr -r--r--r-- 1 0 0 4556148 Jul 06 2004 vmrdr.ikr When I do gets for parmfile (62 bytes), initrd (12361298 bytes) and vmrdr.ikr (4556148 bytes) ftp shows that is receives 64 bytes, 12361360 bytes, and 4556160 bytes respectively. They differ. In the SuSE doc, the counts match. Later on, when I run the SLES9 EXEC to IPL the Installation System, the IPL eventually fails with a crc error and a Kernel panic: md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. RAMDISK: Compressed image found at block 0 crc error Kernel panic: VFS: Unable to mount root fs on ram1 HCPGIR450W CP entered; disabled wait PSW 000A0000 80442B6A Anyone encounter this sort of thing before? Thanks Dave Froberg ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
