Jerry,

The detection messages don't show the new DASD volumes.  Are 3380-3388
configured on to the LPAR?  Does the IODF know about them?

Mark Post

-----Original Message-----
From: Jerry Whitteridge [mailto:jerry.whitteridge@;safeway.com]
Sent: Wednesday, October 23, 2002 2:46 PM
To: [EMAIL PROTECTED]
Subject: Adding DASD not recognized ?


I've been preparing to move my dasd for the linux system to a new
subsystem. This is SuSe linux 2.2.16 running in an LPAR. Original system
is on 16DC (DASDA Swap) 16DA (DASDB root) 16DB (DASDC home). I created a
new boot directory on dasdc, updated parmline to include the new dasd
addresses and ran silo. I then IPL'd from 16DB.  

My plan was to use backups done with the OFFLNLDR tool to restore to the
new dasd. Mount these and edit the parmline file, run silo and then IPL
from the newly added dasd. However following the boot from 16DB I can
see that my parmline changes were read but I do not see the additional
dasd in /proc/dasd/devices. Do I just need to run the dasdfmt for the
new devices (or do the dasd restore) to have them recognized or have I
missed a step in the procedure ? 

I am trying to preserve the original 3 pack system to have as a fall
back incase my move is unsucessfull. 

boot.msg shows 

Inspecting /boot/System.map-2.2.16 
Loaded 5658 symbols from /boot/System.map-2.2.16. 
Symbols match kernel version 2.2.16. 
No module symbols loaded. 
klogd 1.3-3, log source = ksyslog started. 
<4>Linux version 2.2.16 ([EMAIL PROTECTED]) (gcc version 2.95.2 19991024
(release)) #1 SMP Wed Nov 8 10:57:03 GMT 2000 
<4>Command line is:
dasd=16DC,16DA,16DB,3380,3381,3382,3383,3384,3385,3386,3387,3388
root=/dev/dasdb1 noinitrd 
<4>� ro 
<4> 
<4>We are running native 
<4>This machine has an IEEE fpu 
<4>Initial ramdisk at: 0x02000000 (16777216 bytes) 
<4>Detected device E500 on subchannel 0072 - PIM = 80, PAM = 80, POM =
FF 
------- snip devices E501 - E539 
<4>Detected device E540 on subchannel 00AC - PIM = 80, PAM = 80, POM =
FF 
<4>Detected device 16DA on subchannel 27CD - PIM = FF, PAM = 03, POM =
FF 
<4>Detected device 16DB on subchannel 27CE - PIM = FF, PAM = 03, POM =
FF 
<4>Detected device 16DC on subchannel 27CF - PIM = FF, PAM = 03, POM =
FF 
<4>Detected device 16DD on subchannel 27D0 - PIM = FF, PAM = 03, POM =
FF 
<4>Detected device 16DE on subchannel 27D1 - PIM = FF, PAM = 03, POM =
FF 
<4>Subchannel FC80 reports non-I/O subchannel type 0001 
<4>Highest subchannel number detected (hex) : FC80 
<4>SenseID : device E500 reports: CU  Type/Mod = 1731/01, Dev Type/Mod =
1732/01 
-----   snip devices E501 - E539 
<4>SenseID : device E540 reports: CU  Type/Mod = 1731/01, Dev Type/Mod =
1731/01 
<4>SenseID : device 16DA reports: CU  Type/Mod = 3990/EC, Dev Type/Mod =
3390/0A 
<4>SenseID : device 16DB reports: CU  Type/Mod = 3990/EC, Dev Type/Mod =
3390/0A 
<4>SenseID : device 16DC reports: CU  Type/Mod = 3990/EC, Dev Type/Mod =
3390/0A 
<4>SenseID : device 16DD reports: CU  Type/Mod = 3990/EC, Dev Type/Mod =
3390/0A 
<4>SenseID : device 16DE reports: CU  Type/Mod = 3990/EC, Dev Type/Mod =
3390/0A 
<4>Calibrating delay loop... 419.43 BogoMIPS 
<4>Memory: 499864k/524288k available (1136k kernel code, 0k reserved,
6904k data, 0k init) 
<4>Dentry hash table entries: 65536 (order 7, 512k) 
<4>Buffer cache hash table entries: 524288 (order 9, 2048k) 
<4>Page cache hash table entries: 131072 (order 7, 512k) 
<6>debug: 16 areas reserved for debugging information 
<6>debug: reserved 4 areas of 4 pages for debugging ccwcache 
<7>ccwcachedebug area is 0x  17e0a8 
<5>VFS: Diskquotas version dquot_6.4.0 initialized


"WorldSecure Server <safeway.com>" made the following
 annotations on 10/23/02 12:48:49
----------------------------------------------------------------------------
--
Warning: 
All e-mail sent to this address will be received by the Safeway corporate
e-mail system, and is subject to archival and review by someone other than
the recipient.  This e-mail may contain information proprietary to Safeway
and is intended only for the use of the intended recipient(s).  If the
reader of this message is not the intended recipient(s), you are notified
that you have received this message in error and that any review,
dissemination, distribution or copying of this message is strictly
prohibited.  If you have received this message in error, please notify the
sender immediately. 
  

============================================================================
==

Reply via email to