The problem lies in SLES 10 SP 1, which introduced the fstab mount by obscure id "feature". While noble and in the right direction, much like my arrows at the archery range, they missed the mark.
The change was made so that when new devices are added, fstab can find the correct devices even if their order has changed and there's a new /dev/dasda that wasn't what it was before. In order to keep the spirit of the change, but avoid the cloning error, what you need to do is change the fstab entry from using /dev/disk/by-id to using /dev/disk/by-path. Within the by-path directory, all your minidisks (the actual thing indicative of what you're really trying to mount. Assuming partition one on the minidisk at address 391, the entry you want to use would be: /dev/disk/by-path/ccw-0.0.0391-part1 This doesn't have the downside of the magic number based on the physical device the minidisk resides on, while still not depending on the order in which the disks are presented to the Linux system. If you make this change to fstab in your clone master, it should clone correctly. When you create new masters, I think you can make this change as you define the disks, via the fstab options button. -- Robert P. Nix Mayo Foundation .~. RO-OE-5-55 200 First Street SW /V\ 507-284-0844 Rochester, MN 55905 /( )\ ----- ^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/14/08 12:57 PM, "Lee Stewart" <[EMAIL PROTECTED]> wrote: > 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 ---------------------------------------------------------------------- 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
