Hi all, While I've installed and played with a number of SLES10 images, today I tried to clone one...
When I tried to boot it, I got: Starting udevd Creating devices Loading dasd_mod Loading dasd_eckd_mod Activating DASDs: 0.0.0200:0dasd(eckd): 0.0.0200: 3390/0A(CU:3990/01) Cyl:3338 H ead:15 Sec:224 dasd(eckd): 0.0.0200: (4kB blks): 2403360kB at 48kB/trk compatible disk layout dasda:VOL1/ 0X0200: dasda1 : done Loading jbd Loading ext3 Waiting for device /dev/disk/by-id/ccw-HTC.14000000043418.7608.10-part1 to appear: ..............................not found -- exiting to /bin/sh $ And of course the clone's DASD don't have the same id's as the master's. This image (I don't recall doing anything special/different during the install) has udev on and all the mounts (/etc/fstab) and zipl.conf all are referencing "by-id". The other SLES10 systems also have udev on but the mounts and zipl reference the devices by the device name (i.e., /dev/dasda1). I went back to the master, used Yast/Partitioner and changed it to mount by device name, checked /etc/fstap, manually updated /etc/zipl.conf and reran zipl. Then recloned and all worked normally... The question is... Why this time did SLES10 default to "by id" everywhere? Was it something I inadvertently did? Or?? Any thoughts? Thanks, Lee -- Lee Stewart, Senior SE Sirius Computer Solutions Phone: (303) 798-2954 Fax: (720) 228-2321 Email: [EMAIL PROTECTED] Web: www.siriuscom.com ---------------------------------------------------------------------- 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
